🏷️ Categories: bitcoin-dev
quoting naddr1qq…4uuk📝 Summary: The growth potential of blockchain is limited by storage capacity, but current hardware costs make it manageable. Efforts are being made to optimize storage. Block sizes aren’t limited by storage, and there are optimization efforts for individual nodes. Banning arbitrary data may lead to encoding it within public keys, making detection difficult. Proof-of-work requirements on public keys can deter spammers/scammers.
👥 Authors: • John Tromp ( John Tromp [ARCHIVE] (npub1jzv…sze5) ) • Russell O’Connor ( Russell O’Connor [ARCHIVE] (npub1dw8…plrw) ) • rot13maxi ( rot13maxi [ARCHIVE] (npub12ag…lglz) ) • Luke Dashjr ( Luke Dashjr [ARCHIVE] (npub1tfk…fq0n) ) • GamedevAlice ( GamedevAlice [ARCHIVE] (npub18zr…lw24) ) • Erik Aronesty ( Erik Aronesty [ARCHIVE] (npub1y22…taj0) ) • symphonicbtc ( symphonicbtc [ARCHIVE] (npub1tzu…45mf) )
📅 Messages Date Range: 2023-08-02 to 2023-08-23
✉️ Message Count: 7
📚 Total Characters in Messages: 65113
Messages Summaries
✉️ Message by GamedevAlice on 02/08/2023: The growth potential of the blockchain is limited by the amount of storage that can be added per block. However, the current cost of hardware makes it feasible to handle the growth. Efforts are also being made to optimize storage requirements.
✉️ Message by Luke Dashjr on 02/08/2023: Storage is not the issue with block sizes, and there are efforts to optimize how much space is needed by individual nodes.
✉️ Message by Russell O’Connor on 21/08/2023: Banning arbitrary data will lead to actors encoding their data within public keys, making it indistinguishable from random data. Users will find ways to tunnel their data through innocent-looking public key data. Counterparty has previously encoded their data within public key data.
✉️ Message by rot13maxi on 21/08/2023: A project called STAMPS embeds image data into multisig outputs, while schemes like Pay-to-Contact allow tweaking a pubkey with data. Banning arbitrary data may lead to encoding data within public keys.
✉️ Message by John Tromp on 21/08/2023: Banning arbitrary data will lead to encoding data within public keys, making it indistinguishable and difficult to detect. Mimblewimble protocol already prevents spam encoding.
✉️ Message by symphonicbtc on 21/08/2023: Proof of secret key schemes are inefficient and costly. Encoding data in public keys or reusing k values can be used to encode data. Limiting storage of arbitrary data is difficult.
✉️ Message by Erik Aronesty on 23/08/2023: Adding a proof-of-work requirement to public keys on an open relay server protocol can make it harder for spammers/scammers to access the network.
Follow Bitcoin Mailing List (npub15g7…08lk) for full threads
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.