Master the Protocol Bank interface. Learn how to manage multi-chain payments, visualize your financial network, and secure your enterprise assets.
Protocol Bank supports a multi-chain environment. To begin, click the "Connect Wallet" button in the top right corner. We support the following wallets:
Once connected, the dashboard will automatically sync your balances for USDT, USDC, and DAI across supported networks.
The Batch Payment tool allows you to send multiple transactions in a single session. Protocol Bank integrates advanced standards to optimize for cost, speed, and cross-chain interoperability.
What is it? ERC-3009 is a standard for "Transfer with Authorization". It allows you to move USDC without holding ETH for gas fees.
What is it? Circle's Cross-Chain Transfer Protocol (CCTP) enables native USDC transfers between blockchains without traditional lock-and-mint bridges.
| Payment Method | Network | Avg. Cost (USD) | Settlement Time |
|---|---|---|---|
| Standard Transfer (ERC-20) | Ethereum Mainnet | $2.00 - $15.00+ | ~12 sec (1 Block) |
| x402 Protocol (ERC-3009) | Ethereum Mainnet | $0.00 (Gasless for User) | Instant Signature |
| CCTP Cross-Chain | Eth ↔ Base/Op/Arb | ~ $0.50 (Gas only) | ~13 mins (Finality) |
| Layer 2 Transfer | Optimism / Arbitrum | $0.01 - $0.10 | ~2 sec |
| Solana Transfer | Solana | < $0.001 | ~400 ms |
| Bitcoin Transfer | Bitcoin Network | $1.50 - $5.00+ | ~10 - 60 min |
The Wallet Tags (Entity Network) dashboard provides a visual map of your financial relationships.
Protocol Bank employs a multi-layered enterprise-grade security architecture to protect your assets and data before, during, and after transactions.
Malicious Text / Garbage Data
Automatically filters invisible characters, zero-width characters, control characters.
Malicious Contract Addresses
Checksum validation + optional blacklist checking.
Injection Attacks
SQL/XSS/script tags completely filtered.
Yes. We operate on a strict Zero-Trust / Client-Side Execution model. The application runs entirely in your browser. Your private keys are managed solely by your wallet (MetaMask, Ledger, etc.) and are never exposed to our servers. We cannot access or move your funds.
Your funds always remain in your own non-custodial wallet or on the blockchain itself. Protocol Bank is simply an interface (a "frontend") to interact with the blockchain. We do not hold user deposits.
Blockchain Data: All transactions are public on the blockchain. This is the nature of Web3.
Metadata (Tags & Notes): Your custom data (Vendor Names, Categories, Notes) is encrypted and stored separately. We utilize Row-Level Security (RLS) to ensure that only your authenticated wallet address can read or write this data.
While Protocol Bank implements robust security measures to protect you from common risks, you are ultimately responsible for your own security. This includes but is not limited to:
Protocol Bank provides tools and safeguards, but cannot be held liable for losses resulting from user negligence, compromised devices, phishing attacks, or actions outside our control. Cryptocurrency transactions are irreversible. Please proceed with caution.
Protocol Bank implements cutting-edge protections against sophisticated blockchain attack vectors. Our pre-transaction security analysis automatically scans for these threats before any funds leave your wallet.
Malicious upgradeable contracts can change behavior after deployment.
Malicious dApps trick users into signing harmful messages.
Attackers manipulate prices within a single transaction block.
Bridge exploits have caused billions in losses.
Duplicate transactions or nonce manipulation attacks.
Unlimited token approvals can drain your entire balance.
Before any transaction is submitted to the blockchain, Protocol Bank performs an automated security analysis. You will see a modal displaying:
Note: Transactions with CRITICAL risk level will be blocked. For HIGH/MEDIUM risk, you must acknowledge the warnings before proceeding.
For complex transactions, Protocol Bank can simulate the outcome before submission usingeth_call. This allows you to preview: