Skip to main content
OpenGDP employs a multi-layered security approach, validating data at the header, block, and transaction levels.

Validation Rules

  • Header: Timestamps must be monotonic and within 3 seconds of the future. Gas limits must strictly follow the protocol formulas.
  • Block: Every block must contain exactly one valid end-of-block system transaction.
  • Sub-blocks: Validators can only submit one sub-block per block. Signatures are verified against the epoch’s participant set, and gas usage is strictly bounded.

Runtime Guards

  • Throttling: Non-payment transactions are hard-capped by the general_gas_limit. Even if the block has space, if the general lane is full, these transactions are delayed.
  • Safety: The protocol enforces token pauses and policy blacklists at the pool and execution level, preventing illicit activity.