BLOCK DOCUMENTATION

Use the BLQ network with confidence.

Everything here is for BLQ Mainnet. Start with a wallet connection, inspect activity in the explorer, and use the public RPC only through its HTTPS endpoint.

Open explorer Open bridge

WHAT IS A BLOCK?

A verified step in BLQ history.

A block is a linked, time-ordered record of transactions and the resulting network state. It points to the previous block, carries a miner reward, and includes Proof of Work that anyone can verify.

Every node checks the same block before adding it to its local chain. This is what lets wallets, miners, explorers, and contracts share one canonical history.

A template is prepared.The node selects the current parent, eligible mempool transactions, difficulty, and reward rules.
A miner searches.The miner changes the nonce and searches for a BLQ-RX/2 proof that meets the current difficulty target.
The block is checked.Nodes verify the parent, height, timestamp, Proof of Work, transactions, receipts, gas, and state root.
The block is linked.Once accepted, it becomes the parent available to the next miner and its transactions receive canonical receipts.
The strongest history wins.Two valid blocks can briefly compete. BLQ keeps the branch with the most cumulative work; the other becomes stale.

Issuance0.1 BLQ per minuteTime-based reward

Cadence15-second targetAdaptive block timing

ContentsTransactions and stateRoots make results verifiable

SecurityProof of WorkIndependent node validation

NETWORK

BLQ Mainnet

Block is a CPU-mined Proof-of-Work network using the native BLQ-RX/2 algorithm. It uses Ethereum-style account addresses and supports EVM-compatible tools. Its adaptive cadence is centered on a 15-second target while issuance remains time-based at 0.1 BLQ per minute.

Chain ID: 707070 0xAC9FE
Currency: BLQ 18 decimals
Consensus: BLQ-RX/2 Proof of Work
Cadence: Adaptive 15-second target
Issuance: 0.1 BLQ / minute time-based
Public RPC: https://rpc.blq-chain.online/rpc

WALLET

Add BLQ to an EVM wallet.

Use the official public endpoint. Never add an RPC endpoint received in a direct message or from an unverified site.

Open your wallet’s network settings.Choose the option to add a custom EVM network.
Enter the network values.Network name: Block Mainnet. Chain ID: 707070. Currency symbol: BLQ.
Set the RPC endpoint.https://rpc.blq-chain.online/rpc
Verify before signing.Use the explorer to inspect the recipient, contract, and transaction details.

TRANSACTIONS

From signature to receipt.

Your wallet signs locally. BLQ nodes validate the signed transaction, relay it through authenticated peers, and miners choose eligible transactions for a block.

Before inclusion

Pending

The transaction is accepted by at least one node but has not entered a canonical block. It can still be replaced, expire, or become stale.

After inclusion

Receipt

A receipt proves the transaction was included. Status 1 means success; status 0 means execution reverted but the transaction remains part of the chain.

NonceSender order

Gas limitExecution ceiling

DataContract input

ValueBLQ amount

BRIDGE

Wrap and unwrap BLQ on BLQ Chain.

The bridge converts between native BLQ and wBLQ inside BLQ Chain. Use the dedicated bridge interface at bridge.blq-chain.online/index.html, confirm the transaction, and review the contract state before signing.

BLQ Chain and Polygon

Bridge

Transfer wBLQ between BLQ Chain and Polygon using the cross-chain bridge.

Open bridge

BLQ Chain

Warp

Lock native BLQ and receive the same amount of wBLQ on BLQ Chain.

Open Warp

BLQ Chain

Unwarp

Burn wBLQ and receive the corresponding native BLQ on BLQ Chain.

Open Unwarp

MINING

CPU mining is part of BLQ.

BLQ-RX/2 is the network’s native Proof-of-Work algorithm. A miner requests a template, hashes locally, and submits a valid candidate block back to a compatible node.

BLQ Miner v0.1.1 is available.

Native Windows and Ubuntu builds are published on GitHub. Check the release SHA-256 before running a miner, and download BLQ software only from the official organization.

Download BLQ Miner

Expected hardwareModern 64-bit CPU

NetworkStable network connection

Worker setupOne beneficiary per worker

EXPLORER

Read the chain from canonical data.

The explorer separates live node information from archive-indexed information. A short indexing delay is possible while a new canonical block is being processed.

Blocks

History and rewards

Inspect the block number, timestamp, parent and block hashes, miner, reward, gas, size, and transaction count.

Transactions

Activity and logs

Follow sender, recipient, value, fee, gas, receipt status, contract logs, and the block that included the transaction.

Addresses

Balances and activity

View native balance, indexed transactions, token holdings, and the last canonical balance update.

Contracts and tokens

On-chain detail

Unknown contracts remain visible with bytecode and activity. Verification badges appear only when source matches deployed bytecode exactly.

Pending is informational.

Pending entries come from a bounded mempool view and are reconciled against receipts and confirmed nonces. `Unavailable` means the check timed out; it does not mean a canonical transaction was deleted.

NODES

Validate independently.

Full nodes retain historical chain data. Pruned validating nodes keep current executable state, finalized checkpoints, and the data needed to validate new blocks and choose the canonical PoW branch.

Archive node

Full history

For explorers, indexers, historical RPC, and independent archival providers.

Download BLQ Node

Validating node

Pruned history

For normal verification and P2P participation with bounded local chain storage.

Download BLQ Node

DEVELOPERS

Build against public BLQ services.

Use standard JSON-RPC over HTTPS for public read requests. Rate limits and method allow-lists protect the public gateway; node administration and P2P interfaces are intentionally not public APIs.

POST https://rpc.blq-chain.online/rpc

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_chainId",
  "params": []
}

Useful read methods include eth_blockNumber, eth_getBalance, eth_call, eth_estimateGas, eth_getTransactionReceipt, and eth_getLogs. Signed submissions use eth_sendRawTransaction.

NETWORK BEHAVIOR

Designed to keep moving.

Every node validates data locally. Non-mining nodes can still accept and relay transactions, while miners receive current templates from the canonical network.

RPC temporarily unavailableA public gateway can return a retryable error when its healthy upstream capacity is exhausted. Retry with bounded backoff.

Explorer is behindThe explorer may be indexing the newest canonical block. Compare its height with the public RPC before treating it as a chain problem.

Transaction is staleThe sender’s confirmed nonce advanced without a receipt for that hash. Do not resend it automatically; inspect the sender’s current nonce.

TROUBLESHOOTING

Check the basics first.

Confirm the wallet uses chain ID 707070, the official HTTPS RPC, and enough BLQ for the value and gas. Inspect the transaction hash in the explorer, wait for source confirmations when using the bridge, and never share a seed phrase or private key. Miner telemetry may be unavailable through the public gateway even when templates and block submission work.

SAFETY

Verify the chain, not a screenshot.

Check addresses and transaction hashes in the official explorer. Treat bridge transfers as cross-chain operations: wait for source confirmations, review the destination claim, and never share a wallet recovery phrase or private key.