LOCKJAW Proof, custody, refusal, constrained execution

TXG / Blockchain Integrity Suite

Transaction Gate

Transaction gating before protected execution.

TXG is the pre-execution gate for protected blockchain actions. A transaction must not execute unless authority, policy, timing, governance, and chain context have already been proven.

Layer Blockchain Integrity Suite
Status Local runtime and hostile reference surface implemented.
Boundary One system, one question

What it is

TXG is the pre-execution gate for protected blockchain actions. A transaction must not execute unless authority, policy, timing, governance, and chain context have already been proven.

What problem it solves

High-value blockchain actions still rely on implicit authority, mutable approvals, and verifier trust that arrives too late.

What it does

  • Evaluates protected blockchain actions against verifier-attested authority, policy, timing, and governance inputs.
  • Issues signed allow or refusal receipts derived from canonical request material.
  • Refuses stale, widened, replayed, or unproven execution paths before on-chain action proceeds.

What it does not do

  • It is not a wallet, multisig, timelock replacement, monitoring product, or post-fact analytics system.
  • It does not trust caller-supplied policy or mutable execution context by default.
  • It does not make NEO unnecessary; refusal proof remains a separate concern.

Who it is for

  • Bridge, exchange, treasury, lender, and governance operators protecting privileged execution.
  • Teams that need protected actions to fail before execution rather than explain themselves after loss.

Where it fits

TXG is the execution checkpoint in the blockchain suite. It can consume hostile attestation evidence such as GAC and feed refusal receipts into NEO.

Typical deployment context

Used for protected transfers, privileged admin actions, bridge routes, and lender-containment execution paths.