Vault Protocol
HomeBuilderEntitiesMachinesVaultsWorkspaceAI
Art Layer
Resources
Art layerCasesTraitScoreVerificationLayouts

Cases

Cases are serialised ordinal container objects used for presentation, verification and reversible UTXO composition. They can display packed ordinal content, expose serial metadata and interact with the OrdiFi Composer and Verify registry.

Case types

  • Standard Case — general ordinal collector case.
  • Flickerbox Case — Flickerbox collection case.

Cases as collector infrastructure

OrdiFi cases are designed as infrastructure for the broader ordinals community.

  • 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

Every case is its own serialised object. Verify may expose: - serial number - case type - packed status - contained ordinal references - holder information - mint history - pack/unpack history Only successfully minted public objects appear in the Verify registry.

Recursive layout standard

The recursive layout manifest remains intentionally minimal and generic. Layouts operate through: - positional placement - scaling - slot coordinates This allows recursive compositions without hardcoding collection-specific logic into the viewer.

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

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

TraitScore

TraitScore measures how statistically uncommon an item's recorded traits are within its collection. The Case label displays only three derived values: TraitScore, Rank and State.

For every unique trait type and value pair, the rarity points are:

points(type, value) = log₂(N / count(type, value))
  • N is the number of evaluated items containing at least one recorded trait.
  • count(type, value) is the number of evaluated items containing that exact trait pair.
  • Each unique trait pair is counted once per item.
  • A trait found on every evaluated item contributes zero points.

The item score is the sum of all included trait points:

TraitScore(item) = Σ points(type, value)

The current model is identified as ordifi.traitscore.v2. Accessory Count is included unless it is explicitly excluded when generating a collection score.

TraitScore point scale

Every halving of trait frequency adds exactly one point. This makes very rare traits more influential without requiring an arbitrary rarity multiplier.

Collection frequencyTrait points
100%0
50%1
25%2
12.5%3
6.25%4
3.125%5
1.5625%6
0.78125%7
0.390625%8
0.1953125%9
0.09765625%10

Example: if a trait occurs in 8 of 1,024 evaluated items, it contributes log₂(1024 / 8) = 7 points.

Score and display value

  • score is the calculated raw score, stored with up to twelve decimal places.
  • displayScore is the raw score rounded to the nearest whole number for the Case label.
  • maxItemScore is the highest score observed in the evaluated dataset.
  • maxScore is intentionally undefined. TraitScore is not a fixed 0–100 scale.

Scores should only be compared inside the same collection, dataset version and model configuration. A score from one collection is not directly equivalent to the same score from another collection.

Rank and State

Items are ordered by their raw TraitScore. Equal raw scores receive the same competition rank. The next rank then skips the occupied positions, for example 1, 2, 2, 4.

RankState
1–3Legendary
4–10Mythic
11–50Epic
51–250Rare
251–1,000Uncommon
1,001+Common

State is therefore a rank-based collection state, not a Case trait and not a fixed score threshold. A Legendary state may activate the gold Case presentation while the standard Case uses the red label.

Coverage and interpretation

TraitScore records dataset coverage so that incomplete collections remain transparent:

coverage = evaluatedItems / expectedSupply

Results remain provisional while collection records are missing or their metadata has not been independently verified. Completing the dataset may change frequencies, scores, ranks and states.

  • Missing or absent traits contribute no points.
  • Correlated trait types may each contribute points.
  • TraitScore does not determine authenticity, quality or price.
  • The model and collection-data version should accompany published results.

Pack / unpack (viewer behavior)

Pack and unpack operations are reversible compose/split actions performed through the OrdiFi Composer. Packing associates ordinal content with a case or layout structure. Unpacking reconstructs separated ordinal outputs while preserving deterministic positioning.

Serial + QR overlays (production note)

Cases may contain serial and QR overlay layers used for presentation and verification. Serial identifiers are tracked through the OrdiFi registry infrastructure.