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
Post by twetch#2782
I have something neat brewing though :]
The real fundamental limitation of bitcoin L1 has to do with state management, not loops/jumps etc
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 (3)
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
Another great post by xhliu, in this case imagine how you would implement the EVM's CALL op for distinct "contracts" deployed without a priori knowledge of each other: https://xiaohuiliu.medium.com/how-to-scale-ethereum-today-9bbaece3fb2e