Create or restore on the device
Recovery material reconstructs wallet identity. On first access, the Financial Profile is created automatically and remains linked to that same identity.
SECURITY · SELF-CUSTODY · ARCHITECTURE
Security built to reduce what can be exposed.
Konebe is designed so the wallet is the user’s cryptographic identity while financial infrastructure keeps only the state required for services. The goal is to reduce the places and situations in which asset-controlling material needs to exist.
Self-custodyLocal signingWallet = identityProtected persistence
KONEBESECURITY MODEL
01
You control the wallet
The recovery mechanism remains under the user's responsibility.
02
Protected local access
Encrypted local access has no scheduled time expiry. Inactivity only locks the screen. Inside the app, local wallet data is removed only after Exit is confirmed on the PIN gate or after 8 consecutive incorrect unlock PIN attempts; browser, operating-system or site-data controls may also remove local storage.
03
Signing in your environment
The private key does not need to travel with the transaction to the network.
04
The blockchain receives the signature
The network validates cryptographic authorization without needing to receive your private key.
HOW IT WORKS
Your wallet identifies you. The Financial Profile follows your services.
The wallet itself proves identity through a cryptographic signature. The Financial Profile is created or recovered automatically for that identity; PIN, biometrics and 2FA are protection layers and do not replace the recovery phrase.
Local PIN protection
A PIN protects convenient local access in that browser or PWA. It is not a backup and does not replace recovery material.
The transaction is signed locally
For supported operations, the wallet uses the key in the local environment to produce a valid signature. The private key does not need to be sent with the transaction.
The network receives only what is needed
The blockchain receives the public operation data and the cryptographic signature needed to validate it — not the key used to create that signature.
SECURITY
Security through minimization, not concentration.
A self-custody architecture becomes more resilient when operational services minimize secrets and use the wallet’s own signature to prove identity. Supported user transactions are signed locally, and operational services do not act as a master signing or wallet-recovery authority.
No operational wallet master key
Operational wallet services do not use an administrative credential to sign user transactions or reconstruct user wallets. Product and support operations do not act as a master signing or wallet-recovery authority.
Wallet as identity
The Financial Profile is linked to the wallet’s public identity and does not store the recovery phrase or replace the user’s cryptographic signature.
Protected local persistence
Encrypted local access has no scheduled time expiry. It remains until Exit is confirmed on the PIN gate, 8 consecutive incorrect unlock PIN attempts remove the local wallet, local site/PWA data is cleared, or the device/browser removes that storage.
Support without taking your key
Support can help with the Financial Profile, interface, networks, transactions and recovery guidance. It does not need to receive your recovery phrase or private key to provide support.
ARCHITECTURE COMPARISON
Where Konebe adds a different layer of protection.
No wallet is superior in every scenario. Different architectures address different threat models. Konebe separates wallet signing from server-side product orchestration, encrypts local persistence, and keeps authorization for supported self-custody transactions in the wallet’s own cryptographic signature.
| Characteristic | Custodial | Traditional software wallet | Konebe |
|---|---|---|---|
| User retains the primary recovery mechanism | Varies | Usually | Yes |
| Local signing for supported transactions | Usually no | Common | Yes |
| Profile/PIN are the blockchain key | Can be | Not applicable | No |
| Encrypted local access without scheduled expiry | Varies | Not standard | No time expiry |
| Administrative recovery of the user's key | Often possible | Usually no | No |
HW
What about hardware wallets?
A good hardware wallet adds dedicated physical isolation and can provide stronger protection when the computer or phone is compromised. Konebe has a different goal: deliver multichain self-custody in software while reducing centralization and protecting local persistence without hiding the limits of a PWA wallet.
WHAT THIS MODEL REDUCES
Fewer single points where one failure can escalate.
Infrastructure compromise
An incident in central services should not automatically equal disclosure of every wallet's private keys.
Old or abandoned device
Protected local access has no scheduled expiry. Before abandoning or transferring a device, lock the app, return to the PIN gate, choose Exit and confirm the local data removal.
Financial Profile
The Financial Profile stores service state linked to the wallet’s public identity; it does not contain the wallet recovery phrase or private key.
Improper internal access
Support and routine product operations are not a wallet-recovery or signing authority. Users should never manually send a recovery phrase or private key to support, forms, social channels, or third parties.
SELF-CUSTODY IS NOT INVINCIBILITY
No software wallet can protect a fully compromised environment.
Malware, phishing, malicious extensions, keyloggers, fake sites, clipboard hijacking and a compromised operating system remain real risks. Architecture can reduce classes of risk; it cannot make the device invulnerable.
Never manually send your recovery phrase to support, forms, social channels or third parties.Never send a private key to support.Never transfer funds to “verify” a wallet.Verify network, asset and destination before signing.
Security without custody.
Konebe operational services are designed to provide product infrastructure without acting as the signing or recovery authority for your wallet. Supported self-custody transactions remain authorized by the wallet’s own cryptographic signature.
No operational wallet master keyNo administrative wallet recoveryLocal signingReal self-custody
Open Konebe →