Skip to content
Prototype · Devnet · Simulated custodyAbout this prototype

Custody workflow

From deposit to retirement

The custody process map v0.1: seven stages, who acts at each step, what record changes, and whether the prototype step is Real, Simulated, or Mockup.
No vault partner exists. The custodian is a fictional role, and no legal agreement makes a token represent title. In Phase 1, steps tagged Real for devnet are front-end mockups; they become real devnet transactions in Phase 3.

Custody record

Physical layer. Written only by the custodian: where the item is, its condition, and who the custodian recognizes as holder of record.

Link

A custodian-signed attestation (hash on-chain as link_hash) referencing a placeholder agreement.

Ownership record

Digital layer. The Metaplex Core asset on devnet plus its transfer history. Wallet control is not proof of legal title.

Passport lifecycle

  1. Draft
  2. Documented
  3. Intake requested
  4. In custody
  5. Tokenized
  6. Listed
  7. Transferred
  8. Redemption requested
  9. Redeemed
  10. Retired

Branches: hold (dispute or freeze) and withdrawn.

Stage 1 · Deposit & intake

  • 1.1Create draft passport (core + category module), upload owner photos labeled “pre-intake”Actor: OwnerOutput: lifecycle draft → documentedReal
  • 1.2Choose custodian, submit deposit requestActor: OwnerOutput: custody status = intake_requestedSimulated· fictional custodian
  • 1.3Custodian reviews request and accepts or declinesActor: CustodianOutput: Decision event in custody recordSimulated
  • 1.4Shipping / drop-off arrangements, transit insuranceActor: Owner + CustodianOutput: Shipping referenceMockup
  • 1.5Physical receipt; intake receipt issuedActor: CustodianOutput: intake_receipt_doc_id, status = intake_in_progressSimulated· sample receipt

Stage 2 · Verification

  • 2.1Intake photographyActor: CustodianOutput: media (captured_by = custodian), hashesSimulated· existing photos, labeled
  • 2.2Measurements, materials, collationActor: CustodianOutput: Attested item fieldsSimulated
  • 2.3Condition reportActor: Custodian or conservatorOutput: condition.reports[] + doc hashSimulated· SAMPLE
  • 2.4Authentication (if the category requires it)Actor: Third-party authenticatorOutput: authentication.records[]Simulated· Becker: none
  • 2.5Optional appraisal / insurance valuationActor: AppraiserOutput: valuation.records[] (private)Mockup
  • 2.6VaultLit document review (completeness, hashes match)Actor: VaultLit (remote)Output: Checklist completeReal· automated checklist

Stage 3 · Custody

  • 3.1Custodian accepts into custody; location assigned (custodian-only)Actor: CustodianOutput: status = in_custody, location_label (locked)Simulated
  • 3.2Storage plan and prepaid termActor: Owner + CustodianOutput: storage_termsSimulated· no billing
  • 3.3Custody & transfer terms presented and acceptedActor: Owner + CustodianOutput: agreement status = placeholder_not_a_legal_agreementMockup· needs specialist review

Stage 4 · Token issuance

  • 4.1Custodian signs attestation linking custody record ↔ passport versionActor: Custodian (demo wallet)Output: custody_ownership_link, link_hashReal· signature by a simulated custodian
  • 4.2Mint Metaplex Core asset into custodian collection, to owner wallet, with attributes and freeze/burn delegatesActor: PlatformOutput: ownership_record (network = devnet)Real· devnet
  • 4.3Passport version anchored; lifecycle tokenizedActor: PlatformOutput: Version hash on-chainReal· devnet

Stage 5 · Transfer

  • 5.1List on marketplace (illustrative devnet SOL price, DEMO label)Actor: OwnerOutput: ListingReal· UI + DB; price illustrative
  • 5.2Buy, or gift/transfer to another walletActor: Buyer / OwnerOutput: Devnet transfer txReal· devnet
  • 5.3(Later) KYC of new holder before custodian recognitionActor: Platform / vendorOutput: holder_identityMockup· needs specialist review
  • 5.4Indexer detects transfer; ownership record + dashboards updateActor: PlatformOutput: transfers[]Real
  • 5.5Custodian portal shows new on-chain holder vs recognized holder; custodian confirmsActor: CustodianOutput: Custody record updatedReal· sync Real · recognition Simulated

Stage 6 · Redemption

  • 6.1Holder requests physical redemption (signed wallet message)Actor: HolderOutput: status = redemption_requestedReal· signature
  • 6.2Custodian freezes token (permanent freeze delegate)Actor: CustodianOutput: Frozen assetReal· devnet
  • 6.3Identity and fee checks; shipping arrangedActor: CustodianOutput: Release checklistMockup· Simulated / Mockup
  • 6.4Item released/shipped; release receiptActor: CustodianOutput: status = releasedSimulated· nothing moves

Stage 7 · Retirement

  • 7.1Custodian burns token (permanent burn delegate)Actor: CustodianOutput: Burn txReal· devnet
  • 7.2Passport marked redeemed → retired; passport persists as a permanent recordActor: PlatformOutput: Final anchored versionReal

Actors (swimlanes)

ActorIn realityIn the prototypePhysical contact?
Owner / DepositorCollectorFounder (demo wallet A)Ships or hands over the item
CustodianProfessional storage partnerDemo custodian login + demo walletYes: receives, photographs, stores
Third-party specialistsConservator, authenticator, appraiserSimulated uploads by the demo custodianYes, at custodian facility
VaultLit platformSoftware + remote ops staffThe appNever: remote only
Solana (devnet)Public chainDevnet (Phase 3)—
Buyer / RecipientSecond collectorDemo wallet BOnly at redemption

Remote-operation rule: intake, photography, condition reports and authentication are done by the custodian or third parties and uploaded through the partner portal with captured_by / attested_by. VaultLit never handles other people's items.