Subnet-EVM Compliance PrecompileTxAllowList at 0x0200...0002

Permissioned Consensus & Institutional Whitelist

Nyxor L1 enforces regulatory access controls at the consensus layer using the Avalanche TxAllowList stateful precompile. Unauthorized transactions are filtered at the node mempool boundary before consuming gas or executing smart contract code.

Your Connected Institutional Status
No wallet connected

Transactions from restricted addresses revert automatically at the consensus mempool boundary.

Precompile Role Inspector

Live L1 Query

Query any address against the native readAllowList(address) function on the Nyxor L1 node:

Admin Role Manager

Requires Role 2 (Admin)

Why Consensus Precompiles?

Traditional EVM applications enforce KYC inside Solidity smart contracts (`require(isKyc[msg.sender])`). This has two major security flaws:

Flaw 1: Gas is Still Wasted on Reverts

Smart contract reverts must still be included in blocks, consuming block space and charging gas to failed transactions.

Flaw 2: Mempool Denial-of-Service

Non-allowlisted bots can flood the node mempool with spam transactions, crowding out institutional orders during market hours close.

The Subnet-EVM Solution

With Avalanche TxAllowList, the check happens in the Golang consensus client before the transaction ever reaches the EVM.

  • Zero Gas Spent: Rejected transactions never hit the blockchain.
  • Mempool Gated: Nodes refuse to gossip unapproved signatures.
  • Institutional Grade: Satisfies regulatory isolation requirements.