-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TIP-19 Dust Protection Based on Byte Costs #39
Conversation
text/0039-dust-protection-based-on-byte-costs/0039-dust-protection-based-on-byte-costs.md
Outdated
Show resolved
Hide resolved
Minimum state rent virtual byte counts are incorrect given that the calculations still work with uint16 for denoting the feature blocks slice length (instead of uint8). |
the link is changed to https://github.com/muXxer/protocol-rfcs/blob/master/tips/TIP-0019/tip-0019.md |
<tr> | ||
<th>Name</th> | ||
<th>Description</th> | ||
<th>Weight</th> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should specify that these can be floating point / fractional values. vbyte_cost
on the other hand is of type integer, right? Maybe we should specify that somewhere too?
tips/TIP-0019/tip-0019.md
Outdated
|
||
Another solution is to convert all `SigLockedDustAllowanceOutput` into `BasicOutputs` and leave the `SigLockedSingleOutput` below 1 MIOTA untouched. | ||
|
||
### Unresolved questions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When consider merging this TIP, we should remove this section.
Are there even still open? I guess we obviously have to define some v_byte_cost
value so we could maybe just remove the entire section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should remove this section as you said because any parameter values are subject to be put into a separate TIP or the actual network configuration anyway, so this is not the place to put it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will removed it 👍
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
Co-authored-by: Wolfgang Welz <welzwo@gmail.com>
This RFC describes a new dust protection mechanism that prevents bloating of the IOTA ledger database.
Rendered Version
The scripts for byte cost calculations can be found here.