BankNode
Security

Security Factors

BankNode distributes key generation, key shares, and transaction authorization across independent participants to reduce single-key and single-node failure risk.

hub

Distributed Key Generation

Each participant creates its own contribution during DKG; no node creates the complete private key.

Protocol Layer
grid_view

Distributed Key Storage

Each node stores only its local key share, reducing the impact of a single-node compromise.

Storage Layer
no_accounts

Zero Client Exposure

Client applications do not store signer key shares; signing remains within the participant infrastructure.

Access Layer
handshake

Consensus Transaction Authorization

A transaction requires cooperation from two authorized participant nodes.

Execution Layer
settings_backup_restore

Distributed Redundancy

A wallet remains signable while any two of its three participant nodes are available.

Recovery Layer
shield_lock

Threat & Error Mitigation

Protocol checks and participant separation reduce the impact of external compromise and operational error.

Protection Layer
trending_flat

Deployment Scalability

Independent wallet groups and signer-node deployments can be added without changing the underlying 2-of-3 signing model.

Risk Layer
settings_suggest

Post-Quantum Readiness

Protection against future quantum-computing threats is considered at the blockchain-protocol level.

Protocol Layer
High-end server room
Infrastructure Status
Test Environment Monitored

AI-Assisted Security Review

The Bitcoin Schnorr and Ethereum threshold ECDSA implementations were reviewed with Claude Mythos and GPT-5.6 as AI-assisted analysis tools. This review does not replace an independent professional security audit.

  • check_circle AI-assisted review of threshold-signature control paths
  • check_circle Validation of custody-layer separation and failure isolation assumptions
  • check_circle Scenario analysis for operational, cryptographic, and governance edge cases