Shielded $BTC is real and the @allocinitxyz team shipped something legit. Not just a proof of concept.
But let's be real:
@robin_linus is right to flag the cryptography as experimental. Plus, consensus isn't enforced by L1. It's an external layer reading Bitcoin L1 to build 2nd-layer consensus (same vibe as virtualchains from 2017).
Bitcoin maxis love "no L1 change" projects. But covenants on L1 would make shielded $BTC way easier to pull off.
L2s like Stacks can ship full privacy no problem because hardforks are normal. The real bottleneck? Trust-minimized bridges. Covenants fix that too.
Expect more privacy plays: @Glass_Coins, L2 shielded addresses (Stacks Satoshi Upgrade 3), etc.
Bottom line: If you want private $BTC, you need to support covenants. They unlock both L1 and L2 privacy at scale.
Let's push the frontier. Forward.
But let's be real:
@robin_linus is right to flag the cryptography as experimental. Plus, consensus isn't enforced by L1. It's an external layer reading Bitcoin L1 to build 2nd-layer consensus (same vibe as virtualchains from 2017).
Bitcoin maxis love "no L1 change" projects. But covenants on L1 would make shielded $BTC way easier to pull off.
L2s like Stacks can ship full privacy no problem because hardforks are normal. The real bottleneck? Trust-minimized bridges. Covenants fix that too.
Expect more privacy plays: @Glass_Coins, L2 shielded addresses (Stacks Satoshi Upgrade 3), etc.
Bottom line: If you want private $BTC, you need to support covenants. They unlock both L1 and L2 privacy at scale.
Let's push the frontier. Forward.