Permissioned ledger
Chiliz Chain ticker CHZ
Summary
Proof of Staked Authority in the Parlia engine of ccv2-geth, a fork of BNB Smart Chain's client, which is itself a go-ethereum fork. A capped set of main validators (13 in 2026) produces blocks about every 3 seconds. The set is refreshed each 28,800-block epoch (about a day) from approved validators ranked by staked CHZ, and delegators add CHZ to a validator's pool. Since the Snake8 hard fork of October 2025 each block's producer is drawn at random in proportion to the CHZ staked on it, with a floor of 1/(2N) per validator. Validator owners vote on governance proposals with power set by delegated stake and a two-thirds quorum. Chiliz's docs say this design gives short block times and low fees at the expense of decentralization, and describe finality as probabilistic. 12348102526
Design
- System
- Permissioned ledgerChiliz Chain (chain ID 88888) runs its own validator set and consensus; it does not post data to or settle on another chain. Anyone can hold CHZ, send transactions, deploy contracts and delegate stake, but a validator joins only after the existing validators approve it in a governance vote, so this profile uses the permissioned class. The current network, launched in May 2023 as Chiliz Chain 2.0, replaced the Chiliz Legacy Chain, whose Fan Tokens were migrated by September 2023. CHZ and other tokens reach other chains only through bridges and token-transfer contracts.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Probabilistic
- Who makes blocks
- Main validators are the highest-staked members of the approved set; candidate validators wait on standby. Joining needs a running node, at least 10 million CHZ staked and approval by a governance vote of existing validators. The docs list Allnodes, Animoca Brands, Ankr, Cointelegraph, Exaion, InfStones, Luganodes, Mercado Bitcoin, Meria, OKX, Paribu, Paris Saint-Germain and Socios.com as main validators and K League as a candidate. Documented penalties are loss of an epoch's rewards for missed blocks and a four-epoch jail for extended downtime.
- Fork choice
- Parlia gives a block signed by the validator whose turn it is a difficulty of 2 and any other validator's block a difficulty of 1, and the client keeps the branch with the greater total difficulty. The client also carries its upstream's vote-based finality (the Plato fork), under which justified blocks would win first, but it is not active on mainnet: the client reports the genesis block as the finalized head while that fork is off.
Qualifications
- System class · Contested. Chiliz's white paper calls Chiliz Chain an open, public and permissionless layer 1, and anyone can use it. Joining the validator set, however, needs at least 10 million CHZ staked, an application, and approval in a governance proposal voted on by the existing validators. This profile follows who can produce blocks; a reviewer could reasonably file it either way.
- Scarce resource · Partial. Staked CHZ decides which approved validators enter the 13-seat main set each epoch and, since Snake8, how likely each is to produce a block, so the scarce resource is recorded as stake. Staking alone does not let anyone join consensus: admission needs the existing validators' approval vote. The published client and staking contract penalize missed blocks by withholding rewards or jailing, without reducing stake.
- Slashing · Contested. The Chiliz Group's white paper (October 2025) says a validator that breaks protocol rules, for example by producing two blocks at once, can be jailed or partially slashed, burning part of its staked CHZ. Chiliz's penalty page lists only downtime penalties: missed blocks cost that epoch's rewards and longer downtime brings a four-epoch jail. The published code matches that page: the client calls the slashing contract only when a validator misses its turn and only logs a double-signed block, and the staking contract then withholds rewards or jails without reducing stake.
- Validator admission · Partial. Any CHZ holder can delegate (the minimum was lowered to 0.01 CHZ in May 2023), but becoming a validator needs at least 10 million CHZ and approval by a governance vote of the existing validators, and only the main set (raised to 13 in February 2025) produces blocks.
- Vote based finality · Not applicable. The client inherits the upstream fast-finality forks (Luban, Plato), which the April 2024 changelog says were present but not enabled. The July 2026 docs still describe probabilistic finality, and the client returns the genesis block as the finalized head while that fork is off.
- Settlement to other chains · Not applicable. Chiliz Chain posts no data to and does not settle on Ethereum or any other chain. CHZ and tokens move to Ethereum, Base and Solana through bridges: a Chiliz-run Ethereum bridge, LayerZero-based omnichain transfers since April 2026, and Dcentralab's Chainport. Since July 2026 Chiliz's token list also shows CHZ and PEPPER contracts on Robinhood Chain.
- Protocol balance edits · Applies. The Pepper8 hard fork, approved by a validator vote in August 2025 and activated on 9 September 2025 according to the Chiliz Group's white paper, credited newly issued CHZ to one address through an irregular state transition written into the client, to convert Paribu Net's PRB supply held by the Paribu exchange; Chiliz says later inflation years were lowered to offset it.
Tradeoffs
- Emphasizes
- Scalability
- Gives up
- Decentralization of block production. A capped set of 13 main validators, each needing 10 million CHZ and approval by a vote of the existing validators, produces every block. Chiliz's own documentation says proof of staked authority brings short block times and reduced transaction costs at the expense of decentralization. The validator list names the Chiliz Group's own Socios.com among the main validators.Security is not listed as an emphasis: blocks are final only in a probabilistic sense because vote-based finality is off, the validator penalty page and the published client and staking contract code penalize downtime only although the white paper mentions stake slashing for misbehaviour, and in May 2024 a coordinated client release rolled back 37 blocks after a failed hard fork. Readers who count the approval vote and the named institutional operators as a security design may reasonably disagree.
- Full node at home
- Unknown 67The validator guide asks for a dedicated server with at least 2 CPU cores, 4 GB of RAM, an SSD with 300 GB free and 10 Gbps of bandwidth, and validators run full-sync archive nodes. The general node guide, which runs the ccv2-geth Docker image, gives no hardware figures and offers a Chiliz-hosted snapshot to speed up syncing, which means trusting that snapshot. The CPU, memory and disk figures fit a home machine but the bandwidth figure does not, and the current chain size was not measured.
- Throughput claims
- Theoretical peak: 400 tx/s 24Theoretical peak; not comparable across chains or with observed load.The Chiliz Group's white paper says blocks average about 3 seconds, allowing up to about this rate under normal conditions.Issuer statement in a regulatory white paper, with no stated method, measurement window, transaction mix, gas assumptions or hardware. Not an observed rate: no mainnet window was measured in this review, and actual activity can be far below it. Chiliz's technical documentation and client releases give no throughput figure, so the white paper is the only source for this number.
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 | No hash-time-locked or other trust-minimized swap mechanism deployed on Chiliz Chain was found in the reviewed sources. Smart contracts could host one, but none was reviewed. |
| Authenticated data publication | Built into the protocolLimited scope | Blob transactions, enabled by the Cancun upgrade on 30 June 2026: a transaction records the versioned hash of each blob's KZG commitment, the client's data-availability check requires a recent block's blob sidecars to be present and to match those commitments under KZG proofs, and nodes keep blob data available so readers can fetch it and check it. Limited: the client keeps blobs for about 18 days, whether anyone publishes data this way was not measured, and there is no update mechanism. 112728 |
| Light clients | Unknown | No light client that checks Chiliz validator signatures was found in the reviewed docs; developers are pointed to shared public RPC providers or to running their own node. 14 |
| 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 Chiliz Chain was found in the reviewed sources. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Chiliz Chain runs the EVM inherited through its go-ethereum lineage, so spend conditions are smart contracts; the docs recommend Solidity up to 0.8.30 targeting the Prague rules. The governance record lists an October 2023 decision disabling a whitelist mechanism, and the Chiliz Group's white paper describes the chain as open for any third party to deploy applications. 121224 |
| 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. The changelog says the Pectra upgrade of 30 June 2026 lets ordinary accounts delegate to contract code, which wallets can use for recovery features, but no deployed delay or recovery module was verified. 11 |
| Rollups | Unknown | No rollup or validium anchored to Chiliz Chain was found in the reviewed sources; absence was not verified, so the cell stays unknown. |
| 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 | ThinKayen Finance, FanX Protocol | Chiliz's contract page says the Kayen Finance and FanX teams created contracts for their own decentralized exchanges, and DeFiLlama lists both as Chiliz exchanges alongside a few smaller venues. Kayen describes itself as a DeFi ecosystem built for Chiliz Chain and Fan Tokens. Operators, audits and liquidity depth were not reviewed; DeFiLlama lists no audits for either. 203132 |
| Issuer-native stablecoins | ThinBRZ (Transfero, Brazilian real) | Chiliz's October 2024 announcement, which quotes Transfero's chief executive, says BRZ would be integrated on Chiliz Chain, and its docs list a BRZ contract with no bridge. Transfero's current BRZ page does not list Chiliz Chain among its networks, so issuer confirmation is missing. The USDT and USDC here are bridged in through Chainport; neither Tether's nor Circle's own network list includes Chiliz Chain. The docs also list AUSD0 via Stargate; its issuer link was not confirmed. 181930343536 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Chiliz Chain were not reviewed. |
| Bridges | First-partyChiliz Bridge: Ethereum bridge for CHZ (Chiliz), Chiliz Bridge: omnichain transfers over LayerZero (Chiliz), Chainport (Dcentralab) | Chiliz runs an Ethereum bridge that locks ERC-20 CHZ on Ethereum and releases native CHZ from a handler contract on Chiliz Chain, and since April 2026 an omnichain bridge to Base and Solana built on LayerZero, whose endpoint contracts the docs list. Dcentralab's Chainport moves CHZ as wrapped CHZ and brings in bridged USDT and USDC. Chiliz's token list also shows CHZ and PEPPER contracts on Robinhood Chain. Risk: The reviewed docs do not say who signs or relays Ethereum bridge transfers, and no bridge audit was reviewed. LayerZero transfers depend on the verifier set Chiliz configured, which Chiliz calls a multi-verifier setup, and Chainport's trust model was not assessed. A bridged token is only as sound as the bridge that minted it. 1718202129 |
| Block explorers | First-partyChiliz Block Explorer (scan.chiliz.com, Blockscout), Chiliscan (Routescan) | Chiliz's docs list both explorers and recommend Chiliscan. The Chiliz Block Explorer runs Blockscout software on a Chiliz domain; Chiliscan's footer says it is built by Team Routescan and powered by Chiliz. Who runs the Blockscout servers was not confirmed, and no explorer independent of Chiliz was reviewed. Explorer data is provider-indexed, not consensus. 141633 |
| Hardware wallets | ThinLedger through MetaMask, Trezor through MetaMask or Rabby | See custody rows: Chiliz documents Ledger signing through MetaMask, Trezor's Chiliz page lists third-party wallet apps, and neither vendor's own wallet code lists the Chiliz Chain network. 15383940 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Through an intermediaryMetaMask set to Chiliz Chain, with the Ledger device signing (Chiliz's hardware-wallet and staking guides)Same as native: Unknown | Can: Import a Ledger account into MetaMask on Chiliz Chain Mainnet and approve CHZ transfers on the device, per Chiliz's hardware-wallet guide Can: Stake CHZ from a Ledger through MetaMask and Chiliz's staking app, per Chiliz's staking guide Cannot: Find Chiliz Chain (chain ID 88888) in Ledger's published Ledger Wallet currency list (@ledgerhq/cryptoassets 13.56.0) Cannot: See the CHZ ticker on the device while signing; Chiliz's guide says only MetaMask shows itLedger's Chiliz page (modified 2024-12-19) invites users to add a Chiliz account in Ledger Live but does not say which network it covers; CHZ also exists as an ERC-20 token on Ethereum, while Ledger's currency list has no Chiliz Chain entry. 9153738 |
| Trezor | Through an intermediaryMetaMask or Rabby, which Trezor's Chiliz page names among compatible wallet apps; Chiliz's guide documents MetaMaskSame as native: Unknown | Can: Use a Trezor Safe 3, 5 or 7 with the third-party wallet apps listed on Trezor's Chiliz page, which names Chiliz among the supported networks Cannot: Add Chiliz Chain in Trezor Suite: the Ethereum-family network list in Trezor Suite's current source code has no Chiliz Chain entry (chain ID 88888)Trezor's Chiliz page also says users can manage Chiliz in Trezor Suite and lists Base, Ethereum, Chiliz and Solana as networks without matching networks to apps. Inference: the Suite claim covers CHZ on the networks Suite supports, not native CHZ on Chiliz Chain. 153940 |
Public data
iKnow Blockchain has no public-data lookups for Chiliz Chain 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: Reviewed Sep 29, 2026 Next review due Oct 9, 2026, 12:00 UTC.
Publication date · newest first
-
Client 2.9.5 fixed archive resync failures and was marked a mandatory upgrade
A change in client 2.7.3 made nodes charge 2,500 more gas when replaying the historical blocks that ran a runtime upgrade of the DeployerProxy system contract (mainnet block 31,384,697), so archive nodes resyncing from scratch failed there. Client 2.9.5 restores the canonical gas, adds a replaycheck tool that re-executes blocks and compares them with the chain's receipts, and says governance must not run another DeployerProxy runtime upgrade until every validator runs a patched build.
- Implementation:fix shipped in client 2.9.5
- Release:mainnet release published 2026-09-10; notes call the fleet upgrade mandatory
- Activation:no fork height; applies as each node upgrades; how many validators have upgraded was not checked
Sources: Chiliz (GitHub) — Chiliz Chain client v2.9.5 release notes (external site) · Chiliz (GitHub) — chiliz-chain/v2 releases (external site)
-
Client 2.8.1 scheduled the Cancun, Prague and Pascal upgrades for 30 June 2026
Chiliz released client v2.8.1, which set mainnet fork times of 11:00 CEST on 30 June 2026 for Cancun and 11:30 CEST for Prague and Pascal, after release candidate 2.8.0-rc1 had scheduled the same upgrades for the Spicy testnet on 18 May 2026. Chiliz's changelog says they bring blob transactions, transient storage and EIP-7702 account delegation, and the docs moved the recommended compiler target to Prague with Solidity 0.8.30.
- Implementation:client 2.8.0-rc1 on Spicy (2026-05-18) and 2.8.1 for mainnet
- Release:v2.8.1 published 2026-06-10
- Activation:scheduled for 2026-06-30; header fields observed in a 2026-09-29 mainnet block
Sources: Chiliz (GitHub) — Chiliz Chain client v2.8.1 release notes (external site) · Chiliz (GitHub) — Chiliz Chain client v2.8.0-rc1 release notes (Spicy testnet) (external site) · Chiliz Chain Docs — Blockchain code changes (external site) · PublicNode (Allnodes) — PublicNode Chiliz RPC: latest block read on 2026-09-29 (external site)
-
CHZ and Fan Tokens began moving to Base and Solana through LayerZero
The Chiliz Group announced LayerZero-based omnichain transfers that let CHZ and PEPPER, followed by selected Fan Tokens, exist on Solana and Base with one supply shared across chains, through its new omnichain bridge. Chiliz describes a multi-verifier (multi-DVN) setup and says that 10% of Fan Token sale revenue across chains will fund CHZ buy-backs that are burned. A February 2026 governance proposal (CIP-050) asked validators to clean up the contract registry as a prerequisite for the LayerZero integration; its vote result was not found.
- Proposal:registry clean-up proposal CIP-050 put to validators in February 2026
- Implementation:LayerZero endpoint contracts deployed on Chiliz Chain, per the docs
- Release:omnichain bridge live at bridge.chilizchain.com
- Activation:the docs say support started in April 2026 with CHZ and PEPPER first; by the review date Chiliz's token list showed every Fan Token on Base and Solana, and CHZ and PEPPER also on Robinhood Chain
Sources: Chiliz blog — Chiliz brings Fan Tokens to Solana and Base (external site) · Chiliz Chain Docs — Using Chiliz Bridge (external site) · Chiliz Chain Docs — Smart Contract Addresses (external site) · Chiliz Chain Docs — Token Contract Addresses (external site) · Chiliz Chain Docs — February 2026: Contract Removal and Clean-Up Proposal (CIP-050) (external site)
-
Fan Tokens moved to 18-decimal contracts
Chiliz announced that from 27 April 2026 Fan Tokens would move across exchanges from whole-unit (0-decimal) contracts to new 18-decimal CAP-20 contracts. Most exchanges migrate balances for their customers; holders in self-custody swap through Chiliz's migration app, which takes the old tokens and returns the same amount in the new contract. The docs say every Fan Token had moved by the second quarter of 2026.
- Implementation:new 18-decimal contracts deployed per token
- Release:exchange-wide transition announced to start 2026-04-27
- Activation:docs say all Fan Tokens migrated by Q2 2026; per-token dates are given by quarter only
Sources: Chiliz blog — Decimal Fan Token Rollout: Upgrading the Digital Asset Class for Sport (external site) · Chiliz Chain Docs — 2026 Migration to Decimal Fan Tokens (external site) · Chiliz Chain Docs — Doc Updates (external site)
-
Snake8 hard fork made block production stake-weighted
Chiliz activated the Snake8 hard fork on mainnet at 11:00 CEST on 14 October 2025. Before it, each main validator produced roughly the same number of blocks; now each block's producer is drawn at random with a probability proportional to the CHZ staked on it, and no validator's share may fall below 1/(2N) of blocks. Client v2.6.0, published on 30 September 2025, set the fork time.
- Proposal:specified on the docs' Snake8 page
- Implementation:shipped in client v2.6.0
- Release:mainnet release published 2025-09-30
- Activation:activated on mainnet 2025-10-14 at 11:00 CEST, per Chiliz
Sources: Chiliz blog — Chiliz announces Snake8 hard fork to enhance validator performance and ecosystem incentives (external site) · Chiliz Chain Docs — October 2025: Snake8 Hard Fork (external site) · Chiliz (GitHub) — Chiliz Chain client v2.6.0 release notes (Snake8 mainnet) (external site) · Chiliz Chain Docs — Run a Chiliz Chain Node (external site)
Topics your AI can explain
Your AI can explain these topics for Chiliz Chain through the connection, with sources.
Known gaps
What this profile's review did not establish:
- How staked CHZ is spread across the 13 main validators, and how much stake the Chiliz Group's own validators (such as Socios.com) hold, were not measured.
- The December 2024 and February 2025 governance proposals in the docs all came from one proposer address and were applied by the Chiliz team; who controls that address was not verified.
- The white paper says misbehaving validators can have part of their stake burned, but the penalty page and the published client and staking contract code penalize missed blocks only; whether the deployed system contracts match the published source was not verified.
- No Chiliz plan to enable the vote-based finality forks already present in the client was found.
- The validator guide's 10 Gbps bandwidth figure is unexplained, the general node guide states no hardware, and the current chain and archive sizes were not measured.
- The only throughput figure found is the white paper's unexplained upper bound; Chiliz's docs and releases give none, and no observed rate was classified.
- The BRZ page linked from Chiliz's docs returned an error and Transfero's current BRZ page does not list Chiliz Chain, so BRZ issuance on Chiliz Chain rests on Chiliz's announcement and docs; AUSD0's issuer relationship was not confirmed.
- Who signs or relays Ethereum bridge transfers, any bridge audit, the LayerZero verifier configuration, the route to Robinhood Chain and Chainport's trust model were not documented in the reviewed sources; bridge.chiliz.com now redirects to bridge.chilizchain.com.
- Ledger did not state which network its Chiliz page covers; Ledger Wallet support for Chiliz Chain was not tested.
- Operators, audits and liquidity of Kayen Finance and FanX were not reviewed; their documentation overviews use closely matching text, Chiliz's doc log pairs them as FanX/Kayen, and their relationship was not established.
- Who operates the servers behind scan.chiliz.com (Chiliz or Blockscout's hosted service) was not confirmed.
- Whether blobs have been used on mainnet since Cancun was not measured, and the blob settings were read from the published client source rather than from running nodes.
- The outcome of the February 2026 contract-registry clean-up proposal (CIP-050) was not confirmed from a vote record.
- The client source defines further Chiliz forks (Pipe8 and a DeployerProxy sunset) whose content and mainnet activation were not verified.
- Trust-minimized swaps, payment or state channels, recovery or delay features, light clients and rollups anchored to Chiliz Chain were not found; absence was not verified.
- Current CHZ supply and cumulative fee burn were not read; the Chiliz Chain API supply endpoint was not queried.
Sources
Oldest dated source check: Source checked Sep 29, 2026 Next check due Oct 29, 2026.
- About Chiliz Chain (external site)
- Differences from Ethereum (external site)
- Defining Validators and Delegators (external site)
- How to Become a Validator (external site)
- About Validator slashing (external site)
- Running a Validator node (external site)
- Run a Chiliz Chain Node (external site)
- Governance (glossary) (external site)
- Stake your CHZ (including staking from a Ledger) (external site)
- October 2025: Snake8 Hard Fork (external site)
- Blockchain code changes (external site)
- Governance Proposals & Decisions (external site)
- Details on the May 21st outage (Dragon8 hard fork rollback, 2024) (external site)
- Connect using RPC (external site)
- Use a hardware wallet (external site)
- Use a Block Explorer (external site)
- Using Chiliz Bridge (external site)
- Using Chainport (external site)
- Stablecoins on Chiliz Chain (external site)
- Smart Contract Addresses (external site)
- Token Contract Addresses (CHZ, PEPPER and Fan Tokens on Chiliz Chain, Solana, Base and Robinhood Chain) (external site)
- Chiliz Chain Ecosystem (validators, wallets, tools) (external site)
- contracts/Staking.sol (v2-genesis-config master branch: staking system contract, missed-block penalties and jail) (external site)
- Chiliz White Paper, version 1.1 dated 10 October 2025 (CHZ crypto-asset white paper) (external site)
- consensus/parlia/parlia.go (master branch) (external site)
- core/forkchoice.go (master branch) (external site)
- core/data_availability.go (master branch): blob sidecar availability and KZG checks (external site)
- params/protocol_params.go (master branch): blob settings and retention period (external site)
- Chiliz brings Fan Tokens to Solana and Base (2026-04-28) (external site)
- Chiliz Integrates BRZ Stablecoin (2024-10-16) (external site)
- DeFiLlama protocols API (Chiliz entries: Kayen Finance, FanX Protocol and others) (external site)
- Kayen Finance Docs: Overview (external site)
- Chiliscan: Chiliz (CHZ) Blockchain Explorer (footer: built by Team Routescan, powered by Chiliz) (external site)
- BRZ Stablecoin (issuer page and network list) (external site)
- USDC contract addresses (external site)
- Supported Protocols and Integration Guidelines (external site)
- Chiliz wallet (external site)
- @ledgerhq/cryptoassets 13.56.0 currency list (external site)
- Safe & secure Chiliz wallet (external site)
- Trezor Suite Ethereum-family network config (network-ethereum-suite-common networkConfig.ts, develop branch) (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