Songbird went live on 16 September 2021 as a separate, working blockchain with its own token, its own validators and its own market price. Nobody bought in. There was no public sale, no venture round and no pre-mine for insiders. The entire starting supply of 15 billion SGB was handed out once, to the same snapshot of XRP holders who had already been promised the Flare distribution, at a fixed ratio of 0.1511 SGB for every 1 XRP held at the 12 December 2020 snapshot. That single distribution detail explains most of the confusion around the ticker, because it means nobody ever paid a launch price for SGB.
Songbird is a canary network, which is not the same thing as a testnet
A testnet usually runs on tokens that cannot be sold, handed out freely from a faucet, and reset whenever something breaks. Songbird was built the other way round. Its token was scarce from block one, it traded on public venues within weeks of launch, and the developers testing the software had real value on the line. That is the whole point of a canary network: you want people to behave as if the money matters, because on this chain it does.
Flare set out the plan in its own launch material. Songbird would carry the Flare Time Series Oracle, the State Connector and the F-Asset systems before those systems were exposed on the main Flare network, so that bugs and bad governance would surface somewhere cheaper to fix.
The trade-off was stated just as plainly. Flare warned that Songbird should not be treated as production ready, that the team made no promise to keep supporting the chain, and that participants should expect a higher chance of lost liveness and lost tokens than on a mainnet deployment. Read that warning twice if you are sizing a position.
Roughly five years on, the network is still running and still holds a market price. Neither fact cancels the warning.
What the chain is actually built on
Songbird runs the Ethereum Virtual Machine, so Solidity contracts port across with the usual tooling, and its consensus is the Flare design: an Avalanche-style protocol adapted to a Federated Byzantine Agreement model, where a set of validators reaches agreement on ledger state by voting rather than by burning electricity. Two pieces of infrastructure do the visible work. The State Connector lets the chain read facts about other networks, so an application on Songbird can respond to something that happened on Bitcoin or XRP without a custodian in the middle. The Flare Time Series Oracle pushes price and time-series data to contracts, with independent providers submitting values that are then weighted and aggregated. Most holders never run a node; they delegate SGB to data providers and validators instead.
F-Assets are the third piece, and the one most likely to matter commercially. The idea is to mint a token on Songbird that is backed by an asset held on another chain, so that a holder can use that value inside smart contracts without selling the original. Because these systems were switched on in stages, the network launched first as a plain EVM chain and only later enabled the oracle, the connector and the asset layer. If you are testing an application here, check which of those stages it depends on, because that determines what happens to your position when the network is upgraded.
SGB itself, by the numbers
The token has three jobs. It pays gas. It carries governance weight, through Songbird improvement proposals that feed into the wider Flare governance process. And it is the asset you delegate to earn a share of oracle and validation rewards.
On supply, the published figures are easy to confuse, so keep them apart.
| Item | Figure | Notes |
|---|---|---|
| Network launch | 16 September 2021 | Live chain with real economic value |
| Snapshot date | 12 December 2020 | Same snapshot used for the FLR distribution |
| Starting supply | 15,000,000,000 SGB | Distributed once, no public sale |
| Airdrop ratio | 0.1511 SGB per 1 XRP | Paid via supporting exchanges or self custody |
| Initial inflation | 10% per year | Paid through oracle and validator rewards |
| Minting pool | Held by the Flare Foundation | No pre-funded reward pool |
Inflation is the part that catches people out. A 10% starting rate means supply was never meant to sit at 15 billion, and on-chain trackers now put total supply a little above 16 billion SGB. The published schedule has been adjusted since 2021, so any emission figure you read in a forum post is probably stale. Check the live total on a block explorer and compare it with whatever number the article you are reading gives you.
Songbird and Flare are not interchangeable
The two networks share technology and people, but they are separate ledgers with separate tokens, separate validators and separate risk profiles. FLR is the asset of the main Flare network. SGB is the asset of the network that tests changes first. The common shorthand compares the pair to Kusama and Polkadot, which is fair as far as it goes: the earlier network ships riskier features sooner, and pays for that with higher variance.
What matters for a holder is that the upgrade path runs one way. Features land on Songbird first, get stressed, break, get fixed, and then arrive on Flare. That makes SGB a leading indicator of the Flare roadmap, and it makes Songbird the place where a poor governance decision becomes visible first.
The risk here is structural, not just price
Three things sit on top of ordinary crypto price risk. First, the network is explicitly experimental, so a contract bug or a failed upgrade is part of the environment rather than a freak event. Second, support for the chain has always been discretionary, and the original documentation said as much. Third, liquidity is thin: SGB lists on a short list of centralised venues plus Songbird-native decentralised exchanges, so a position that looks comfortable on a chart can be hard to exit at the quoted price. Published price history shows the token trading near $0.30 in late 2021 and below $0.01 for much of 2022, which is what a small, speculative market looks like over time. None of this makes SGB fraudulent. It makes it an infrastructure bet with an unusually visible failure mode.
A verification routine you can run before buying
Most SGB losses come from sending the wrong asset to the wrong address rather than from the token itself. Songbird uses its own chain identifier, and an address that looks correct can belong to a different EVM network.
Open the official Flare documentation and confirm you are on the Songbird network before you copy any address. Verify the contract address on a block explorer rather than trusting a link from a chat group. Confirm that the venue you are buying on lists SGB and not a token that merely shares the ticker. If you plan to delegate, review the validator or data provider you are choosing, including uptime and fee, because delegation hands over voting weight along with tokens. And never send SGB to a Flare or Ethereum address on the assumption that the formats are interchangeable, because they are not.
One more habit is worth building. Before you buy any canary-network token, write down in one sentence what would have to happen for the project to keep supporting it. If you cannot answer that, you are holding a price chart rather than a position.
Our search of Flare's published material did not turn up a commitment to fund Songbird indefinitely, and no regulator supervises SGB as a security or a deposit. Treat the chain as it was described on day one.
This article is general information, not investment advice. Token supply, inflation and support commitments change; verify current figures on the Flare documentation and a live block explorer before acting.