Gnodi Protocol
A compliance-first
Layer 1.
Gnodi is not a general-purpose blockchain with a compliance layer added on. It is a Byzantine fault-tolerant L1 where regulatory framework coverage is enforced at the consensus layer — before any transaction reaches finality.
2500
ms to finality
Single-slot deterministic
10000
TPS sustained
Under load testing
5
Regulatory frameworks
At the consensus layer
100
% on-chain audit coverage
Every transaction
Architecture
Technical specification
Gnodi is built on the Cosmos SDK with CometBFT as the consensus engine — a mature, production-tested BFT implementation securing billions in on-chain value across the IBC ecosystem. Block Reign extends the core consensus layer with the Oracle PoS mechanism and the Veracore compliance hook, both integrated at the application-blockchain layer.
EVM compatibility is provided via an Ethermint-derived execution environment, allowing Ethereum smart contracts to deploy to Gnodi without modification while benefiting from Gnodi's compliance infrastructure and single-slot finality.
Consensus Model
How Gnodi reaches finality
Proposal
A designated proposer — selected by weighted validator stake — assembles a block from the mempool. The Veracore compliance hook validates each transaction against applicable regulatory frameworks before the block is proposed.
Pre-vote
Validators broadcast pre-vote signatures. CometBFT requires ≥ 2/3 of weighted stake to pre-vote before advancing. Oracle PoS validators submit off-chain attestations alongside their pre-votes — anchoring real-world compliance signals in the consensus layer.
Pre-commit
A second round of ≥ 2/3 pre-commit signatures locks the block. No block advances without supermajority agreement on both the transaction set and the compliance attestations attached to it.
Finality
The block commits to state. Finality is single-slot and deterministic — unlike probabilistic finality chains, Gnodi transactions are irreversible at commit. Settlement latency: under 2.5 seconds from mempool entry.
Security Model
Defense in depth — from consensus to compliance
Byzantine Fault Tolerance
CometBFT maintains liveness and safety while up to 1/3 of validator stake is controlled by adversarial or offline validators. The network does not fork — it stalls and recovers.
Sybil Resistance via Economic Stake
Validator admission requires a minimum bonded stake. Slashing conditions penalize equivocation (double-signing) and downtime. Delegated stake creates economic alignment between validators and protocol health.
Oracle PoS Attestations
Oracle validators submit external compliance and data attestations that are validated by the consensus layer before block finalization. External data is not trusted — it is attested by staked validators who share slashing risk.
IBC Security Boundary
Cross-chain settlement uses Inter-Blockchain Communication with channel-level light client verification. Each IBC transfer is secured by the destination chain's validator set — not by a bridging third party.
GDPR-Native Architecture
On-chain records contain only cryptographic proofs and hashes. Underlying personal data lives off-chain under configurable data controller arrangements, satisfying GDPR Article 17 erasure rights without breaking chain integrity.
Veracore Compliance Hook
Every transaction passes through the Veracore compliance engine at intake. Transactions that conflict with applicable regulatory frameworks are rejected at the mempool layer — not after settlement.
Node Economics
Validator and delegator incentives
Gnodi validators earn block rewards denominated in the native token, split between the validator and delegated stakers according to the commission rate set by the validator. Oracle PoS validators earn additional attestation rewards for accurate compliance data submissions.
Slashing is applied for equivocation (double-signing) and extended downtime. The slashing mechanism creates economic alignment — validators who behave honestly earn more than those who risk their bonded stake through negligence or adversarial behavior.
Validator commission range
Set by validator, bounded by protocol
Oracle PoS attestation reward
Additional APY for accurate off-chain submissions
Equivocation slash
Delegators share proportionally
Downtime slash
After 18h downtime threshold
Unbonding period
Standard Cosmos SDK parameter
Build on Gnodi
Integrate on Gnodi's compliance-first L1.
Testnet access is available for qualified teams. Contact us to begin the Veracore integration review and receive testnet credentials.