BOARD PRESENTATION

D.A.R.A. · the member experience

DIGITAL ASSET RECOVERY ALLIANCE

One member.
Four passes.
Separate accounts.

The pass is the identity reference. It is not the database.

Current homepage preview

THE MODEL

Four layers. Four passes.

01User Contract

02Product Gateway

03NFT Contract

04Token-bound account

Connected layers. Not separate copies of the same record.

PRODUCT 1 · OWN NFT AND ACCOUNT

PRODUCT 2 · OWN NFT AND ACCOUNT

PRODUCT 3 · OWN NFT AND ACCOUNT

PRODUCT 4 · OWN NFT AND ACCOUNT

CURRENT PREVIEW

The member journey

01

Homepage → emailBrand before access

02

Claim dashboardGenus is required for the claim

03

Mint Genus → Mint My ClaimActions simulated in this preview

04

Passes → token-bound accountsEach pass retains its own account

Claim Dashboard showing Mint Genus first and a not-deployed contract — Current Claim Dashboard · no deployed claim contract

MINT MY CLAIM

The claim sequence · simulated

01

Claim NFTExample id only

02

Master Claim NFTPrototype / concept

03

Master Claim AccountPrototype / concept

04

Deposit TokenFuture production integration

05

Recovery FundFuture production integration

EXAMPLE ONLY · NOTHING SENT TO A CONTRACT

Current Claim Dashboard after simulated mint, with steps and Master Claim Account — Current simulated claim state

BRIEF ALIGNMENT

What the preview represents

DEMONSTRATED NOW

Four passes / separate accounts
Chapel chain id 97
Canonical ERC-6551 registry
TEST in and out, once deployed

PROTOTYPE / CONCEPT

Mint My Claim
Example position
Preview account address
Preview TEST movement

FUTURE PRODUCTION

Real wallet and contracts
Verified claim data
On-chain ownership
Redemption mechanics

No deployed claim contract. Nothing here is evidence of a live on-chain claim or financial entitlement.

SECOND CLIENT BRIEF

A separate path to reconcile

01Claim NFT

Authenticated claim

02Approval

Claim accepted

03Redemption

Rules not defined here

04Partnership Platform Token

Issuance not shown

05E.D.E.N.

Product Ecosystem

This path comes from the Complete User #1042 brief. It is not built into the current claim preview.

CLIENT CONFIRMATION REQUESTED

How do the two paths connect?

PATH A · FIRST BRIEF

Deposit Token → Recovery Fund Staking Protocol

PATH B · SECOND BRIEF

Redemption → Partnership Platform Token → E.D.E.N.

TEAM DIRECTION: BOTH IN SEQUENCE

Does redemption follow staking, or branch at another step? What event links them, and in which order?

BEFORE CONTRACT WORK

Decisions & dependencies

01Confirm the handoff between the two ending paths.

02One Claim NFT per Master Claim, or several?

03Which pass details may be shown to members?

04Approve final pass artwork and actual balance split.

05Supply verified BSC contracts, addresses, ABIs, and claim data.

Sources: D.A.R.A. board documents 01–10; Mint My Claim Developer Architecture Brief; I AM’s ERC-6551 Complete User #1042 brief. Preview screens shown as examples.