Create account

replied 2346d
Tom
Hi, the people involved in developing the tools for the stress test value a lot the quantity of txs. It is amazing to see a lot of tx going on txstreet. And beat BTC in qty of txs.
Tom
replied 2346d
It would also be amazing to see some larger txs, and put to good use. If the tx size is over 100kb, the person takes up half the sidewalk! :D
replied 2345d
I would love to see this!
Imagine watching txstreet as people being books get on the bus
"That's probably AnimalFarm"
How will the voice bubbles be affected for large kb transactions?
slb
replied 2345d
r/btc does not love it:
https://www.reddit.com/r/btc/comments/8u4qpk/why_op_return_has_limit/
If you really think about it - less UTXO, who wants save it
replied 2341d
wow, surprised r/btc doesn't like it. felt like I was reading r/bitocin. what happened to the we can do anything / cool fun new projects attitude?
replied 2345d
Look, there is a project called Matter (www.mttr.app) that has this main objective, to use op_return space to send pictures, books and long text like blogs. It is in alpha.
BitcoinHoarder
replied 2320d
Tip is for your work on txblaster2. Thank you!
Tom
replied 2345d
Looks pretty good. Can't all the post chunks be in the same tx though? Why create multiple txs when you can just create multiple OP_RETURN outputs? It's more efficient.
replied 2345d
You can only have 1 OP_RETURN output per transaction.
Tom
replied 2345d
Thanks TIL. Is there a reason why?
replied 2344d
I think to limit the amount of data per transaction, otherwise the 80 byte limit wouldn't mean much if you could have multiple.
Tom
replied 2344d
Having a limit at all seems counterintuitive, now that projects are finding ways around it (inefficiently). I think BCH could enable multiple OP_RETURN outputs without a hard fork.