Quickstart Integration
Integrate applications with the BlockCore parallel consensus protocol. BlockCore client libraries manage thread dispatch, wallet signature packaging, and automatic failover handling across regional RPC gateways.
The client library exposes a typed interface to dispatch parallel transactions to the network shards directly.
import { Client, Wallet } from '@blockcore/sdk';
// Initialize network gateway instance
const client = new Client({
endpoint: 'https://rpc.mainnet.blockcore.network',
shardId: '0x04'
});
// Configure parallel execution keypair
const wallet = new Wallet(process.env.PRIVATE_KEY);
const txHash = await client.sendParallel({
to: '0x88fA12...F2E1',
amount: 12500000000000n, // Denominated in Core Satoshis
gasPrice: '14.5 Gwei',
payload: '0x0d3e5f'
});
console.log(`Consensus Checkpoint Broadcasted: ${txHash}`);
Parallel Consensus Specs
BlockCore replaces sequential block validation with an asynchronous Directed Acyclic Graph (DAG) state model. Transactions are dynamically segmented into non-overlapping shards based on memory access patterns. This allows multiple validators to commit state changes in parallel without race conditions or memory locking.
When state dependencies do overlap, our Conflict-Free Replicated Data Type (CRDT) memory registry resolves mutations deterministically, avoiding traditional locks and ensuring optimal parallel processing latency.
SDK Node Setup
To configure a validator node, install the official BlockCore command-line tools. Node client configurations are fully declarative and support hot-swappable validator key rotation.
# Download mainnet validation client binary
curl -sSf https://get.blockcore.network | sh
# Configure local genesis file parameters
blockcore-cli init --network mainnet --validator-id VAL-99B
# Launch state synchronizer daemon
blockcore-cli daemon start --shards=0,1,2,3 --rpc-port=8545