BUILD / TEST / CONTRIBUTE
One kit. Two developer tracks.
Start Solidity and Solana projects on your machine. Bloch DevKit packages local runtimes, persistent workspaces and an export interface designed for future Bloch network adapters.
Your familiar Ethereum tools.
Anvil, Cancun semantics and a Solidity counter starter. Local chain ID 31337, ready for Foundry and EVM wallets.
Build with the Solana runtime.
Agave test-validator with a persistent local ledger and a Rust program starter. Use the Solana CLI and your preferred client tools.
macOS and Linux · Python 3.9+ · Foundry and Agave installed separately. Verify SHA-256.
Local today. A defined path to Bloch.
The kit executes locally. Bloch settlement, SVM network execution and asset bridging remain integration work. The included integration guide defines the adapter boundary, preserves native PQ authorization and separates block observations from execution proofs.
BLOCH / CROSS-NETWORK DEVELOPMENT
Build the connection with Bloch Bridge.
Explore bridge reference contracts, local escrow and ERC-20 roundtrips, and the integration path to Bloch. The EVM execution core supports signed transactions and witness replay; the Genesis-4 source adapter has been exercised with a zero-value batch against a Bloch checkpoint.
Follow the implementation.
The project hub explains the architecture, available components and release status. The blochbridge.com custom domain is awaiting DNS configuration.
Open Bloch Bridge ↗Inspect the native EVM work.
The source adapter connects execution inputs to Bloch source data. A complete node service, production settlement and asset verification remain development work.
Explore the EVM repository ↗Deposits and withdrawals are not enabled.
Local runtime execution and bridge tests do not establish live settlement. The current bridge verifier uses trusted checkpoints; production finality verification and native BLCH escrow must be completed before public asset transfers.
Build the community by building together.
Bloch Builders brings together Solidity developers, Solana developers and protocol contributors. Start by running a project, reporting a reproducible issue or improving an example.
Make the next builder’s first run easier.
Test macOS or Linux installation, improve a starter or add a client example. Record commands and runtime versions so another developer can reproduce your result.
Open GitHub Issues ↗Help connect execution to Bloch.
Contribute signed EVM replay, SVM determinism tests and a Genesis-4 connector. The download includes a proposed backlog and founding developer cohort plan.
Explore Bloch Builders ↗Repository access may be required. Cohort dates, registration and a discussion channel have not been launched.
A starting point for builders.
Build on Bloch
Developer resources and the entry point to the ecosystem’s technical documentation.
Open developer portal ↗Protocol implementation
Inspect the node, consensus code, release notes, and contribution instructions. Repository access may be required.
Open GitHub ↗Run a Bloch validator — step by step
Install the CLI, verify the checkpoint, prepare your identity, authorize the deposit and monitor activation.
Open the complete validator guide →Run a Bloch validator — step by step
Install the CLI, verify the checkpoint, prepare your identity, authorize the deposit and monitor activation.
Open the complete validator guide →Node operation and validator admission.
The original network launched with one operator. Historical documentation describes restrictions on new validator deposits. Development work alone does not establish that admission is enabled on the deployed network.
Verify the active release.
Before bonding, verify the deployed release, funded deposit support, admission configuration, and checkpoint requirements. Use the release’s operator guide for actual commands and network identifiers.
The published genesis-verification window ended on 5 September 2026. A new operator must check the current checkpoint and synchronization procedure rather than follow an expired onboarding deadline.
The published RPC endpoint.
The existing wallet connects through the Postern Labs endpoint below. This website does not sign transactions or send RPC requests.
Endpoint behavior, availability, and enabled methods must be checked against the active network release.
Size your node for its actual work.
Historical resource measurements were taken from a young chain and a concentrated operator fleet. They do not establish current storage, replay, bandwidth, or independent-validator requirements.
Consult the active operator guide, monitor replay and peering, and account for chain growth. A validator also accepts operational and slashing exposure.
Inspect the GitLab mirror ↗