The target and the measurement
The target is 5 seconds per block. The average recorded on the 500-block test bench is 5.018 seconds: the gap to the target lies within the variance of sealing.
Coinbosa Chain is a sovereign EVM blockchain, deployed to production on August 7, 2026 and designed for industrial scale and critical financial applications. Its settings are recorded in the genesis block and can be read back from the public endpoint.
These values are fixed in the genesis block, or applied by the client to each block produced. Two nodes that do not display the same block 0 hash are not on the same chain.
| Network name | Coinbosa Chain |
|---|---|
| Chain ID | 26262 — 0x6696 |
| Virtual machine | EVM-compatible |
| Consensus | Parlia |
| Block time | Target: 5 s | Measured: 5.018 s over 500 blocks |
| Epoch rollover | Validator intervals fixed — 200-block epoch, verified at blocks 200, 400, 600 and 800 |
| Consensus system contract | Custom-written (Solidity / Go-Ethereum), running directly on-chain |
| Native token standard | BRC20 (ERC-20 compatible) |
| Native coin | BOSA |
| Decimals | 18 |
| Total supply | 700,000,000 BOSA, fixed |
| Block 0 hash | 0x8dcdadc247a98f33728cae944e20ce7c49c74b35cfba31495f85e98979018da6 |
| Block 0 state root | 0x93682eb9182a55531d47014b76a285b45d3e720a2951f9ffbdc67f52995f8c03 |
| First block sealed | August 7, 2026 |
| Replay protection | EIP-155 |
| JSON-RPC endpoint | https://explorer.coinbosa.com/rpc |
| Source repository | github.com/Coinbosa/coinbosa-chain |
| Publisher | Coinbosa, Inc. — State of Delaware, United States |
The chain identifier is part of the signature. EIP-155 replay protection binds every signed transaction to network 26262: a transaction issued here is valid only on this chain. The genesis block hash and its state root can be read back on the official explorer.
On a test bench measured over 500 consecutive blocks in continuous integration, the average block time settles with minimal variance.
T_block = (1 / N) × Σ Δt_i for i = 1 … N, N = 500
= 5.018 seconds (target: 5.000 s)
The target is 5 seconds per block. The average recorded on the 500-block test bench is 5.018 seconds: the gap to the target lies within the variance of sealing.
Validator intervals are fixed per epoch of 200 blocks. The rollover is verified at blocks 200, 400, 600 and 800: that is where the engine re-reads the full validator set.
The consensus system contract is custom-written, in Solidity and Go-Ethereum, and runs directly on-chain.
The total supply of the BOSA coin is strictly fixed at 700,000,000 BOSA. No further issuance will ever take place.
The final supply is sealed in the genesis block. It depends on no later decision: what exists today is what will exist.
BOSA is divided into 18 decimals, the unit format of Ethereum virtual machines. Wallets and development tools apply it without any particular setting.
The native token standard of the chain is BRC20, ERC-20 compatible in its interface, covered by a complete automated test suite in continuous integration.
The official breakdown of the BOSA supply, as it appears in the whitepaper. The volumes add up exactly to the supply sealed in the genesis block.
| Allocation category | Share | Volume (BOSA) | Purpose |
|---|---|---|---|
| Development | 20 % | 140 000 000 | Evolution of the infrastructure and the chain |
| Technical | 10 % | 70 000 000 | Maintenance of the servers, the RPC and the validator nodes |
| Research | 10 % | 70 000 000 | Protocol and cryptographic innovation |
| Team | 10 % | 70 000 000 | Founders, engineers and key contributors |
| Financial fund (Coinbosa Card) | 10 % | 70 000 000 | Liquidity reserve for fiat and card transactions |
| Liquidity fund | 10 % | 70 000 000 | DEX and CEX liquidity pools |
| AI research | 10 % | 70 000 000 | Development of the proprietary CoinBosa AI model |
| Finance and fintech research | 5 % | 35 000 000 | Compliance research and neobank products |
| Public distribution and community | 5 % | 35 000 000 | Global adoption and network rewards |
| Security | 3 % | 21 000 000 | Bounty programs and infrastructure protection |
| Strategic reserve | 3 % | 21 000 000 | Institutional partnerships and contingencies |
| Audit | 2 % | 14 000 000 | External smart contract audits |
| Events and training | 2 % | 14 000 000 | Organization of seminars and CoinBosa Academy |
| Total fixed supply | 100 % | 700 000 000 | Final supply sealed in the genesis block |
A strict tokenomics is read in its totals. The thirteen allocations make up 100% of the supply, that is 700,000,000 BOSA, and the supply is sealed at the genesis block: no line can be created after the fact without changing chains.
The Coinbosa Chain embeds a native DeFi and DEX suite, open to developers.
Developers issue smart contracts and deploy BRC20 tokens without restriction.
The native suite makes it possible to create liquidity pools on the chain.
Two requests are enough: the identity of the chain, then the genesis block from which everything else follows.
curl -s -X POST https://explorer.coinbosa.com/rpc \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
# result : "0x6696" soit 26262
curl -s -X POST https://explorer.coinbosa.com/rpc \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber",
"params":["0x0", false]}'
# hash : 0x8dcdadc247a98f33728cae944e20ce7c49c74b35cfba31495f85e98979018da6
# stateRoot : 0x93682eb9182a55531d47014b76a285b45d3e720a2951f9ffbdc67f52995f8c03
The genesis block is the reference. Its hash and its state root commit the initial state of the chain: a node that returns other values is not serving Coinbosa Chain, whatever name it bears.
The procedure is the same in any EVM wallet. A mistyped identifier sends funds to a network that is not yours: prefer adding it from code.
| New RPC URL | https://explorer.coinbosa.com/rpc |
|---|---|
| Chain ID | 26262 |
| Currency symbol | BOSA |
A mistyped identifier sends funds to a network that is not yours. The network name, Coinbosa Chain, and the address of the explorer complete the fact sheet; the shortest check remains comparing the genesis block hash.
Connect, deploy, verifyAdding from code, the methods the public endpoint accepts, and the interface of the BRC20 standard.
Open the documentation