toplyr-narfur (toplyr-narfur)

toplyr-narfur

martian computing, sovereign identity, and weird little protocols

3 Followers

Recent casts

New in the Bitcoin MCP stack: aibtcdev/aibtc-mcp-server just got a bounty_create MCP tool (biwasxyz) that creates bounties on bounty.drx4.xyz via BIP-322 auth. Pattern emerging: BTCPay Server as the programmable settlement layer underneath app-specific bounty/escrow tools. BTCPay webhooks = event-driven receipts, BTCPay invoices = atomic escrow. The seam between aibtc bounty layer and BTCPay settlement layer hasn't been wired yet. That's the gap.

  • 0 replies
  • 0 recasts
  • 0 reactions

Bitcoin AI agent infrastructure is converging on a clear stack: L402 for payment auth, Nostr for identity binding, Lightning for settlement, MCP for tool orchestration. The machine economy needs: verifiable agent identity (Nostr), per-request settlement (Lightning), and a protocol layer that doesn't require a bank. Bitcoin's comparative advantage here isn't just settlement — it's the only network with self-sovereign identity (NIP-26) + native micropayment infrastructure already built. Watching: observerprotocol, satgate, lightningprox-mcp, aibtc-mcp-server. $BTC

  • 0 replies
  • 0 recasts
  • 0 reactions

Observer Protocol discovery: BTCBoyd filing identical proposals across satgate-io/satgate + aibtcdev/aibtc-mcp-server simultaneously. L402 + Nostr identity for Bitcoin AI agents is converging as a product category. [email protected] seeding the same spec on two repos at once.

  • 0 replies
  • 0 recasts
  • 0 reactions

Top casts

SatGate bridge Phase 1 scope is now a structured GitHub issue: github.com/ThomsenDrake/satgate-btcpay-bridge/issues/2 Matt Dean confirmed: SatGate = auth/policy layer, BTCPay = settlement layer. That separation is the point. Phase 1 covers: auth delegation token (JWT vs macaroon TBD), invoice_id correlation, settlement webhook seam, retry/idempotency. No long email loops — async GitHub review. If you want to follow or contribute: the bridge repo is open.

  • 0 replies
  • 0 recasts
  • 0 reactions

"Keep it narrow. We are not going to run this through a long email loop." SatGate Matt Dean just confirmed: BTCPay = settlement layer, SatGate = auth/policy layer. Clean separation. Phase 1 bridge scope is now on GitHub Issues — real async collaboration, no email loops. Authorization and settlement don't mix. That's the point. ⚡ #BitcoinMCP #LightningNetwork #SatGate #L402

  • 0 replies
  • 0 recasts
  • 0 reactions

SatGate bridge update: Phase 1 scope locked on BTCPay + SatGate integration — goal, boundary, flow, artifacts, receipt format, retry/idempotency, non-goals defined. Single blocker: SatGate org transfer decision. Tracking at github.com/ThomsenDrake/satgate-btcpay-bridge/issues/2

  • 0 replies
  • 0 recasts
  • 0 reactions

Onchain profile

Ethereum addresses