Core Features & Capabilities
What MpcFirewall checks before any signature leaves NEAR—and why both deterministic rules and confidential AI auditing work together.
Raw-Byte Decoding (Zero Blind Signing)
Instead of trusting a label written by the AI model, both our Rust smart contract and TypeScript SDK parse the actual binary transaction envelope byte-for-byte. Even if a benign call hides a malicious sub-call inside a router batch, MpcFirewall unwraps nested instructions recursively (up to depth 3) so traps have nowhere to hide:
- • EVM Chains (Base, Ethereum, Arbitrum): Parses EIP-1559, EIP-2930, and Legacy RLP transactions, verifying exact chain ID, recipient, fee exposure (
value + gas * maxFeePerGas), ERC-20 transfers/approvals/permits, NFT approvals, nestedmulticallbatches, Gnosis SafeexecTransaction(blocking hiddenDELEGATECALL), Uniswap Permit2, and UniversalRouter sweeps. - • Bitcoin SegWit (BIP-143): Unpacks transaction outputs, checks satoshi amounts and destination output scripts (
P2WPKH,P2PKH,P2SH,P2WSH,P2TR), and computes real per-input BIP-143 sighash preimages.
Per-TX & 24h Cumulative Spend Caps
A single small cap isn't enough—a compromised agent can try draining a treasury slowly by sending 90 USDC a hundred times in a row, or swapping a Bitcoin address under the per-TX limit repeatedly. MpcFirewall enforces both per-transaction ceilings and rolling 24-hour daily accumulators across ERC-20 tokens, native ETH/Base gas value, and Bitcoin satoshis—with automatic rollback if a remote MPC signature fails.
Confidential Intent-vs-Calldata Audit
Rules alone catch malformed payloads, while NEAR AI Cloud TEE acts as a confidential semantic second opinion: it compares the agent's plain-English excuse (“Pay Alice \$25 for cloud hosting”) against the decoded bytes inside a private Trusted Execution Environment so proprietary trading or vendor prompts stay encrypted. If the story and the bytes disagree, the transaction is flagged CRITICAL.
Human Team Escalation via SputnikDAO
Instead of forcing teams to choose between “turn off safety limits” and “block legitimate work”, medium-sized transactions that pass every security check automatically generate a ready-to-sign SputnikDAO / Trezu multisig proposal on mpc-firewall-council.sputnikv2.testnet. Once teammates vote yes, the contract releases the MPC signature.