ration/docs/near-hackathon/PITCH-DECK.md
caelum0x 7dd0b7facb docs(near-hackathon,soonami): add narrated submission videos + pitch decks
NEAR Hackathon: replace the 4.6s demo video with a 69.8s narrated
version (Deepgram Aura-2 + burned-in captions, -14.5 LUFS / -1.9 dBTP)
covering append -> anchor -> independent raw-RPC re-read -> a real
replay attempt rejected live on-chain, recorded against a freshly
deployed NEAR Testnet account (tx 5YebAM2...ome1t, replay-rejection tx
7v6m81j...469o). Old video kept, not deleted. Adds an 11-slide pitch
deck (PITCH-DECK.md/.pdf/.pptx) mapping the submission to NEAR's own
judging criteria (technical implementation, design, impact,
originality, sustainability, confirmed live from the hackathon FAQ).

soonami Venturethon 11: adds a venture-framed pitch deck
(docs/soonami/PITCH-DECK.md/.pdf/.pptx) covering market, business
model (flagged as an unpriced hypothesis), go-to-market, honest
traction, the 10-day sprint ask, and an explicitly flagged co-founder
placeholder (soonami requires >=2 co-founders; none invented). Reuses
the NEAR demo video per plan.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-11-11 01:05:19 +03:00

7.6 KiB
Raw Permalink Blame History

marp, theme, paginate, backgroundColor, color, style, footer
marp theme paginate backgroundColor color style footer
true default true #0d1117 #e6edf3 section { font-family: -apple-system, 'Helvetica Neue', Arial, sans-serif; padding: 60px 70px; } h1 { color: #e6edf3; font-size: 44px; } h2 { color: #58a6ff; font-size: 30px; } a { color: #58a6ff; } code { background: #161b22; color: #7ee787; padding: 2px 8px; border-radius: 6px; } pre { background: #161b22; border: 1px solid #30363d; border-radius: 8px; } table { font-size: 22px; border-collapse: collapse; width: 100%; } th { background: #21262d; color: #e6edf3; border: 1px solid #30363d; padding: 10px 14px; text-align: left; } td { background: #0d1117; color: #e6edf3; border: 1px solid #30363d; padding: 10px 14px; } tr:nth-child(even) td { background: #11161d; } .kicker { color: #00ec97; letter-spacing: 4px; font-weight: 700; font-size: 18px; text-transform: uppercase; } footer { color: #6e7681; font-size: 16px; } Ration — NEAR Hackathon 2026 — AI Security & Defense

RATION — AUDIT ANCHOR

An AI agent just moved real money.

How do you know it wasn't tampered with afterward?

NEAR Hackathon 2026 — AI Security & Defense track ("Trust, but verify") github.com/caelum0x/ration


The problem

  • AI agents are increasingly trusted to make real financial decisions — bridge-funding, approvals, spend.
  • Every decision ends up in somebody's database. If that database can be edited, the "proof" of what the agent did is only as trustworthy as whoever operates it.
  • Today, a judge, an auditor, a regulator, or a counterparty has no way to independently check an AI agent's financial history without trusting the company that built it.

Logging isn't proof. A log you can quietly edit isn't an audit trail — it's a story.


Who actually has this problem

  • Fintechs and card-issuing platforms running LLM-driven approval/decisioning loops (exactly where Ration lives today).
  • Any AI-agent framework that gives an agent spend authority — agent-commerce, autonomous procurement, agentic trading.
  • Regulators and auditors who are being asked to sign off on AI-operated money flows with no independent verification primitive.
  • Counterparties (banks, BaaS partners, card networks) who need proof an agent's decision trail wasn't rewritten after the fact.

The solution

Ration already runs AI agents inside a hard, deterministic spending envelope they can never override — a real, running 11-service system (Rust ledger core + Go services).

Every agent decision was already journaled into audit-log: a genuine append-only, hash-chained trail, kept deliberately separate from the ledger's own write-ahead log.

This submission anchors that chain's current tip on NEAR Testnet — so anyone, not just Ration, can verify what the agent did, without ever touching Ration's own infrastructure.


How it works

 agent / ledger-core          audit-log (Go)              NEAR Testnet
 ───────────────────          ───────────────              ────────────
 financial decision  ───►  append-only hash chain
                           sha256(prev_hash || record)
                                      │
                                      ▼
                           near-anchor commit  ───────►  audit_anchor (Rust/NEAR SDK)
                                                          commit_anchor(seq, hash)
                                                          ├─ stores chain tip + history
                                                          └─ rejects any sequence that
                                                             doesn't strictly advance
                                      ▲
                                      │
                           near-anchor verify  ◄───────  get_latest_anchor()
                           (independent re-read, byte-for-byte compare)

Hand-rolled Go NEAR transaction signer (Borsh + ed25519) — no maintained Go NEAR SDK exists — cross-checked byte-for-byte against near-api-js.


Live proof — recorded today, not simulated

Step Real result
Append 2 real audit-log records sequence advances, VerifyChain confirms intact
Anchor the chain tip on NEAR Testnet tx 5YebAM2YRyoneabk8npkH3a8VnnevnLv9NLkBT5ome1t
Independent raw-RPC re-read (not our own tool) EXPERIMENTAL_tx_status → SuccessValue, matches local tip
Replay the same anchor again nearcore itself rejects it: "sequence must strictly advance past the last anchored sequence"

Full unedited recording: docs/near-hackathon/media/ration-near-demo-2026-11-11.mp4 Primary submission account separately live: ration-anchor-286ca315f1.testnet (3 real anchors, 1 rejected replay, see HACKATHON.md)


Why this fits the track

Track: AI Security & Defense — "Trust, but verify." Ration gives an AI agent money and a hard, external, independently-checkable record of what it did with it — literally the track's own framing.

The hackathon's own FAQ states projects are evaluated on technical implementation, design, impact, originality and sustainability — mapped explicitly on the next slide.


...and the judging criteria

  • Technical implementation — real contract, real signer, 5/5 Rust + Go tests, 4 real on-chain transactions this submission, zero regressions (15/15 ledger-core, full go test ./... -race).
  • Design — audit-log kept deliberately separate from ledger-core's own WAL; anchoring is additive, not a rewrite.
  • Impact — a reusable trust primitive for any AI-agent-with-money system, not Ration-specific.
  • Originality — not a payment rail; a verification layer, with a provably-enforced replay guard.
  • Sustainability — ships as a standalone CLI (near-anchor) today; wiring it into the agent's own poll loop is one small, obvious next step.

Traction — honest

  • $0 revenue, pre-revenue infrastructure. Ration is a real, running fiat-ledger + AI-agent platform (11 services, Rust + Go) already live for development/testing — not a hackathon-only demo app.
  • This submission is a focused add-on: one new capability (on-chain anchoring), not a rewrite.
  • No mainnet transactions, no claimed users of the anchor feature yet — Testnet only, exactly as the evidence above shows.
  • What's not done, on purpose: automatic periodic anchoring isn't wired into the agent's poll loop yet (manual/cron-invoked today) — scoped out to keep this submission honest about what was built and tested under the deadline.

Roadmap

  • Next 2 weeks: wire near-anchor commit into services/agent's own poll loop (periodic, not manual) — the one concrete gap called out above.
  • Next month: per-tenant anchor namespacing (today: one global chain tip per contract); mainnet deployment path.
  • Ongoing: publish the Go NEAR signer as a standalone open-source package — no maintained Go NEAR SDK currently exists.

Arhan Subaşı (GitHub: caelum0x) — solo founder/engineer. Builds production infrastructure: distributed systems, payment ledgers, and now AI-agent safety rails.

  • Repo: github.com/caelum0x/ration
  • Full writeup: docs/near-hackathon/HACKATHON.md
  • Demo video: docs/near-hackathon/media/ration-near-demo-2026-11-11.mp4
  • Sibling entry, same hackathon: Cred402 — SpendGuard (Agent Economy track)

Thank you — questions welcome.