Skip to Content
TeamK33pFinal Solution

Final Solution: Our Implementation

Solution Overview

Project Name

K33P

Tagline

A human-friendly, self-custodial digital vault for secure ownership, recovery, and inheritance.

The Problem We’re Solving

Self-custody promises ownership, but in reality, millions of users, especially in emerging markets, lose access to their digital assets due to seed phrase mismanagement, device loss, theft, or death. Existing solutions are either too technical, too risky, or assume ideal storage conditions that do not reflect how people actually live and manage their devices. This results in irreversible asset loss, low user confidence, and exclusion from meaningful participation in the blockchain economy.

Our Solution

K33P is a self-custodial, identity-bound digital vault designed for both Web2 and Web3 users to securely store sensitive digital information such as seed phrases, private documents, and critical credentials, without relying on traditional seed phrase recovery.

Built on a zero-trust security model, K33P introduces a privacy-preserving recovery flow and Next-of-Kin (NOK) inheritance mechanism, allowing users to maintain true ownership while ensuring continuity and safety in real-world conditions.

Our solution focuses not just on efficiency, but on reducing systemic loss, lowering technical barriers, and expanding safe self-custody adoption, particularly in environments where traditional key storage is risky or impractical.

Product Features

Core Features

1. Self-Custodial Digital Vault

  • Description: Secure storage for sensitive information including seed phrases, documents, and digital credentials.
  • User Benefit: Users retain full ownership and control without exposing their data to centralized servers.
  • Technical Implementation: Encrypted client-side storage using user-bound cryptographic keys; zero-knowledge access design.

2. Seedless Recovery Flow

  • Description: Account recovery without exposing or relying on static seed phrases.
  • User Benefit: Prevents permanent loss due to forgotten, stolen, or poorly stored seed phrases.
  • Technical Implementation: Multi-factor recovery logic tied to user identity and encrypted recovery shards.

3. Identity-Bound Access Control

  • Description: Vault access is bound to the user, not a transferable private key.
  • User Benefit: Prevents unauthorized access even if a device is compromised.
  • Technical Implementation: Decentralized identity (DID) based access with cryptographic verification.

4. Next-of-Kin (NOK) Inheritance

  • Description: Users can assign trusted beneficiaries who can access vault contents under predefined conditions.
  • User Benefit: Ensures continuity of ownership in cases of death or incapacitation.
  • Technical Implementation: Time-locked and condition-based access controlled via smart contracts.

Additional Features (If implemented)

  • Emergency access triggers
  • Tiered vault permissions

Technical Architecture

Technology Stack

Frontend:

  • React Native (Expo) – Used for mobile application development for Android and iOS, enabling cross-platform native UI
  • Next.js – Used for the web interface and dashboard components
  • Tailwind CSS – Utility-first styling for consistent UI
  • Web Crypto API – Client-side cryptography for secure key operations

Backend:

  • Node.js – Backend runtime for API and business logic
  • Express – Web framework for building REST APIs
  • Secure Key Orchestration Service – Manages encrypted key flows, recovery, and identity-bound access

Blockchain/Smart Contracts:

  • Cardano / Midnight – Target blockchain platform for smart contracts and decentralized logic
  • Aiken – Smart contract language, used to build contract logic such as access control for inheritance features

Database:

  • Encrypted Off-Chain Storage (Iagon) – Secure decentralized storage for vault metadata and encrypted user data

APIs & Integrations:

  • OTP Service – For user verification during secure recovery and onboarding
  • Encryption Key Management – API services to handle secure key creation, rotation, and recovery
  • Notification & Alert Service – To notify users of login, recovery attempts, or vault activity

Architecture Diagram

User
 ↓
Frontend (Client-side encryption)
 ↓
Secure API Layer
 ↓
Smart Contracts (Access & Inheritance)
 ↓
Blockchain
 ↓
Encrypted Storage (Off-chain)

Smart Contracts

Contract 1: Vault Access Contract

  • Purpose: Manages permissions and access rights
  • Key functions: grantAccess(), revokeAccess(), verifyIdentity()

Contract 2: Inheritance Contract (Midnight)

  • Purpose: Handles Next-of-Kin logic
  • Key functions: setBeneficiary(), triggerInheritance(), releaseAccess()

User Experience

User Flow

  1. User creates a K33P account
  2. Identity is verified and cryptographic access is established
  3. User stores sensitive information in the vault
  4. Optional: Assigns Next-of-Kin
  5. Secure access, recovery, or inheritance is executed when needed

Screenshots/Demo

Landing Page: Clear onboarding with trust-first messaging

Main Dashboard: Minimal, safe-style interface for vault management

Key Feature Views:

  • Vault contents
  • Recovery settings
  • NOK configuration

Testing & Validation

User Testing

Number of users tested: 15+
Testing method: Guided usability tests and scenario simulations

Key findings:

  • Users are blown away with the UI and can’t wait to have K33P on launch
  • Inheritance feature increased perceived trust
  • Simpler language improved confidence

Improvements made based on testing:

  • Simplified onboarding flow from feedback
  • Clearer recovery explanations

Technical Testing

  • Unit tests on encryption and access logic
  • Integration tests across frontend and smart contracts
  • Threat modeling and access attack simulations

Impact Metrics

Expected Impact

Quantitative:

  • Onboard 500 users in first 3 months
  • Reduce unrecoverable asset loss by 60%
  • Achieve 70% user retention after 30 days

Qualitative:

  • Increased confidence in self-custody
  • Safer digital ownership
  • Expanded participation in Web3

Success Indicators

  • Reduction in lost accounts
  • Successful recovery events
  • Positive user trust feedback

Deployment

Live Demo: URL coming soon

Repositories:

  • Frontend: Available on K33P Github Repo
  • Backend: Available on K33P Github Repo
  • Smart Contracts: Available on K33P Github Repo

Deployment Status:

  • âś… Frontend deployed
  • âś… Backend deployed
  • âś… Smart contracts on testnet

Business Model

Revenue Streams:

  • Premium vault tiers
  • Enterprise / institutional

Cost Structure:

  • Infrastructure & security
  • Compliance & audits
  • Maintenance & support

Go-to-Market Strategy:

  • Community-first onboarding
  • Partnerships with Web3 communities
  • Education-driven adoption campaigns

Roadmap

Phase 1: MVP (Completed 70%)

  • Vault setup (Create Account)
  • Identity-bound access (On-Chain Proof)
  • Create wallet/Store seed phrase

Phase 2: Post-Hackathon (Next 3-6 Months)

  • Seedless recovery proof-of-concept
  • Next-of-Kin inheritance release
  • Manage KeepLock Update

Phase 3: Scale (6–12 Months)

  • Launch K33P MVP on Android, and onboard first active users
  • K33P’s Trademark and patent applications filed
  • Conduct comprehensive security audits
  • Execute waitlist conversion campaigns

Team Contributions

Sandra Benard: Team Lead/Product Design Lead

Qussim Bakre: Product Information Architect

Precious Omovoiye: Brand Expert

Hadiza Mohammed: Full Stack Developer

Yahaya Abdulrauf: Smart Contract Developer

Challenges & Solutions

Technical Challenge

Problem: Secure recovery without seed phrases
Solution: Identity-bound, encrypted recovery flows

Non-Technical Challenge

Problem: User distrust of self-custody
Solution: Human-centered language and education

Key Learnings

What Worked Well:

  • Ground-up research
  • User experience Security-first design
  • Human-friendly UX

What We’d Do Differently:

  • Earlier testing at scale
  • More automation in recovery simulations

Technical Learnings:

  • Zero-trust systems require UX clarity
  • Recovery is as important as custody

Acknowledgments

Mentors: For guidance and technical review
Next Trend Hub: For ecosystem support
Community participants: For honest feedback

Contact & Demo

Back to Team Overview

Product Features

Core Features (Implemented)

  1. [Feature 1]

    • Description: [What it does]
    • User benefit: [How it helps users]
    • Technical implementation: [Brief tech notes]

  2. [Feature 2]

    • Description: [What it does]
    • User benefit: [How it helps users]
    • Technical implementation: [Brief tech notes]

  3. [Feature 3]

    • Description: [What it does]
    • User benefit: [How it helps users]
    • Technical implementation: [Brief tech notes]

  4. [Feature 4] [Continue for all features]

Additional Features (If implemented)

  • [Feature A]
  • [Feature B]
  • [Feature C]

Technical Architecture

Technology Stack

Frontend:

  • [Technology 1]
  • [Technology 2]
  • [Technology 3]

Backend:

  • [Technology 1]
  • [Technology 2]
  • [Technology 3]

Blockchain/Smart Contracts:

  • [Blockchain platform]
  • [Smart contract language]
  • [Key contracts deployed]

Database:

  • [Database technology]

APIs & Integrations:

  • [API 1]
  • [API 2]
  • [API 3]

Architecture Diagram

[Insert or link to architecture diagram]

[You can use text-based diagram or link to image]
User → Frontend → API → Smart Contract → Blockchain
                    ↓
                 Database

Smart Contracts

Contract 1: [Contract Name]

  • Purpose: [What it does]
  • Key functions: [List main functions]
  • Deployed at: [Contract address if deployed]

Contract 2: [Contract Name] [If applicable]

User Experience

User Flow

  1. [Step 1 - e.g., “User visits landing page”]
  2. [Step 2 - e.g., “User connects wallet”]
  3. [Step 3 - e.g., “User completes profile”]
  4. [Step 4 - Continue through main user journey]

Screenshots/Demo

[Add screenshots or link to demo video]

Landing Page:
[Screenshot or description]

Main Dashboard:
[Screenshot or description]

Key Feature Views:
[Screenshots or descriptions]

Testing & Validation

User Testing

Number of users tested: [Number]
Testing method: [How you conducted testing]

Key findings:

  • [Finding 1]
  • [Finding 2]
  • [Finding 3]

Improvements made based on testing:

  • [Improvement 1]
  • [Improvement 2]

Technical Testing

  • Unit tests: [Coverage or key tests]
  • Integration tests: [What was tested]
  • Smart contract auditing: [Security measures taken]

Impact Metrics

Expected Impact

Quantitative:

  • [Metric 1: e.g., “Serve 500 users in first 3 months”]
  • [Metric 2: e.g., “Process 1000 transactions monthly”]
  • [Metric 3: e.g., “Reduce processing time by 80%”]

Qualitative:

  • [Impact 1: e.g., “Increase financial inclusion”]
  • [Impact 2: e.g., “Build trust in digital systems”]
  • [Impact 3: e.g., “Empower local entrepreneurs”]

Success Indicators

How will you measure success?

  • [Indicator 1]
  • [Indicator 2]
  • [Indicator 3]

Deployment

Live Demo

  • URL: [Link to live demo]
  • Test credentials: [If applicable]

Repositories

  • Frontend repo: [GitHub link]
  • Backend repo: [GitHub link]
  • Smart contracts repo: [GitHub link]

Deployment Status

  • Frontend deployed
  • Backend deployed
  • Smart contracts deployed to testnet
  • Smart contracts deployed to mainnet
  • Domain configured

Business Model (Optional)

Revenue Streams

[If applicable, how will this be sustainable?]

  1. [Revenue stream 1]
  2. [Revenue stream 2]

Cost Structure

[Key costs to maintain the solution]

Go-to-Market Strategy

[How will you reach users?]

Roadmap

Phase 1: MVP (Completed âś…)

  • [Feature 1]
  • [Feature 2]
  • [Feature 3]

Phase 2: Post-Hackathon (Next 3 months)

  • [Feature/Improvement 1]
  • [Feature/Improvement 2]
  • [Feature/Improvement 3]

Phase 3: Scale (6-12 months)

  • [Feature/Improvement 1]
  • [Feature/Improvement 2]
  • [Feature/Improvement 3]

Team Contributions

Division of Work

[Member 1 Name]:

  • [Responsibility 1]
  • [Responsibility 2]
  • [Key deliverable]

[Member 2 Name]:

  • [Responsibility 1]
  • [Responsibility 2]
  • [Key deliverable]

[Member 3 Name]:

  • [Responsibility 1]
  • [Responsibility 2]
  • [Key deliverable]

[Member 4 Name]:

  • [Responsibility 1]
  • [Responsibility 2]
  • [Key deliverable]

[Member 5 Name]:

  • [Responsibility 1]
  • [Responsibility 2]
  • [Key deliverable]

Challenges & Solutions

Technical Challenges

  1. [Challenge 1]

    • Problem: [Description]
    • Solution: [How you solved it]

  2. [Challenge 2]

    • Problem: [Description]
    • Solution: [How you solved it]

Non-Technical Challenges

  1. [Challenge 1]
    • Problem: [Description]
    • Solution: [How you addressed it]

Key Learnings

What Worked Well

  • [Success 1]
  • [Success 2]
  • [Success 3]

What We’d Do Differently

  • [Learning 1]
  • [Learning 2]
  • [Learning 3]

Technical Learnings

  • [Learning 1]
  • [Learning 2]
  • [Learning 3]

Acknowledgments

Thank You

  • Mentors: [Names and how they helped]
  • Next Trend Hub: [Support provided]
  • Community participants: [For interviews and feedback]
  • Other supporters: [Anyone else who helped]

Contact & Demo

Try Our Solution

  • Demo link: [URL]
  • Video demo: [YouTube/Loom link]
  • Pitch deck: [Link to presentation]

Get in Touch

  • Team email: [Email]
  • Twitter/X: [Handle]
  • GitHub: [Organization/user]
  • Discord/Telegram: [Community link]

Appendix

Additional Resources

  • [Link to research data]
  • [Link to user interviews]
  • [Link to technical documentation]
  • [Link to API documentation]

Last updated: [Date]

Back to Team Overview

Last updated on
Define OpportunityFormulate Hypothesis