- Songbird (SGB) research overview
- Historical market behavior
- YearBull metric interpretation
- Market structure and supply
- Key risks and limits
- Primary sources and review scope
- Songbird (SGB): Flare’s Live Protocol Testing Network
- A production-like network for protocol testing
- What SGB does inside the network
- FTSO and the data layer
- Governance and upgrade control
- Applications, FAssets, and practical dependencies
- How to assess Songbird’s role
- Key takeaways
- Risks and open questions
- YearBull Rank context
Songbird (SGB) research overview
Songbird (SGB) is tracked by YearBull under the source identifier songbird. Source categories place the asset in the Layer 1 Cryptocurrencies universe, with additional labels including Smart Contract Platform. Category labels describe market context; they do not prove project activity, adoption, or investment quality.
Market structure and supply
Observed market capitalization is about $18.09 million and reported 24 hour volume is about $77.6 thousand. That volume equals 0.43% of market capitalization in the dated snapshot. Current circulating supply is 18,618,739,705. Recorded total supply is 19,498,963,150. Circulating supply changed +15.5% across the available historical window. Reported volume and supply fields can change through source revisions, issuance, burns, migrations, or venue coverage.
Key risks and limits
Validator or miner concentration, client faults, network outages, token issuance, ecosystem activity, bridges, and governance are material dependencies. High YearBull Risk appeared on 2.8% of stored observations. Historical metrics describe the available YearBull record; they do not predict future returns. Contract addresses, network support, custody, and venue availability should be verified before use.
Primary sources and review scope
YearBull methodology | Official project website. Identity, categories, supply, and historical market fields were reviewed from locally stored source records on 2026-09-12. The live analytical snapshot may be newer than this editorial review.
Songbird (SGB): Flare’s Live Protocol Testing Network
Songbird is an EVM-compatible canary network where Flare tests protocol upgrades, data systems, governance processes, and decentralised applications under real economic conditions. SGB pays transaction fees and supports delegation, voting, and participation in the network’s data infrastructure.
A production-like network for protocol testing
Songbird is not positioned as a conventional testnet. Flare’s developer documentation describes it as an experimental canary network for protocol upgrades, with real transactions and SGB fees. The documented development path is Songbird Testnet Coston, then Songbird, followed by Flare Testnet Coston2 and Flare Mainnet. This gives protocol changes a live environment in which to be tested before they are considered for Flare’s production network.
The network is EVM-compatible and uses chain ID 19. SGB is its native currency with 18 decimal places, and the official documentation lists a public RPC endpoint and Songbird block explorer. Developers therefore interact with Songbird through familiar Ethereum-style tooling, while still needing to confirm that contracts, wallets, bridges, and applications specifically support the Songbird network.
What SGB does inside the network
SGB has a direct operational role because it pays transaction fees on Songbird. It can also be wrapped into WSGB for governance and related smart-contract functions. The Flare Portal supports management of SGB and FLR, including wrapping, delegation to FTSO data providers, and governance participation.
For data-provider infrastructure, native SGB is used to fund registered service-provider addresses for gas, while wrapped native tokens contribute to voting power and delegation. This means SGB’s network utility is broader than paying for transfers: it is connected to the systems that produce protocol data and administer network functions. Participation still depends on the relevant contracts, provider rules, and the user’s ability to operate compatible wallet infrastructure correctly.
FTSO and the data layer
A central Flare mechanism is the Flare Time Series Oracle, or FTSO. Flare describes FTSO as an enshrined oracle that supplies decentralised data feeds to applications. Data providers submit and sign information, while voting power is influenced by validator stake and delegations of wrapped native tokens. The official FTSOv2 documentation describes block-latency feeds, support for multiple asset classes, and a provider set targeted at roughly 100 participants.
Songbird is also connected to Flare’s data-availability services and FTSO contracts. Developers can query Songbird data through the documented Songbird data-availability endpoint, while official contract references identify deployed protocol contracts such as FTSOv2. Flare recommends resolving protocol addresses through its contract registry rather than relying on hard-coded or unofficial addresses, which is a practical dependency for application developers and infrastructure operators.
Governance and upgrade control
Songbird governance is divided into Songbird Test Proposals and Songbird Improvement Proposals. STPs are intended to test potential changes before they may be proposed for Flare, while SIPs concern changes specific to Songbird. Both use WSGB for voting. STPs use a rejection-based model: a proposal is rejected only if participation reaches the stated quorum threshold and more than half of participating votes oppose it. SIPs use an acceptance-based majority vote without a quorum requirement, according to the current developer documentation.
The process is not equivalent to unrestricted permissionless proposal creation. The documentation identifies the Flare Foundation as the initiator for these proposal types, while voting takes place through the Flare Portal after an announcement and notice period. Some accepted changes may execute through smart contracts, but proposals requiring coordination or offchain action may depend on the Flare Foundation. This creates a governance model with token-holder voting but meaningful institutional involvement in agenda-setting and execution.
Applications, FAssets, and practical dependencies
Songbird can host decentralised applications and is used to test Flare-related systems, including FAssets components. Flare’s FAsset specifications describe Flare or Songbird as the native chain and FLR or SGB as the native currency. The design uses collateral, price data, and information about activity on connected chains, so applications in this area depend on more than the base chain: they also rely on oracle inputs, attestation systems, collateral rules, and the connected underlying networks.
The existence of a security assessment should not be read as a guarantee that every deployment or integration is safe. The published FAssets assessment covers a defined review scope, while Songbird itself remains an experimental network by design. Users and developers must distinguish the security of a particular contract, the reliability of a data provider, the operation of the base chain, and the solvency or behaviour of any connected bridge, agent, exchange, or application.
How to assess Songbird’s role
Songbird is best understood as a live proving ground and parallel smart-contract network rather than simply a preliminary version of Flare. Its value to users depends on whether protocols, data systems, governance changes, and applications are actually deployed and maintained there. The network’s architecture gives developers a place to expose changes to real transactions and incentives, but that same exposure means failures, parameter changes, provider concentration, and application-specific exploits can have real consequences.
Key takeaways
- Songbird is Flare’s live canary network for testing protocol-level changes and applications.
- SGB pays transaction fees and can be wrapped for governance and data-provider delegation.
- FTSO and related data services are core parts of the network’s intended architecture.
- Songbird governance uses STPs and SIPs, with WSGB voting and a continuing Flare Foundation role in proposal initiation and execution.
- Developers must verify network-specific contracts, RPCs, data endpoints, providers, and application dependencies before relying on Songbird.
- FAssets and other applications add risks from collateral, attestations, oracles, bridges, and connected chains.
Risks and open questions
- Songbird’s experimental role means protocol changes, parameters, and application deployments may change over time.
- Governance is token-weighted and the Flare Foundation initiates the documented STP and SIP proposal processes; practical control is therefore not equivalent to fully permissionless governance.
- FTSO accuracy and resilience depend on data providers, delegated voting power, provider incentives, and protocol parameters.
- Applications using FAssets or connected-chain data inherit dependencies on collateral, attestations, oracle inputs, and external networks.
- Security reviews cover defined scopes and dates; they do not establish that the entire Songbird ecosystem or every deployed contract is secure.
- Wallet, custody, bridge, exchange, and contract support may differ between Songbird and Flare Mainnet.
YearBull Rank context
Most recent YearBull Rank reading for songbird is #6652.
Rank movement (nearest daily data).
Reading rule: smaller rank numbers are better.
- 7d window (2026-09-22): #8384 → #6652 (up by 1732).
- 30d window (2026-08-30): #4339 → #6652 (down by 2313).
Regime context: If both windows align, the direction is clearer. cycle shifts often show up as slope changes, not spikes.
Listing context: If the line is step-like, watch for discrete market changes. changes can follow how the coin is routed across markets.
Liquidity angle: If the line only moves on high-volume days, liquidity is a key filter. relative rank is sensitive to who is active in the window.
Volatility posture: If the curve is step-like, it may be reacting to discrete inputs. range behavior tells more than a single point.
Practical note: read the move, then read the stability of the move.
YearBull Rank is a relative ranking on YearBull designed to compare coins on a common scale and time window. A smaller rank number indicates a stronger position at that moment.
