Layer 1 blockchain
Juno ticker JUNO
Summary
Proof-of-stake chain (juno-1) built on the Cosmos SDK with CometBFT consensus; nodes queried on 2026-09-27 ran Juno v30.0.0 on Cosmos SDK 0.53 and CometBFT 0.38. JUNO holders delegate to validators. Governance cut the active set to 25 in March 2026 (proposal 372), and 25 validators were bonded when checked. Unbonding takes 28 days; double-signing is slashed 5% and downtime 0.01%. A block commits once validators holding more than 2/3 of voting power precommit it, assuming less than 1/3 is byzantine. Juno is secured by its own validators, not by Cosmos Hub stake. 19101112131830
Design
- System
- Layer 1 blockchainJuno is a sovereign Cosmos SDK chain (chain ID juno-1) with its own JUNO-staked validator set and permissionless CosmWasm contracts. It is not a Cosmos Hub consumer chain and does not borrow Cosmos Hub stake. The current chain is a 2022 relaunch: the mainnet upgrade repository describes a pre-attack era and two post-attack relaunches, the second after an attack on 28 July 2022.
- Settlement family
- Cosmos SDK
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- Validators take turns proposing blocks in proportion to their voting power, per the CometBFT specification. On 2026-09-27 the largest validator held about a fifth of voting power (20 to 21% across two reads that day); the three largest together held more than a third, and the ten largest more than two thirds.
- Fork choice
- No fork choice in the Nakamoto sense: each height is decided by precommits from more than 2/3 of voting power. Two conflicting commits would need at least a third of voting power to double-sign, which is attributable and slashable. If more than a third is offline or refuses to vote, the chain halts instead of forking; with the 2026-09-27 set, three validators acting together could halt it.
Qualifications
- Ibc · Applies. IBC is messaging between independently governed chains, checked by on-chain light clients of each counterparty. It is how USDC, ATOM and other outside assets reach Juno, but connected chains are not Juno layer 2s. It is recorded in the bridge row of this profile.
- Shared security · Not applicable. Juno's consensus is run only by its own bonded validator set staked in JUNO (25 bonded validators on 2026-09-27), and it is not a Cosmos Hub consumer chain. Juno's homepage says it is part of the Mesh Alliance, but its roadmap lists Mesh Security as a 2024 item, not among the items marked done; no mesh security module appears in the chain's module list, and no live cross-chain staking arrangement protecting Juno was found.
- Tps · Unknown. No sourced, classed throughput measurement for Juno was found. Two block headers 1,000 heights apart, read on 2026-09-27, imply an average of about 2.9 seconds per block; that is a block interval, not a capacity figure.
- Chain history · Applies. The current juno-1 state continues from a relaunch after a July 2022 attack that exploited a smart-contract vulnerability; the docs call the relaunch Phoenix 2, starting at height 4,136,532. The operator repository records an earlier restart on version 3.0.0 before an April 2022 security upgrade. In 2022 governance also approved a software upgrade (proposal 20, after proposal 16) that moved one stakedrop recipient's funds into a governance-controlled contract; the operator repository's Unity upgrade notes describe that step.
Tradeoffs
- Emphasizes
- Security and Scalability
- Gives up
- Breadth of consensus participation. Only 25 validators produce blocks, governance cut the set to that size in 2026 because rewards were spread too thinly, and voting power is concentrated enough that three validators could stall the chain. Validator hardware guidance asks for 32 GB of memory. Juno halts rather than forks when more than a third of voting power is missing.Security here means fast, attributable finality backed by the chain's own JUNO stake; it is not Cosmos Hub security. Scalability means running contracts on a dedicated chain with blocks roughly three seconds apart, linked to other chains over IBC; no sourced throughput figure was found. The homepage says Juno is part of the Mesh Alliance, but its roadmap lists Mesh Security as a 2024 item rather than among the items marked done, and no live cross-chain staking arrangement protecting Juno was found.
- Full node at home
- Demanding 3433Juno's joining-mainnet guide gives 4 modern cores, 32 GB of RAM and 1 TB of SSD or NVMe storage as the minimum for a validator, and warns that low-spec machines can get stuck on complex contract blocks; it suggests swap on fast storage below 32 GB. State sync and pruned snapshots cut storage sharply: a validator-run pruned snapshot was about 5 GB on 2026-09-27. Memory is the main barrier for typical home machines; parts of the guide are older than the current release.
- 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 | Swaps inside a Juno contract settle all-or-nothing within one transaction, but no hash-time-locked or equivalent cross-party swap mechanism in use on Juno was verified. IBC token transfers are not atomic swaps. |
| 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, and Juno's IBC connections rely on on-chain light clients that verify each counterparty's consensus. Limit: clients that are not updated in time expire and need a governance recovery vote, which Juno used in July 2026 for a Quicksilver client; a 2025 attempt to recover an Injective client did not pass. On 2026-09-27 Juno's light client for Noble, the chain where Circle issues USDC, reported as expired. 17252631 |
| 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 Juno was reviewed. IBC channels are messaging paths, not payment channels. 31 |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Juno runs CosmWasm contracts. On-chain parameters read 2026-09-27 let anyone upload and instantiate code, so contract deployment is permissionless. v30 supports CosmWasm 2.2 contracts. Token factory lets accounts create native tokens, and FeeShare sends half of the fees from a transaction that calls contracts to the withdrawal addresses registered for those contracts. 5681415 |
| 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 module list shows no feature for cancelling, delaying or reclaiming a payment or for recovering an account. Contract-based recovery setups may exist but were not reviewed. The 2022 governance action that took one address's stakedrop funds into a governance-controlled contract was a one-off intervention through a software upgrade, not a feature users can configure. 162022 |
| 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 Juno was found in reviewed sources. IBC-connected chains are separate sovereign chains, not rollups. 31 |
| 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 | ThinWYND DEX (legacy contracts), Juno DEX (pre-launch) | No actively developed AMM on Juno mainnet was verified. In 2024 governance approved withdrawing community liquidity from WYND DEX because it was no longer developed; its WYND/JUNO pair still held about 50,000 JUNO when queried on 2026-09-27. Juno's docs list Juno DEX, an Astroport-derived contract set, as open to build under launch gates and say not to claim a public mainnet launch yet. Juno's validator guide points JUNO buyers to Osmosis, a separate chain, alongside the WYND DEX app. 37192329 |
| Issuer-native stablecoins | None found | Circle's USDC list includes Noble but not Juno. USDC on Juno arrives as IBC vouchers: USDC from Noble (listed as USDC.n in the chain registry) and Axelar-bridged USDC, whose on-chain denomination trace leads over the Axelar channel. Neither is issuer-native USDC on Juno. On 2026-09-27 Juno's light client for Noble reported as expired, so the Noble route was frozen until governance recovers it. 2242526272832 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Juno were not reviewed. |
| Bridges | Native to the protocolIBC (ibc-go), Axelar (over IBC) | IBC connects Juno to other IBC chains through light clients; the v30 upgrade notes counted 674 IBC channels. Juno has transfer channels to Noble for USDC, to the Cosmos Hub for ATOM and to Axelar, whose USDC is one of the denominations FeeShare shares with contract developers. On 2026-09-27 the Noble client had expired. Circle's own cross-chain transfer service was not found for Juno. Risk: An IBC voucher is only as sound as its origin chain, its light client and the path it took. Clients that expire freeze their routes until governance recovers them: the Noble client was expired on 2026-09-27, a 2025 recovery for Injective failed and a 2026 one for Quicksilver passed. Axelar-bridged assets also depend on Axelar's own validator set. 28151725262831 |
| Block explorers | Established in the ecosystemEZStaking, Ping.pub, ATOMScan, Stakeflow, Valopers | The chain registry lists ten explorers for juno-1, mostly run by validators or staking services. Their pages render in the browser and could not be read by the review tools, so listing is not a quality or availability check. Whether Mintscan still indexes Juno was not verified. 134 |
| Hardware wallets | Unknown | See the custody rows: Ledger Wallet has no Juno support, and the only Ledger evidence is a generic key option in Juno's command-line reference and Keplr's general guide for Cosmos-based chains, so no hardware path is confirmed. Trezor Suite does not support Juno. 2135363738 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | UnknownSame as native: Unknown | Cannot: Manage JUNO inside Ledger Wallet itself: Juno is not among Ledger Wallet's Cosmos chain integrations Cannot: Find a Ledger coin page for Juno; the URLs tried returned not foundJuno's command-line reference lists a generic option to keep a key on a Ledger device, and Keplr's Ledger guide covers Cosmos-based app chains without naming Juno. Neither is a Ledger or Juno page documenting Ledger use for JUNO, so the route is recorded as unconfirmed rather than as a documented path. Juno shares the Cosmos Hub key path (coin type 118), per Keplr's Juno entry and the chain registry. 121353637 |
| Trezor | None foundSame as native: No | Cannot: Manage juno-1 accounts in Trezor Suite, which Trezor's Juno page says does not support JUNO Cannot: Treat the JUNO representation on Evmos that the page lists as Juno custody; the Cosmos chain registry now marks Evmos as shut downTrezor's page lists only MetaMask and Rabby on Evmos. Third-party signing paths for native Juno accounts with a Trezor were not exhaustively checked. 3839 |
Public data
iKnow Blockchain has no public-data lookups for Juno 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
-
Juno v30 approved: fee market and Cosmos SDK 0.53
Governance proposal 377 passed and scheduled the v30.0.0 upgrade at height 40,420,069. The release moves Juno to Cosmos SDK 0.53, CometBFT 0.38, IBC-Go 10 and CosmWasm 2.2 support, turns on an on-chain fee market for JUNO with a minimum base gas price of 0.075 ujuno, adds voting-snapshot state and removes several retired modules, including the global fee and interchain query modules.
- Proposal:proposal 377 passed
- Implementation:released as v30.0.0
- Release:released 2026-07-16
- Activation:applied at height 40,420,069 per on-chain upgrade record
Sources: Juno on-chain state via PublicNode REST endpoint — Juno proposal 377: Upgrade Juno Mainnet to v30.0.0 (external site) · CosmosContracts — Juno v30.0.0 release (external site) · CosmosContracts mainnet repository — Juno v30 mainnet upgrade instructions (external site) · Juno on-chain state via PublicNode REST endpoint — Juno applied upgrade plan v30 (external site) · Juno on-chain state via Polkachu REST endpoint — Juno fee market parameters (external site)
-
Juno Agents DAO allowed to distribute tokens to stakers
Governance proposal 375 passed and added the Juno Agents DAO contract to the drip module's allow list, so the DAO can send native or token-factory tokens it already holds to JUNO stakers. The proposal states this grants no minting power, treasury access, module control or permission to change the drip module's settings.
- Proposal:proposal 375 passed
- Implementation:allow list updated by the proposal
- Release:no software release needed
- Activation:active: drip parameters listed the DAO address on 2026-09-27; no distribution was checked
Sources: Juno on-chain state via PublicNode REST endpoint — Juno proposal 375: Authorize Juno Agents DAO for x/drip distributions (external site) · Juno documentation — Juno Agents DAO (external site) · Juno on-chain state via PublicNode REST endpoint — Juno drip module parameters (external site)
-
Juno cuts its active validator set to 25
Governance proposal 372 passed and set the maximum number of active validators to 25, down from the 80 set in April 2025. The proposal said falling network activity and fee income left rewards spread too thinly, and that operators were already leaving. Validators outside the top 25 became inactive, and their delegators had to redelegate to keep earning rewards.
- Proposal:proposal 372 passed
- Implementation:parameter change executed by the proposal
- Release:no software release needed
- Activation:active: staking parameters showed a cap of 25 and 25 bonded validators on 2026-09-27
Sources: Juno on-chain state via PublicNode REST endpoint — Juno proposal 372: Reduce Maximum Validator Set to 25 (external site) · Juno on-chain state via Polkachu REST endpoint — Juno proposal 362: Reduction of the Validator Set (external site) · Juno on-chain state via PublicNode REST endpoint — Juno staking parameters (external site) · Juno on-chain state via PublicNode REST endpoint — Juno bonded validators (external site) · Juno on-chain state via Polkachu REST endpoint — Juno latest validator set (external site)
-
Juno votes to unwind community pool stJUNO liquidity
Governance proposal 371 passed and handed the community pool's stJUNO/JUNO liquidity tokens to Juno co-founder Dimi to withdraw the pool on Osmosis, return the JUNO and redeem the stJUNO through Stride. The proposal said most stJUNO stake sat with jailed validators earning nothing and that stJUNO had lost most of its venues.
- Proposal:proposal 371 passed
- Implementation:transfer to the named executor authorised; execution not verified
- Release:no software release needed
- Activation:not verified in this review
Topics your AI can explain
Your AI can explain these topics for Juno through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Validator cap, bonded count, voting-power shares, unbonding, slashing and upload permissions are on-chain values read on 2026-09-27; governance has cut the validator cap twice since April 2025 and can change them again.
- The live fee market floor was read on 2026-09-27; the fee market's price list named only JUNO that day, but whether ATOM or other tokens listed as fee tokens in the chain registry are now rejected was not tested.
- Parts of Juno's own documentation predate current releases (older gas prices, a 150-validator active set, WYND DEX links), so hardware guidance may also be dated.
- The Unity upgrade that moved one stakedrop recipient's funds into a governance-controlled contract is documented in the operator repository, but what governance later did with those funds was not traced.
- Juno's homepage says Juno is part of the Mesh Alliance and lists Mesh Security as a 2024 roadmap item; whether any Mesh Security contracts are deployed on Juno was not checked.
- Juno's IBC light client for Noble reported as expired on 2026-09-27; whether a recovery proposal is planned was not checked.
- No actively maintained AMM on Juno mainnet was verified; Juno DEX mainnet status and any other live venue contracts were not checked beyond the docs and one legacy pair.
- No trust-minimized cross-party swap mechanism, channel layer, reversible or delayed transfer or recovery feature, or algorithmic stablecoin on Juno was reviewed.
- No sourced, classed throughput measurement was found; the block interval comes from only two sampled blocks.
- Ledger's coin pages for Juno returned not found, and no Ledger or Juno page documenting Ledger use for JUNO was found; Juno's command-line reference and Keplr's general guide suggest a route that was not tested. Third-party Trezor signing paths for native Juno accounts were not checked.
- Explorer pages render in the browser and could not be read; whether Mintscan still covers Juno was not verified.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Juno chain registry record (external site)
- Juno asset list (external site)
- Joining Mainnet (external site)
- Sync with state-sync (external site)
- TokenFactory (external site)
- FeeShare (external site)
- Juno DEX (external site)
- Juno v30 mainnet upgrade instructions (external site)
- Juno node info (application and CometBFT versions) (external site)
- Juno staking parameters (external site)
- Juno slashing parameters (external site)
- Juno bonded validators (external site)
- Juno latest validator set and voting power (external site)
- Juno CosmWasm code upload parameters (external site)
- Juno FeeShare parameters (external site)
- Juno module versions (external site)
- Juno governance proposals (latest 30) (external site)
- Juno proposal 372: Reduce Maximum Validator Set to 25 (external site)
- Juno proposal 348: Withdraw Community Funds from WYND (external site)
- Unity Upgrade (v4.0.0) operator notes (external site)
- keys (junod command-line module) (external site)
- Juno proposal 16: Correcting the gamed stakedrop (external site)
- WYND/JUNO pair contract on Juno (external site)
- IBC denomination trace for Noble USDC on Juno (external site)
- Juno channel-224 client state (Noble) (external site)
- Juno IBC client 07-tendermint-334 (Noble) status (external site)
- IBC denomination trace for Axelar USDC on Juno (external site)
- Juno channel-71 client state (Axelar) (external site)
- juno-dex repository (external site)
- Byzantine Consensus Algorithm (external site)
- IBC overview (external site)
- USDC contract addresses (external site)
- Juno node snapshot (external site)
- ATOMScan Juno explorer (external site)
- Ledger Wallet Cosmos chain integrations (source directory) (external site)
- Connect your Ledger with Keplr Extension (external site)
- Keplr chain registry entry for Juno (external site)
- Juno Network wallet (external site)
- Evmos chain registry record (external site)
- Juno Network homepage (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