Pitch what you'd build on Arkiv — the queryable, tamper-proof Web3 database. Design the idea, not the deployment.
Each track closes when its window ends · last close Aug 31 · 23:59 UTC
August is over and the ideas are in. Four tracks, three places each — $500, $300 and $200 — picked by the track hosts against the published rubric.
Host: Santiago · window 3–11 Aug 2026 · 80 canonical submissions judged
A shared, self-expiring registry of what does NOT work, so coding agents stop burning tokens rediscovering the same dead ends — confidence is simply how many reports are still alive.
Positive knowledge wants permanence. Negative knowledge wants expiry.
An agent capability index where every claim dies unless an independent prober re-proves it, so the product's answer is an absence nobody can suppress.
The main output is a negative — nobody has verified this agent recently — and it is trustworthy only when the hiding party cannot suppress it.
A neutral, expiring evidence layer where independent scanners, publishers and monitors attest to an exact MCP release and tool-schema hash before an agent connects.
Arkiv does not prove a claim is true, but it prevents one operator from becoming the sole author and lifecycle authority.
Host: Santiago · open all month, closed 31 Aug 2026 · 89 canonical submissions judged
A shared game world with no server and no studio, where every building is an Arkiv entity you pay rent on — pine lasts a week, stone a season, a monument five years — and whatever the players stop caring about literally sinks off the map, because the decay is not game code someone can patch, it is the database.
On Postgres, upkeep is a cron job and a promise a patch can break; on Arkiv it is physics.
Indonesian statutory crane and forklift fitness certificates written as Arkiv entities whose lifetime IS the certificate's legal validity, so the gate check at a site entrance is one existence query with no date comparison in it to get wrong.
An expired certificate is not a row with a stale date on it; it is a row that no longer exists to be returned.
Data that lives on the publisher's own machine and surfaces on Arkiv only during the window it is actually needed, with the timetable itself published on-chain so anyone can query when it comes back.
A window needs no close transaction, no cron, no contract call: its expiry IS its closing time.
Host: Shantelle Awomoyi · window 12–20 Aug 2026
A listing that stays alive only while the seller keeps proving they still have the item — an unrenewed claim simply disappears, so a sold ticket cannot stay listed on four other venues.
In a double-sale dispute, whoever runs the database decides who was at fault, and that operator is a rival.
A signed lease ledger for ephemeral agent sandboxes where the lease and the reservation are the same object, so orphaned compute dies on schedule instead of leaking budget and two agents cannot silently hold the same box.
Here neglect frees the resource. Same laziness, opposite blast radius.
Every price a listing has been offered at is written as an append-only, self-expiring entity signed by the seller, so the struck-through was-price becomes a fact anyone can verify in one query instead of a claim the seller makes about its own past.
The record's author is the party it indicts.
Host: Marcos Miranda · window 21–31 Aug 2026
A witness log, not an oracle — solvers and keepers publish signed, short-lived observations of DeFi state too small or fast-moving to justify oracle-grade economic security, and their standing is only as good as their last corroborated report.
Nothing stops one operator writing three rows and calling it redundancy.
PARALLAX lets a DeFi risk analyst see the blast radius of a protocol failure before it cascades, not after.
The moment you need multiple mutually distrusting observers writing to the same dataset without one of them controlling it, you've left what a plain database can honestly promise.
Turn your wallet's invisible token approvals into shared security intelligence, see what each permission can do, how much is at risk, and which real exploit it resembles, powered by an exploit-and-reputation graph that lives on Arkiv so any wallet or dApp can read it.
Native expiry = self-cleaning intel — decay without cron jobs or a moderation DB.
Podium-grade ideas that carry no prize — two because their authors already won in another track (one prize per person, across every entry), one because of a host tie-break recorded in the winners sheet.
A 90-day vulnerability disclosure embargo as a transferable Arkiv entity whose lifetime IS the deadline, so the notification date, the party responsible right now, and every request for more time become facts instead of claims.
An accessibility map where every fact rots on purpose, so a step-free route shows green only while somebody has confirmed it in the last six hours, and the operator cannot delete the reports that say otherwise.
A public warranty registry where the entity's lifetime IS the coverage period, so a second-hand buyer verifies a phone with one query and no wallet, and the shop that owes the repair no longer holds the record that decides whether it owes it.
Winners first, then the 50 strongest from AI & DevTools and the open Other lane by the judging panel's score — plus 20 from Marketplaces, which its own host judged. Filter by track, or search all 70.
Showing all 70 ideas
A shared, self-expiring registry of what doesn't work, so coding agents stop burning tokens rediscovering the same dead ends.
An agent capability index where every claim dies unless an independent prober re-proves it, so "what is missing" becomes the answer.
A neutral, expiring evidence layer where independent publishers, security scanners, and uptime monitors attest to the safety and health of exact MCP server releases before AI agents connect.
An open, serverless game world the tide is always taking back: every wall and monument is an Arkiv entity kept alive by Lifetime Extension, materials are lifetimes (pine lasts a week, stone a season), and whatever the players stop caring about literally sinks off the query surface.
Statutory inspection certificates for lifting equipment written as Arkiv entities whose lifetime IS the certificate's validity period — so an expired certificate is not a row with a stale date on it; it is a row that no longer exists to be returned.
Data that lives on your own machine and surfaces on Arkiv only during the window it is actually needed, with the timetable itself published on Arkiv so anyone can see when it comes back.
A listing that stays alive only while the seller keeps proving they still have the item.
A signed lease ledger for ephemeral agent sandboxes where the lease and the reservation are the same object — so orphaned compute dies on schedule instead of leaking budget, and two agents can't silently hold the same box.
Every price a listing has been offered at is written as an append-only, self-expiring Arkiv entity signed by the seller, so the struck-through "was" price becomes a fact anyone can verify in one query instead of a claim the seller makes about its own past.
Ctrl-C is not a permission system. Airlock makes every agent delegation a signed, self-expiring Arkiv entity delete one link and every sub-agent beneath it loses authority instantly.
Countersign gives two companies integrating over webhooks an independent, tamper-proof record of exactly when something was sent and when it was actually received, so a "we never got that" dispute has a real answer instead of one side's word against the other's.
A vulnerability embargo as a transferable entity whose lifetime is the deadline, so the notification date, the party responsible right now, and every request for more time become verifiable facts.
A map of accessibility facts that expire on their own, so a step-free route you can see is one somebody actually confirmed today — and an operator cannot delete the reports that say otherwise.
A public warranty registry: merchants issue coverage as Arkiv entities whose lifetime IS the warranty period — buyers and second-hand buyers verify with one query and no wallet, and the shop that owes you a repair no longer owns the database that says whether it owes you.
Funded work with deadlines, recorded so a missed milestone is a signed public event instead of a quiet renegotiation.
A public calibration record for prediction markets: what a venue priced an event at before it resolved, written where nobody can edit it afterwards.
A shared, self-expiring registry of "framework X actually worked against tool Y version Z last Tuesday" — where compatibility is a signed, decaying claim rather than a green badge somebody stopped maintaining in 2024.
A credential registry with no revocation list — validity is not a field, it is whether the entity still exists, so an expired or revoked attestation cannot be presented as valid because it is no longer there to present.
Provenance lets a smallholder farm land (e.g, cocoa plot) carry its EUDR verification from one buyer/exporter to another. An accredited surveyor verifies the plot once, and other exporters can check that record instead of paying to map the same farm again.
A live trust graph for real-world safety claims — an inspection goes invalid the moment whoever vouched for it loses their own standing, not just when the paperwork's timer runs out.
Signed, self-expiring attestations that implementation X conformed to spec revision S — so "which clients are actually ready for this fork?" is a query, not a spreadsheet somebody forgot to update.
A VS Code and Cursor extension that turns an Arkiv entity model into safe types, valid queries, meaningful lifetimes, and explicit privacy boundaries before the first write
Hasp is a live claim board for heavy equipment serials that shows who currently holds the machine, who published the claim, and when that claim expires.
A raffle platform for tech communities: attendees import in one click from Luma, the entry list freezes as tamper-proof Arkiv entities, and winners derive from a public randomness beacon — a stadium llama race on top, provable fairness underneath, no wallets needed for participants.
A shared validity layer for AI agents that turns operational assumptions into scope-bound, attributable leases that expire back to “unknown” when they should be rechecked.
A tamper-evident, queryable record of every action your agents take in production - and the permission that authorized it.
Two coding agents on one repo refactor the same file and open competing PRs because neither sees what the other is doing; Deadman gives them a shared ledger on Arkiv where each claim is a self-renewing lease, so live work is visible and abandoned work expires by itself.
A tamper-proof flight recorder for AI agents that act on real businesses: every agent action is signed and written to Arkiv next to an expiring, queryable permission slip — so the party being audited never owns the audit log.
CivicLibro is a public, tamper-proof accountability trail for public infrastructure: citizens report problems, authorities log inspections and responses, and neither side can quietly bury the record.
Eval prevents coding-agent benchmarks from being rewritten after submissions: organizers commit the hidden exam upfront, while independent runners publish reproducible scores and disputes on Arkiv.
Principal-signed, short-lived capability mandates that agents, approvers, and MCP/A2A gateways verify before executing side-effecting work.
A verifiable, self-expiring reality layer for open-source rewards, so contributors can distinguish live bounties from stale, claimed, or settled listings before doing the work.
ScopeTrace is a queryable registry of signed, expiring AI-agent mandates and execution receipts that lets wallets and payment resolvers verify authorization before execution and audit it afterward
An AI agent's logs live in a database its operator can edit — Witness is the copy they can't.
Agent Action Warrants gives AI agents short-lived, human-signed permission records they can check before sensitive actions, while credentials and execution stay outside Arkiv.
A creator-controlled permission layer where anyone can verify who may use a creative work, for what purpose, and until when.
ProofSignal is a shared evidence layer for crypto opportunities. Projects, researchers, and AI agents can publish time-scoped assessments, attach sources, challenge each other, and let different apps decide what to trust.
A shared, expiring threat-intelligence layer that lets wallets and agents query what trusted security providers knew about an address or domain before a user signed.
An eval index where a failed run is a recorded state instead of a missing row, so a score can still be defended a month after it was published.
Smart-contract audit reports as queryable Arkiv entities with a validity clock: the 'audited' badge expires when the audit expires, and nobody can quietly delete or backdate a report.
Signed, self-expiring support leases that let a coding agent check whether an SDK symbol is still promised to work before it writes the call — so an abandoned API stops being generated even when nobody remembers to deprecate it.
A tamper-proof exercise ledger where red and blue team agents log adversarial security tests as signed Arkiv entities, so MTTD/MTTR can't be edited by either side after the fact.
AI can generate architectures. Arkitect proves they're valid.
CausalGraph preserves the chain between construction events, evidence and their consequences while a project is happening, so disputes don’t have to reconstruct causality months later.
A public, self-expiring debugging index in which coding agents look up past verified fixes for the problem they just hit, before spending tokens re-discovering it.
Prove turns duplicate bug discoveries from autonomous coding agents into independent reproduction evidence before they become maintainer spam.
A community dictionary for endangered Nigerian languages where unconfirmed words expire on their own and confirmed ones survive — so the archive prunes itself without a moderator.
An AI agent that audits your code against real law — GDPR, CCPA, the EU AI Act — quoting the statute verbatim anchored to a file and line and drafting the fix as a PR, while writing its findings and its own self-grades to Arkiv so a reviewer can trust the audit trail without trusting the vendor.
A tamper-proof, queryable custody trail for temperature-sensitive goods where every handler signs their handoff to Arkiv and breach evidence outlives the product's shelf life for dispute resolution.
The open, tamper-proof product passport for circular economy - EU DPP compliant, built for 2027 regulation
ArcContext is a verifiable company memory layer on Arkiv: AI agents get provenance-checked, time-scoped context from Slack, Notion and email — and auditors or counterparties verify the same memory without trusting a vendor.
Clearance shows whether a worker’s required credentials stay valid for the entire duration of an assignment, not just whether they’re valid today.
An offline workbench where you design an Arkiv schema and run your real queries against a local mock of Arkiv's engine — catching the model's footguns (string-vs-numeric, no ORDER BY, per-type expiry) in seconds, with no network.
A hire-and-verify marketplace where agent reputation is built from immutable, independently-countersigned records instead of an editable database row
The signal marketplace where the track record can't lie — analysts commit calls on Arkiv before the market moves, stale signals expire themselves, and anyone can independently verify every win rate.
An Agentic Marketplace Where Trust is the Currency.
Quaerium is an open request-for-quote marketplace where humans and AI agents purchase expiring, verifiable answers from private datasets without acquiring the datasets themselves.
Beba is a freight marketplace where posting a load and accepting a quote are the same entity changing hands - the moment a shipper accepts, ownership transfers on-chain from shipper to carrier, turning an open listing into a provable booking. No separate bookings table, ever.
A reputation system for Nigeria's informal errand economy, built so trust follows the runner, not the platform.
The seller's promise, signed and timestamped at checkout, that stays alive exactly as long as the buyer's claim does and then provably closes itself.
A quant-signal marketplace where every seller's track record is assembled from sealed commitments anchored before the outcome was knowable — so buyers never have to trust the platform, the seller, or the screenshot.
``` A verifiable, self-expiring dispute-evidence layer any marketplace can plug in. Both sides commit a hash of their evidence up front, reveal it only if a dispute opens, and every write is signed, so nobody can forge, backdate or delete the record. Fair disputes, less churn.
A marketplace for paid agent services where every listing carries delivery receipts written by the buyers, so a buying agent can filter on what was actually delivered instead of what was advertised.
Tukiv is a self-pruning marketplace that rescues reusable construction materials before disposal deadlines through filterable lots, expiring offers, and creator-verifiable inspections.
A peer-to-peer marketplace where people and agents post short, self-expiring skill/time availability slots that buyers can query and match with verifiable offers — no stale listings, no fake availability.
A shared, tamper-proof evidence log for marketplace disputes. Both sides attach timestamped proof to an order, and neither can fabricate or backdate what they submitted.
A fit-aware fashion marketplace where every listing, quote, and stock signal is a queryable, self-expiring, tamper-proof Arkiv entity — so human shoppers and AI agents browse the same verified inventory.
An open, self-pruning marketplace protocol where AI agents and service providers publish live capabilities, jobs and offers on Arkiv, while completed-work receipts create portable, tamper-proof reputation that any marketplace can query
A bounty marketplace where dead listings self-prune and reviewer verdicts can be challenged and staked, so reviewer reputation is provable instead of platform-asserted.
Researchers list a time-bounded exclusive first look; exclusivity ends when the Arkiv entity leaves the query surface.
No idea on the board matches that. Clear the search to see all 70.
The ranked part of this board is the judging panel's first read, not the verdict — the prizes were decided by the track hosts after a second, adversarial pass, which is why the podium and this order differ. The Marketplaces cards are a sample and carry no ranking at all: that track's scorecards belong to its host. All 232 ideas across the three tracks are listed in the repo, one line each: SHOWCASE.md .
Arkiv is the Web3 database: CRUD + built-in indexes over Arkiv entities — filter, paginate and count like you would in SQL. Ethereum-aligned, $GLM-powered.
prompt
"show me Messi's goals against Real Madrid" await arkiv.buildQuery().where(eq("opponent", "Real Madrid")).fetch() result
prompt
"keep every goal until August 20, then let it expire" await arkiv.createEntity({ goal, expiresIn: 2_592_000 }) result
prompt
"prove goal_311 was really recorded" await arkiv.getEntity("goal_311") // creator, block & tx — checkable on-chain result
prompt
"where do these goals actually live?" await arkiv.getEntity("0x2f81…9c04") result
Each track closes at the end of its own window — the open Other lane runs all month. Tap a card for its brief — ideas, data model, host, and when it closes.
Each track closes at the end of its own window — the open Other lane runs all month. Windows run in sequence and each one closes at 23:59 UTC on its last day.
One connection: the Ideathon MCP. Your agent gets the tracks, the rules, the exact judging rubric and Arkiv's fundamentals — plus a prompt that pressure-tests your idea before you submit. No wallet, no key, nothing to deploy.
One URL, read-only, no key. Works with MCP clients that support remote servers — Claude Code, Claude.ai, Cursor and more. It carries everything official — tracks and briefs, rules and rubric, Arkiv fundamentals — so your agent designs grounded, not guessing.
https://ideathon-mcp.arkiv.network/api/mcp What's inside → Ask for a track's brief and idea seeds, search the knowledge base, or pull the scoring rubric — the same 100 points the judges use. Your agent even knows what deliberately stays OFF Arkiv, so it won't over-promise.
tools: list_tracks · get_doc · search_kb Arkiv docs → The built-in idea coach: it places your draft on a readiness band and asks the 3–5 highest-leverage questions on the judges' angles — the Arkiv counterfactual, data & query design, growth, scope. Answer, iterate, then submit sharp.
prompt: review_my_idea Then submit it → New to the entity model? Start with the Arkiv Fundamentals → — it explains exactly what the form asks about. Or connect the MCP above and ask your agent instead: it serves that same doc.
Pitch the idea and its Arkiv data model — no deploy. Every track has its own $1,000 USDC pool — $4,000 in total. Each track closes at the end of its own window — the open Other lane runs all month.
Tap a track card for its brief — buildable ideas + what a strong submission looks like. Or bring anything to the open Other lane. The track you pick sets your deadline.
Map it to Arkiv: which entities, which attributes, which queries. That data model IS the pitch.
Your form answers ARE the submission — no repo, no deploy. Optional: a mock, diagram or short video.
Submit before your track's window closes — its host reviews every idea.
Every track has its own $1,000 USDC pool: $500 for 1st place, $300 for 2nd, $200 for 3rd — $4,000 USDC in total, ranked by the judging team against the published rubric. If a track doesn't receive three ideas that meet the judging criteria, the remaining prize money from that track may be redistributed to other tracks. Strong ideas can also earn mainnet credits, follow-on build support and marketing amplification.
Prizes are paid in USDC to an EVM wallet. Prize winners complete KYC before payout. Winners & highlights roll out the week of Sept 1.