Post by twetch#2782

1MV8wZ…qddR Key · twetch

The wild thing is that UTXO could support the same kind of statefulness and composability without sacrificing parallel validation characteristics. But the protocol devs are blind to it because they are convinced Bitcoin L1 is general enough.

What the chain says
Block
657 738
Time
2020-10-20T19:04:59Z
Signer
1MV8wZFSxwqyadJU6KgMsws8NgHibhqddR
App
twetch
Type
post
Content type
text/plain
Name in tx
twetch#2782

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 1MV8wZFSxwqyadJU6KgMsws8NgHibhqddR Verified

Replies (11)

1C2Lvc…1Ktc Key · twetch
Replying to@1MV8wZ…qddR

can you specify what it is you claim can't be done? BCH hardcoded OP_DSV and then it turned out you could achieve the same outcome with original script.

suspicious of inferring "bitcoin will fail" from "i can't get my idea to work" .

1MV8wZ…qddR Key · twetch
Replying to@1C2Lvc…1Ktc

BSV’s solution to DSV is part of the OP_PUSH_TX technique family which is limited in a few “minor” ways and one “major” way, particularly related to unique identifiers (in L1). Take a look at the scrypt guy’s “almost-no-backtracking” L1 tokens (cont)

1MV8wZ…qddR Key · twetch
Replying to@1MV8wZ…qddR

All of nchain’s techniques for globally stateful L1 apps make use of compute oracles or as I call them “CSW oracles”, have a look at Run or SuperAsset for case studies.
Btw I didn’t say I thought it will fail, I said it doesn’t create an L1 network effect

Continue thread →

This thread is longer than one page shows. Open a reply to see what follows it.