Hear me out... a Bitcoin Script interpreter written in Bitcoin Script.
Bitcoin Virtual Machine, written to be interpreted inside the Bitcoin Virtual Machine.
This will be yuge.
Post by twetch#2782
Not possible by design (unless you accept exponential script sizes)
What the chain says
- Block
- 658 159
- Time
- 2020-10-23T19:26:48Z
- Signer
- 1486QpNpWYjokSfc3DxChCQG6gS2cTvVpL
- 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
1486QpNpWYjokSfc3DxChCQG6gS2cTvVpL VerifiedReplies (19)
Again I wish to reiterate that the more BSV protocol devs keep saying "BSV can do everything ETH can" the more crushing the disappointment will be for creative devs like OP
Haha. How much do you want to bet?
I'll bet 10 BSV, just don't show me something that grows like O(k^n) script size, or uses compute oracles to string transactions together
Can you please clarify what is k and n in the example above?
Also, can you please define 'compute oracles'? Just want to make sure we are on the same page.
I have something neat brewing though :]
The real fundamental limitation of bitcoin L1 has to do with state management, not loops/jumps etc
I look forward to it!
Can you characterize or quantify the "limitations" as it pertains to state management?
Each day that passes, I'm realizing there are less obstacles to what I thought was impossible before.
This will also be covered in coming paper but for now have a look at xhliu's "tokens without backtracking (almost)" and then @702's comment in this thread: https://powping.com/posts/a8323f5a627b1e26ba6d5493b6c61fdb238c0c439017ee265e4fc307d021cfb6
🤔
This thread is longer than one page shows. Open a reply to see what follows it.