> ⚔️ The size of compiled program which evaluates one pairing is 10.5 KBytes and it consumes ~4.2M weight units. It sounds even Simplicity programs need the Virtual Mempool of @Ark Labs

GitHub

GitHub - distributed-lab/simplicity-bn254: The implementation of Ethereum's BN254 using Liquid's SimplicityHL script

The implementation of Ethereum's BN254 using Liquid's SimplicityHL script - distributed-lab/simplicity-bn254

sats. Peer to peer. View quoted note →

Nostr 🤝 Ark View quoted note →

GM

Gucci, Fentanyl and Proof of Stake

GM ✨

Few.

Wen Silent Payments @Geyser

Been thinking about scaling in #Bitcoin vs #Ethereum lately. Gotta say, I'm not sold on the whole #rollup thing. Rollups basically create a separate blockchain. Even with trustless bridges, you're splitting your ecosystem. It's like having two competing universes instead of one cohesive system. Bitcoin's approach with Lightning and Ark? Way more fluid. These are just unconfirmed txs we choose not to broadcast, protected by some clever counterfactual schemes. Take Ark: mempool empty? Just send on-chain. Congested? Join an Ark round. Same wallet, smooth transition. It's all one system, not two competing layers. This is why I think Bitcoin's scaling smarter. It's not about adding more blockchains, it's about making the base layer more efficient and powerful. Curious what you all think. Are rollups really the future, or is #Bitcoin onto something better here? 🤔

Virtual Bitcoin Account TM

Hey @primal would very cool to implement language models (can be small and kinda easy to run on-device) to implement a more personalized content discovery I don’t think scaling is the issue of Nostr (can be fixed) but rather being useful without the need of a centralized honeypot server creating timelines.

What’s the best cashu impl in Go? @calle