FUEGO · XFG · HEAT

Parked Capital

What happens to the XFG a mint takes out of circulation, why it is the same idea as liquid staking, and the one part of liquid staking Fuego leaves out.

AUDIENCE: AUDITORS, AGENTS, SKEPTICS

EVERY MECHANISM CARRIES A STATUS

A HEAT mint takes XFG out of the minter's hands for good. A first-time reader sees XFG disappear, a new coin appear, and nothing deposited in between, and concludes that value created a coin and was then thrown away.

That conclusion is wrong for the same reason early objections to liquid staking were wrong. Capital that sits idle helps no one. Ethereum's staking market settled on tokens that let staked ETH keep securing the chain while its value works elsewhere, and the network is stronger for it. Fuego applies the same principle at the protocol. The XFG a mint takes is parked with the protocol, and the protocol puts it to work for everyone who uses the chain.

One thing differs from liquid staking, and it matters more than everything else on this page. Liquid staking hands the staker a receipt. Individuals then pledged that receipt, borrowed against it and bought more of it, and that is where liquid staking's failures came from. Fuego issues no receipt against parked XFG.

THE RULE

Nobody holds a claim on parked XFG.

The protocol may use it in more than one place. No individual may redeem it, pledge it or borrow against it. Every section below checks that this holds, and section 10 lists how to show that it does not.

01

The principle liquid staking proved

Staked ETH secures Ethereum. Liquid staking tokens such as stETH let that same ETH also serve in lending and trading, so a holder no longer chooses between securing the chain and keeping capital usable. The market adopted it because it removed that choice.

Parked XFG does two jobs at the protocol level. It pays for security, and it supplies liquidity. The people who benefit are the people who use the chain. Miners are paid without new issuance beyond the supply cap, traders get a deeper market, and holders outside the chain get an outward unit in DIGM.

02

What went wrong was the receipt

Liquid staking has three layers, and they carry different risk.

  1. Use. The ETH is staked and earns. Nothing else claims it.
  2. Receipt. stETH replaces the staker's direct claim with a tradable one. It is one claim in a new form, and it is sound while the receipt stays redeemable at par.
  3. Pledge. The receipt is posted as collateral, borrowed against and bought again. One ETH now stands behind several claims at once. The structure holds while the receipt trades near par and positions unwind in order. In 2022 stETH traded below ETH while leveraged positions unwound, and firms that had built on it failed.

Layers one and two are sound. The risk sits in layer three, and layer three exists because an individual holds a claim they can re-pledge.

03

What Fuego keeps and what it leaves out

Liquid staking compared with a Fuego mint
LIQUID STAKINGFUEGO MINT
Who gives up control of the assetThe staker, in exchange for a receiptThe minter, in exchange for HEAT
What the individual holds afterwardsA claim on the same ETHHEAT, a different asset
Can the individual get the original asset backYes, through the withdrawal queueNo
Can the individual pledge a claim on itYesThere is no claim to pledge
Who decides how it is usedValidators and the staking protocolConsensus rules
Where the risk concentratesLeverage built on the receiptCorrectness of the rules

OBJECTION

Liquid staking returns your asset. A mint does not. Calling this staking is a stretch.

ANSWER

A mint is a sale to the protocol, and this page does not claim otherwise. The comparison is to the principle and to where the risk sits. The minter gives up the XFG and gets HEAT, a different asset with its own issuance rule (section 06). Because the minter keeps no claim on the XFG, the layer where liquid staking accumulated its risk does not exist for this capital.

The risk does not vanish. It moves from many individuals' leverage to one rule set. That is why the last section is a list of tests against the source.

04

What parked XFG does

Uses of parked XFG and their stated status
USEHOWSTATUS
SecurityHalf of each burn is recorded in the Eternal Flame. The block reward formula treats those coins as available and re-emits them to miners, under the 8,000,008.8 XFG cap.LIVE
Liquidity, premium1% of each burn is withheld from the minter, paired with the HEAT it buys, and added to the Hearth pool as the protocol's own position (AuntPoL).LIVE
Liquidity, retained halfThe other half of the burn is kept as real XFG. At each epoch boundary part of it becomes AuntPoL's XFG leg, and just enough is converted to HEAT for the HEAT leg to match. The XFG consumed in that conversion goes to the Eternal Flame in full.BUILT, DORMANT

The re-emission is bounded by an explicit guard:

Osavvirsak  = alreadyGeneratedCoins − eternalFlame;   // coins in circulation
if (Osavvirsak > m_moneySupply) return false;         // fails the block
baseReward  = (m_moneySupply − Osavvirsak) >> emissionSpeedFactor;

The Eternal Flame moves emission forward inside a total that was committed at genesis. It does not raise the total.

The retained half, stated exactly. In fuego-suite today the second half of each burn is recorded in a counter, m_swfBurnedXfgPendingHeat, and nowhere else. No vault output holds it, and the audit RPC describes it as left circulation but still in total supply. The source comment on bankedBurn says that only the remainder of a burn after the premium "is destroyed". That half leaves circulation and is not re-emitted. That is the conservative state, and it is what the chain does until the change below is switched on.

On the claude/swf-auntpol-v2 branch, from a start height that is not yet set, the SWF half of a HEAT mint is kept instead as real XFG in m_swfXfgReserve. At each epoch boundary the protocol deploys it. Part stays as AuntPoL's XFG leg, and just enough is converted to HEAT, at the time-weighted price and never the live spot, for the HEAT leg to match. The deployment is sized so the deposit it feeds always fits under the 50% share cap.

Whenever retained XFG is converted to HEAT, the consumed XFG goes to the Eternal Flame in full. It is not split 50/50 with the SWF, which would hand half straight back to the reserve being spent, and it is not retired from the supply accounting. Each atom of the reserve leaves it once and lands once, either as the XFG leg or in the Flame.

Parked XFG reaches an individual in two ways. It arrives as a block reward for securing the chain, or by trade: when someone sells HEAT into the pool, the pool pays XFG out of its reserves at the pool price. Nobody withdraws it for free.

src/CryptoNoteCore/Currency.cpp for the reward formula and the cap guard; src/CryptoNoteCore/Blockchain.cpp for bankedBurn and the burn routing

05

Why protocol-level use is not double-dipping

Using one asset in two places is not the hazard. The hazard is use that nobody can see, nobody can cap and somebody can call. Parked XFG meets all three conditions. An individual's rehypothecation meets none of them.

Conditions compared for individual rehypothecation and parked XFG
CONDITIONINDIVIDUAL REHYPOTHECATIONPARKED XFG
BoundedSet by the borrower's appetite for leverageRe-emission stops at the supply cap. The protocol's share of the pool stops at 50% of LP shares, and the reserve is deployed only up to that headroom.
UncallableA lender can demand collateral at the worst momentNobody can demand it back. No code path redeems HEAT for XFG. DIGM is designed to redeem against HEAT locked at mint.
VisiblePositions sit in private accountsBurn tallies, HEAT supply, pool reserves and protocol shares are consensus state.

A run needs a claim that can be called while the assets cannot be sold. No such claim exists on parked XFG, so there is nothing to run on.

The cap is measured in pool shares rather than in depth or price. A share ratio cannot be moved by trading against it. The protocol regains room to add liquidity only when someone else adds real liquidity, which dilutes the protocol's share.

OBJECTION

You moved the double use from individuals to the protocol. The protocol can still fail.

ANSWER

Yes. That is the risk named in section 03. The three conditions above and the tests in section 10 are how it is contained.

06

HEAT: why a mint stays honest

The word backed covers three different things. Keeping them apart answers most objections.

  • Cost-constrained at issuance. HEAT has this. A mint must consume XFG at the oracle price or the validator rejects the transaction. Nobody can create HEAT at will, in any amount.
  • Working capital. Parked XFG supports security and market depth. It is not HEAT's collateral, and HEAT holders have no claim on it.
  • Redeemable. HEAT is not. No code path redeems HEAT for XFG. The exit is a sale into the Hearth market at the prevailing price.

The arithmetic is enforced. Every sum in the validator runs over amounts the transaction author chose, so each is checked for wrap before use:

// Every sum below is over amounts the transaction author chose, so each one
// must be checked: a wrapping sum turns an unbacked mint into a "valid" one.
bool addChecked(uint64_t& sum, uint64_t value) {
  if (sum > std::numeric_limits<uint64_t>::max() - value) return false;
  sum += value;
  return true;
}

The price multiply runs in 128 bits. TransactionInputCommitmentTransfer is refused as a burn source, because counting it without valuing it would let a transaction claim a burn it never made.

The 1% premium is a haircut inside the burn. It moves one percent of the minter's entitlement to the protocol's pool position, and total issuance is unchanged:

premiumXfg   = xfgBurned × 100 / 10000
HEAT created = (heat(xfgBurned) − heat(premiumXfg)) + heat(premiumXfg)
             = heat(xfgBurned)

The premium's HEAT leg is defined as what its XFG leg buys at the current price, so both legs arrive already paired at the pool ratio. A larger premium would tax the action the system most needs, so the position is fed from trading fees instead. In the v12 design, 35% of each Hearth fee goes to the position, 35% to makers and 30% to savers (status in section 11).

src/CryptoNoteCore/HeatMintEngine.cpp for addChecked, scanMintTx and validateMint; src/CryptoNoteConfig.h for HEAT_MINT_PREMIUM_BPS and heatMintPremiumXfg

07

The oracle

Mints are priced from an eight-block time-weighted average of the Hearth pool, so the oracle is the component an attacker goes after. Each defence closed a hole that existed.

  • The mint prices from the average only. A spot fallback once let a swap earlier in the same block set the price a mint paid.
  • The average excludes the mint's own block, so a transaction cannot contribute to the price it pays.
  • The average reads the pool spot and never the call-auction clearing price, so two tiny crossed orders cannot manufacture a reading.
  • A per-block band limits how far the pool may move from its opening price, so one trade cannot drag the average.
  • Fewer than two samples returns no price, and the mint is refused.

src/CryptoNoteCore/Blockchain.cpp for twapBefore() and validateSettlement()

08

DIGM: the one receipt

DIGM is the outward-facing unit, built for markets where XFG has no wrapped form and HEAT does not travel. It is a receipt for HEAT. Minting requires locking HEAT at a fixed peg:

requiredHeat = digmOutputs × DIGM_PEG_HEAT_ATOMIC / COIN;
if (heatInputs < requiredHeat + fee) return false;

Because the peg is a constant, mint and redemption are exact inverses with no drift. The first-generation cap of 10,000 DIGM against a 0.1 HEAT peg locks 1,000 HEAT in total.

Two limits apply. Once DIGM is bridged out, the protocol cannot stop anyone from re-pledging it elsewhere. That stack sits on HEAT locked at a fixed ratio and carries no claim on XFG. The bridge itself is a stub (DigmBridgeEngine.h is ten lines), and whoever operates it off-chain can issue claims against nothing. That is the counterparty risk that matters.

src/CryptoNoteCore/DigmMintEngine.cpp for validateMint

09

What it costs and what is not claimed

  • HEAT is not redeemable. Anyone holding it is exposed to the Hearth price.
  • Deflation is smaller than it looks. Half of each burn returns to miners through the Flame. When the retained half ships, it stops being deflation for holders and becomes protocol working capital. Holders trade that deflation for depth and an outward connection.
  • The cost index is a target. It sets what one HEAT is meant to represent and re-bases quarterly. Its on-chain reader has one consumer, a status endpoint, and appears in no pricing or redemption path. If supply outgrows demand, HEAT trades below its target.
  • Dilution is possible. The protocol mints HEAT to pair with the retained XFG. Under the launch defaults that is at most about a quarter of the HEAT users mint, and less whenever the Hearth fee share has already fed the HEAT leg. It is sized to what the legs need, bounded by the 50% share cap, and credited to supply when created. It is a wager that added depth attracts added demand.
  • Depth is thin. The seeded pool is a fraction of one percent of supply. Fees compound depth and cannot create it, so the first depth has to be contributed.
  • Precedent. Protocol-owned liquidity funded by users selling assets to a treasury has been tried. Several bonding-based tokens marketed their treasuries as a price floor and lost most of their value when demand ended. Fuego promises no floor.
10

How to prove this wrong

Each item is a specific check against the source. Any one failing breaks the rule, and the correct response is to publish that.

  1. A path from parked XFG to an individual that is not a trade or a block reward. withdrawTreasuryLp can burn protocol LP shares and has no caller anywhere in the tree. A commit that adds one breaks the rule.
  2. A token, output or balance that works as a claim on parked XFG. The SWF counter must stay a statistic with no issuance authority.
  3. A ceiling denominated in a price. The share cap must stay in pool shares.
  4. Interest funded from a burn. Trace yield to its source. Burn-derived value, the mint premium or the CD creation fee reaching an interest payment fails the rule.
  5. Protocol-minted HEAT missing from supply. It must be credited when it is created. deploySwfReserve credits m_heatSupply in the same step that mints it.
  6. An epoch-boundary operation priced at spot. Epoch boundaries are deterministic, so a trade in the closing block sets that rate. Two such sites existed and both were fixed.
  7. DIGM issued without locked HEAT. The bridge is where this breaks if it breaks.
  8. A conversion that credits the Flame with less than the XFG it consumed, or retires that XFG from supply. testSwfDeployCreditsConvertedXfgToEternalFlameInFull pins it, and breaking it on purpose fails the suite.
11

Status

Implementation items and their stated status
ITEMSTATE
Mint validation, 1% premium, TWAP oracle, Eternal Flame, AMM, AuntPoL pairing from the premiumLIVE in fuego-suite
Epoch CD-yield priced at TWAP, saturating reserve credit, accumulator carried forwardBRANCH claude/usexfg-merge-redo
SWF conversion removed, 35/35/30 Hearth split, 50% LP-share cap, XFG-leg donation route, retained SWF reserve with epoch deployment and full Eternal Flame routingBRANCH claude/swf-auntpol-v2. Compiled with the project's flags and covered by core_tests (354 assertions). The split, the cap and the reserve stay dormant until a start height is set. The donation route is gated to v12. Cache format moves to version 17, so nodes replay once on upgrade.
DIGM bridge and redemptionNOT BUILT
Genesis seed recorded as owed to its providerAccounting only. The one reader sets a flag and no payout exists. Zeroing it is a one-line change, pending.

Where this page and the code disagree, the code is the fact and this page is the bug.

Back to Answers