dev.malpercio.cards.transfer

Written by the current owner to hand a card to another DID. The recipient completes the transfer by writing a dev.malpercio.cards.item whose 'via' strongRefs this record. Repos are mutable, so an appview indexing the firehose resolves conflicting transfers of the same give (first seen wins).

Details · record, key tid
Kindrecord
Record keytid
Authoritycards.malpercio.dev
Indexed

Record

record · key tid

Properties

createdAt

requiredstring · datetime

expiresAt

string · datetime

If the recipient hasn't accepted by then, the sender may delete this and keep the card.

give

requiredstring · at-uri

Root give, denormalized so indexers can key conflicts without fetching the item.

item

requiredref

The sender's dev.malpercio.cards.item being transferred.

note

string
  • maxLength: 512

recipient

requiredstring · did

Optional: the counterparty's transfer this is exchanged for. Both sides reference each other for a two-way trade.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • An appview's signed observation of a card changing hands, written into the appview's own repo. Triggered by a dev.malpercio.cards.item appearing on the firehose. Accepted witnesses form a prev-linked chain per give; exactly one accepted witness exists per (give, hop). Rejected witnesses explain why a claimant's item is not recognized. The chain is durable against player-side deletions and auditable by replaying the firehose.

  • A card (or sealed pack) held by the repo owner. Not authoritative on its own: validity comes from the chain of strongRefs back to a provider give whose recipient matches the current owner at each hop. Blobs are the owner's local copies and must hash to the CIDs on the root give.

  • The listing owner's attestation of an exchange: who was chosen to give/receive the listed gift, and when it was completed. The counterparty attests via community.gifthood.exchangeResponse; a mutually confirmed pair is follow-through evidence. Public, like the interest record.

  • Consumes finalized value outputs to transfer value and optionally return change to the sender.