tiero

Grazie per invito

super divertente parlare di quello che faccio in Italiano che non capita quasi mai!

Alla prossima

Add Bitcoin payments and more to your claw bot

https://github.com/arkade-os/skill

Tapscript gives you wings

Most of you are not aware yet, but Arkade from

already supports executing any Bitcoin Tapscript offchain you can think of.

Same Bitcoin L1 constructions, not constrained by block space or waiting for the next block anymore.

Concrete examples? Lendsat offers Bitcoin-backed loans with a simple escrow contract. Boltz allows you to move BTC between layers with a Hash Time Locked contract. Many other use cases coming soon.

All of this is composable with the Lightning Network out of the box. Scan a QR code, pay with your favorite LN wallet, execute the VTXO contract offchain and pull it back.

VTXOs (Virtual Transaction Outputs) are self-custodial offchain representations of Bitcoin UTXOs. Backed by presigned Bitcoin transactions that can be published to the blockchain unilaterally. You always retain the ability to exit without cooperation.

The Arkade executes transactions by co-signing, providing instant preconfirmation. The server never holds custody. This is enforced by the protocol: every VTXO includes both a collaborative path (fast, requires server) and a unilateral path (slower, independent of server).

You get instant execution without giving up control.

An escrow with three spending paths using standard Bitcoin Tapscript. Path one requires buyer and seller signatures. Path two allows an arbiter to resolve disputes. Path three refunds to the buyer after 30 days using CHECKLOCKTIMEVERIFY.

This produces a standard Bitcoin address. Spending requires satisfying one of the three script paths. Taproot makes this efficient by only revealing the path actually used.

The scripting capability exists today on Bitcoin. The constraint was always execution speed, not capability.

HTLCs enable atomic swaps. Two parties lock funds in interlocked contracts gated by hash preimages. Revealing the preimage to claim one side automatically enables claiming the other. The swap completes atomically or not at all.

The collaborative path requires the preimage, receiver signature, and server signature. The script uses HASH160 and EQUALVERIFY to verify the preimage, then CHECKSIGVERIFY and CHECKSIG for the signatures.

The unilateral path adds a relative timelock using CHECKSEQUENCEVERIFY. After the exit delay expires, the receiver can claim with just the preimage and their signature.

Boltz uses this pattern for Lightning swaps. Same Bitcoin opcodes, executed offchain at Virtual Mempool speed.

Bitcoin's Tapscript can express multi-path conditions today. The challenge has been execution speed, not scripting capability.

Blocks arrive approximately every ten minutes. Fee markets introduce unpredictability. For applications requiring multiple sequential operations, these delays compound. Bitcoin Script lacks the ability to maintain state continuity between transactions. Each transaction executes independently.

Escrow patterns that are theoretically expressible in Tapscript become impractical to deploy on the base layer. The script is capable. The execution environment doesn't match.

Arkade's Virtual Mempool executes the same Tapscript logic offchain while preserving the ability to settle to Bitcoin at any time. The script remains native Bitcoin Tapscript. The execution environment now supports the speed and composability that complex contracts require.

This opens up applications that were always possible in theory but impractical in execution. Atomic swaps. Bidirectional payment channels. Discreet Log Contracts. Lending collateral with health monitoring. Oracle-gated settlements.

Each application is an escrow composition with domain-specific parameters. The underlying mechanics remain consistent.

Don't listen to those that say "You cannot do anything with bitcoins"

Bitcoin is coming back.

Contracts Docs: https://docs.arkadeos.com/contracts

→ Building Bitcoin apps? Reach out about builder programs: [email protected]

⚔️ 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

https://github.com/distributed-lab/simplicity-bn254

wow, didn't noticed Jack comment at the time.

Ego boost!

Today I logged into

web app on my dekstop using my Primal mobile app on my phone. It felt magical.

Next stop is to leverage private keys to do more than signing Nostr events. Bitcoin transactions. Payments, Loans and Financial Primitives.

One phone, multiple web apps.

Onward

Interesting

Nostr Connect Accelerate

NIP-46 FTW

Amazing to see Nip-46 gaining traction! Good job

sats. Peer to peer.

Nostr 🤝 Ark

GM

Gucci, Fentanyl and Proof of Stake

GM ✨

Few.

Wen Silent Payments

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

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?

Coin control is fundamental for #bitcoin transactions privacy, but it’s annoying to have to handle the change output and keep track/label on every spend.

What if merchants accepting bitcoin could let me create a simple payment channel address that can be funded spending an arbitrary amount of coin(s) without generating a remainder, hence no change output in the transaction?

User wallet would send funds and right away sign the initial state deducted of the first spend in favor of merchant

ie. Funding amount 0.1525 BTC First payment 0.01 BTC

It a basically the Bitrefill account balance, but with somewhat a guarantee you can get back your “gift card” if service is not delivered to you anymore.

I have been preaching for many years how for many use cases federated custody is the perfect trade-off, the caveat is to make it connected to the global Lightning Network.

All of this has been possible thanks to the work behind the scenes of many builders! Kudos!

Grateful to be part of

journey.

Let’s scale #Bitcoin

Is there any multi-npub nostr Client out there? Ie. From the same app I want to switch to many identities/need without having to “logout” and enter again the nsec

Nostr rocks

Running Nostr Connect 🔌

Running Nostr Connect 🔌

Announcing ☸️ Nostrum, the first implementation of a 🔌 Nostr Connect enabled remote signer.

🔌 Nostr Connect allows #Nostr web apps to connect to your phone and request your Nostr ID, a signature for an event, etc.

iOS TestFlight https://testflight.apple.com/join/JIbjvN2p

Android APK https://expo.dev/accounts/tiero/projects/nostrum/builds/79ca2ec4-524e-49de-a7ec-fe8d58090720

Playground web app to test against

https://nostr-connect.github.io/connect/

Running Nostr

Running Damus #introduction