STABLEGOLD
Back to Main Site
Transparency First

How STABLEGOLD Makes Decisions

This page explains exactly what is fixed, what is automated, and why settings change. No marketing shorthand. If a value is dynamic, we show the rule that drives it.

Buy Fee3.0% total: 0.1% dev + 2.9% reserve side.
Sell Fee LogicFixed 0.1% dev + dynamic burn component (0-0.9%).
Rebalance TriggerEffective trigger = base threshold + tax buffer (default: 500 + 250 = 750 bps).
Controller TargetDefault 0.42% implied daily appreciation target.
Update CadenceFee controller loop runs every 300 seconds by default.
Fixed Rules

1) What Never Changes Automatically

  • Buy fee total is fixed at 300 bps (3.0%).
  • Buy dev slice is fixed at 10 bps (0.1%).
  • Sell dev fee target is fixed at 10 bps (0.1%).
  • Sell max fee target is fixed at 100 bps (1.0%) so sell dev + sell burn cannot exceed max.
  • Keeper does not auto-change the headline 3.0% buy fee itself. It only adjusts routing behavior inside policy bounds.
Automated Rules

2) What The Keeper Can Adjust

  • Sell burn fee target between 0 and 90 bps.
  • Pump regime buy-fee burn share (portion of 2.9% reserve side directed to burn vault reserve).
  • Slowdown regime buy-fee burn share.
  • Slowdown reserve burn ratio.
  • Policy writes are sent on-chain only when values actually changed.
Live Policy Snapshot

3.25) Current On-Chain Rebalance Policy

These values are read directly from the on-chain config account when available. If the page cannot reach Solana RPC, the last known defaults are shown.

Base Threshold 500 bps
Tax Buffer 250 bps
Effective Trigger 750 bps (7.5%)
Config Status Loading…

Source: awaiting on-chain config lookup.

3) Core Decision Math

The keeper records implied price snapshots and compares observed daily movement to target. When growth lags, it raises sell burn pressure. When growth is ahead, it reduces sell burn pressure.

error = targetDailyPct - observedDailyPct
rawCorrectionBps = round(error * 30)
newSellBurnBps = clamp(prevSellBurnBps + rawCorrectionBps, 0, 90)

A minimum 5 bps change threshold is used to avoid noisy churn.

3.5) Rebalance Trigger Math (Tax-Aware)

Rebalancing is now tax-aware and configurable. The protocol combines a base rebalance threshold with a tax buffer to reduce low-value churn from frequent vault swaps.

effectiveRebalanceThresholdBps = baseRebalanceThresholdBps + rebalanceTaxBufferBps
default: 500 + 250 = 750 bps (7.5%)

Both base threshold and tax buffer are admin-configurable on-chain.

4) Why Buy Routing Changes Too

Sell-side burn alone is not enough under all regimes. The keeper also adjusts how defensive the reserve side should be by combining two inputs:

  • Price pressure: how far observed growth is below target.
  • Market stress signal: neutral, USD weakening, gold weakening, both weakening, or risk-off.
  • Combined score: 60% pressure + 40% signal intensity.
  • Higher score means higher burn-share routing and stronger slowdown defense settings.

5) Market Signal Ladder

  • Neutral: intensity 0.0
  • USD weakening or gold weakening: intensity 0.5
  • Both weakening: intensity 0.8
  • Risk-off: intensity 1.0

This intensity does not directly set fees. It weights the buy-routing defense score and works jointly with target-gap pressure.

6) Adjustment Flow, End To End

Step 1Fetch market data and classify regime signal.
Step 2Compute implied price trend and daily error versus target.
Step 3Compute sell burn target plus buy-routing defense parameters.
Step 4If policy changed, submit one on-chain adaptive policy update transaction.

7) Current Default Bounds

Parameter Default Bounds / Notes Who Changes It
Target Daily Appreciation 0.42% Config value, environment-driven. Operator config
Initial Sell Burn Fee 45 bps Runtime starting value before enough history exists. Operator config
Dynamic Sell Burn Fee Controller output 0 to 90 bps clamp. Keeper automation
Pump Buy Burn Share 0 bps base Scales toward max, bounded by policy checks. Keeper automation
Slowdown Buy Burn Share 1000 bps base Always at least as defensive as pump path. Keeper automation
Slowdown Reserve Burn 100 bps base Scales to configured max in stressed regimes. Keeper automation
Base Rebalance Threshold 500 bps Admin-configurable. Used as the base drift trigger. Protocol admin
Rebalance Tax Buffer 250 bps Admin-configurable additive buffer for tax-aware triggering. Protocol admin
Effective Rebalance Trigger 750 bps Computed as base threshold + tax buffer. On-chain rule

8) Live Now vs Staged Behavior

Live / Active

  • Adaptive fee-control loop runs on schedule.
  • Sell burn + buy-routing policy are computed together.
  • Keeper submits adaptive policy updates when values change.
  • Program-side bounds validation prevents out-of-range policy writes.

Staged / Partial

  • Implied price currently uses market proxies in keeper runtime unless replaced with full on-chain backing reads.
  • Some non-fee loops still log intended actions until full on-chain execution paths are enabled.
  • Public dashboard values stay N/A where on-chain data is not yet surfaced.
Risk Disclosure

9) What Could Still Go Wrong

  • Bad or delayed market data can produce wrong pressure signals.
  • Keeper downtime means policy lags real market conditions.
  • Liquidity stress can make intended rebalancing execution expensive or slow.
  • Configuration mistakes can over-tighten or under-tighten controller responses.

Transparency policy: if a feature is not fully on-chain and observable yet, it should be treated as staged behavior, not guaranteed final production behavior.