Flow 01
Buying strengthens the reserve first.
- 0.1% is minted as STABLEGOLD to the dev vault
- 2.9% deepens the USDC reserve and earmarks a pending gold rebalance allocation until the daily +0.25% target is reached
- Once the target clears, that same 2.9% is minted as STABLEGOLD and accumulated in reserve support instead
- The rest of the buy enters the shared reserve system
Flow 02
Sells are handled with restraint so utility does not turn punitive.
- 0.1% is routed to the dev vault as STABLEGOLD
- 0.9% is burned before the daily +0.25% target is met
- Once the target is met, that same 0.9% routes to the reserve support vault
- The routing adjusts automatically each day based on the daily state
Flow 03
Transfers stay light so people actually want to use the token.
- 0.1% is routed to the dev vault as STABLEGOLD
- The goal is low-friction wallet-to-wallet movement
- Everyday utility is treated as a core design rule, not an afterthought
Profit Handling
Rebalance gains stay organized instead of being blurred into the base layer.
- The rule applies when gold is sold at a profit during rebalance
- One third of realized profit is stored in the tax reserve vault
- The remainder is held within the reserve layer to support the protocol
- This keeps treasury readiness explicit and keeps the accounting honest
The +0.25% Daily Target In Practice
Each day resets the protocol's state. The 0.1% path routes to the dev vault as STABLEGOLD. Before the +0.25% mark, sell protocol fees are burned. After the mark clears, buy reserve fees and sell protocol fees route to the reserve support vault.
Phase A · Before Target
Reserve-building mode
- Buy: 2.9% deepens the USDC reserve and tracks a pending gold allocation
- 0.1% of sells routes to the dev vault as STABLEGOLD
- 0.9% of sells is burned
- The active path resets each day at 00:00 UTC
Phase B · Target Cleared
Reserve-support accumulation mode
- Buy: 2.9% is minted as STABLEGOLD and added to the reserve support vault
- 0.1% of sells routes to the dev vault as STABLEGOLD
- 0.9% of sells routes to the reserve support vault
- Inventory is held by vault policy and rebalance controls
★ The distinction is important: before target, sell protocol fees are burned; after target, buy reserve fees and sell protocol fees route to the reserve support vault. These are deterministic routing rules tied to daily state.
Two Layers, Two Different Jobs
Layer 01
Daily progression layer
- Funded by buy, sell, and transfer activity across the network
- Operates on a defined daily target instead of discretionary promises
- Does not depend on rebalance wins to exist
- Acts as the steady base layer the community can understand
Layer 02
Separate upside layer
- Receives net profit from rebalance trades and hedge activity
- Accumulates independently and is never merged into the primary reserve loop
- Adds optional upside on top of the fee-backed base layer
- Two thirds can remain here while one third goes to the tax reserve
★ Keeping these layers separate makes the protocol easier to trust. The base promise comes from usage, while treasury wins remain visible as additional strength rather than hidden support.
Protocol Mint Addresses
Core mint references for STABLEGOLD and its backing assets on Solana mainnet. Verify independently at any time.