A white paper on 54: the problem it solves, how it is built, how money moves, what it guarantees and what it does not do yet. Every price and number on this page comes from the same code that charges, so it cannot say anything other than what the product does.
Updated: October 12, 2026
Abstract
54 is a protocol for being on the internet without technical middlemen: you describe what you want, the system builds it, publishes it on your domain, takes payments for you and grows it with agents. Each piece (generate, store, charge, index, serve) is a protocol service with rules written in code, not a support promise.
One sentence is enough for a working site, with data, visitors and its own address.
Money moves on the server, charged up front with an exact refund of whatever was not delivered.
Published sites can be served from a network of nodes that keep copies verified by their fingerprint.
The people who use the network decide: votes weigh in Lust, the currency earned by holding up the network.
The problem
Having a site that sells still means stitching five or six providers together: a builder, hosting, a domain, mail, a payment gateway, an SEO tool and someone to maintain it. Every seam between them is a place where something breaks silently.
An AI builder rewrites what was working and does not say so.
A site that "takes payments" sometimes only records that someone wanted to pay.
A search engine does not index what the browser builds with JavaScript.
And everything depends on a single server staying up.
Architecture
54 has three layers. Gates receive each request, know who the person is and whether they can do what they ask. Capabilities each do one thing (raffles, members, crypto payments…) and are registered in one place. And the database keeps the state, with money operations as transactional functions.
A site is a saved version plus its data: each change creates a new version and none is lost.
What a visitor is served is assembled on the server (readable body, sitemap, llms.txt), so a search engine or an AI reads it without running anything.
Capabilities are injected when serving: the story reader, the gallery, photos and comments work on any site without touching its code.
The same platform serves the editor, the API with keys and the 54 app inside ChatGPT.
Building your site
Write what you want in one sentence and 54 builds the site: a working page with its own 54.wtf address, its data and its visitors. Then you keep changing it by talking: "make the logo bigger", "add a pricing page".
A request with several changes is done one at a time; if one fails, the rest stays in the box so you can continue.
Every save is a version. You can go back to the published one or the previous one at no cost.
A change does not take away what you did not ask to remove: if a table, a form, an image or the title would disappear, 54 puts it back or tells you.
A change that would break the site is not delivered: the site stays as it was and the coins come back.
You can bring a site made elsewhere (upload a ZIP, or «Bring it from another site» with a public address or your Vercel account) and download yours as a ZIP.
Plans and coins
Without a plan you get 3 AI requests a day. After that, each one costs ◎3.
Basic ◎99 a month, Pro ◎390 and Unlimited ◎990. Each plan adds daily requests, storage, version history and your own domain.
The site's AI (the assistant, SEO, documents) is included: ◎50 a month on Basic, ◎200 on Pro and ◎600 on Unlimited. Anything above that is paid from your coins.
A site's first domain comes with 30 free days of Basic. It expires on its own; it never charges.
From each site's Studio you connect a domain you already own or buy one right there. The www version sends visitors to the other with a permanent redirect, the way Google prefers.
Mail on your domain (hello@yourdomain): read and answer it in the Mails tab, with keyboard shortcuts like a desktop inbox.
An AI filter sorts what arrives: To reply, Important, Promotions and Spam.
You can give a person access to only some mailboxes (the 👥 on each mailbox). They see and answer those and nothing else.
If you want it in Gmail, ask for forwarding: it only starts once that address clicks the confirmation link.
Getting paid
A site charges in your own Stripe account (site Studio → payments). Nobody at 54 sees card numbers.
What you sell is declared by the site and loaded automatically when you publish. You set the price, never the visitor.
Raffles, auctions and loyalty points run on the server: tickets, who wins and what comes back as credit do not depend on the browser.
Cash or transfer sales are entered from the site's /admin.
Notices → Income shows what came in over 12 months by site, month and payment method, and what Stripe has not paid out yet.
Media: images, music, video and NFTs
Images: ◎1 fast, ◎2 standard, ◎4 high. You are charged first and get back exactly what did not come out.
Music: a clip of about 30 seconds ◎2, a song ◎6. You can also upload your own track, declaring it is yours.
8-second video: ◎15 fast, ◎40 high. It takes a few minutes; if it fails, the coins come back.
Edit with AI (in Videos): upload up to 6 clips and pick a track from Music; it cuts on the beats and adds the music. ◎5; if it fails, the coins come back.
Documents: ask for a report, a proposal or a letter and the AI writes it; edit it in place and download it as PDF. Lite free, Smart ◎1, Genius ◎2; if nobody answers, you get it back.
Presentations: ask for a pitch, a class or a report and the AI builds the slides; flip through them, edit them and download them as a landscape PDF. Same price as a document.
Designs: ask for a poster, a post, a flyer or an invitation in square, story, landscape or A4, and the AI designs it; view it, touch up its code and download it. Same price as a document.
An image can be shared with someone, given a public link or commented on. You decide who sees it.
NFTs: link your wallet by signing a message and see your collection. With a linked wallet you can also sign in to 54.
Agents
Each agent reply runs on Lite (free), Smart (◎1) or Genius (◎2); you choose on every message. You are charged first and refunded if nobody answered. Up to 60 messages a day.
Your agent (Your profile): one per account, with Marketing and Social inside. Where the channel is enabled, you can also write to it on Telegram, WhatsApp, Slack or Microsoft Teams (Settings → Connect), always on Lite. With your X account connected, each reply has *Post on X*: you review it and it goes out only when you press Post.
Each site's agents (the site's Agents tab): up to 12 per site, each with the role you write ("handles complaints", "writes the weekly promos").
The growth agents, with the CMO plan: SEO, Reddit, X, X influencers, articles, Hacker News, LinkedIn and UGC videos. They work on their own and leave proposals ready to review.
The site assistant answers your visitors with what the site knows.
No agent publishes or sends anything on its own: it drafts and advises, and you publish.
Your site's SEO
Every site ships with what a search engine needs to read without running anything: title, description, its sitemap and its llms.txt for AI.
Every change you ask for also fixes missing SEO along the way: a main heading, the language, alt text on photos.
The SEO agent reviews your site and leaves the fixes as proposals.
A change does not delete pages or pieces that rank: deleting a page is your decision, never the AI's.
The Review tab in each site's Studio: with Google connected, it compares the last 4 weeks against the 4 before and proposes up to five things to do that week, taken from Search Console. Nothing changes by itself, and a page touched less than 60 days ago stays on hold.
In the 90-day diagnosis of the same tab: the pages reached by fewer than five links from other pages of your site, counted over the 30 Google shows most.
A site in several languages: ask the editor for the languages you want; each one gets its own address (?lang=) and Google knows which to show in each country (hreflang).
If you load many pages at once, the SITEMAP_NUEVAS_POR_SEMANA site variable makes the sitemap declare them to Google that many per week, oldest first.
In the same tab, Do AIs mention your site?: write up to five questions a customer would ask and each AI (ChatGPT, Gemini, Claude…) is asked; it says whether you appear, in what place and which competitors are named. Charged to your coins and runs by itself once a month.
54 in ChatGPT: add the 54 app (https://54.wtf/api/54-mcp) in ChatGPT and ask it for a site. The first time it asks for permission on 54; it builds the site in your account as a draft, charged like the editor, and gives you the link to see and publish it. It also lists your sites and applies changes to them (as a new version, unpublished). The permission is a key you see and revoke at 54.wtf/developers.
And the Free tool: 54 reads your site and proposes three tools people search for (a calculator, a generator, a checker), with the search for each. The one you pick becomes its own page of your site, with its title and in the sitemap, and the editor builds it like any change.
Notices, chats and Community
The Notices tab gathers everything from your sites: a plan about to expire, unread chats and mail, agent suggestions, sales, sites someone wants to hand you, images shared with you and coins sent to you.
If something could not be read, the tab says so; it never shows zero instead.
Community: channels, replies, reactions and Votes. In a vote each person weighs what they hold in Lust at that moment.
Lust is earned by leaving a device on as a node (it keeps verified copies of published sites): every 10 minutes a block of 50 Lust goes to one node, and there will never be more than 21,000,000 in total.
Your public page is 54.wtf/@yourusername, with your year of activity and your published sites.
The network: nodes and Lust
Any device can be a node: it keeps copies of published sites and the platform confirms each one by its sha-256 fingerprint. Each site looks for 2 copies on different nodes.
If the origin goes down, a visitor who has been there once keeps seeing the site from a node, and a changed copy is discarded.
A site can stop being stored by 54: only its fingerprint remains and it is brought back from a node.
Every 10 minutes a block closes and its reward goes to a node with confirmed copies. The reward starts at 50 Lust and halves every 210,000 blocks.
Total issuance never goes above {miles(N.lustTope, 'en')} Lust, and only blocks that had copies are paid.
Governance
Network decisions are voted in Community → Votes. Each vote weighs what the person holds in Lust at that moment, and the weight is set by the server, never by the browser.
Results are public: how much Lust each option adds up to and how many people voted.
Whoever holds up the network with a node is who gains weight to decide.
Identity and access
An account is a person. You sign in with an email code, with Google, with a device passkey (face or fingerprint) or by signing with a wallet; none of the four stores a password.
Passkeys are verified on the server (origin, site, user presence, signature and counter) and each challenge is valid once.
The wallet signs a standard message (EIP-4361) with a one-time challenge; an address belongs to a single account.
From your code, an API key acts as you: the database stores only its fingerprint, it has a daily cap and can hold its own balance.
Inside ChatGPT, the 54 app asks for permission once and stays as a key you revoke at 54.wtf/developers.
Guarantees
What the protocol promises is written in code and covered by tests that break if it stops holding:
It charges before doing and refunds exactly what did not come out: a rejected image, a video that did not finish, an answer that never arrived.
A change that breaks the site is not delivered, and one that would take away a table, a form or the title puts it back or says so.
What could not be read is said: no screen shows zero in place of "I do not know".
The price of what you sell is set by whoever publishes, and a purchase is delivered only once payment is confirmed.
A site can also take crypto (USDC) through Stripe; if Stripe has not enabled it yet, the charge goes through by card.
Deleting the account takes your sites, what your visitors saved, your mailboxes and your media.
Your account
Sign in with an emailed code, with Google, with face or fingerprint (Password and face or fingerprint → Add this device) or with your wallet.
Send coins: from your balance, to a @username or an email. Before sending it tells you who receives it.
Hand a site to someone else: Your profile → Hand over a site. Nothing moves until the other person accepts.
From your code: with a key from 54.wtf/developers you use the same engine through the API.
Deleting your account (Your profile) takes your sites, what your visitors stored, your mailboxes and your media with it.
Limits and what comes next
What it does not do today, said so nobody finds out halfway:
Nodes serve a site to a visitor who has been there once with 54 running; the first visit still goes through 54.
Music does not split stems or clone voices.
Wallets and NFTs are on Ethereum-compatible chains; not Solana yet.
Your agent's channels (Telegram, WhatsApp, Slack, Teams) and posting to X are turned on channel by channel.
No agent publishes or sends anything on its own, and that will not change.