@mr_word is on PowPing!

PowPing is a place where you can earn Bitcoin simply by socializing, for FREE.
Never tried Bitcoin? It's OK! Just come, socialize, and earn Bitcoin.
Check out mr_word's activities

Bitcoin Script

visit channel home
Total Economy: 0.26 USD
We just published an extract from our draft documentation for an overlay UTXO machine which addresses what we see as a critical limitation of UTXO as designed in Bitcoin's native L1. https://github.com/mr-word/manadocs-public/blob/master/for-bsv-devs.md Tagging@xhliu /@joe, because of earlier discussions on OP_PUSH_TX and "no trackback" solutions.@shadders thank you for showing how introspection (OP_PUSH_TX) is currently possible -- we would love to hear what you have to say about our current problem and solution.
xhliu tipped:
0.01 USD
1 year ago
venezia tipped:
0.01 USD
1 year ago
joe tipped:
0.22 USD
1 year ago
I think that there might be room to do what you are proposing in native script. I can't propose a full solution, but it might have something to do with storing the contract state in a binary hash tree.
volt tipped:
0.04 USD
1 year ago
Just got around to looking through it, very cool. there's no additional memory accesses to secure uref (miners are already fetching UTXOs when validating inputs). On paper, I think this is the most elegant solution to solve the backtracking problem :) I think more difficult issue is convincing SV devs or miners to be interested, even as a softfork. If they spent so much time removing P2SH why would they allow uref?
Inspiring article! The solution of uref looks reasonable. Tbh, I don't like any fork for adding new features.