cred402/SUBMISSION-CHECKLIST.md
caelum0x 07136e7b73 feat(near-hackathon): fold Ration's audit-anchor work into this repo as ONE combined NEAR submission
Owner directive (2026-11-11): submit a single project to the NEAR
Hackathon instead of two separate entries from the same person. Vendors
Ration's NEAR audit-anchor work (github.com/caelum0x/ration, commit
cff0ed3 + follow-ups) into ration-anchor/ as a first-class component:

- contracts-near/audit_anchor (NEAR Rust contract, 5/5 cargo tests
  green, target/ deleted)
- signer/ — a new, self-contained Go module (no dependency on Ration's
  other services or go.work) with the hand-rolled NEAR transaction
  signer + JSON-RPC client (cross-checked byte-for-byte against
  near-api-js) and the hash-chained audit ledger it anchors; 15/15 Go
  tests green (go test ./... -race)
- docs/ and media/ — Ration's original pitch deck, demo recordings, and
  submission checklist

Re-verified live via raw NEAR Testnet JSON-RPC this pass:
ration-anchor-286ca315f1.testnet still deployed and queryable, the
deliberate replay-rejection transaction still fails with nearcore's own
"sequence must strictly advance" panic — no redeploy needed.

Provenance notes added throughout (package doc comments, lib.rs header,
README) crediting the origin repo. README.md and HACKATHON.md rewritten
to tell one story: Cred402's SpendGuard enforces the protocol-level
spending limit, the vendored Audit Anchor proves the tamper-evident
spend history, both independently verifiable on NEAR Testnet. No mainnet
claims anywhere (see prior overclaim fix 524f2dd). cred402's own build
(npm run typecheck) and existing tests are untouched.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-11 15:32:24 +03:00

7.4 KiB

NEAR Hackathon submission checklist (Nov 1-14, 2026, results Nov 18)

Code, docs, tests, and repo visibility are done. What's left is short and owner-only (identity + a social post + the form submission).

Done (no action needed)

  • NEAR x402 settlement built and tested: lib/x402/near_*.ts, api/near_x402_routes.ts, api/near_receipt_anchor.ts.

  • Buyer example: examples/near-paid-score/typescript.ts (+ README).

  • Status/usage/attempt routes: /v1/x402/near/status, /v1/x402/near/usage, /v1/x402/near/payments/:id.

  • Tests: 14 new (test/near_x402.test.ts), full suite 450/450 green (re-verified 2026-11-05), npm run typecheck clean.

  • Real end-to-end NEAR Testnet verification (2026-11-02): live local server, real 402/invalid-proof/underpaid-proof rejections, and one genuine on-chain NEAR Testnet payment (tx C1LNxQFEaR2AQj79U9WzToiB1eY86jwzmxoHKvr9W7jk) settled for real — see "Verification" in docs/near_x402.md.

  • HACKATHON.md written (what/why/how-to-run/track/NEAR tools used).

  • Repo caelum0x/cred402 confirmed public (gh repo view → visibility: PUBLIC) — already satisfied the hackathon's public-repo requirement before this work started; re-verified, no change needed.

  • Changes committed and pushed to origin/main.

  • SpendGuard NEAR smart contract (contracts-near/spend_guard) — AI Security & Defense complement to the x402 rail above: policy-underwritten credit lines, protocol-enforced spend caps via real NEAR Function Call Access Key allowances, a dispute-rate circuit breaker, and a real revolving-credit repay_credit_line + top_up_allowance pair. 18/18 unit tests green. Real near-workspaces sandbox test (tests/sandbox.rs) against a live local nearcore node proves the full loop end to end: draw → real on-chain repayment (outstanding exposure verified zeroed via get_exposure before/after) → real on-chain top-up that restores exactly the freed headroom and re-mints the SAME still-active key → a real spend that succeeds again on that key → dispute spike → freeze → revoked-key rejection — see "SpendGuard" section in HACKATHON.md.

  • Demo video recorded (2026-11-07) — scripts/record_near_spend_guard_demo.mjs (npm run record:near-spend-guard) screen-captures the real terminal session of npm run demo:near-spend-guard with asciinema, then renders it with agg + ffmpeg. Real output, real on-chain NEAR Testnet calls against the live spendguard-024e8dd6f7.testnet contract — not staged/fake terminal text. Files, all committed: media/cred402-near-spend-guard-demo.cast (raw asciicast, full fidelity — play with asciinema play), .gif and .mp4 (17.0s, 1174x560, rendered from the real cast), -poster.png (thumbnail). Covers the full required loop on camera: cargo build + 18 unit tests + sandbox integration test green, then the live-Testnet bonus run — 25 real spend_to_seller calls, a real repay_credit_line call, a real top_up_allowance call, one more real spend on the SAME original key, a dispute spike, a freeze, and a real rejected post-freeze call, ending on the script's own real_spends: 25, revolving_credit_proved: true, scammer_frozen: true summary. A ready-to-post X draft referencing this video is at X-POST-DRAFT-2026-11-07.md in this same directory (owner posts it — needs a logged-in X account, see item 3 below).

  • Ration audit anchor, now part of Cred402 (added 2026-11-11, owner decision to submit ONE combined project instead of two separate entries) — ration-anchor/ vendors in Ration's NEAR audit-anchor work (contract, hand-rolled Go NEAR signer, anchoring service, tests, demo assets) as a first-class component. 15/15 Go tests + 5/5 Rust contract tests green; deployed contract ration-anchor-286ca315f1.testnet and its replay-rejection evidence re-verified live via NEAR Testnet RPC this pass. See "Audit Anchor" section in HACKATHON.md and ration-anchor/README.md.

Owner-only (fill in before submitting)

  1. Team info — the hackathon form asks for a team lead name/email and team size. This agent does not have and must not guess your identity:

    • Team lead name: [OWNER: fill in]
    • Team lead email: [OWNER: fill in] (likely subasiarhan3@gmail.com, but confirm — this is your call, not an automated default)
    • Team size: [OWNER: fill in] (solo founder → 1, unless you're entering with others)
  2. NEAR payout account — if the hackathon asks for a NEAR account to receive prize funds, it must be a real wallet you control:

    • Payout NEAR account id: [OWNER: fill in]
    • If you don't have one yet: create a free NEAR account at near-faucet.io (testnet) or NEAR Wallet (mainnet, for a real payout account) in under a minute, then fill this in.
    • This is also the account you can optionally set as CRED402_NEAR_PAY_TO if you want the deployed demo to actually charge into your own wallet instead of a disposable test account.
  3. Demo post on X (required, confirmed against the real hackathon page 2026-11-05) — must state you built this at NEAR HACKATHON, tag @NEARProtocol and #NEARHackathon, and have a demo video or screenshots attached. The video itself is now a finished artifact (media/cred402-near-spend-guard-demo.mp4, recorded 2026-11-07 — see above), so the only remaining step is uploading it to X, which needs your logged-in X account. A ready-to-post draft caption is in X-POST-DRAFT-2026-11-07.md — copy it, attach the mp4, post.

    • Demo video: media/cred402-near-spend-guard-demo.mp4 (done, in-repo)
    • X/Twitter post URL (must tag @NEARProtocol + #NEARHackathon): [OWNER: fill in once posted]
  4. Submit the form at nearhackathon.com before Nov 14, 2026 23:59 UTC (results by Nov 18, 2026 23:59 UTC). Confirmed fields on the real form (2026-11-05): project name, team lead name + email, team size, track (up to 13 available — pick Agent Economy and, if the form allows multi-select, also AI Security & Defense for the Ration Audit Anchor half), NEAR wallet address for prize distribution, repository link (required), demo post link on X (required), a 20-2000 character project description (the "What it does" section of HACKATHON.md, ~1,100 chars, pastes in directly), and an optional website URL.

    • Repo URL: https://github.com/caelum0x/cred402 (public, confirmed)
    • The team info, payout account, and demo link from steps 1-3 above.
    • Submission form confirmation: [OWNER: fill in once submitted]

Not done, and intentionally so

  • No real NEAR Mainnet payment was made or claimed. This submission runs on NEAR Testnet only, per the task's own instruction not to attempt a real mainnet payment. CRED402_NEAR_MAINNET_RELEASE_ACK gates Mainnet and is unset.
  • Nothing was posted to X/Twitter and the hackathon form was not submitted — both require your logged-in accounts and are listed above as the only remaining steps. (The demo video itself is done and no longer part of this gap — see item 3 above.)