-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fee calculation unit #41
Conversation
@sunnyking what's the long term plan for these fields? do we only need it at block level (vs. txn level)? |
minters can decide these units in each block. all tx fee in block can be calculated by these units. based on the real cost (linear combination of these unit), different txs will be charged in different tx fee. all tx fee will be destroyed (shared by the whole community). tx sender need to set the upper-bound tx fee of each tx (similar as gas) |
These names would look better imo: |
@@ -0,0 +1,7 @@ | |||
package vee.fee | |||
|
|||
case class FeeCalculationUnitBlockData(computationalUnit: Long, storageUnit: Long, memoryStorageUnit: Long, randomIOUnit: Long, sequentialIOUnit: Long) |
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.
Imo it's better called ResourcePricingBlockData
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.
computationUnitCost
storageUnitCost
memoryUnitCost
randomIOUnitCost
sequentialIOUnitCost
…posConsensusField
fixed current block info:
|
current block information in API: