ISBE Network Technical Parameters
This document collects the operational parameters relevant to teams developing and deploying use cases on the ISBE blockchain network. It includes only the information necessary to connect, deploy contracts, and operate correctly in each environment (dev, pre, pro).
The ISBE network is based on Hyperledger Besu and uses the QBFT consensus mechanism, fully EVM-compatible.
The values presented in this document correspond to the ISBE MVP reference configuration and may vary according to:
- Environment (dev, pre, pro): each environment may have specific configuration.
- Project Phase (MVP, R1, R2): parameters may evolve between deliveries.
- Network Updates: subsequent improvements and optimizations after initial deployment.
⚠️ Before configuring your development tools, verify the specific values for your environment by contacting the ISBE infrastructure team. Critical parameters to confirm are:
- Chain ID and Network ID
- RPC Endpoints (URLs and ports)
- Current block time
- Recommended Besu version for your environment
1. Client and Version
The network runs:
- Client: Hyperledger Besu
- Recommended version: 24.12.2 (updated according to project delivery)
- Compatibility: EVM (Ethereum Virtual Machine)
- Consensus: QBFT (QBFT is the improved evolution of IBFT 2.0)
- Hash Algorithm: Keccak-256 (Ethereum standard)
Besu is an enterprise client maintained by the Linux Foundation, with support for permissioned networks and flexible QBFT configuration.
The specific Besu version may vary depending on the environment and the project phase (MVP, R1, R2). Consult with the ISBE infrastructure team for the exact version for your environment.
2. Consensus: QBFT
The ISBE network uses QBFT (improved evolution of Istanbul BFT 2.0), a Byzantine fault-tolerant mechanism where:
- A set of validators proposes and signs blocks.
- The block is only valid if it reaches a quorum of signatures.
- The system allows tolerating down or non-honest nodes within BFT limits.
Configured consensus parameters:
- Block period: 5 seconds (time between blocks)
- Epoch length: 1000 blocks (for validator rotation)
- Request timeout: 2 seconds (proposal timeout)
Relevant features for use cases:
- No mining exists: consensus is deterministic.
- Block time is stable (5 seconds configured).
- Transaction behavior is predictable.
- No deep chain reorganization exists (minimal reorgs).
3. Block Time
The block generation time configured in ISBE is:
- Block time: 5 seconds (
blockperiodsecondsparameter) - Variability: very low (deterministic consensus)
- Suitable for:
- Notarization protocols
- General purpose smart contracts
- Backend integrations with predictable latency
This block time may be adjusted if the network requires subsequent optimizations, but use cases must be designed considering that blockchain writing is never instantaneous and always implies structural latency (minimum 5 seconds for confirmation).
4. Gas Limit and Transaction Cost
ISBE, being a Besu-based permissioned network, does not use an economic token. Therefore:
- There are no economic costs per transaction.
- Gas is used solely as an execution control mechanism.
- Transactions must include a reasonable gas limit to avoid excessively heavy operations or infinite loops.
Configured Limits:
- Gas per block: 32,000,000 (0x1e84800 in hexadecimal)
- Gas per transaction: dynamic, per contract, always within block limit.
- Minimum gas per transaction: 1 wei (
min-gas-priceparameter)
This allows deploying complex contracts without artificial restrictions, but it is recommended to avoid:
- Contracts with massive storage in a single block.
- Unnecessarily heavy internal logic.
5. Chain ID and Network ID
The ISBE network uses the following identifiers:
- Chain ID: 2023
- Network ID: 2023
The Chain ID is the same for all environments (dev, pre, pro) in the current reference configuration. This means:
- Signed transactions include identifier 2023.
- Wallets and EVM libraries must be configured with
chainId: 2023. - Frameworks like Hardhat or Foundry must use this value in their configuration.
If your environment uses a differentiated Chain ID by environment (dev/pre/pro), the ISBE infrastructure team will provide the specific values. Always verify with the team before configuring your development tools.
6. Types of RPC Endpoints
Each environment exposes Ethereum JSON-RPC compatible endpoints:
-
HTTP RPC: used for most backend interactions (reads, writes)
- Standard port: 8545
- Enabled APIs:
ETH,NET,QBFT - CORS enabled for development
-
WebSocket RPC: necessary for listening to real-time events (logs emitted by contracts)
- Available according to node configuration
RPC Configuration Parameters:
--rpc-http-enabled
--rpc-http-host=0.0.0.0
--rpc-http-port=8545
--rpc-http-api=ETH,NET,QBFT
--rpc-http-cors-origins="all"
--host-allowlist="*"
Use cases will receive final URLs for their endpoints when their regular node or shared node access is activated.
7. Permissioning Rules
The network is permissioned: each node must be included in the authorized node list to join the P2P.
Permissioning affects only:
- Regular nodes (belonging to a use case).
- Validator and permissioner nodes (managed by ISBE).
Permissioning does not affect dApps: any application can connect to the assigned RPC without needing to be part of the P2P.
8. Recommended Operational Limits
To ensure proper use of the network:
- Avoid sending more than 10–20 transactions per second from the same account without prior coordination.
- Wait for block confirmation before starting dependent processes.
- Design smart contracts following efficiency patterns:
- Avoid redundant storage.
- Use events instead of storing internal logs.
- Do not make loops dependent on dynamic size without control.
9. Additional Node Configuration
ISBE nodes use the following additional Besu parameters:
Networking:
- P2P port: 30303 (TCP/UDP)
- P2P host: configurable according to deployment
Metrics:
- Metrics enabled by default
- Metrics port: 9545
- Metrics host:
0.0.0.0
Logging:
- Default level:
INFO
Customizable Paths:
--data-path: Path to the node data directory--genesis-file: Path to the genesis.json file--node-private-key-file: Path to the node private key file
10. Summary of Parameters
| Parameter | Value |
|---|---|
| Client | Hyperledger Besu 24.12.2 |
| Consensus | QBFT (evolution of IBFT 2.0) |
| Block time | 5 seconds |
| Gas per block | 32,000,000 gas |
| Minimum gas | 1 wei |
| Economic cost | None |
| Compatibility | Ethereum/EVM |
| Chain ID | 2023 |
| Network ID | 2023 |
| HTTP RPC Port | 8545 |
| P2P Port | 30303 |
| Metrics Port | 9545 |
| RPC APIs | ETH, NET, QBFT |
| Network | Permissioned |