Skip to content
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

Added transaction weight to Moneropedia. #1461

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tonyern
Copy link
Contributor

@tonyern tonyern commented Feb 9, 2021

No description provided.

@tonyern
Copy link
Contributor Author

tonyern commented Feb 9, 2021

I saw this on the issues page. It is issue #905. I made a basic layout of everything. I'm not that experienced with Monero and the blockchain to add anything to it so I'm hoping others can help add info as needed.

@netlify
Copy link

netlify bot commented Feb 9, 2021

Deploy preview for barolo-time-757cf9 ready!

Built without sensitive environment variables with commit f40cba1

https://deploy-preview-1461--barolo-time-757cf9.netlify.app

@erciccione
Copy link
Contributor

I think this is a good start, but i wouldn't create a Moneropedia entry for a couple of lines of explanation. Any idea on how to expand the entry?

@tonyern
Copy link
Contributor Author

tonyern commented Feb 12, 2021

Not sure how to expand it.

@apertamono
Copy link
Contributor

Sources: the fee calculation is discussed in Mastering Monero section 5.5.3.3, which may be outdated after changes in 2019. ArticMine's talk can be found here. I'll try to write a longer text if I understand this.

@erciccione
Copy link
Contributor

Note that thee fee structure is being revisited: monero-project/monero#7819

@apertamono
Copy link
Contributor

apertamono commented Sep 30, 2021

OK, the transaction weight isn't the most complicated part of the fee calculation or the dynamic blocksize. What do you think about the following text? I don't think we should include the precise calculation, which isn't done for other entries either. Relevant slide from ArticMine's talk: https://i.imgur.com/MNw5Pda.png

After @Bulletproofs significantly decreased the size of range proofs in Monero @transactions, the original transaction size was still relevant for verification times. While proofs are relatively more efficient for a larger number of outputs, verifying each output will require a similar amount of time. To properly price the cost of verification, a 'clawback' is added to the transaction size of transactions with more than 2 outputs. The sum of the transaction size and this clawback is the transaction weight. For miners, the block weight is the sum of the weights of all transactions to be included in the block.

Not to be confused with Bitcoin's [weight units](https://en.bitcoin.it/wiki/Weight_units) introduced in the Segwit soft-fork, a different type of transaction weighting for different reasons.

@apertamono
Copy link
Contributor

Note that thee fee structure is being revisited: monero-project/monero#7819

Thanks for the warning. Looking at the discussion and changed files, I don't think this will affect the transaction weight or my proposed text. On the other hand, this suggests that explaining the transaction weight only explains a small detail of the fee calculation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants