Skip to main content
Trust in a sovereign protocol must be earned through transparency and rigorous testing — not marketing claims. This page documents the threat scenarios our architecture is designed to survive, the cryptographic primitives we rely on, and how to reach us if you discover a vulnerability.

​
Threat architecture

Our architecture is designed to remain functional under extreme adversarial conditions. Each scenario below describes a real threat and the technical reason it cannot compromise your data.
If Inheribase ceases operations, the protocol continues without us. Storage costs are paid entirely upfront via the Arweave endowment model, and the smart contracts governing access are immutable — no organizational continuity is required to keep them running.
We cannot be legally compelled to reveal your data because we do not possess your keys. Encryption and decryption happen entirely client-side. A court order served to Inheribase produces only encrypted blobs, which are mathematically useless without the keys that only you and your guardians hold.
A leak of our database exposes only encrypted blobs and non-sensitive metadata. Your files remain protected by AES-256-GCM encryption. Without the split guardian key shares (distributed via Shamir’s Secret Sharing), a database breach yields nothing an attacker can use.
Even complete physical destruction of our servers does not affect the Base network or the Arweave permaweb. Your rules and your data live on infrastructure that operates independently of anything we own or manage.

​
Live contract verification

We believe security through obscurity is a vulnerability in itself. Our smart contracts are fully verified and readable on the blockchain — anyone can audit the exact logic that governs access to your vault. The InheribaseAnchor contract is deployed and verified at address 0xf43e5cC7a7fCF115B573CfF92273B762Bb12C3c7 on BaseScan. You can review the compiled source code there at any time, with no account required.

​
Cryptographic supply chain disclosure

We do not invent cryptography. The protocol relies exclusively on federal-standard primitives with well-established security proofs. The table below documents every cryptographic component in use.
PrimitiveImplementationPurpose
AES-256-GCMNative Web Crypto APIAuthenticated symmetric encryption of all vault assets
SHA-256Native Web Crypto APIImmutable data integrity verification (file hashing)
Shamir’s Secret SharingBattle-tested polynomial interpolationDistributing decryption key shares across M-of-N guardians
Using the browser-native Web Crypto API means cryptographic operations are handled by your device’s optimized, audited runtime — not by third-party JavaScript libraries that could introduce supply chain risk.

​
Vulnerability disclosure program

We actively engage with the security research community. If you have discovered a potential vulnerability in the Inheribase protocol, please submit your findings to our dedicated security contact. We enforce strict SLAs for responding to, verifying, and patching any disclosed vulnerability:
  • Initial acknowledgment: within 48 hours of submission.
  • Triage and severity assessment: within 5 business days.
  • Patch or mitigation: timeline communicated based on severity, prioritizing critical issues immediately.
Responsible disclosure benefits everyone who relies on this protocol. We take every report seriously and will work with you throughout the remediation process.