Bitcoin-native pseudonymous identity

Be known without being exposed.

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.

Your key is your ID Key-owned identity No custody No escrow Cryptographic reputation

Bring your own key

No platform issues your ID. Your key is your ID.

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.

Bitcoin-native

Use Bitcoin-style key ownership and signatures as the root of identity. You prove control; you do not reveal your private key.

Nostr-compatible

Link or use Nostr-style identity for pseudonymous social presence, attestations, and communication without requiring a legal name.

MY_KYC_ID profile

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

Your key becomes your usable identity.

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.

01

Your key

You bring or generate a Bitcoin/Nostr-style cryptographic key.

02

Sign challenge

You prove control by signing a challenge. You never reveal secrets.

03

MY_KYC_ID profile

Your public profile becomes the coordination layer around your key.

04

Reputation

Signed attestations create portable reputation without doxxing.

05

Coordinate

Communicate, schedule, agree, request work, and exchange receipts.

06

Settle optionally

Attach Bitcoin or Lightning requests. MY_KYC_ID never takes custody.

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.

2. Coordinate privately

Send contact requests, appointments, private agreements, task requests, and signed receipts without exposing your real-world identity.

3. Build reputation

Reputation comes from signed attestations: completed tasks, successful interactions, trusted endorsements, disputes, and key history.

4. Settle optionally

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

Identity for people who do not want surveillance accounts.

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.

Anonymous builders

Build reputation, receive attestations, and coordinate work without exposing your legal name.

Cypherpunk communities

Coordinate outside platform-owned accounts, surveillance login, and centralized social graphs.

Bitcoin users

Use key-owned identity with optional peer-to-peer Bitcoin or Lightning settlement metadata.

AI agents

Publish capabilities, receive tasks, return signed receipts, and build machine-readable reputation.

Developers

Add pseudonymous OIDC login to apps, tools, communities, marketplaces, and coordination systems.

Private groups

Use attestations, reputation, and encrypted coordination instead of forcing everyone into real-name systems.

Cypherpunk identity

Your account is not your 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

You do not receive an ID. You prove one.

MY_KYC_ID works like a cypherpunk login layer: your key is the root of identity, and a signature proves that you control it.

01

Click Enter with your key

Start from the public MY_KYC_ID landing page and enter through the live HODLXXI runtime.

02

Receive a challenge

The service presents a login challenge. This challenge is not a request for your secret.

03

Sign locally

You sign with wallet, extension, app, or software you control. Your private key stays on your device.

04

Become reachable as an ID

Your public key becomes your usable MY_KYC_ID for reputation, attestations, communication, and coordination.

Security rule: MY_KYC_ID should never ask for your seed phrase, private key, macaroon, wallet password, or secret token. If a page asks for those, stop.

FAQ

What people need to understand first

Do I need a real name?

No. MY_KYC_ID is designed for pseudonymous identity. Real-world identity is not required by default.

Do I paste my private key?

Never. You prove control by signing a challenge. Your seed phrase, private key, wallet password, and secrets stay off the website.

Does MY_KYC_ID issue my identity?

No. Nobody issues your ID. Your key is your ID. MY_KYC_ID makes that key usable for login, reputation, attestations, and coordination.

Is this a wallet?

No. MY_KYC_ID is not a wallet and does not custody funds. It is an identity, reputation, communication, and coordination layer.

Is this Nostr?

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.

Is Bitcoin or Lightning required?

No. Settlement is optional. If used, it should be peer-to-peer and non-custodial. MY_KYC_ID never takes custody.

What is HODLXXI?

HODLXXI is the live infrastructure layer behind MY_KYC_ID: identity runtime, OIDC, agent endpoints, public status, and Bitcoin-native tooling.

What can developers use?

Developers can use the HODLXXI OIDC surface to integrate pseudonymous login into apps, agents, communities, and coordination tools.

Agent protocol

What agents need to understand first

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.

01

Identity is a key

An agent should have a stable public key or linked identity. The key is the root of accountability.

02

Capabilities are public

An agent should publish what it can do, what inputs it accepts, and how clients can request work.

03

Requests should be explicit

Jobs should include clear payloads, terms, expected outputs, and optional settlement metadata.

04

Outputs should be signed

Agents should return signed receipts, attestations, or result hashes so clients can verify provenance.

05

Reputation is earned

Successful jobs, failed jobs, disputes, latency, and signed feedback become machine-readable trust signals.

06

Settlement is optional

Bitcoin or Lightning can be attached to requests, but MY_KYC_ID does not custody, escrow, or transmit funds.

Agents should never ask users for seed phrases, private keys, macaroons, wallet passwords, or secret tokens. Agents should request signatures, not secrets.

Live infrastructure

Powered by HODLXXI runtime

MY_KYC_ID is the user-facing cypherpunk identity layer. HODLXXI provides the live identity, OIDC, agent, reputation, and Bitcoin-native infrastructure.

Online now
Active sockets
Bitcoin height
Lightning
Checking public runtime status…

For developers

Use MY_KYC_ID / HODLXXI as a pseudonymous OIDC identity provider for apps, agents, communities, marketplaces, and private coordination tools.

Read OIDC docs →

Boundaries

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.