Vault Protocol
Art Layer
Resources
Art layerCasesVerificationLayouts

Cases

Layouts are collector infrastructure: a presentation layer for ordinals, designed to be shown in vitrines, albums and showrooms. Layouts may be empty shells or verified as “full” based on proof.

Case types (current)

  • Standard Case — general ordinal collector case (unbound, supports pack/unpack via viewer).
  • Flickerbox Case — member presentation object (may be bound by policy / verification).
  • Rare Sat Case — proof-based display (two-asset proof: case + sat).
  • Rare Sat Hardcase — a stricter/premium variant (planned).

Cases as collector infrastructure (not members-only)

OrdiFi cases are designed as infrastructure for the broader ordinals community. Membership adds identity and premium presentation, but the base collector tooling is intended to remain accessible.

  • Cases are mintable layouts even without content.
  • Content display can require proof, depending on clayout type.
  • Showroom surfaces exist to curate and exhibit cases (vitrines, albums, suitcases).

Verification model (full vs empty)

A case is a distinct object (its own inscription/ID). “Full” status depends on proof requirements for the case type. This prevents confusion in secondary markets: a case can exist without verified content.

  • Primary ID: the case itself.
  • Contained IDs: the ordinal/sat IDs.
  • Status: verified full vs empty.

Recursive layout standard (v1 minimal)

OrdiFi uses a minimal layout manifest that composes inscriptions with simple transforms. The manifest is generic: it does not know what the content “is” (mouse hole, window, case label, etc.). It only applies:

  • scale (uniform or explicit)
  • x, y placement

This keeps the standard flexible and broadly useful for recursive compositions beyond OrdiFi.

Pack / unpack (viewer behavior)

Packing/unpacking is a display linkage used by OrdiFi’s collector tooling. A case can remain tradeable even when “packed”; unpacking is the user-controlled process to remove the display content.

For strict binding (e.g., immutable burn-in), a separate bound case flow may exist, where content is burned into the case at mint time and cannot be changed.

Serial + QR overlays (production note)

Cases can include a serial + QR overlay layer. Serial overlays can be pre-rendered and pre-inscribed so mint flows can reference them immediately. This supports predictable presentation and verification UX.