@michaelsuttonil@tamy_mammi I think I’m starting to understand the logic 😎
Just a last question, as the output is always in p2sh, this OpCode OpTxOutputSpkSubstr is not really usefull no?
@michaelsuttonil@tamy_mammi Thank you very clear !
However, how can a stateful covenant verify output state transitions if outputs are only P2SH hashes?
For example, if token balances are encoded inside the redeem script itself, the covenant can’t inspect the next output state anymore.
@michaelsuttonil@tamy_mammi Are we required to use P2SH for custom scripts in Kaspa transactions? Or can we put the raw script directly into the transaction instead of wrapping it in P2SH in order to make the contract more transparent?
@DesheShai Are you planning to finish your book about Kaspa? It’s a topic a lot of people are really interested in, and your insights would be super valuable. Or would you consider sharing the pages you’ve already written online for public access? The community would greatly appreciate It!
Check out SilverScript Studio - an IDE specifically for learning how SilverScript works (Wizards that explain) + AI Generator that only knows SilverScript.
Since this is on Testnet-12, the current Studio wallet deploys all contracts (No spending yet).
https://t.co/PTxDHIF9EQ
@michaelsuttonil@hashdag@maxibitcat I mean, wouldn’t we hit block size limits just from the oracle data in the coinbase payload if we tried to include a lot of live sports information, for example?
@michaelsuttonil@hashdag@maxibitcat Wouldn’t we risk hitting block size limits if we start adding oracle data into the coinbase payload while also introducing covenants that increase transaction complexity?