Usage Guide & Help Center
Master the Protocol Bank interface. Learn how to manage multi-chain payments, visualize your financial network, and secure your enterprise assets.
Getting Started
Protocol Bank supports a multi-chain environment. To begin, click the "Connect Wallet" button in the top right corner. We support the following wallets:
- Ethereum & EVM: MetaMask, Rabby, Coinbase Wallet.
- Solana: Phantom, Solflare.
- Bitcoin: Unisat, Xverse.
Once connected, the dashboard will automatically sync your balances for USDT, USDC, and DAI across supported networks.
Batch Payments & Advanced Protocols
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.
X402 & ERC-3009 (Gasless)
What is it? ERC-3009 is a standard for "Transfer with Authorization". It allows you to move USDC without holding ETH for gas fees.
- Gasless for Sender: You cryptographically sign an authorization message instead of a transaction.
- Delegated Execution: A third-party relayer pays the gas to submit your transaction.
- How to use: Toggle "x402 Protocol" in the Batch Payment settings. When prompted, sign the typed data message in your wallet.
CCTP (Cross-Chain)
What is it? Circle's Cross-Chain Transfer Protocol (CCTP) enables native USDC transfers between blockchains without traditional lock-and-mint bridges.
- 1:1 Efficiency: USDC is burned on the source chain and minted natively on the destination chain.
- No Slippage: Unlike liquidity pools, you receive exactly what you send (minus network fees).
- How to use: In Batch Payment, simply select a different Destination Chain for any recipient. The system automatically routes via CCTP.
Payment Cost & Efficiency Analysis
| 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 |
Network Visualization
The Wallet Tags (Entity Network) dashboard provides a visual map of your financial relationships.
- Tagging: Assign names and categories (e.g., "Supplier", "Subsidiary") to wallet addresses.
- Interactive Graph: Visualize payment flows as animated particles. Click nodes to view detailed financial history.
- Privacy: All tags are stored locally or encrypted with your user session. Your labeled data is never exposed publicly.
Security Architecture
Protocol Bank employs a multi-layered enterprise-grade security architecture to protect your assets and data before, during, and after transactions.
Principle of Least Privilege
- • Exact Authorization: Each transaction only approves the exact amount needed, avoiding unlimited approvals.
- • Amount Verification: System compares UI-displayed amount with actually submitted amount to prevent tampering.
- • Batch Limits: Maximum $100,000 per transaction, $500,000 per batch.
Rate Limiting
- • Batch Payments: Maximum 3 per hour
- • Single Payments: Maximum 10 per minute
- • API Requests: Automatic detection and blocking of anomalous traffic
Address Validation & Tamper Protection
- • EIP-55 Checksum: Validates mixed-case address format to detect input errors.
- • Homograph Detection: Identifies visually similar malicious characters (e.g., Cyrillic letters).
- • Integrity Hash: Stores address hash values, re-verified before each transfer.
Audit Logging
- • Operation Records: All payments, modifications, and logins are logged.
- • Address Change Tracking: Complete history of vendor wallet address modifications.
- • IP/Device Logging: Anomalous access can be traced.
Transaction Lifecycle Security
Malicious Content Protection
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.
Is Protocol Bank Safe?
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.
Where are my funds held?
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.
Is my data private?
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.
Important: User Responsibility Disclaimer
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:
- Safeguarding your private keys and seed phrases - never share them with anyone.
- Verifying recipient addresses before confirming any transaction.
- Using hardware wallets for large holdings.
- Keeping your browser, wallet extensions, and devices updated and secure.
- Being vigilant against phishing attacks and social engineering.
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.
Advanced Blockchain Security
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.
Proxy Contract Backdoors
Malicious upgradeable contracts can change behavior after deployment.
- • Bytecode analysis for proxy patterns
- • Detection of upgrade functions
- • Verified contract whitelist checking
- • Self-destruct capability warnings
Signature Phishing
Malicious dApps trick users into signing harmful messages.
- • EIP-712 typed data validation
- • Domain name verification
- • Unlimited approval detection
- • Spender address analysis
Flash Loan Attacks
Attackers manipulate prices within a single transaction block.
- • Large transaction warnings
- • Price impact analysis
- • MEV/sandwich attack detection
- • Private mempool recommendations
Cross-Chain Bridge Attacks
Bridge exploits have caused billions in losses.
- • Official CCTP contract verification
- • Destination chain validation
- • Amount limit enforcement
- • Recipient address verification
Double Spending
Duplicate transactions or nonce manipulation attacks.
- • Pending transaction tracking
- • Nonce conflict detection
- • Duplicate transaction warnings
- • 30-second rapid-fire protection
Malicious Approvals
Unlimited token approvals can drain your entire balance.
- • Max uint256 approval detection
- • Exact-amount approval enforcement
- • Existing approval scanning
- • Safe approval calculation
Pre-Transaction Security Check
Before any transaction is submitted to the blockchain, Protocol Bank performs an automated security analysis. You will see a modal displaying:
Risk Assessment
Security Checks
- ✓ Contract Verification
- ✓ Double Spend Protection
- ✓ Flash Loan Risk Analysis
- ✓ Signature Safety (if applicable)
- ✓ Bridge Security (if cross-chain)
Note: Transactions with CRITICAL risk level will be blocked. For HIGH/MEDIUM risk, you must acknowledge the warnings before proceeding.
Transaction Simulation
For complex transactions, Protocol Bank can simulate the outcome before submission usingeth_call. This allows you to preview:
- • Whether the transaction will succeed or revert
- • Estimated gas consumption
- • Potential revert reasons (decoded from error data)