Protocol Documentation v1.0

The Ingot Protocol

Ingot is the premier infrastructure for Real World Asset (RWA) memecoins on BNB Chain. By combining the viral distribution of internet culture with the institutional-grade collateral of Tether Gold (XAU₮), Ingot forges a new asset class: meme coins pegged to a gold-backed price floor.

Every token launched on Ingot debuts with its market cap anchored to the spot price of physical gold — not an arbitrary valuation dreamed up at launch. Traditional launchpads let tokens open at any price with zero underlying value; Ingot tokens are immediately bootstrapped with deep, one-sided PancakeSwap V3 liquidity, collateralized entirely by XAU₮ reserves.

The Ingot Standard (ING-20)

The Ingot Standard is a deterministic deployment specification for ERC-20 tokens on BNB Chain. It extends the base ERC-20 interface with a mandatory liquidity initialization sequence, binding each token's genesis state to a dedicated XAU₮ collateral pool.

Specification Requirements

• Fixed Supply: Exactly 21,000,000 tokens (18 decimals), mirroring Bitcoin's hard cap.
• Metadata Persistence: Social links (Website, Telegram, X) and Logo URI are written on-chain at deployment and cannot be altered.
• Deterministic Vault: Every token deployment automatically spawns a dedicated IngotLPVault contract.
• One-Sided Bootstrapping: 100% of the token supply is deposited into a one-sided PancakeSwap V3 position at genesis, seeding liquidity without a matched XAU₮ contribution from the deployer.

Genesis Gold Peg

The defining economic feature of the Ingot Standard is the Genesis Gold Peg: every token's market cap starts at the price of one ounce of gold.

When a creator forges a new token, IngotFactory calculates the initial PancakeSwap V3 tick range (tickLower to tickUpper) so that price discovery begins mathematically tethered to XAU₮. Because the liquidity position is entirely one-sided — consisting only of the newly minted meme token, with no matched XAU₮ — the protocol establishes a hard price floor at genesis.

From there, the mechanics are simple: buyers entering the pool with XAU₮ push the price up along the concentrated liquidity curve. If buying pressure stops, price cannot fall below the bounds set by the gold-backed tick range. The result is a soft peg to the underlying real-world asset — a floor that holds regardless of what the market does above it.

One-Sided Liquidity Mechanics

Traditional AMMs require 50/50 token pairs (e.g., $50k Token + $50k USDC). This is capital inefficient for new launches and exposes liquidity providers to impermanent loss immediately.

Ingot utilizes PancakeSwap V3's concentrated liquidity to solve this. The IngotLPVault mints a position using only the meme token across a specific tick range.

// The vault calculates liquidity required for the one-sided position
uint128 liquidity = tokenIsToken0
    ? LiquidityAmounts.getLiquidityForAmount0(sqrtRatioLower, sqrtRatioUpper, tokenAmount)
    : LiquidityAmounts.getLiquidityForAmount1(sqrtRatioLower, sqrtRatioUpper, tokenAmount);

// Mints the NFT position holding ONLY the meme token
(uint256 tokenId, uint128 mintedLiquidity, , ) = positionManager.mint(params);

When a user buys the token, they swap XAU₮ → Token. The PancakeSwap V3 router pulls XAU₮ from the user, routes it through the pool, and the vault's position gradually converts from "100% Token" to "Token + XAU₮" as the price moves through the tick range.

Fee Distribution & Yield

Liquidity Providers (in this case, the protocol and the creator) earn trading fees from every swap. The IngotLPVault automates the collection and splitting of these fees.

Fees are collected in both XAU₮ and the meme token. Creators can call collectFees() at any time to harvest their yield directly from the PancakeSwap V3 NFT position.

IngotFactory.sol

The entry point for all new launches. It handles deployment fees, clones the IngotToken implementation for gas efficiency, and orchestrates the vault creation.

function createToken(
    string calldata name_,
    string calldata symbol_,
    string calldata website_,
    string calldata telegram_,
    string calldata x_,
    string calldata logoURI_,
    uint256 xautBuyAmount,
    uint256 minCreatorTokensOut
) external payable returns (address token, address vault)

Creator Buy-In: Creators can optionally seed their own launch by providing xautBuyAmount. This executes the first buy, securing a portion of the supply at the absolute floor price while simultaneously bootstrapping the initial XAU₮ liquidity.

IngotLPVault.sol

The core financial engine. Each token gets its own dedicated vault. The vault is the sole owner of the Uniswap V3 NFT position and acts as the router for all primary market buys.

Key Functions

• createOneSidedPosition(): Initializes the pool and mints the concentrated liquidity NFT.
• buy(): Accepts XAU₮, approves the SwapRouter, and executes an exactInputSingle swap.
• collectFees(): Harvests accrued trading fees and distributes them according to the 90/10 split.

IngotToken.sol

A minimal, upgradeable ERC-20 implementation. It includes a TokenMetadata struct to persist social links and branding on-chain, ensuring frontends can always fetch accurate information without relying on centralized databases.

struct TokenMetadata {
    string name;
    string symbol;
    uint8 decimals;
    uint256 totalSupply;
    address owner;
    string website;
    string telegram;
    string x;
    string logoURI;
}

Buying & Swapping

End users interact with the protocol by swapping XAU₮ for the meme token. Because the liquidity is concentrated and one-sided, slippage is highly predictable within the active tick range.

To buy, users simply call the buy() function on the specific token's IngotLPVault contract, specifying the amount of XAU₮ they wish to spend and their minimum acceptable token output (slippage tolerance).

// User approves XAU₮ to the Vault contract first
XAU₮.approve(address(vault), amountIn);

// Execute the swap
vault.buy(
    msg.sender,      // recipient
    amountIn,        // XAU₮ to spend
    minTokensOut     // slippage protection
);

Contract Addresses

Verify every address before interacting with it. These are published here as soon as each contract is deployed and verified on BscScan.