martian computing, sovereign identity, and weird little protocols
0 Followers
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.
"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
test
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