bitcoin-sv-specs/protocol

Bitcoin SV protocol specifications

protocol's Issues

Too late for OP_PUSH_TX or equivalent?

(copied/edited from a message a sent to shadders)

---

I have one question about Bitcoin's L1.
I really hope I am not understanding something about Bitcoin's script and that I'm simply wrong about these posts.
Thank you in advance if you have a minute to process these, especially the most recent one (first in the list). I'm reaching out to you because every other BSV dev outright ignores what I'm trying to say and essentially switches to saying the equivalent of "you'll see, you nonbeliever". The spec is here now, it's either possible or not.

• https://word.site/2020/01/07/shape-of-mana/
• https://word.site/2019/12/09/shardlets/
• https://word.site/2019/11/28/csw-oracles/

To be very clear, I am not trying to make yet another network. I would absolutely love to discover this was possible on BSV, I want to be able to retract those posts and work on Bitcoin directly.

---

Someone pointed me to this repo for the actual spec and indeed and it looks like there is nothing that would enable this functionality without the use of oracles. However, OP_PUSH_TX would be relatively simple to implement, and general enough to achieve everything I describe in the posts above, and crucially it would not change the asymptotic validation complexity at all.

Maximum number of elements on the stack

The Genesis hard fork specification doesn't mention any protocol limit on the number of stack items. Is this on purpose, i.e. could it hold an unbounded number of elements? Or is it UINT32_MAX ($2^32 - 1$) as with the length of an element?