Authorization Engine

Overview

The ClawBank authorization engine implements a pull-based validation model where transactions require explicit cryptographic approval before execution. Unlike push-based approval systems (ERC20 allowances), this architecture eliminates unlimited delegation risk through programmable spending policies enforced at both the smart contract layer and off-chain policy evaluation.

Architecture

Transaction Request


┌───────────────────┐
│ Policy Evaluation │
│   (Off-Chain)     │
└────────┬──────────┘

    ┌────┴────┐
    │         │
    ▼         ▼
┌────────┐ ┌──────────────┐
│Merchant│ │   Velocity   │
│ Check  │ │   Control    │
└───┬────┘ └──────┬───────┘
    │             │
    └──────┬──────┘


    ┌──────────────┐
    │  ZK-Proof    │
    │  Validation  │
    └──────┬───────┘


    ┌──────────────┐
    │ Smart Contract│
    │  Execution   │
    └──────┬───────┘


    [ Approve/Decline ]

Policy Types

WhitelistOnly

Restrict transactions to pre-approved merchants or contract addresses.

Use Case: Company treasury with strict vendor management

VelocityControl

Rate limiting per time window to prevent rapid transaction patterns.

Use Case: Fraud prevention and anomaly detection

MultiParty

Threshold-based multi-signature approval for high-value transactions.

Implementation Flow:

  1. Transaction over threshold held pending

  2. Approval requests sent to designated approvers

  3. Minimum signatures collected within timeout

  4. Transaction executes or declines based on threshold

ZKProof

Zero-knowledge proof validation for transaction privacy.

Privacy Guarantees:

  • Transaction amounts remain private

  • Merchant details encrypted

  • Only proof of valid authorization is public

  • Vault balances never revealed on-chain

Performance Comparison

Proof System
Generation
Verification
Proof Size
Gas Cost

Groth16

~2s

~5ms

128 bytes

Low

PLONK

~5s

~10ms

512 bytes

Medium

STARK

~10s

~20ms

45 KB

Higher

Policy Evaluation

Rule Processing

Decision Latency

  • Off-chain evaluation: < 100ms

  • On-chain verification: < 2s (Solana finality)

  • Total authorization: < 240ms average

Combining Policies

Multiple policies evaluated simultaneously. Transaction must pass ALL checks:

Advanced Features

Dynamic Limits

Contextual limit adjustments based on conditions:

Contextual Authorization

ML-enhanced risk scoring with conditional rules:

Smart Contract Integration

On-Chain Policy Enforcement

Multi-Signature Validation

Monitoring & Analytics

Authorization Metrics

Decline Analysis

Best Practices

1. Start Restrictive

2. Test in Sandbox

3. Monitor Effectiveness

Troubleshooting

Transaction Declined

Next Steps

Last updated