[ ARKIV ]

Evidence
has a shelf
life.

Queryable, expiring data for ERC-8004 agents.

Shantelle Awomoyi

Head of Ecosystem

DEVCON 8 · AGENTIC HUB · MUMBAI · 3 NOV

[ ARKIV ] · HEAD OF ECOSYSTEM

[ 01 ]The problem

The score is on-chain.
The evidence isn't.

Stored on-chain

Emitted only · no retention rule

WHY IT MATTERSIf you can't see the evidence, the score is just a number.

[ 01 ] · The problemSource: EIP-8004 (Draft), eips.ethereum.org

[ 01 ]The problem

The score
goes stale.

92REPUTATION

agent-42 · v1

Summarises contracts. Accurate, careful, slow.

92REPUTATION

agent-42 · v2

Not shipped yet.

WHY IT MATTERSYou end up trusting last month's agent.

[ 01 ] · The problemarkiv.network

[ 02 ]The pain

One contract.
How many
systems?

1

"What's waiting for my validator?"

WHY IT MATTERSEvery team rebuilds this alone. Retention is decided differently, or not at all.

[ 02 ] · The painarkiv.network

[ 03 ]What others are saying

It's not just
me saying this.

"On-chain pointers and hashes cannot be deleted."

EIP-8004Security considerations

The Validation Registry is "still under active update and discussion with the TEE community."

erc-8004-contractsREADME

"Last month's feedback describes last month's agent."

AlchemyScores age badly

"Cross-chain aggregation is an indexer problem the standard does not yet solve."

AlchemyReputation stays on one chain

"The standard remains a draft and has already been redesigned once."

AlchemyInterfaces may still move

The standard is still moving. That's the window to fix it.

So→

[ 03 ] · What others are sayingeips.ethereum.org · github.com/erc-8004 · alchemy.com

[ 04 ]Why Arkiv

Data as a
first-class
citizen.

An Ethereum-aligned Web3 database.

From Web2 databases

Structured records, indexing, a query language.

From Web3

Ownership, tamper-evidence, permissionless access.

Of its own

Rules the data carries itself, such as a lifetime or who may extend or change it.

Web2	Web3	Arkiv
Battle-tested DB UX	UX tailored for transactional logic and asset transfer	Data-centric UX in a Web3 setting
Centralized	Permissionless	Permissionless
Control depends on host	Wallet-owned	Wallet-owned
Queryable data	Data not easily queryable	Queryable data

[ 04 ] · Why Arkivarkiv.network

[ 05 ]How it works

Data
lifecycle.

01

Write

Store expirable data with queryable attributes in a DB-Chain.

02

Own

Manage your data with a wallet. Write, update and delete.

03

Query

Anyone can retrieve data using a query language served over familiar RPC endpoints.

04

Expiration

Data is pruned when the expiration time comes. Extend it when needed.

DB-Chains. Data-centric blockchains. Where Ethereum runs its state through the EVM, a DB-Chain runs it through a database engine. Every write is a signed transaction.

Database engine. Runs inside every DB-Chain. Deterministic, so every node computes the same state: structured records, indexing and a query language.

[ 05 ] · How it worksarkiv.network

[ 05 ]How it works · agent-42

Evidence, with a shelf life.

const Validations = defineSchema("devcon8004_validation", { agentId: str().indexed(), validator: str().indexed(), version: str().indexed(), status: str().indexed(), requestHash: str(), createdAt: u64().indexed(), body: bytes(),}) await wallet.createEntity(Validations, { agentId: str("agent-42"), validator: str(validator), version: str("v1"), status: str("pass"), requestHash: str(keccak256(body)), createdAt: u64(Date.now()), body,}, { expiration: ExpirationTime.fromSeconds(60), flags: { readonly: true } }) await reader .select({ $key: true, $expiresAt: true }) .from(Validations) .createdBy(writer) .where(and( eq("validator", str("validator-alpha")), eq("status", str("pending")), gte("createdAt", u64(Date.now() - 10 * MINUTE)), )) .fetch()

01

Model it

Indexed attributes are what you query on. The evidence travels in the body, and the hash commits to it.

02

Write it

Owned by your wallet, read-only once written. 60 seconds in the demo; in real life, the dispute window.

03

Query it

Two indexed attributes and a time window in one filter, straight from the chain. No indexer.

[ 05 ] · The code running in the demo@arkiv-network/sdk 1.0 · Rabdi

[ 06 ]Why it fixes it

Verifiable,
without keeping it forever.

No home for the evidence	→	Lives on Arkiv, owned by a wallet, checked against its on-chain hash."Only your wallet can update and delete your data."
No retention rule	→	Expiry is set when you write it. Explicit, not a cron job."Data is removed from the query surface on expiration."
Scores go stale	→	Query by time: only evidence from the last 30 days.
Six systems	→	One write. One query.
Cross-chain reputation	·	Still open. We don't solve this today.

[ 06 ] · Why it fixes itQuotes: Arkiv leaflet

[ 07 ]Demo · Rabdi testnet

LIVE ON RABDI

Trust has a
shelf life.

01agent-42 writes its validation evidence to Arkiv every 5 seconds, each record with a 60-second shelf life

02Ship v2: the lifetime score stays put, the live score moves as v1's passes drop out of queries

03The explorer: a record's expiration block, then the record gone

04Re-hash the evidence: ✓ matches on-chain. An edited copy: ✗

Open the live dashboard ↗ D Open in the Rabdi explorer ↗

[ 07 ] · DemoRabdi DB-Chain · chain ID 7794095

[ 08 ]The ask

The hash is forever.
The evidence
needs a window.

01

How long does it live?

02

Who can extend it?

03

What does the hash point to after?

Let's agree a lifecycle for agent evidence while ERC-8004 is still a draft: rules the data carries itself.[ ARKIV ] · SHANTELLE AWOMOYI · HEAD OF ECOSYSTEM

Start
building.

hub.arkiv.network

[ 08 ] · The askarkiv.network

Evidencehas a shelflife.

The score is on-chain.The evidence isn't.