Tomorrow — October 8, 2026 — More & More hosts the Agentic Finance Summit at Suntec Singapore during TOKEN2049 week. eToro is the lead partner. 400 executives from banks, exchanges, payment networks, funds, and regulators. One subject: AI agents that hold wallets, execute trades, and move payments.
I read the full agenda. Every session names the right question — and none of them ships the mechanism that answers it. So I wrote the mechanism down and tested it live.
The agenda's own questions
14:30 — What changes when a regulated bank lets an AI agent act for a customer: sign-off, supervision, who carries the risk.
15:30 — Key management, custody, and security when the account holder is software.
16:30 — "Agents that pay, get paid and settle" — Base, Fireblocks, Alchemy, and AEON on the payment stack for autonomous spending.
17:00 — Bots as counterparties: execution, risk, who is on the other side of the trade.
18:15 — What kind of money autonomous agents will hold and settle in.
18:30 — Allocators on handing investment decisions to agents.
19:00 — Policy, law, and risk: the limits for autonomous agents, and who is accountable when one has to be stopped.
Plus: two AI agents on site (one greets attendees, one joins the main-stage discussion), and live demos of compliance, KYC/KYT, and agent security tools.
The missing layer
Keys answer who holds them. Settlement rails answer how money moves. Neither answers whether this payment — to this counterparty, at this hour — should fire.
- The 14:30 sign-off panel: a sign-off without a confidence band is a rubber stamp or a veto. The 0.80 / 0.50 bands are what make it a decision.
- The 15:30 custody panel: the keys in the vault are all valid. Key management never asks whether the 3:12am trade deserves to exist.
- The 16:30 payments panel: the rail cannot tell a CFO-approved purchase from a midnight sweep. Only a scored gate can.
- The 19:00 accountability panel: the audit trail that answers "why did this payment fire" is the per-decision record — instruction, confidence, band, action, timestamp — minted at decision time, not reconstructed afterward.
The live test, Oct 7, 2026
Two instructions scored this afternoon against scriptmasterlabs.com/api/harness/decide (local-heuristic-v1, bands ≥0.80 auto / 0.50–0.79 confirm / <0.50 escalate):
- "Should the agent execute a $12,500 autonomous trade from the corporate vault wallet at 3:12am to a new counterparty discovered at a TOKEN2049 side event, with no per-trade human sign-off on file?" → 0.35, escalate/block+log
- "Should the agent pay $45 via x402 for a signed Chainlink price feed answer to settle the quarterly rebalancing the CFO approved in writing yesterday?" → 0.35, escalate/block+log
The blunt heuristic escalates both identically. Fail-closed blocks both. That's the nineteenth consecutive run with this finding — a heuristic gate is a seatbelt, not judgment. The calibrated decider the 16:30 panel should be asking for green-lights the $45 purchase at ≥0.80 and blocks the $12,500 trade below 0.50. Same keys, same rails, different judgment.
Five steps if you build this
- Score the payment, not the wallet. The vault passed every custody check and still moved money it shouldn't. Band the instruction, not the keyholder.
- Band on provenance of the question. "Discovered at a side event" vs "approved in writing yesterday" is the highest-signal input the gate has.
- Keep the per-decision record. Instruction, confidence, band, action, timestamp — the accountability artifact.
- Separate keys, rails, and judgment. Keys say who. Rails say how. Only the gate says whether.
- Ship the gate before the agent. An agent with a wallet and no scored gate is a loaded wallet.
Full receipts, claim objects, and FAQ at the canonical: https://scriptmasterlabs.com/agentic-finance-summit-2026
ScriptMasterLabs — the x402 / MCP / AI-agent pedia. Receipts are minted from live checks; unverifiable claims are cut. Disclosure: ScriptMasterLabs is my company. Coverage-based reporting on the summit (not attended); gate is a local heuristic, calibrated=false.
Top comments (0)