ChainSQL

@seanwestfall·Sean Westfall·31 followers·added 2026-10-24

ChainSQL puts a payment command boundary inside PostgreSQL. A native extension (chainsql/extension/*.sql) exposes chainsql.approve_transfer_v1, claim_transfer_v1, dispatch_transfer_v1 and reconcile_transfer_v1, so a vendor bill moves through approve, claim, dispatch and reconcile as SQL calls, with set_budget_v1 budgets, _fence_v1 fencing, enable_arc_v1 network enablement and save_arc_authorization_v1 storing encrypted authorizations. Five Odoo 19 addons (chainsql_base, chainsql_account, chainsql_arc_account, chainsql_resource_account, chainsql_transfer_boundary) surface the workflow inside accounting, where a human policy operator approves each transfer. A credential-less Python worker (chainsql/boundary/worker.py, AES-GCM handling in signer.py) executes approved transfers, and Node adapters sign with Circle developer-controlled wallets: chainsql/arc/adapter.mjs pays USDC on Arc through sign-only transactions, and chainsql/x402/adapter.mjs buys an x402 v2 resource with @x402/core EIP-3009 exact-scheme payments against chainsql/x402/merchant.mjs. Odoo is a pinned submodule; milestone0/ to milestone4/ hold scripts, tests and evidence.