Layer 1 blockchain
Osmosis ticker OSMO
Summary
Sovereign proof-of-stake chain (osmosis-1) running the Osmosis exchange application on the Cosmos SDK with CometBFT consensus. OSMO holders delegate to validators; governance capped the active set at 70 in May 2026, after earlier cuts to 120 in February 2025 and 100 in September 2025. Unbonding takes 14 days and double-signing is slashed. Superfluid staking, which once let approved liquidity-pool shares count toward stake, was switched off for all pools by proposal 956 in July 2025, and no pool was eligible on 2026-09-27. A block commits once validators holding more than 2/3 of voting power precommit it, assuming less than 1/3 is byzantine. On 2026-09-27 the six largest validators held more than a third of bonded stake. Osmosis is secured by its own validator set, not by Cosmos Hub stake. 710121417202122
Design
- System
- Layer 1 blockchainOsmosis is a sovereign Cosmos SDK application chain (chain ID osmosis-1) with its own OSMO-staked validator set. In April 2026 Osmosis governance approved redeploying its exchange onto the Cosmos Hub, but the matching Cosmos Hub vote was rejected and the proposal required both to pass, so Osmosis still runs as its own chain.
- Settlement family
- Cosmos SDK
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- Validators selected round-robin in proportion to voting power, per the CometBFT consensus specification. Voting power comes from OSMO delegated to each validator; the pool-share staking route was switched off for all pools in July 2025.
- Fork choice
- No fork choice in the Nakamoto sense: a height is decided by +2/3 precommits. Two conflicting commits would require at least 1/3 of voting power to double-sign, which is attributable and slashable. If more than 1/3 of voting power is offline the chain stops producing blocks instead of forking.
Qualifications
- Ibc · Applies. IBC is messaging between independently governed chains, checked by on-chain light clients of each counterparty. It is how most assets reach Osmosis, but connected chains are not Osmosis layer 2s. It is recorded in the bridge row of this profile.
- Shared security · Not applicable. Osmosis is secured by its own bonded validator set staked in OSMO (70 bonded validators in a live query on 2026-09-27). It does not borrow Cosmos Hub security. Governance approved becoming a Babylon Bitcoin-secured network in April 2025 (proposal 919), but no later upgrade enabling it was found.
- Migration into cosmos hub · Not applicable. Osmosis proposal 1007 (passed 2026-04-14) would have redeployed the exchange onto the Cosmos Hub and offered an optional OSMO-to-ATOM conversion, but only if both chains approved. Cosmos Hub proposal 1029 was rejected on 2026-04-16, and no later Hub proposal on the merger appeared through proposal 1057.
- Tps · Unknown. No sourced, classed throughput measurement for Osmosis was found. Two blocks sampled on 2026-09-27, 1,000 heights apart, were about 1.3 seconds apart on average; that is a block interval, not a capacity figure.
Tradeoffs
- Emphasizes
- Security and Scalability
- Gives up
- Breadth of participation. Block production is limited to a capped set of 70 validators, and governance shrank the set partly to get faster, more reliable blocks. On 2026-09-27 six validators together held more than a third of bonded stake, enough to halt the chain. Nodes need 32 to 64 GB of memory. Osmosis halts rather than forks if more than a third of voting power is unavailable.Scalability here means short block intervals for one exchange-focused chain, not a sourced throughput figure. Security means the chain's own OSMO stake plus attributable slashing; it is not borrowed from the Cosmos Hub. A 2025 plan to add Bitcoin timestamping through Babylon was approved by governance but was not confirmed live in this review.
- Full node at home
- Demanding 356The Osmosis docs give 32 GB of RAM as the minimum recommendation for a mainnet node and 64 GB for a validator; the repository README lists a quad-core CPU, 64 GB RAM, 1 TB NVMe storage and a 100 Mbps connection. Storage is modest with pruning: official pruned snapshots were about 28 GB on 2026-09-27, against about 24 TB for an archive snapshot. Memory is the main barrier for typical home machines.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | Not yet assessed under the current definitions; no hash-time-locked or other cross-party swap mechanism was verified. Swaps against Osmosis pools settle all-or-nothing in one Osmosis transaction but trade against a pool, not between two parties. The limit-order book, whose trades also settle in one transaction, is a contract venue (a CosmWasm pool) recorded in the amm-or-cfmm row; its cited page names no publisher and shows no dated mainnet release, so no swap tool is shown live. IBC hooks can run a swap when a transfer arrives, which is a contract action. IBC token transfers are not swaps. 2829 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Built into the protocolLimited scope | CometBFT consensus produces the validator-signed commits that IBC light clients check. IBC connections rely on on-chain light clients that verify the counterparty chain's consensus; relayers carry packets but do not replace verification. Limit: clients expire if not updated in time, and Osmosis governance regularly votes to recover expired clients. 8914 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to Osmosis was reviewed. IBC channels are messaging paths, not payment channels. 8 |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Osmosis runs CosmWasm contracts and smart-account authenticators (signature checks, message filters, all-of and any-of composites, and contract-defined policies). On-chain parameters read 2026-09-27 let anyone instantiate contracts but restrict code upload to a governance-approved list of addresses. 4132627 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; the smart-account module lets an account add extra keys, message filters or contract-defined authenticators, and the docs present key rotation and recovery from a lost device as uses, but say the module provides these only as composable building blocks. No recovery role or delay defined for recovery, and no way to cancel or reclaim a sent payment, was found. The module is opt-in, and designated controllers can switch it off. 2526 |
| Rollups | Unknown | The review did not verify absence, so the rule that absence needs a source makes this unknown rather than not present. Earlier finding: no rollup settling to Osmosis was found in reviewed sources. IBC-connected chains are separate sovereign chains, not rollups. 9 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Native to the protocolOsmosis weighted pools, Osmosis stableswap pools, Osmosis concentrated liquidity pools, Osmosis order book (CosmWasm pools) | The exchange is built into the chain: pool management, weighted, stableswap and concentrated-liquidity pools are chain modules, and CosmWasm pools add contract-based venues such as the limit-order book. A single swap can route across pool types. A separate taker fee (default 0.1%) funds OSMO burns, staking rewards and the community pool. 12328 |
| Issuer-native stablecoins | None found | Circle's USDC list includes Noble and Injective, not Osmosis. USDC on Osmosis arrives as IBC or bridge representations. Since late August 2026 governance treats Alloyed USDC as the canonical USDC on Osmosis (proposal 1039, followed in September by proposal 1042 moving protocol-held USDC into it). It is an Osmosis wrapper exchangeable 1:1 for USDC.noble, USDC.inj or USDC.eth.axl, not issuer-native USDC. 1823313435 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins currently trading on Osmosis were not reviewed. |
| Bridges | Native to the protocolIBC, IBC Eureka (via the Cosmos Hub), Axelar, Wormhole Gateway, Nomic (nBTC), Skip:Go routing | IBC connects Osmosis to other IBC chains through light clients. The asset-listing docs name Axelar as a canonical bridge for Ethereum and other major networks (proposal 206), plus Wormhole, Nomic, Squid and Skip:Go routes; the frontend routes through Skip:Go. Governance also recognizes Wormhole and Eureka, an IBC-based route to Ethereum through the Cosmos Hub (proposal 928), as canonical bridges. In February 2025 Wormhole said it would stop hosting Osmosis transfers in its Portal and stop subsidizing Gateway IBC relaying. Alloyed assets pool bridged versions of one asset behind a 1:1 wrapper. Risk: Each bridged asset is only as sound as its bridge. On 25 June 2026 the Nomic bridge minted about 40.65 BTC of unbacked nBTC on Osmosis, undisclosed for 74 days, pulling allBTC backing to about 64%. An emergency upgrade on 7 September froze the attacker's allBTC; allBTC deposits and withdrawals stay suspended until the nBTC is removed. A recovery plan passed on 20 September (proposal 1044), but part of it needs an upgrade not yet shipped. Expired IBC clients freeze routes until governance recovers them; rate limits only cap abnormal flows. 919242930313233 |
| Block explorers | Established in the ecosystemMintscan, Celatone, Ping.pub, ATOMScan, Explorers.guru | The chain registry lists 15 explorers for osmosis-1, including Mintscan, Ping.pub, ATOMScan and Explorers.guru; Celatone runs an Osmosis explorer that covers contracts. Listing is not a quality or completeness check; explorer data is provider-indexed. 43637 |
| Hardware wallets | Established in the ecosystemLedger | See the custody rows: Ledger's Osmosis page points users to its own Ledger Wallet app for managing and staking OSMO; Trezor Suite does not support Osmosis accounts. 3839 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Yes | Can: Send and receive OSMO in the Ledger Wallet app Can: Stake OSMO from the Ledger Wallet appLedger's Osmosis page tells users to manage and stake their Osmosis with the Ledger Wallet app; its list of actions (send, receive, swap, stake) is general page wording rather than an OSMO-specific compatibility table. It does not describe providing liquidity or using Osmosis pools from Ledger Wallet; those actions normally go through a separate Osmosis-capable wallet connected to the device, which was not verified here. 38 |
| Trezor | None foundSame as native: No | Cannot: Manage osmosis-1 accounts in Trezor Suite Cannot: Treat OSMO representations on other networks as Osmosis custodyTrezor's page says Osmosis is not supported in Trezor Suite and lists OSMO only on Evmos through MetaMask or Rabby; third-party signing paths for native Osmosis accounts were not exhaustively checked. 39 |
Public data
iKnow Blockchain has no public-data lookups for Osmosis yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Governance approved a recovery plan after unbacked nBTC impaired allBTC
According to proposal 1044, the Nomic bridge minted about 40.65 BTC of nBTC on Osmosis on 25 June 2026 with no Bitcoin behind it. The mint went undisclosed for 74 days, until Nomic halted on 7 September. It cut allBTC backing to about 64%. The same day validators ran an emergency upgrade that froze the attacker's 22.65 allBTC; allBTC deposits and withdrawals stay suspended until the nBTC is removed. The passed proposal funds a recovery from community-pool assets, a redirected liquidity plan and the attacker's frozen allBTC, and marks nBTC for removal.
- Proposal:proposal 1044 passed
- Implementation:community-pool steps approved; the asset-reclaim upgrade was still pending
- Release:recovery upgrade not yet released as of review
- Activation:partially active
Sources: Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 1044: Alloyed BTC: Restore backing after the nBTC incident (on-chain record) (external site) · Osmosis Community Hall — Alloyed BTC: Restore backing after the nBTC incident (forum draft) (external site)
-
Osmosis cut its active validator set to 70
Governance proposal 1017 lowered the maximum number of active validators from 100 to 70, removing the lowest-staked validators. The proposal cited more efficient network communication, lower hardware demands and faster block production. It follows earlier cuts to 120 in February 2025 and 100 in September 2025.
- Proposal:proposal 1017 passed
- Implementation:parameter change
- Release:no software release needed
- Activation:active; cap of 70 observed on 2026-09-27
Sources: Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 1017: Reduce Validator Set to 70 (on-chain record) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis staking module parameters (on-chain query) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis bonded validator count (on-chain query) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis governance proposals, newest 200 (on-chain query) (external site)
-
Osmosis v31.0.3 updated CometBFT to v0.38.23 with vote, sync and light-client fixes
Osmosis v31.0.3 was released on 14 May 2026 and was still the newest tagged Osmosis release on 27 September 2026. Its notes list only a CometBFT update, and the dependency file at that tag pins CometBFT v0.38.23. The CometBFT v0.38.23 notes, published 8 May 2026, fix the handling of empty (nil) votes, stop a peer from feeding a syncing node a false maximum height, correct when the light client stops comparing witnesses and remove a crash path in the ABCI socket server's error recovery.
- Implementation:CometBFT v0.38.23 included in Osmosis v31.0.3
- Release:released 2026-05-14
- Activation:takes effect on each node when its operator installs it; how many validators run it was not checked
Sources: Osmosis maintainers — Osmosis v31.0.3 release (external site) · Osmosis maintainers — Osmosis v31.0.3 go.mod (external site) · CometBFT maintainers — CometBFT v0.38.23 release (external site) · Osmosis maintainers — Release notes from osmosis (Atom feed) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 1044: Alloyed BTC: Restore backing after the nBTC incident (on-chain record) (external site)
-
Osmosis v31.0.2 updated CometBFT to v0.38.22 with stricter sync and evidence checks
Osmosis v31.0.2 was released on 22 April 2026. Its notes list one change, an update of the bundled CometBFT consensus engine to its latest version, and the dependency file at that tag pins CometBFT v0.38.22. The CometBFT v0.38.22 notes, published 10 April 2026, add checks on reported validator-misbehaviour evidence and make a node fully verify block commits while it catches up through block sync. Neither set of notes ties these changes to a security advisory.
- Implementation:CometBFT v0.38.22 included in Osmosis v31.0.2
- Release:released 2026-04-22
- Activation:takes effect on each node when its operator installs it; how many validators run it was not checked
Sources: Osmosis maintainers — Osmosis v31.0.2 release (external site) · Osmosis maintainers — Osmosis v31.0.2 go.mod (external site) · CometBFT maintainers — CometBFT v0.38.22 release (external site)
-
Osmosis approved, and the Cosmos Hub rejected, a plan to move Osmosis onto the Hub
Osmosis proposal 1007 passed on 14 April 2026. It proposed redeploying the Osmosis exchange onto the Cosmos Hub, ending OSMO inflation and offering a one-year optional OSMO-to-ATOM conversion. The matching Cosmos Hub proposal 1029 was rejected on 16 April 2026. The plan stated nothing would be implemented unless both chains approved.
- Proposal:passed on Osmosis; rejected on the Cosmos Hub
- Implementation:not implemented
- Release:no release
- Activation:not active
Sources: Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 1007: Integration and Migration of Osmosis into the Cosmos Hub (on-chain record) (external site) · Cosmos Hub on-chain state via PublicNode REST endpoint — Cosmos Hub proposal 1029: Acquisition and Merger of Osmosis into the Cosmos Hub (on-chain record) (external site) · Cosmos Hub on-chain state via PublicNode REST endpoint — Cosmos Hub governance proposals, newest 80 (on-chain query) (external site)
-
Osmosis v31.0.1 moved to the CometBFT version that fixes the Tachyon block-time flaw
Osmosis v31.0.1 was released on 27 January 2026. Its only listed change moves the node software to CometBFT v0.38.21. Four days earlier CometBFT published advisory CSA-2026-001, known as Tachyon and rated critical. The advisory says a mismatch between how commit signatures are checked and how block time is calculated let faulty validators push block timestamps forward. It lists CometBFT v0.38.20 and earlier as affected, names v0.38.21 as the patched v0.38 version and says upgrading is the only fix.
- Implementation:CometBFT v0.38.21 included in Osmosis v31.0.1
- Release:released 2026-01-27
- Activation:takes effect on each node when its operator installs it; how many validators run it was not checked
Sources: Osmosis maintainers — Osmosis v31.0.1 release (external site) · CometBFT maintainers — CSA-2026-001: Tachyon (GHSA-c32p-wcqj-j677) (external site) · Osmosis maintainers — Osmosis v31.0.0 go.mod (external site) · Cosmos chain-registry maintainers — Osmosis chain registry record (external site)
-
Osmosis v31 approved: automatic OSMO burns and a higher minimum gas price
Governance proposal 990 passed and scheduled the v31 upgrade at height 47,626,000. The release automates burning of the burn share of taker-fee OSMO, applies the same burn and staker split to OSMO bought back with other tokens, spreads staker payouts from taker fees over several epochs, adds an inflation endpoint and triples the consensus minimum gas price to 0.03 uosmo per unit of gas.
- Proposal:proposal 990 passed
- Implementation:released as v31.0.0, with patch releases through v31.0.3
- Release:released 2025-10-27
- Activation:applied at height 47,626,000 per on-chain upgrade record
Sources: Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 990: Osmosis v31 Software Upgrade (on-chain record) (external site) · Osmosis maintainers — Osmosis v31.0.0 release (external site) · Osmosis maintainers — Osmosis changelog (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Applied upgrade plan v31 (on-chain query) (external site)
-
Osmosis switched off superfluid staking for all pools
Governance proposal 956 removed every liquidity pool from superfluid staking, the feature that let pool shares count toward chain security, and approved removing the module in a later upgrade. The proposal said only about 39,000 OSMO was staked this way. Positions using it were unbonded when the change took effect.
- Proposal:proposal 956 passed
- Implementation:all pools removed by parameter change; full removal of the module was left to a later upgrade and was not confirmed
- Release:no software release needed for the pool removal
- Activation:active; no eligible pools on 2026-09-27
Sources: Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 956: Remove Superfluid Staking and Deprecate the x/superfluid Module (on-chain record) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis superfluid-eligible assets (on-chain query) (external site) · Osmosis documentation — Superfluid module (external site)
Topics your AI can explain
Your AI can explain these topics for Osmosis through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Validator cap, bonded count, unbonding and slashing values are on-chain parameters read on 2026-09-27; governance has changed the validator cap three times since early 2025 and can change them again.
- Whether the Babylon Bitcoin timestamping plan approved in April 2025 was ever activated was not confirmed; no later upgrade or proposal enabling it was found.
- The Osmosis-into-Cosmos-Hub merger failed on the Hub side in April 2026; a future resubmission on either chain would change this profile.
- The nBTC loss figures come from the Osmosis recovery proposal; Nomic's own homepage showed no incident notice when checked, and a Nomic post-mortem was not found. The follow-up upgrade to reclaim the attacker's frozen allBTC was still pending.
- The emergency upgrade of 7 September 2026 is named v31.1.0 in the recovery proposal, but it was not among the tagged releases in the public repository when checked; the node software version could not be confirmed from the public endpoint.
- The Osmosis documentation page for the superfluid module still describes pool-share staking as active, although governance switched it off for all pools in July 2025 and the on-chain list of eligible assets was empty on 2026-09-27. Whether the module has been fully removed from the software was not confirmed.
- The stake concentration figure (six validators holding more than a third of bonded stake) comes from one live query on 2026-09-27 and moves with delegations.
- Axelar's 2026 roadmap says it will cut some underused connections; whether the Axelar route to Osmosis is affected was not verified.
- Current relaying and frontend coverage for Wormhole Gateway assets on Osmosis after Wormhole ended subsidized relaying was not verified.
- No trust-minimized cross-party swap mechanism, channel layer or algorithmic stablecoin on Osmosis was reviewed.
- Who controls the addresses allowed to upload CosmWasm code, and who the smart-account circuit-breaker controllers are, was not reviewed.
- No sourced, classed throughput measurement was found; the block interval comes from only two sampled blocks.
- Third-party Trezor signing paths for native Osmosis accounts, and liquidity or swap actions through Ledger, were not exhaustively checked.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Osmosis overview (external site)
- OSMO token (external site)
- osmosis-labs/osmosis repository (external site)
- Osmosis chain registry record (external site)
- Joining Mainnet (external site)
- Osmosis chain snapshots (external site)
- Byzantine Consensus Algorithm (external site)
- IBC overview (external site)
- IBC on Osmosis (external site)
- Osmosis staking module parameters (on-chain query) (external site)
- Osmosis bonded validator count (on-chain query) (external site)
- Osmosis slashing module parameters (on-chain query) (external site)
- Osmosis CosmWasm code upload and instantiate parameters (on-chain query) (external site)
- Osmosis governance proposals, newest 200 (on-chain query) (external site)
- Osmosis proposal 1007: Integration and Migration of Osmosis into the Cosmos Hub (on-chain record) (external site)
- Cosmos Hub proposal 1029: Acquisition and Merger of Osmosis into the Cosmos Hub (on-chain record) (external site)
- Osmosis proposal 1017: Reduce Validator Set to 70 (on-chain record) (external site)
- Osmosis proposal 1042: Migrate Protocol USDC to Alloyed USDC (on-chain record) (external site)
- Osmosis proposal 1044: Alloyed BTC: Restore backing after the nBTC incident (on-chain record) (external site)
- Osmosis proposal 956: Remove Superfluid Staking and Deprecate the x/superfluid Module (on-chain record) (external site)
- Osmosis superfluid-eligible assets (on-chain query, empty list) (external site)
- Osmosis bonded validators with stake (on-chain query) (external site)
- Osmosis proposal 1039: Migration of Parameters and Usage from Noble USDC to Alloyed USDC (on-chain record) (external site)
- Osmosis proposal 928: Add Eureka as a Canonical Bridge Service Provider (on-chain record) (external site)
- Smart accounts (external site)
- Smart account module (external site)
- CosmWasm on Osmosis (external site)
- Orderbook (external site)
- Cross-chain swaps (external site)
- Listing an asset: transfer methods (external site)
- Alloyed assets (external site)
- IBC rate limit (external site)
- Updates to Wormhole's supported networks (external site)
- USDC contract addresses (external site)
- CCTP supported blockchains (external site)
- Mintscan Osmosis explorer (external site)
- Osmosis Explorer (Celatone) (external site)
- Osmosis wallet (external site)
- Osmosis wallet (external site)
- Osmosis to Become a Bitcoin Secured Network (BSN) via Integration with Babylon Genesis (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding