Skip to content

Economic — Overflow Play

TL;DR: H2O and VITUS have two-tier overflow: above Meridians[13] your personal mint spills to WORLD; above Meridians[20] WORLD's holdings burn. Withdraw or redistribute before the first cliff.

Why this matters

Both H2O and VITUS enforce identical two-tier spillover logic on Mint(). The contract does not revert when you'd exceed the cap; it silently reroutes the excess. That means a busy session can quietly donate your earnings to WORLD (or vaporize them entirely) without any visible failure.

If you chat-mine and WAR-farm without periodically clearing your personal balance, you're leaking.

The numbers

The logic (from H2O and VITUS) is equivalent to:

_max  = War.World().Map().Map().Meridians(13)   // personal cap
_max2 = War.World().Map().Map().Meridians(20)   // WORLD cap

if balanceOf(you) + amount > _max:
    excess = (balanceOf(you) + amount) - _max
    amount -= excess
    # excess goes to WORLD, not you
    if balanceOf(WORLD) + excess > _max2:
        burn_excess_excess    // burn anything over _max2
    else:
        _mint(WORLD, excess)
_mint(you, amount)
Variable Source Notes
Meridians[13] HECKEMERIDIANS Personal holdings soft ceiling.
Meridians[20] HECKEMERIDIANS WORLD-held hard ceiling; over this, new mint burns.
balanceOf(you) ERC-20 balance of H2O/VITUS on your YUE Both tokens mint to Chi, which resolves to YUE.
balanceOf(WORLD) ERC-20 balance of H2O/VITUS on the WORLD contract Accumulates other players' overflow too.

The specific numeric values of Meridians[13] and Meridians[20] are lookups in the global Hecke table — on-chain-readable but not practical to memorize. What matters is that Meridians[13] < Meridians[20] and there's a big numeric gap between them.

The play

  1. Set a withdrawal heuristic. If your YUE holds H2O or VITUS approaching Meridians[13], either withdraw to wallet or spend down (Purchase/Redeem into other assets via YUE.Hong/Hung).
  2. Prefer many small withdraws to one big one. Gas efficient under normal fee conditions; avoids the scenario where you rack up a huge single mint that spills.
  3. Watch for silent failure. If your post-action balance increase is smaller than the Iota you saw in a WAR or the Dione you saw in a Code, you overflowed. Diff balanceOf before and after.
  4. (inferred) Don't be the one to fill WORLD. If WORLD's H2O/VITUS is near Meridians[20], your next overflow burns rather than donates. Check balanceOf(WORLD) before chasing big WAR highs.
  5. Use Hong / Hung to swap out of capped tokens. YUE gives you an internal market; you don't need external DEXes. Swap H2O → QING-asset when you're within spitting distance of Meridians[13].

Worked example

Say Meridians[13] is (hypothetically) 1e24 atomic units and you hold 0.95e24 H2O in your YUE. You Faa a position where Iota = 0.1e24.

Without planning:

  • Intended mint: 0.1e24 H2O to you.
  • Post-math: 0.95e24 + 0.1e24 = 1.05e24 > 1e24. Excess = 0.05e24.
  • You receive: 0.05e24 H2O.
  • WORLD receives: 0.05e24 H2O.
  • You lost half your expected earnings silently.

With planning (withdraw 0.5e24 first):

  • New personal balance: 0.45e24.
  • Mint: full 0.1e24 to you.
  • No overflow, no donation.

The difference — 0.05e24 H2O — is pure revenue captured by planning.

Gotchas

  • Meridians[13] and Meridians[20] are absolute, not per-token. Both H2O and VITUS use the same two indices. H2O's cap is the same number as VITUS's cap, measured independently per token.
  • Overflow goes to WORLD, not to the contract caller's counterparty. It's not a "tax to the protocol"; it's routed to WORLD specifically, which then distributes over time via WORLD.Distribute.
  • Burn is only at Meridians[20], not at Meridians[13]. Your cliff is "donate"; the second cliff is "burn".
  • There's no event for the spillover path. Don't expect a Spillover or OverflowBurn log. Compute it from balance diffs.
  • (inferred) Because WORLD accumulates others' overflows too, balanceOf(WORLD) rises faster than any single player can cause. If lots of farmers are spilling, Meridians[20] fills and your future spillover burns outright.

Where it cross-connects