Skip to content

Security: DigitalGekko77/bnns-protocol

SECURITY.md

Security Policy

BNNS is research software and must not be used with real funds.

Publicly report design flaws that do not endanger deployed funds through a GitHub issue. Do not publish wallet seeds, API keys, private keys, real customer data, or exploitable details affecting an unrelated production system.

The reference model performs accounting only. It does not create valid Bitcoin or Lightning contracts and provides no custody guarantee.

The local MVP hard-blocks mainnet and generates disposable test identity keys inside its SQLite database. Those keys are not production wallet keys and must never receive value. Its built-in settlement button is a simulation. The separate pinned Taproot Assets runner creates only isolated regtest evidence and keeps its runtime under /Volumes/Storage/Projects/bnns-runtime.

The pure-Python BIP-340 module is test-oriented, passes an official test vector, and has not received a cryptographic audit. A real-funds implementation would need an audited signing library, external wallet signing, public RPC adapters, adversarial review, and a new security policy.

There aren't any published security advisories