Naming and identity, a hashed and settled trade layer, NFT services, real estate tokenised in the open — and apps that run inside your wallet. Every one of them self-custodial: your keys sign, the public ledger settles, and the private data stays with its owner. Our first implementations run on a coin-set (UTXO) chain; the designs are written to travel to any open chain.
Every application we ship follows one shape: the fact that matters — who holds a name, that a trade settled, that a title changed hands — is committed to an open public blockchain as a hash or a coin anyone can verify. The document, the terms, the personal data stay with the people they belong to and are revealed one field at a time, to one party, when they choose. There is no custodian in the middle, no honeypot to breach, no rake on the way through. We build the platform; you keep the asset.
Each card links to the live application — and most of them also run inside your wallet. The protocols and interfaces are chain-agnostic by design.
A naming layer where a root (.xch, .mojo, .chia, .x) is a coin that can never be sold, the names beneath it are coins people own, and every name is a W3C decentralized identifier (did:namid) you can sign in with. Names resolve only with a proof a wallet verifies against consensus. Application outlet at namidbase.com; the name marketplace at names.cat; the SageX wallet on desktop, CLI and browser.
namid.net → NamIDBase → names.cat →A public–private trade layer. Trades are expressed as offer files: the commitment is public and hashed on chain, the settlement is atomic on chain, the counterparties' details stay private. Today it is a curated, non-custodial offer book (listening to the Splash! network, indexing only verified assets); it is the base for exchange and DeFi services on the roadmap. It never holds a coin.
offerfiles.com →Mint, store and browse NFTs from what is actually on chain — minting is a real spend signed in your own wallet, storage is content-addressed, offers publish where people already look. Issues .chia names to its users and shows a NamID beside every owner.
chianfts.com →A social square where the username is the identity, not an account we hold: every member gets a soulbound .mojo name bound to their key, never transferable, never renewed. Sign in with it, post from it, mint what you make into a vault you hold yourself.
mymojos.com →Real estate, tokenised in the open — India and the United States first. Every project is found, underwritten and listed in public; its documents are hashed on chain and its interests are deed-bound units on a register Web3UTXOS keeps as transfer agent — never an exchange, custodian or broker. Listing 1 is the Lucknow plot; township studies, the Township Manual, site logs and an asset check are published. Information, not an offer: access is requested with a wallet signature, never a payment.
xchfi.com → Listings → Townships →Desktop, CLI and browser extension. Resolves names against the chain rather than a server, signs you in to any NamID-aware site with your name, and keeps roots in a vault with guardian recovery.
Our venues also run inside the wallet as dApps — NamID, NamID Messenger, ChiaNFTs, OfferFiles, MyMojos and XCHFi: preinstalled in SageX, installable in Sage through Sage Apps, and in the official Chia reference wallet through ChiaX, our build of it. On the web, every venue connects to SageX, Sage or the reference wallet over WalletConnect. Nothing is signed without the wallet asking; your keys never leave it.
Get SageX →Each product is also a base other applications stand on — on the web and inside the wallet. What is not open yet is marked coming soon and sits on the roadmap below; we do not sell what is not running.
Ship one static bundle and it runs inside SageX, inside Sage through Sage Apps, and inside the Chia reference wallet through ChiaX — its own origin, its own network allowlist, every request through the wallet's permission dialog. Our venues already run this way.
OfferFiles: public hashed commitments, atomic on-chain settlement, private terms. Any marketplace — names, NFTs, tokenised assets — can settle through it without a custodian. XCHFi's listings and intake already run on it.
NamID names are DIDs any application can accept as a login: the wallet that holds the name signs a challenge, the registry proves the match. OfferFiles, ChiaNFTs and MyMojos already do.
Hash-chained updates for a plot, a building or a project: photos and documents stored by their SHA-256, one owner key per asset, questions answered in public, every chain verifiable in the browser. Running for XCHFi's assets today.
A title, a parcel, a lien, a transfer — committed as coins and hashes on a public chain, documents held by their owners, the registrar's role reduced to a record keeper. XCHFi's transfer-agent register is the first.
Verifiable credentials with selective disclosure: reveal one field to one verifier, revoke instantly, the record's hash anchored on chain and never the data.
Name-to-name payments and N-party channels: lock once, reallocate off-chain, settle once. Scan a QR to pay a name.
Share classes as un-inflatable, identity-bound tokens with vesting enforced by the chain. We run our own this way.
The rules every product follows, whatever chain it runs on.
What is running, what is next, and what is only a plan. Dates are targets; the evidence for each finished item is public.