High Tower
@htwtech
🍋 Part 3 — Infrastructure & the bigger picture 1/ In Part 1, we looked at what already works on @citrea_xyz - things like escrows, swaps, BTC-backed stablecoins. In Part 2, we explored why zk is native to the design - powering private transfers, zkID, zkML, and Bitcoin-aligned DeFi. Now let’s talk about what ties it all together: Infrastructure. The stuff under the hood. 2/ Onchain infra Every L2 needs plumbing. zk gives you new pipes.
3 replies
0 recast
11 reactions
High Tower
@htwtech
• zk oracles & price feeds • Data availability beyond Bitcoin L1 • zk-bridges (Citrea ↔️ BTC ↔️ other L2s) • zk-sigs + validator logic w/o identity leaks 3/ Citrea isn’t an Ethereum clone. No accounts. No general-purpose VM. Just Bitcoin, UTXOs, and zero knowledge. But: 🛠EVM compatibility is in the works - so ETH-native apps can eventually run on Bitcoin infra. 4/ If you're done re-skinning EVMs...
0 reply
0 recast
0 reaction
High Tower
@htwtech
And want to build something that’s actually Bitcoin-native, with provability as a base layer, not a feature Citrea is a blank page. 5/ That’s it for Part 3 - and the full Citrea breakdown. We started with BTC-native apps and then went deeper into zk as a base layer. Now we’ve zoomed out to infra. Citrea isn’t trying to replicate what already exists. It’s rethinking what’s necessary - and what can finally be dropped.
0 reply
0 recast
0 reaction
High Tower
@htwtech
No accounts to track. No network memory to sync. Just commitments, proofs, and one base layer that still matters. A blank page - not to rewrite the past, but to build forward.
0 reply
0 recast
0 reaction