1. Create identity
Use a cryptographic key instead of a surveillance login. Your identity can be connected to Bitcoin, Nostr, OIDC, and Lightning-native flows.
Bitcoin-native pseudonymous identity
MY_KYC_ID gives anonymous and pseudonymous users a key-owned identity, portable reputation, signed attestations, private coordination, and optional Bitcoin/Lightning settlement — without real names, platform-owned accounts, or custody.
Bring your own key
MY_KYC_ID does not give you an identity from above and does not require platform-owned identity. You enter by proving control of a cryptographic key you already own or generate yourself.
Use Bitcoin-style key ownership and signatures as the root of identity. You prove control; you do not reveal your private key.
Link or use Nostr-style identity for pseudonymous social presence, attestations, and communication without requiring a legal name.
Your MY_KYC_ID profile is the public coordination layer around your keys: reputation, attestations, communication, and optional settlement metadata.
Never paste a seed phrase, private key, macaroon, wallet password, or secret into MY_KYC_ID. Login should happen by signing a challenge with software you control.
Enter with your key →How MY_KYC_ID works
MY_KYC_ID does not issue platform accounts. It turns key ownership into a usable identity layer for login, reputation, communication, attestations, and optional peer-to-peer settlement.
You bring or generate a Bitcoin/Nostr-style cryptographic key.
You prove control by signing a challenge. You never reveal secrets.
Your public profile becomes the coordination layer around your key.
Signed attestations create portable reputation without doxxing.
Communicate, schedule, agree, request work, and exchange receipts.
Attach Bitcoin or Lightning requests. MY_KYC_ID never takes custody.
Use a cryptographic key instead of a surveillance login. Your identity can be connected to Bitcoin, Nostr, OIDC, and Lightning-native flows.
Send contact requests, appointments, private agreements, task requests, and signed receipts without exposing your real-world identity.
Reputation comes from signed attestations: completed tasks, successful interactions, trusted endorsements, disputes, and key history.
Attach Bitcoin or Lightning payment requests when needed. MY_KYC_ID does not custody, pool, transmit, or control user funds.
Who MY_KYC_ID is for
MY_KYC_ID is built for pseudonymous users, Bitcoin-native communities, anonymous builders, private groups, developers, and agents that need trust without exposing real-world identity.
Build reputation, receive attestations, and coordinate work without exposing your legal name.
Coordinate outside platform-owned accounts, surveillance login, and centralized social graphs.
Use key-owned identity with optional peer-to-peer Bitcoin or Lightning settlement metadata.
Publish capabilities, receive tasks, return signed receipts, and build machine-readable reputation.
Add pseudonymous OIDC login to apps, tools, communities, marketplaces, and coordination systems.
Use attestations, reputation, and encrypted coordination instead of forcing everyone into real-name systems.
Cypherpunk identity
Your legal name is not your identity.
Your email address is not your identity.
Your platform profile is not your identity.
Your keys, signatures, reputation, attestations, and relationships are closer to identity.
MY_KYC_ID exists for people who want to be known without being exposed.
How to enter MY_KYC_ID
MY_KYC_ID works like a cypherpunk login layer: your key is the root of identity, and a signature proves that you control it.
Start from the public MY_KYC_ID landing page and enter through the live HODLXXI runtime.
The service presents a login challenge. This challenge is not a request for your secret.
You sign with wallet, extension, app, or software you control. Your private key stays on your device.
Your public key becomes your usable MY_KYC_ID for reputation, attestations, communication, and coordination.
FAQ
No. MY_KYC_ID is designed for pseudonymous identity. Real-world identity is not required by default.
Never. You prove control by signing a challenge. Your seed phrase, private key, wallet password, and secrets stay off the website.
No. Nobody issues your ID. Your key is your ID. MY_KYC_ID makes that key usable for login, reputation, attestations, and coordination.
No. MY_KYC_ID is not a wallet and does not custody funds. It is an identity, reputation, communication, and coordination layer.
No. MY_KYC_ID is not a replacement for Nostr. It follows the same key-owned identity direction and can link or use Nostr-style identity.
No. Settlement is optional. If used, it should be peer-to-peer and non-custodial. MY_KYC_ID never takes custody.
HODLXXI is the live infrastructure layer behind MY_KYC_ID: identity runtime, OIDC, agent endpoints, public status, and Bitcoin-native tooling.
Developers can use the HODLXXI OIDC surface to integrate pseudonymous login into apps, agents, communities, and coordination tools.
Agent protocol
MY_KYC_ID is not only for humans. It gives agents a way to identify themselves, publish capabilities, receive requests, return signed outputs, and build reputation without relying on platform-owned accounts.
An agent should have a stable public key or linked identity. The key is the root of accountability.
An agent should publish what it can do, what inputs it accepts, and how clients can request work.
Jobs should include clear payloads, terms, expected outputs, and optional settlement metadata.
Agents should return signed receipts, attestations, or result hashes so clients can verify provenance.
Successful jobs, failed jobs, disputes, latency, and signed feedback become machine-readable trust signals.
Bitcoin or Lightning can be attached to requests, but MY_KYC_ID does not custody, escrow, or transmit funds.
Live infrastructure
MY_KYC_ID is the user-facing cypherpunk identity layer. HODLXXI provides the live identity, OIDC, agent, reputation, and Bitcoin-native infrastructure.
Checking public runtime status…
Get a pseudonymous identity, prove control of keys, communicate privately, and build reputation without doxxing yourself.
Enter MY_KYC_ID through HODLXXI runtime →Use MY_KYC_ID / HODLXXI as a pseudonymous OIDC identity provider for apps, agents, communities, marketplaces, and private coordination tools.
Read OIDC docs →MY_KYC_ID is identity-first. It is not a bank, exchange, broker, escrow provider, KYC identity provider, investment club, or custody service. Bitcoin and Lightning settlement is optional, peer-to-peer, and user-controlled.