A browser wallet for MobileCoin and Ethereum. No accounts. No tracking. No compromise.
Get the WordPress PluginOne wallet. Two chains. Zero compromise on privacy or access.
From install to first transaction in under a minute.
Add Kyoto to Chrome. Create a wallet with a 6-digit PIN. That's it. No email, no account, no phone number.
MobileCoin transactions use ring signatures and encrypted fog. Nobody sees your balance or history — not even us.
Use Kyoto as your Ethereum wallet on any dApp. Uniswap, Aave, OpenSea — it all works. One wallet, two worlds.
Three lines of code. No SDK, no API key, no backend. The Kyoto payment API lets any website request MobileCoin payments directly from the browser.
Read the docsconst result = await window.kyoto.requestPayment({ recipientB58: '3Uf7Kz9...', amount: '1000000000000', // 1 MOB memo: 'Order #1234' }); // Listen for confirmation window.addEventListener('kyoto-payment-update', e => { const { status, txId } = e.detail; });
Every design decision starts with the same question: what if we get hacked?
Your PIN is protected by hardware security modules. Five wrong guesses and the wallet locks permanently. No server knows your PIN — it's split across independent HSMs using threshold cryptography.
Unlock with your face or fingerprint. WebAuthn PRF derives encryption keys from your biometric — the key never exists outside the secure enclave. Every transaction requires a fresh biometric challenge.
No analytics. No telemetry. No IP logging. Kyoto uses anonymous authentication tokens (VOPRF) so we can't tell users apart even if we wanted to. Your usage patterns stay yours.
Every line of code is public. The cryptographic core is written in Rust and compiled to WebAssembly. Auditable, forkable, verifiable. Don't trust us — read the code.