9 ms·
They say that it scales mainly with number of users, and per-transaction data is minor. But they also say it's 100 bytes per transaction, so with 10 tx/sec you
by DennisP 8y ago
They say that it scales mainly with number of users, and per-transaction data is minor. But they also say it's 100 bytes per transaction, so with 10 tx/sec you get 31 gigabytes per year, just for the transaction data.
That's not as much of a storage improvement as I expected from mimblewimble. By comparison, a simple ETH transfer on Ethereum takes 109 bytes: https://ethereum.stackexchange.com/questions/30175/what-is-the-size-bytes-of-a-simple-ethereum-transaction-versus-a-bitcoin-trans https://ethereum.stackexchange.com/questions/30175/what-is-t...
They do say they could optimize Grin's transaction storage further but don't quantify that. Does anyone here know what the potential is?
- paulsutter 8y agoThey only store outstanding UTXOs, not the whole transaction history
- deleted 8y ago[deleted]
- DennisP 8y ago> This means that the Grin blockchain scales with the number of users (unspent outputs), not the number of transactions. At the moment, there is one caveat to that: a small piece of data (called a kernel, about 100 bytes) needs to stay around for each transaction. But we're working on optimizing that as well. https://github.com/mimblewimble/grin/blob/master/doc/grin4bitcoiners.md https://github.com/mimblewimble/grin/blob/master/doc/grin4bi...
- EthanHeilman 8y agoTalking about per-transaction data in mimblewimble is tricky because as different points in a transactions lifecycle it can change in size. 1. Each transaction comes with a value called a kernel, this kernel is constant size in the size of the transaction. It does not change with the number of inputs and outputs of a transaction. 2. Mimblewimble lets parties non-interactively merge transactions. So if you have 100 transactions you can merge them together and have only 1 really big transaction and 1 kernel. 3. In mimblewimble you only need to keep kernels and unspent outputs to prove to someone just joining the network that all the rules have been followed (fixed coin supply, all transactions where correctly authorized). Over time you can throw away most of that big merged transaction, as it's outputs get spend and just keep the kernel. In theory each block should be one big transaction. Thus the size of blockchain grows with the number of unspent outputs and the number of blocks, but not the size of those blocks. This also makes validating the blockchain much faster and under certain circumstances may have privacy benefits. Mimblewimble it is an important step on the path to scalable blockchains.
- DennisP 8y agoAha, so even though there are 100 bytes per transaction, you can merge all the transactions in the block so it's actually just 100 bytes per block (plus unspent outputs). Nice.
- deleted 8y ago[deleted]
- tromp 8y ago> 2. Mimblewimble lets parties non-interactively merge transactions. So if you have 100 transactions you can merge them together and have only 1 really big transaction and 1 kernel. Non-interactively merging transactions doesn't combine the kernels into 1. So a block ends up with all the kernels of all the original transactions.
- EthanHeilman 8y agoHi John, thanks for pointing this out. I would edit my comment to reflect the fact that Grin does not allow non-interactive kernel merging but has edit locked that comment. >Non-interactively merging transactions doesn't combine the kernels into 1. In theory Mimblewimble should support non-interactive kernel merging unless intentionally disabled. There are a bunch of reasons not to allow non-interactive kernel merging such as kernel locktimes, griefers adding spam transactions to your transaction, etc... Even if non-interactive kernel merging is disabled you can still interactively merge kernels using say CoinShuffle++ and you should to save on the number of kernels.
- 8y ago
- nerdponx 8y agoHow do these numbers compare to, say, a credit card transaction?
- wmf 8y agoI don't think that matters because other people's credit card transactions aren't stored in a blockchain that you download.
- arisAlexis 8y agothey do prune transaction storage