Why ordinals? Why not just in OPRETURN? To save on fee?
I'm just confused why outputs need to be inscribed as an ordinal and not just a new protocol? If ordinals is just abstracting main chain for a shared delusion then why not abstract something new?
I'm not hating. Just very curious. It's a key design decision.
Login to reply
Replies (3)
Simplification is key, like a carnivore diet, cutting out the noise.
I read it. It didn't answer really why this couldn't be done with a new shared delusion instead of ordinals. Ord indexes are not backwards compatible. Ie I have to reindex the whole thing on any upgrade. Can I build a index that only gets these addresses and not have to index every sat? It takes weeks for a ordinals database to sync, especially if you're indexing sats.
Damnit... I keep thinking. Now you got me rethinking building anchor on inscriptions...

GitHub
GitHub - 0ceanSlim/anchor: Immutable, permissionless constant-product AMM for Liquid.
Immutable, permissionless constant-product AMM for Liquid. - 0ceanSlim/anchor