RBM Product Roadmap

Phase 1 → Initial MVP & Adoption Growth

  • Marketing campaign for protocol adoption and initial traction: hack our protocol! (bounty)
  • Deployment of the RBM protocol protecting BlueChip NFT collections (ERC-721) on ETH Mainnet → opt-in with % fee based on asset value
  • Integration of Zama Confidential tokens to funnel out assets
  • Deployment of the Fungibles protection in the RBM protocol on ETH Mainnet

Phase 2 → Ecosystem Expansion to Solana & Marketplace Integrations

  • Deployment of RBM protocol for NFTs & fungible tokens protection on Solana
  • Operator1 → integration of RBM protected assets in a Solana NFT marketplace
  • Integration of SDK/Stack in Web3 Studios/Brands infrastructure (B2B2C: protection as a service)
  • Distribution of our RBM semi-fungible (DiBs) token release (pre-TGE) with trading phase

Phase 3 → Cross-chain (EVM) Expansion & New Asset Types

  • RBM expansion across all EVMs (L2s) for both NFTs & Fungibles
  • Coverage of Web3 gaming assets (SFTs ERC-1155) & brands tokenised assets (NFTs) in the RBM protocol (Mainnet: ETH & SOL)
  • Operator2 → integration of RBM protected assets in an NFT marketplace (ETH)
  • Deployment of semi-fungibles (SFTs ERC-1155) coverage to EVM chains (L2s)

Phase 4 → DeFi Integrations, Full Decentralization & Advanced Token Assets

  • Deployment of composable semi-fungible RBM-protected assets (ERC-3525)
  • Operator3 → integration in DeFi platforms (ETH/SOL Mainnets) for composables
  • Coverage of RWA, bonds, and other tokenised formats in the RBM protocol
  • Decentralisation of the RBM infrastructure (distributed via nodes for reliability avoiding single point of failure)

LockerApp Product Roadmap

Phase 1 → Cross-Platform Foundation & Strong Local Security

  • Independent third-party cryptographic & security audits before public launch
  • Bounty program: "Break LockerApp" → public security challenge post-audit
  • Ship production-ready LockerApp for Windows and Linux with consistent cryptographic behavior across OS environments
  • Introduce hardware-based authentication support (YubiKey + biometric passkeys) as optional additional unlock factors

Phase 2 → Mobile Expansion & Device Trust Architecture

  • Launch mobile version (iOS/Android) with biometric integration (FaceID / fingerprint)
  • Implement device whitelist system using per-device UUID binding and optional approval workflow
  • Release USB-based unlock mechanism (hardware-bound key access, integrated into device trust architecture)
  • Introduce secure inter-device sync logic → end-to-end encrypted locally, no server relay, vault identity consistency without weakening encryption model

Phase 3 → Secure Backup, TEE Infrastructure & B2B Seed

  • Deploy optional online encrypted backup via Trusted Execution Environment (TEE) infrastructure with recovery validation workflow
  • Introduce vault redundancy architecture for disaster recovery scenarios
  • Provide advanced session security modes (configurable memory retention, stricter auto-lock models)
  • Release B2B API/SDK for enterprise secrets management integration → allow businesses to embed LockerApp vault as a service

Phase 4 → Advanced Cryptographic Capabilities & B2B Expansion

  • Launch LockerVault ZK/FHE computation modules for monitoring rotation of API keys, private keys, and secrets without revealing plaintext (research-track deliverable → performance-gated release)
  • Enable ZK-signature workflows for transaction authorization using FHE computation over vault-stored keys & programmable vault modules for secure key orchestration across systems
  • Introduce post-quantum cryptographic primitives (CRYSTALS-Kyber / CRYSTALS-Dilithium) ahead of the 2030 NIST PQC transition → future-proof vault encryption layer
  • Full B2B expansion: enterprise licensing, DevOps/SecOps integrations (CI/CD pipeline secrets, infrastructure key management)