Plan a useful feed
Decide what your feed should price and which application could use it.
A few words first: a token's mint is its address on Solana. The quote is the currency the price is shown in, such as USDC (a dollar stablecoin) or SOL. Pools are the places where the token is traded; their liquidity is how much is in them. A composite is a feed made by adding other feeds together.
For example: “My application needs a reference for this token,” or “I want one price for this specific combination of assets.”
Choose the definition
- Identify the asset. Use its Solana mint, not just a name or ticker.
- Choose the quote. Is the price expressed in USDC, SOL, or another supported quote?
- Check the sources. The relevant pools must be supported and admitted, with suitable liquidity.
- For a composite, choose quantities and conversions. Components can start in different quotes. Include the conversion feeds Mimir needs to express them in the composite's quote, such as SOL/USDC for an input priced in SOL.
For a composite, write down the exact tokens, quantities and quote. A name such as “AI Chips” describes the idea; the composition defines the price.
Give it a unique ticker
Your feed gets a short, unique ticker so people can recognize it quickly in the Mimir app. For a feed named AI Chips, you might choose CHIPS, if it is available.
Choose 2 to 12 letters or digits. Letters are converted to uppercase, and Source and Composite Feeds share the same ticker namespace. A ticker already assigned to another feed cannot be reused within the same Mimir deployment. Shorter tickers carry a higher ticker fee, and one-character tickers are reserved. See the ticker fees →
The ticker identifies your feed, not a token. It does not have to match an underlying asset's symbol, and it does not replace the mint addresses or composition that define the feed.
Plan how it stays useful
Which application needs this reference? It can refresh the feed and consume the result in the same transaction, without relying on a keeper to update it continuously. A Source Feed refresh pays only the Solana network fee; a composite refresh that records a new price also pays a refresh fee. Plan who covers these fees and what source quality the application requires.
Applications select feeds according to their source coverage, liquidity, freshness and risk policy. Designing for a clear use case helps your feed meet those needs.
Understand the costs
You pay creation in SOL. The app buys the ticker fee in $COLA with your SOL and the program permanently burns it; account rent and network fees come on top. A composite also pays the feeds it uses, and its paid updates use SOL. Review the amounts before signing.
Feed activity and fees depend on how applications and other feeds use it. Read fees and claims →
Before you confirm
Check the mint, quote, sources and component quantities carefully. Finalized source bindings are immutable, and a feed cannot be closed; a different definition requires a new feed.
Step by step: Create a feed in the app →