Eleven networks,
one iPhone view.
Including native Bitcoin and Solana.
Automated tests cover wallet cryptography, signing, transaction, and record paths.
KYKY Labs / User-held keys
The self-custodyfinance company.
KYKY Labs builds financial software around user-held keys. KYKY Wallet brings that model to iPhone and browser clients; KYKY Names adds a public, controller-signed record.
Every name points to a controller-signed record. Public profiles are server-checked and readable without an app.
Three to twenty characters. Start with a letter; use lowercase letters, numbers, and single underscores.
USER-HELD KEYSIPHONE CLIENTBROWSER EXTENSION
CONTROLLER-SIGNED NAMESNO ANALYTICS OR TRACKING SDKS
01
The product constellation
One company / three product surfaces
Control should travel
with the person.
KYKY begins with one wallet implemented for two local client environments, plus a signed-name system that remains readable on the public web. KYKY Assurance documents the checks and limitations underneath all three.
01 / NATIVE CLIENT
KYKY Wallet
for iPhone
for Chromium
Names
for iPhone
Eleven-network portfolio, native Bitcoin and Solana, transaction review, and supported hardware-signing flows.
EXPLORE IPHONE 02 / BROWSER CLIENT KYKY Walletfor Chromium
Dapp connection, per-origin permissions, pinned networks, separate approvals, and a full-tab workspace.
EXPLORE BROWSER 03 / SIGNED NAMES KYKYNames
A readable financial handle backed by a controller-signed public record with an explicit verification boundary.
EXPLORE NAMESKYKY ASSURANCE
Checks, limitations, and transaction boundaries beneath every product surface.
OPEN THE TRUST MODEL02
Product one / KYKY Wallet
One wallet / two local clients
From pocket
to browser.
KYKY Wallet is implemented for iPhone and Chromium browsers. The client surfaces differ, but both are built around a local wallet boundary and an explicit review before signing. Distribution links appear only when an official listing is configured.
KYKY / IPHONELOCAL WALLET
PORTFOLIO OVERVIEW
Assets under your key
Account values intentionally omitted from this demonstration.
EVMBITCOINSOLANA
RECEIVEMOVETRADE
Illustrative information architecture. No account, balance, quote, projection, or performance data is shown.
KKKYKY BROWSERLOCAL CLIENT
SITE REQUESTConnected origin shown here
REQUEST BOUNDARY
The page requests.
The page requests.
The wallet approves.
ACCOUNT ACCESSPer origin
NETWORKPinned before review
SIGNINGSeparate approval surface
REJECTREVIEW IN WALLET
Illustrative client structure based on the existing Chromium extension. Distribution links are shown only when officially configured.
Eleven networks,
Per-origin browser
permissions.
A site receives an account only after approval.
Available route
details in view.
Minimum received and estimated fees before approval.
The signer gets
the final word.
Device authentication or hardware confirmation, by path.
Digital assets can lose value, transactions may be irreversible, and losing recovery credentials can mean losing access. KYKY Labs does not provide investment advice.
03
KYKY Names / the signed object
Readable name / named controller
A handle with
a cryptographic edge.
A KYKY profile checks the displayed record against the controller named inside it before supported fields render. That is a key-to-record check, not proof of a person, organization, handle history, or payment purpose.
KYKY-NAME-RECORD-V1
name@maya
controller0x7a31…91c0 · neutral demo key
addreip155:* · one address, every EVM network
web rulecase-sensitive V1 destinations withheld
sequence000004
updatedcontroller-signed field
DEMO RECORD · CONTROLLER SIGNATURE CHECK REQUIRED
The canonical record format with neutral demonstration data. No user address is shown.
04
Public profiles / proof with limits
PUBLIC / CHECK 001
DEMO RECORD / PASS-STATE PREVIEW
Maya Chen
@maya · Personal
A valid controller signature renders this state
Resolve an EVM name
For a supported EVM network, open KYKY and resolve @maya.
The wallet shows the destination published for that network.
Receives on
All EVM networks · 0x7a31…91c0
Case-sensitive V1 destinations · withheld on web
Illustrative profile data, not a live @maya record. The production renderer checks the record against its named controller and ships zero client JavaScript.
Readable in any browser
The check is visible.
So is its boundary.
The public renderer checks the record signature against the controller named in that same record. The delivered profile page runs no client JavaScript, and V1 address types whose exact case cannot be authenticated are withheld from the web.
THE CHECK ESTABLISHES
Record ↔ named controller
The renderer checks that the displayed canonical record was signed by the controller named inside that record.
THE CHECK DOES NOT ESTABLISH
Person, history, or purpose
It does not independently prove a real person, organization, handle history, payment purpose, or that a recipient is safe.
05
KYKY Assurance / trust architecture
Check / limit / decide
Security without
the mythology.
KYKY documents the checks performed by each surface, the data those checks cover, and the conclusions they cannot establish. Controls reduce risk; they do not eliminate it.
Tests
Conformance
Signing is held to golden vectors: known inputs, byte-exact expected outputs.
Internal adversarial review
Value-movement paths receive dedicated internal adversarial review.
Privacy as practice
No analytics or tracking SDKs are included in KYKY Wallet.
KYKY Labs
Keep the keys.
Understand the system.
Check a name or explore the wallet built for iPhone and browser clients.
Every name points to a controller-signed record. Public profiles are server-checked and readable without an app.
Three to twenty characters. Start with a letter; use lowercase letters, numbers, and single underscores.