Security & Privacy
How NodeMatrix protects your keys and data
Critical Security Notice
NodeMatrix handles private keys for blockchain operations. While we implement industry-standard security practices, you should never store more funds in connected wallets than you're willing to risk. Always use dedicated trading wallets.
Private Key Security
Local-Only Storage
Private keys never leave your browser
- • Keys stored in browser localStorage
- • Never transmitted to servers
- • Cleared on logout/cache clear
Transaction Signing
All signing happens client-side
- • Transactions signed in browser
- • Only signed TX sent to RPC
- • Raw keys never exposed
Data Privacy
What We Store
- ✓ Flow configurations (node layout, connections)
- ✓ Non-sensitive settings (gas preferences, UI state)
- ✗ Private keys (never stored server-side)
- ✗ Wallet balances (fetched on-demand)
- ✗ Transaction history (on-chain only)
Security Best Practices
1
Use Dedicated Wallets
Create separate wallets for NodeMatrix operations. Never use your main holdings wallet.
2
Start Small
Test workflows with minimal amounts before scaling up operations.
3
Verify Transactions
Always review transaction details before execution, especially for large amounts.
4
Secure Your Browser
Use a clean browser profile. Avoid suspicious extensions that could access localStorage.
5
Regular Audits
Periodically review connected wallets and remove any you no longer use.
MEV Protection
bloXroute Integration
NodeMatrix integrates bloXroute MEV protection to shield your transactions from front-running and sandwich attacks. Enable it in the Multi Wallet node settings.