BankeizEnter bank

A value you can
reproduce.

The original proof fixes the starting point. A chosen Kai coordinate reveals its computed value.

Explore the calculation Verify your proof
One sealed origin, many explicit evaluationsThe original proof coordinate remains at the center. An evaluation travels around it. The graphic represents coordinates, not a price or growth promise.OriginEvaluationOne sealed originMany evaluations

A calculated value. A distinct market price. A separate Settlement balance.

The source stays fixed.

  1. 01

    Verify the original.

    The complete sealed proof carries its lawful Kai origin. Uploading it, opening an account or evaluating it later does not reset that origin.

  2. 02

    Read carried history.

    Admitted ownership and lineage stay attached to their source. A successor seal advances the history of the same proof object.

  3. 03

    Choose the evaluation.

    An explicit Kai µPulse chooses when to evaluate. The existing law uses its whole pulse; the exact admitted coordinate remains in the replay.

A legacy original can carry only whole-pulse precision. The reader reports that limit; multiplying it cannot recover missing precision.

Every term has a source.

valueΦ= floor + band × wave + PV

Rarity floor

The claim moment, early index, model adoption and Fibonacci/Lucas age levels establish the formula’s floor.

Premium band

Series size, craft, geometry and applicable lineage shape the amount above that floor.

Live alignment

Breath, Kai day, Beatty strobe and moment affinity multiply the band at the evaluation coordinate.

Recorded contributions

Cash-equivalent contributions recorded with the object add their present value. They can take effect at sealing or at a later pulse. An absent declaration contributes zero.

What changes as a proof ages?

Age is the distance from the original coordinate to the evaluation coordinate. It changes the capped logarithmic age lift, the model’s adoption delta and its Fibonacci/Lucas accrual levels. “Adoption” here is a deterministic curve of the Kai coordinate, not a count of users or a live demand feed. The live waves can move in either direction, so the complete value is not guaranteed to rise at every evaluation.

The exact composition and policy

One coherent breath is the base unit: 1 Φ. The installed v129 calculator publishes algorithm phi/kosmos-vφ-5, policy checksum b05b2049 and the following composition.

baselinePremium = rarity × quality × creator × provenance
  × closure × cadence × hold × resonance × age × churn
  × geometry × moment

dynamicGrowth = indexScarcity × adoptionLift
  × fibAccrualLift × lucasAccrualLift

floor = claimMoment × dynamicGrowth × max(1, genesisBias)
band = max(0, baselinePremium × dynamicGrowth − floor)
wave = Q(breath × day × strobe × affinity)
valueΦ = floor + band × wave + PV

Q(x) = Math.round(x × 1000000) / 1000000
PhiMicro = Math.round(valueΦ × 1000000)

The calculation retains ECMAScript binary64 numbers and Math functions. It quantizes the oscillators as specified above; rounding Phi micro-units is a display projection. The policy checksum identifies the original sorted-key policy bytes through a noncryptographic 32-bit FNV-like accumulator. It is not a signature.

In the proof-bound path, sealed declarations and admitted history supply the operands. Creator verification and reputation are explicitly unknown inputs, not verified facts. Legacy defaults such as size 1, medium quality, no creator verification, reputation 0 and absent cashflows are recorded as reproducibility-only. The low-level missing-origin fallback is never a substitute for a carried proof origin.

Each cashflow contributes amount / (1 + max(0, atPulse − evaluationPulse) / 17491.270421). This is a declared model operand, not independent evidence of future income.

All published constants, rounding and defaults
Enable JavaScript to inspect the installed SDK policy.

Replay the calculation.

Move through an explicit interval and see how the same formula responds. These editable operands are an illustration; a held original supplies its own admitted inputs below.

Objects in the same edition. Use 1 for a unique object, or 100 for an edition of 100.

Cash value contributions Optional

Enter the cash-equivalent value represented by one object, in Φ, and its effective pulse. Use the origin pulse for value at sealing, or a later pulse for an additional contribution.

No value contributions added.

Future contributions are discounted to the valuation pulse. Contributions already effective retain their full model amount. The underlying funds or asset evidence must verify separately.

The present pulse is captured when you calculate. Move through the chart to inspect earlier pulses.

Present value at pulse

— Φ

Recomputed model samples

Intrinsic valueRarity floor

The source operands and policy stay fixed at every point.

Inspect every term

The complete SDK trace retains each formula, string operand, result, unit and source reference.

Φ to $.
Computed at this pulse.

Your calculated Φ converts automatically. Choose manual entry to convert a separate amount with Market’s exact conversion algorithm applied to this calculation’s metadata. The object inputs and live Kai pulse determine the rate. The rate cannot be edited.

Up to six decimal places. The amount stays in exact integer micro-units.

The live pulse updates automatically. The exchange rate is computed from it.

$ USD conversion

—

—

How the exact Market conversion is computed

Use the same object metadata that produced the Φ value. Take floor(Kai µPulse / 1000000) from the live Kai clock. The Market calls quotePhiForUsd with that object’s intrinsic computation, the pinned default policy, a fixed $100 reference quote, zero streak, zero lifetime USD and zero planned hold. The Φ amount does not change the quoted rate.

q9(x) = Math.round(x × 1000000000) / 1000000000
multiplier = q9(M_adoption × M_premium × M_moment
  × sizeMultiplier × M_streak × M_tier × M_choir
  × M_breath × M_festival × M_milestone)
PhiPerUSD = q9(0.10 × multiplier)
USDPerPhi = q9(1 / PhiPerUSD)
Phi = PhiMicro / 1000000
USD cents = Math.round(Phi × USDPerPhi × 100)
USD display = USD cents / 100

These are Market’s original ECMAScript binary64 operations, nine-decimal quantization and multiplication/rounding order. The calculator uses the same quote and cent-conversion functions as Market. A listed object’s exact quote also depends on its recorded public display seed. The illustrative calculation preserves your selected quality, edition size and contributions; a verified original uses its admitted inputs. Those inputs can differ from a public listing’s display seed. It does not truncate the exchange rate to eight decimals or substitute a wallet aggregate rate.

Read the shared Market conversion · Read every factor and default

Inspect this calculation’s inputs and arithmetic

From proof to independent replay.

  1. 1

    Original bytes

  2. 2

    Verified source

  3. 3

    Exact operands

  4. 4

    Replay digest

Match the bytes, history, policy, coordinates and conversion basis. Then recompute.

See your object’s value.

Choose an original proof object. Verify its source and see its value at the moment you select it, calculated on this device.

Your file stays here. No account or upload is required.

Replay options

Use a complete portable asset to inspect carried ownership. Additional samples use this captured dollar quote. Identity Records and private accounts cannot be valued by this public reader.

Have a replay already?

Reverify its original, SDK-pinned roots and every expected projection digest.

Three values. Three meanings.

Intrinsic proof value
A calculation over the admitted original at a chosen coordinate. Aging changes the calculation; this page performs no payment or account credit.
Market price
An asking price is a seller’s offer. A completed sale requires independently verified payment and accepted delivery for the same asset, participants and committed intent. Neither changes intrinsic calculator inputs.
Spendable Settlement
Qualified account sources, current ownership, selected admitted value heads and committed credits or debits determine available Settlement. A chart point or replay digest does not create that membership.
How qualified account value is derived

The existing v125 lawful-action path admits a verified, sealed action under its registered law and causal completion evidence. It enforces one spendable membership per enclosing artifact. With admitted start, completion and valuation Kai coordinates, its separate integer law is:

Settlement PhiMicro = (completionKai − startKai + 1)
  × (valuationKai − completionKai + 1)

startKai ≤ completionKai ≤ valuationKai

A value head requires SDK-held admission custody, binds the current owner and ownership history, and chains its prior value head. Account projection selects those retained heads and current memberships before summing. It cannot replace missing history with a caller’s amount.

The retained artifact pathway separately projects a complete admitted public membership for the canonical current owner. Its per-artifact base uses the original Kai seed and the intrinsic projector; account composition adds qualified lawful-action amounts and transaction deltas without counting the same membership twice. The verifier and account pathway establish eligibility; the pure formula supplies arithmetic.

Reserve holds proof-backed funds internally. Choosing available legacy payment rails moves value outside proof continuity at the receiving balance; the transfer’s original receipt remains verifiable. Read about Settlement and Reserve

A platform rarity policy can supply a separate market reference only when its canonical digest and named operands match the sealed issuance. A last-sale reference uses the uniquely causally latest applicable completed sale; missing or incomparable evidence remains unknown. Asking prices stay separate.

Same inputs.
Same result.

An independent verifier must accept the same original and history, then reproduce the same canonical projection digests.

Understand receiving conformance
  • Exact original bytes and admitted history head
  • Algorithm, policy constants and checksum
  • Explicit evaluation and sample coordinates
  • Complete declared operands and recorded defaults
  • Matching USD rule and digest-bound basis, when used
  • Matching SDK version and pinned verifier roots

The replay includes the public source, policy, selected options, coordinates and expected digests. Verification checks the enclosing source before recomputation. Sample order, warm caches, prior calls and local wall time cannot choose a different value at the same coordinate.

Missing carried origin or payload, unsupported private sources, incomplete sale joins and unavailable precision remain explicit. Canonical JSON, detached metadata or a recomputed checksum cannot supply proof admission. Browser, Node and MCP parity must be tested with the same bytes and replay; fixture parity alone is not an institution’s conformance assessment.