W3C TPAC hackathon 2026 · Dublin

Agents with Legal Agency

An agent gets data that isn't public, from a party that doesn't own it. The owner issues a Data Rights Credential (W3C VC 2.0, iSHARE profile); the custodian validates it against the iSHARE scheme — and sends a receipt back. One mandate, several doors.

Why: AI that acts for people and organisations needs legal guard rails, not just protocol. Every party here signed the same accession agreement, so a licence in a credential is a contractual obligation with a dispute procedure behind it — and the receipt is the rights holder's proof. Trust comes from the scheme, not the key.

Rights holder · principal

Blue Shipping

Owns the data about container CONS-2026-104455. Does not host it.

iSHARE participantDRC issuer

Data Rights Credential (issued)

— not issued yet —

Receipt inbox

Verifiable proof, held by Blue — not a log at the custodian.

Inspect the live credentials

Every object below is signed and served by this server; open it, paste it into any VC 2.0 verifier.

Data Rights Credential (latest; issue first) · profile
iSHARE participant credential · red · green · yellow
Verification Receipt credentials (Blue's inbox, verified on arrival)
Bitstring Status List · DRCs (signed by Blue) · participants (signed by the scheme)
Trusted list · DID documents: blue · red · green · yellow · scheme

iSHARE trusted list

Who may issue what, with which assurance. The verifier trusts a party admitted to the scheme, not a key.

Agent · data user

Red Forwarding — ETA agent

Holder of the DRC. Carries it; never owns it.

iSHARE participant credentialholder: did:web:red.example

Participant credential (legal prerequisite)

Verifiable Presentation sent at the door

— nothing presented yet —

Event log

ready.

Custodians · access control

Green Terminal

Holds the container data. Validates Blue's conditions; decides nothing itself.

Yellow Carrier

Holds the same container. Same resource id, same DRC, different door.