Layer 1 blockchain
Initia ticker INIT
Summary
Proof-of-stake chain (interwoven-1) built on Initia forks of the Cosmos SDK and CometBFT, running a Move virtual machine and acting as the hub for application rollups. Validators are bonded with INIT and, under Enshrined Liquidity, with a governance-whitelisted USDC-INIT pool token that the chain counts at its own weight. Governance cut the active-set cap from 50 to 20 in November 2025; a live query on 2026-09-27 found only 10 validators in the consensus set, the largest with about 21% of voting power and the top two with about 35%. A block commits once validators holding more than 2/3 of voting power precommit it. Validators must also run the Connect oracle sidecar. Unbonding takes 21 days and double-signing is slashed 5%. Initia is secured by its own stake, not by Cosmos Hub stake. 915182021222933
Design
- System
- Layer 1 blockchainInitia L1 (chain ID interwoven-1) is a sovereign proof-of-stake chain with its own validator set, blocks and BFT commit, so it is a layer 1. It also acts as the settlement and bridging hub for application rollups built with Initia's OPinit framework; those rollups are the layer 2s. Initia L1 does not borrow Cosmos Hub security.
- Settlement family
- Cosmos SDK
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- Validators chosen round-robin in proportion to voting power, per the CometBFT consensus specification; voting power combines bonded INIT and the whitelisted pool token. Rollup blocks are produced separately by each rollup's own operator, not by Initia L1 validators.
- Fork choice
- No Nakamoto-style fork choice: a height is final once more than 2/3 of voting power precommits. Conflicting commits would need 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 instead of forking; in the 2026-09-27 set the two largest validators together held more than 1/3.
Qualifications
- Ibc · Applies. IBC links Initia L1 to other chains such as Noble, Osmosis and Celestia, checked by on-chain light clients. Those chains are not Initia rollups. Rollups can also use IBC to move funds to and from the L1. Recorded in the bridge row.
- Shared security · Not applicable. Initia L1 is secured by its own validator set bonding INIT and a whitelisted pool token. It is not a Cosmos Hub consumer chain. Rollups rely on the L1 for bridging and dispute handling, but the L1 does not borrow security from another chain.
- Rollup bridge security · Contested. The Reactor upgrade (December 2025) described attested IBC, where subsets of L1 validators would attest to rollup blocks to secure withdrawals, with their signatures collected after the sequencer's. On 2026-09-27 every one of the 47 bridge records had an empty attester set, and the IBC clients checked for migrated rollups tracked a rollup chain with a single validator. Whether attestations protect any live route was not confirmed.
- Bridge escrow governance · Applies. In September 2026 governance moved leftover INIT out of the bridge escrow accounts of six shut-down rollups to a team-controlled address; the proposal says users had already been repaid by airdrop, which was not independently checked. Bridge escrow on Initia L1 is therefore within reach of L1 governance.
- Block interval · Applies. About 2.24 seconds on average over 100,000 L1 blocks ending at height 22,355,842 on 2026-09-27. The Reactor upgrade's 100-millisecond figure refers to rollup blocks, not to the L1.
- Tps · Unknown. No sourced, classed throughput measurement for Initia L1 or its rollups was found. The block interval above is a sample, not a capacity figure.
Tradeoffs
- Emphasizes
- Scalability
- Gives up
- Breadth of consensus participation and trust minimization. Only 10 validators were active in a 2026-09-27 query under a governance cap of 20. Each rollup is run by one operator, rollup disputes are settled by a designated challenger and Initia governance rather than by an automatic on-chain proof, and rollups whose bridges moved to IBC rely on that operator's signature.Scalability here means spreading applications across many rollups, not raising L1 capacity; no classed throughput figure was found. The L1's BFT commit gives fast, final settlement, but security is not listed as an emphasis because rollup safety depends on named operators, challengers and governance, and stake is concentrated in a small set.
- Full node at home
- Practical at home 2810The L1 node guide lists a minimum of 4 cores, 8 GB of RAM, a 2 TB NVMe or SSD with write throughput above 1,000 MiB/s and 100 Mbps (16 GB of RAM recommended), and supports state sync. Storage size and the write-speed requirement are the main hurdles for a home machine. Checking a rollup independently needs that rollup's own node and its data availability source, usually Celestia.
- Throughput claims
- No classified figure recorded
Scaling layers
- Interwoven Rollups (OPinit framework) · Rollup, mainnet 24132326283034
Each rollup has one operator (four sampled rollups each had a single validator on 2026-09-27) posting output roots to Initia L1 and transaction batches to Celestia or Initia; since the Reactor release (v1.2.2) rollup blocks advance on one sequencer's signature. Optimistic-bridge withdrawals wait a per-bridge finalization period (1 hour to 7 days across 47 bridges). One designated challenger per bridge can delete a bad output and governance decides disputes. Since January 2026 governance has moved several rollups' bridges to IBC, which removes the wait but trusts the operator's signature.
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 on Initia L1 was reviewed. InitiaDEX and Minitswap swaps settle inside one transaction against pools, and bridge routing through Skip Go is a routed transfer; neither is a swap between two parties. 57 |
| Authenticated data publication | Unknown | Not yet assessed under the current definitions; no L1 feature for publishing data against a chain-recorded commitment was established. Rollups publish transaction batches to Celestia or Initia and output roots to the L1, but the cited executor documentation describes batch submission only to Celestia, which is Celestia's feature, and output roots are rollup settlement data held in L1 state. The Connect oracle relays price feeds. Absence was not exhaustively verified, so the rule that absence needs a source makes this unknown rather than not present. 2 |
| Light clients | Built into the protocolLimited scope | CometBFT consensus produces the validator-signed commits that IBC light clients check, and IBC transfers are checked by on-chain light clients; for example, the L1 client behind the Cabal rollup's channel is a standard Tendermint light client. Limit: a light client is only as strong as the chain it follows, and a single-validator rollup gives it one signer to check. 192526 |
| 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 Initia L1 was found. IBC channels are messaging paths, not payment channels. 19 |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Initia L1 runs a Move virtual machine derived from Aptos Move. The Move parameters read on 2026-09-27 had an empty publisher allowlist, which the standard library treats as open to anyone, and scripts were enabled. The standard library includes a multisig module. 161724 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under this row's current definition. |
| Rollups | Native (protocol or core-team software) Earlier definition | Rollup settlement is built into the L1: its bridge module registers rollups, stores their output roots and escrows bridged funds. On 2026-09-27 there were 47 bridge records (one disabled), and Initia's registry listed seven live mainnet rollups using EVM, Move or Wasm. See the scaling entry for the trust model. 141323 |
| 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 protocolInitiaDEX (weighted and StableSwap pools), Minitswap | InitiaDEX runs on the L1 as weighted pools and StableSwap pools. A February 2026 forum proposal also let newer V3 pools register with the L1 exchange module for bridge and swap routing; those pools were not reviewed. Governance-whitelisted INIT pool positions can also be staked with validators. Minitswap is a StableSwap virtual pool, with rate limits, for swapping rollup-bridged INIT back to L1 INIT. Liquidity depth was not measured. 562731 |
| Issuer-native stablecoins | Unknown | Circle's USDC list names Noble, not Initia; USDC on Initia is an IBC voucher from Noble. Tether's protocol list does not name Initia. Initia's asset list also shows AUSD, iUSD and USDe as Move tokens whose issuers and issuance paths were not reviewed. 123638 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Initia L1 or its rollups were not reviewed. |
| Bridges | Native to the protocolIBC, OPinit optimistic bridge, LayerZero routes, Skip Go routing (includes Circle CCTP via Noble) | The L1 bridge module connects each rollup; IBC links rollups and other chains; ETH arrives as a LayerZero token. Initia's Bridge app uses Skip Go routing to combine these with Circle CCTP and DEX swaps. Circle's CCTP page lists Noble, and only under its legacy first version, not Initia. In August 2025 governance cut optimistic withdrawal periods for live rollups to 24 hours, and since January 2026 it has moved several rollups' bridges to IBC transport. Risk: Optimistic withdrawals depend on a designated challenger and Initia governance, not an automatic proof. Rollups moved to IBC trust their single operator's signature. LayerZero routes depend on off-chain verifiers not reviewed here. Governance has moved funds out of bridge escrow accounts before. A voucher is only as sound as its origin chain and path. 17121932343537 |
| Block explorers | First-partyInitiaScan, Moon Runners | Initia's network page links InitiaScan, run by the Initia team; the Cosmos chain registry also lists Moon Runners. Listing is not a quality or completeness check. 1014 |
| Hardware wallets | Unknown | See the custody rows: Trezor says it does not support Initia, and Ledger support could not be verified from Ledger's own pages. 3940 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | UnknownSame as native: Unknown | Ledger's coin-page address for Initia returned 404, and the static content of Ledger's supported-assets page does not mention Initia. Initia's VIP integration guide for rollup teams shows a command-line option for Ledger-backed operator and deployer keys; that is Initia's documentation, not Ledger's, and it was not tested. 1140 |
| Trezor | None foundSame as native: No | Cannot: Manage Initia accounts in Trezor SuiteTrezor's page states that it does not currently support Initia. Third-party wallets that might use a Trezor device with Initia's Ethereum-format keys were not checked. 39 |
Public data
iKnow Blockchain has no public-data lookups for Initia 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 moved leftover INIT out of six deprecated rollups' bridge accounts
Proposal 93 passed on 2026-09-25 and transfers the INIT left in the bridge accounts of six shut-down rollups (intergaze, ingnetwork, bfb, rena, zaar and moo) to a team-controlled address. The proposal says affected users were already repaid by airdrop. An identical earlier proposal (88) failed to reach quorum in June 2026.
- Proposal:passed (proposal 93); earlier proposal 88 failed quorum
- Implementation:executed through governance per the proposal messages
- Release:no software release needed
- Activation:passed 2026-09-25; one of the six bridge accounts checked and found empty on 2026-09-27
Sources: Initia L1 governance (on-chain record) — Proposal 93: Recover residual INIT from deprecated rollup OP bridges (resubmission) (external site) · Initia L1 governance (on-chain record) — Proposal 88: Recover residual INIT from deprecated rollup OP bridges (external site) · Initia Labs public REST endpoint — INIT balance of the intergaze bridge account (bridge 31) (external site) · Initia Forum — Intergaze Rollup Wind-Down Notice (external site)
-
Governance moved the Cabal rollup's bridge to IBC, continuing a 2026 series
Proposal 92 passed on 2026-09-16 and registered migration information that routes Cabal's bridge (bridge 42) over IBC channel-97, ending its 1-day withdrawal wait. Earlier proposals did the same for Civitia and Echelon (January 2026) and Inertia (May 2026). Users keep the same bridged tokens, but withdrawals now rely on IBC checks of the rollup's single operator.
- Proposal:passed (proposal 92)
- Implementation:migration information registered on chain
- Release:no software release needed
- Activation:passed; IBC client for the channel observed 2026-09-27
Sources: Initia L1 governance (on-chain record) — Proposal 92: Migrate Cabal OPbridge to IBC (external site) · Initia L1 governance (on-chain record) — Proposal 67: Migrate Civitia OPbridge to IBC (external site) · Initia L1 governance (on-chain record) — Proposal 68: Migrate Echelon OPbridge to IBC (external site) · Initia L1 governance (on-chain record) — Proposal 81: Migrate Inertia OPbridge to IBC (external site) · Initia Labs public REST endpoint — IBC client state for transfer channel-97 (Cabal) (external site) · Initia Labs public RPC endpoint (cabal-1) — Cabal rollup validator set (external site)
-
initiad v1.4.9 updated the node's state-storage library with race-condition fixes
Initia Labs published v1.4.9 on 2026-07-18, and GitHub marks it as the latest release. Its one listed change moves the IAVL storage library from Initia's fork v1.2.6-initia.1 to v1.2.8-initia.1. That brings in the upstream IAVL fix for a race between updating the fast-node cache and committing to the database, plus an Initia commit titled as a fix for a race condition in storage-version tracking. The release notes do not describe symptoms.
- Implementation:dependency bump merged in pull request 533 on the release/v1.4.x branch
- Release:released 2026-07-18 as v1.4.9, marked Latest
- Activation:takes effect per node once installed; a team-run node reported v1.4.8 on 2026-09-27
Sources: initia-labs on GitHub — Release v1.4.9 (external site) · initia-labs on GitHub — initia go.mod at tag v1.4.9 (external site) · initia-labs on GitHub — initia go.mod at tag v1.4.8 (external site) · initia-labs on GitHub — Initia IAVL fork: commit history at v1.2.8-initia.1 (external site) · cosmos/iavl on GitHub — IAVL changelog, release/v1.2.x branch (external site) · Initia Labs public REST endpoint — Live node info (initiad and CometBFT versions) (external site)
-
initiad v1.4.8 stopped transactions that panic during pre-checks from crashing nodes
Initia Labs published v1.4.8 on 2026-06-23. Its single commit wraps the transaction pre-checks (the ante handler) in panic recovery where they run outside the SDK's usual protection: the background mempool cleanup worker and the block proposal handlers. The code comments say a transaction that panicked there, for example one with a fee amount larger than a 64-bit integer, would crash the node; now it is dropped or rejected instead.
- Implementation:one commit (4441618) on the release/v1.4.x branch
- Release:released 2026-06-23 as v1.4.8 (not a pre-release)
- Activation:takes effect per node once installed; a team-run node reported v1.4.8 on 2026-09-27
Sources: initia-labs on GitHub — Release v1.4.8 (external site) · initia-labs on GitHub — Commit 4441618: wrap full ante with recover() (external site) · initia-labs on GitHub — initia releases feed (external site) · Initia Labs public REST endpoint — Live node info (initiad and CometBFT versions) (external site)
-
initiad v1.4.7 made nodes back off from re-sending pending transactions
Initia Labs published L1 node software v1.4.7 on 2026-05-20. Its one listed change moves the node to Initia's CometBFT fork v0.38.21-initia.4, which adds a time-limited gossip history to the mempool. A pending transaction that a node keeps re-sending to peers now waits longer between attempts, and a transaction the node has just removed is not taken back in straight away. The same fix shipped that day in the v1.5.0-alpha.2 pre-release.
- Implementation:merged in the CometBFT fork (pull request 94) and backported to the v1.4 release line
- Release:released 2026-05-20 as v1.4.7 (not a pre-release); also in pre-release v1.5.0-alpha.2
- Activation:takes effect per node once installed; no network-wide activation height named
Sources: initia-labs on GitHub — Release v1.4.7 (external site) · initia-labs on GitHub — Initia CometBFT fork release v0.38.21-initia.4 (external site) · initia-labs on GitHub — feat(mempool): add ttl gossip history to guard outbound flow (external site) · initia-labs on GitHub — Release v1.5.0-alpha.2 (pre-release) (external site) · initia-labs on GitHub — initia releases feed (external site)
-
The Reactor upgrade (initiad v1.2.2) passed and was applied
Proposal 64 passed on 2025-12-19 and the upgrade plan is recorded on chain as applied at height 11,270,000. It bundled attested IBC for rollup withdrawals, a single-sequencer block engine for rollups, forwarding accounts with memos, and a way for governance to move pre-allocated rewards into the community pool.
- Proposal:passed (proposal 64)
- Implementation:released as v1.2.2
- Release:released 2025-11-25
- Activation:applied on mainnet at height 11,270,000
Sources: Initia L1 governance (on-chain record) — Proposal 64: The Reactor Upgrade (external site) · Initia Forum — The Reactor Upgrade (external site) · Initia Labs public REST endpoint — Applied upgrade plan v1.2.2 (external site) · initia-labs on GitHub — Release v1.2.2 (external site) · Initia Labs public REST endpoint — Live rollup bridge records (external site)
-
Governance cut Initia's active validator cap from 50 to 20
Proposal 60 passed on 2025-11-14 and changed the multi-staking parameter for the maximum number of active validators from 50 to 20. The Initia Foundation's forum post argued that rewards spread over 50 validators did not cover secure operation. The live parameter read on 2026-09-27 was 20, with only 10 validators in the consensus set.
- Proposal:passed (proposal 60)
- Implementation:parameter change executed on chain
- Release:no software release needed
- Activation:active; cap of 20 observed 2026-09-27
Sources: Initia L1 governance (on-chain record) — Proposal 60: Active Validator Set Reduction (external site) · Initia Forum (Initia Foundation) — Active Validator Set Reduction Proposal (external site) · Initia Labs public REST endpoint — Live multi-staking parameters (external site) · Initia Labs public RPC endpoint — Live consensus validator set (external site)
Topics your AI can explain
Your AI can explain these topics for Initia through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Ledger support for Initia could not be confirmed or ruled out from Ledger's own pages; third-party signing paths were not tested.
- Why only 10 validators were active when the governance cap is 20 was not investigated; the minimum voting-power parameter may explain it.
- Initia's validator guide still says the top 100 validators are active, which does not match the live cap of 20.
- Who operates each bridge's designated challenger, and whether any rollup dispute has ever been raised, was not reviewed.
- Whether rollups moved to IBC transport still post output roots and data batches, and whether attested IBC protects any live route, was not confirmed; attester sets were empty.
- The LayerZero endpoint configuration on Initia L1 (which verifiers must agree) was not reviewed.
- Issuers and issuance paths of AUSD, iUSD and USDe on Initia were not reviewed.
- Atomic swaps, reversible or delayed transfers and recovery, payment or state channels and algorithmic stablecoins were not reviewed.
- No throughput claim was recorded; none was found in a classifiable primary form.
- Where L1 transaction fees go after collection was not reviewed.
- Initia's own registry still recommends node version v1.1.2 while sampled nodes run v1.4.8; the registry was used only for identity, keys, fees and rollup listings.
- Live endpoint citations point at team-run nodes that prune history; the block-interval sample may not be reproducible later.
- Validator counts and shares, slashing and Move settings, bridge records, rollup validator sets and governance-proposal details come from the author's live queries of team-run endpoints; the independent check did not repeat those queries and cross-checked them only against Initia's forum, documentation and release notes.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- OPinit Bridge (external site)
- Executor (external site)
- Challenger (external site)
- OPinit Cosmos SDK modules (README) (external site)
- InitiaDEX (external site)
- Enshrined Liquidity: Introduction (external site)
- Bridge (external site)
- Running L1 Nodes with Initiad (external site)
- Becoming a Validator (external site)
- Initia L1 Networks (external site)
- Integrating VIP (external site)
- Initia mainnet asset list (initia-registry) (external site)
- Initia registry: all chains (external site)
- Initia chain registry record (external site)
- initia go.mod (dependency and fork pins) (external site)
- Initia MoveVM repository (external site)
- Move standard library code module (code.move) (external site)
- Byzantine Consensus Algorithm (external site)
- IBC overview (external site)
- Live multi-staking parameters (external site)
- Live consensus validator set (external site)
- Live slashing parameters (external site)
- Live rollup bridge records (external site)
- Live Move module parameters (external site)
- IBC client state for transfer channel-97 (Cabal) (external site)
- Cabal rollup validator set (external site)
- Minitswap Architecture (external site)
- Release v1.2.2 (the Reactor upgrade) (external site)
- Active Validator Set Reduction Proposal (external site)
- Epoch 21 Civitia IBC Bridge Migration Proposal (external site)
- Enable V3 Pool Discovery for Bridge/Swap Routing (external site)
- Proposal 56: Standardize and Reduce All OP Bridge Withdrawal Periods (external site)
- Proposal 60: Active Validator Set Reduction (external site)
- Proposal 92: Migrate Cabal OPbridge to IBC (external site)
- Proposal 93: Recover residual INIT from deprecated rollup OP bridges (external site)
- USDC contract addresses (external site)
- CCTP supported blockchains (external site)
- Supported protocols (external site)
- Initia wallet (external site)
- Supported crypto assets (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