How It Works.

DEMI

DEMI stands for Digital Exchange Methodology Interface. The proposition behind it is simple: every AI-assisted intellectual work — a manuscript, a research idea, a first attempt at something between philosophy and fiction — deserves a structured, portable, verifiable record of its own substance, independent of whichever platform happened to help produce it.

We turned those records, the results of registration in DEMI Central Registry to a tool referring you to AI assisted publishing.

See the Items of Registration available with disigned for you DEMI Interface

DEMI

‍is a tool for Registration of any text -manuscript, book, article, report and project with a created DEMI Interface and algorithms to refer people holding the registered text to AI web spaces to develop the ideas to their target.

To work with the invented interface you are welcome to learn how the Registry is designed.

The First Anchor

The DEMI Registry is now committed to the Ethereum blockchain

UplitAU Pty Ltd · ABN 91 680 646 495 · Sydney, Australia · 18 July 2026

What happened

At 01:19:47 UTC on 18 July 2026 (11:19 AM Sydney), the entire DEMI Central Registry was committed to the Ethereum blockchain in a single transaction, confirmed in block 25,556,256.

From this moment, the question “when did these records exist?” is no longer answered by UplitAU. It is answered by a public blockchain that no company, bank, or government controls — and that nobody, including UplitAU, can alter or remove.

The evidence

Anchor transaction

0xc09e3011f98e7b9fddd45ea3e5e76a769326e4e6a97bf91d5b8d50ccc93e01fa

Block

25,556,256 · Ethereum Mainnet · status: Success

Block timestamp

2026-07-18T01:19:47.000Z — the blockchain's own clock

Registry digest

0x18458fa694393ef5685001dc535e19675029da7edf1d12b9a4e7a105dfdc8285

Records covered

2 — UPL-NOV-26-100774-EN (demo) and UPL-NOV-26-100645-EN (real)

Sent from

0x1a23c80d81a5c28470421135f74100ee8f818324 — the registered anchor wallet

Value transferred

0 ETH — the transaction carries proof, not money

Total cost

network gas only — approximately eleven cents

Public anchor record

demi-proxy.flat-bonus-ffc5.workers.dev/registry/anchors.json

The exact snapshot

/registry/anchor/18458fa6…8285.json — stored permanently

How anyone can verify it — without asking permission

1.    Open the snapshot at /registry/anchor/{digest}.json and copy its records_json string.

2.    Compute the SHA-256 of that string with any standard tool. It equals the digest above.

3.    Open the transaction on etherscan.io and look at its Input Data field. It contains the same digest.

4.    Read the block timestamp. That is the moment, certified by the Ethereum network.

Four steps, no institution, no permission, no trust in UplitAU required. That is the whole point.

What this changes

✓   Every record now in the Registry — including the DEMO record — carries an independent blockchain timestamp.

✓   Every certificate of a covered record now shows a new line in its Chain of Evidence: “Registry anchor (Ethereum)”, with the block, the time, and a link anyone can open.

✓   The gap described in Paper 4 is closed before card payment even arrives: when authors begin paying in Australian dollars, their records will inherit blockchain evidence from the next anchor, without ever touching cryptocurrency.

✓   Paper 1's honest line — “two records, both ours” — now reads: two records, both ours, both anchored on Ethereum. The proof layer is complete.

The lineage — why this transaction matters beyond its size

The Crypto-Splitting Technology patent (AU2018100999) described a payment whose meaning is divided into parts, each part recorded in a blockchain, without human intervention. In 2018–2019 that idea required deploying custom Solidity smart contracts and placing every participant on-chain — heavy, expensive, and ahead of the infrastructure of its day. The group building it dispersed when war overseas interrupted the work.

This morning the same principle ran as a single transaction: one send whose meaning was divided between value (zero) and registration (everything). It took one button and eleven cents.

The architecture of 2019 was not wrong. It was early. The mature reading infrastructure that arrived since — Etherscan's public API, Cloudflare's edge — let verification replace deployment: the same destination, a lighter vehicle.

Notes for the record

Two obstacles were found and solved on the way, both worth documenting for anyone who repeats this:

•     The iPhone MetaMask app cannot attach data to a normal Send — the setting exists but the field does not. The Anchor Console was rebuilt to construct the transaction itself through the MetaMask browser extension.

•     MetaMask refuses data-carrying transactions sent to one's own accounts (a phishing guard). The anchor is therefore addressed to the standard Ethereum “dead” address, which accepts data. Since the value is 0 ETH, nothing is burned or lost — and the Registry validates the sender and the data, never the destination.

Cost of both lessons: two small gas fees, and one morning.

Cadence from here

Anchor after each batch of new registrations, or weekly — whichever comes first. Each anchor covers everything registered before it. The operation is four minutes: get the digest, press the button, confirm in MetaMask, record the hash.

Skydle / UplitAU Pty Ltd · ramsmile.com · uplitpublisher.com.au · ramsmile@uplitau.com

AU2018100999 · AU2019101249 · © 2026 UplitAU Pty Ltd / Skydle · Developed with Claude (Anthropic)

DEMI PUBLISHING PIPELINE · EDUCATIONAL DIAGRAM A How a Registration Is Verified — the Roles of Cloudflare and Etherscan AUTHOR'S BROWSER client-side · holds no secrets · computes SHA-256 fingerprints (Web Crypto API — the file itself is never uploaded anywhere) · converts DOCX → EPUB locally · sends only the chosen excerpt CLOUDFLARE WORKER "demi-proxy" · serverless edge code · holds API keys as encrypted secrets · enforces the rules server-side: — REAL only if payment re-verified — one transaction = one work — UPL code uniqueness · the browser cannot bypass it — trust decisions are made here, not on the author's device the gatekeeper ETHERSCAN API window onto the Ethereum blockchain reads the public chain and answers: — did the ETH reach OUR address? — was the amount sufficient? — status: Success · block timestamp ANTHROPIC API Claude · AI analysis reads the excerpt and extracts the Conceptual Core: Propositions · Constraints · Mechanisms · Boundaries CLOUDFLARE KV STORAGE namespace DEMI_REGISTRY · the Central Registry · one record per work (rec:UPL-…) · spent transaction hashes ("burned") · the light public index (_index) PUBLIC READ ENDPOINTS — open to every human and every AI system /registry/index.json · /registry/{UPL}.json · /certificate/{UPL} the Registry display page, licensed publishers' pages, and GPT Store Actions all read from here 1 · HTTPS POST excerpt + hashes + Tx Hash 2 · verify payment on-chain answer 3 · analyse excerpt Conceptual Core 4 · write record only after rules pass 5 · served read-only Division of trust: Browser = fingerprints · Blockchain = time & payment · Worker = rules · KV = storage · Public = anyone verifies
DEMI PUBLISHING PIPELINE · EDUCATIONAL DIAGRAM B The Referral to the GPT Store — and the Road Back (the Two-Way Bridge) REGISTRY RECORD in the Central DEMI Registry UPL-NOV-26-100645-EN · Conceptual Core of the work · SHA-256 fingerprints · payment evidence · machine-readable at a public URL GPT STORE PACKAGE generated by the DEMI interface — this IS the referral 1 · GPT Name & Description carries the UPL code as the public reference 2 · System Prompt (Instructions) embeds the Conceptual Core + UPL code — the GPT knows exactly which ideas it serves 3 · OpenAPI Action Schema points to the live Registry endpoints — the GPT can verify its own registration during any chat OPENAI GPT STORE chat.openai.com · Custom GPT · Knowledge base = the author's EPUB · Readers converse with the ideas · The Action resolves the UPL code → live provenance, not a claim · Discoverable in the Store — the work stops being an isolated file the AI development space generates publish NEW WORK IS CREATED inside the GPT Store conversation space technical solutions · sequels · analyses Example: The Ramsmile → NDEV / WDC Analyst — the NDEV Code Base work REGISTERED BACK — A NEW REGISTRY RECORD through the same DEMI interface, with one extra field: derived_from: UPL-NOV-26-100645-EN the lineage of ideas becomes public and permanent — a family tree of ideas readers + author develop register the results joins the Registry — the circle can repeat WHY THIS MATTERS FOR THE GPT STORE ECOSYSTEM Today a Custom GPT is an island: only its owner knows it exists, and nothing proves what ideas it is built on. The UPL referral changes both: the Registry makes each GPT discoverable and its provenance verifiable — live, by anyone, including the GPT itself through its Action. Work born in the Store flows back as registered, attributed new works. attribution travels with the ideas — in both directions across the bridge DEMI Publishing Pipeline · UplitAU Pty Ltd · AU2018100999 · AU2019101249 · © 2026 UplitAU Pty Ltd / Skydle · Developed with Claude (Anthropic)
DEMI PUBLISHING PIPELINE · EDUCATIONAL DIAGRAM C Two Payment Rails, One Registry of Ideas THE AUTHOR chooses how to pay for registration — A$9 fiat money (A$, card) cryptocurrency (ETH) THE FIAT RAIL — the money people already have Lemon Squeezy — merchant of record card checkout · GST handled · receipt with an Order ID settles A$ to the operator's business bank account Cloudflare Worker verifies the Order ID server-side API check — exactly mirroring the blockchain check on the other rail REAL record · evidence = payment receipt status: next integration · reaches everyone with a bank card THE CRYPTO RAIL — value without a central issuer Ethereum blockchain — the payment itself peer-to-peer transfer · confirmed in a public block · the block timestamp is independent, permanent evidence Etherscan + Cloudflare Worker verify on-chain address · amount · Success status — and each transaction can register exactly one work REAL record · evidence = blockchain transaction status: LIVE — tested 15 July 2026, Tx on Etherscan THE CENTRAL DEMI REGISTRY one namespace · both kinds of evidence, side by side every record public, machine-readable, verifiable — for humans and AI systems A growing knowledge base of registered ideas — AI-assisted search finds the work, its author, and its proof The coexistence is the demonstration: value flows through the old rail and the new rail into the same registry of ideas — the monetary thesis of The Ramsmile and the NDEV Code Based WDC, shown in working practice, not in theory.
DEMI PUBLISHING PIPELINE · EDUCATIONAL DIAGRAM F The Journey of an Idea — from a Human Mind to Its Target, with AI 1 THE IDEA Born in a human mind — a story, a theory, an artwork, a technical vision. "The idea came to him in a dream…" — The Ramsmile 2 THE MANUSCRIPT The author writes. AI assists with editing and polishing — Claude and ChatGPT as tireless editorial assistants. the words remain the author's 3 DEMI INTERFACE at UplitPublishing — AI does everything: EPUB · Conceptual Core (Claude) · SHA-256 · verified payment · UPL code · Registry record · one-file Certificate ten minutes, from A$9 4 PUBLISHED The book on sale; the Landing Page live — on UplitPublishing websites or anywhere the author chooses. the work is now findable — by people and AI 5 THE GPT STORE ChatGPT hosts the AI edition. Readers converse; the idea develops toward its target with AI doing the technical work. ex.: The Ramsmile → NDEV Code Based WDC 6 NEW RESULTS — REGISTERED Work born in the AI space returns to the Registry as a new record with derived_from — the public family tree of ideas. and the journey can begin again the circle closes — new works register through the same interface READERS TRAVEL WITH THE IDEA They buy the book at station 4 · converse with it at station 5 · verify any record against the Registry at any time — and some readers become co-developers, whose contributions register at station 6. The author brings the idea and makes the decisions. Everything technical — preparation, registration, publication mechanics, and development — is carried by AI. DEMI Publishing Pipeline · UplitAU Pty Ltd · AU2018100999 · AU2019101249 · © 2026 UplitAU Pty Ltd / Skydle · Developed with Claude (Anthropic)
MASTER_FILE Archive 2019–2025 · hashed & timestamped · for the team

2019 → 2026: The Lineage of the IdeasРодословная идей

What four IT consultants and one author designed in 2018–2019 — and where each mechanism runs today Что четыре ИТ-консультанта и один автор спроектировали в 2018–2019 — и где каждый механизм работает сегодня
2019 · OMNIGATE / CST WHITE PAPER
Built on EthereumПостроено на Ethereum
"The component is built using Solidity… React JS library as a front-end layer. The component interacts with Etherium blockchain network using Web3."
Three levels of smart contracts: form the digital image · split into NDEV shares · convert to equivalents. Три уровня смарт-контрактов: цифровой образ · разделение на доли NDEV · конвертация в эквиваленты.
→
2026 · DEMI REGISTRY — LIVE
Running on EthereumРаботает на Ethereum
Cloudflare Worker + Etherscan verification; plain transactions carry the proof. Same chain, same act — registering a business event on Ethereum, excluding the human factor. Cloudflare Worker + проверка через Etherscan; обычные транзакции несут доказательство. Та же сеть, то же действие — регистрация бизнес-события в Ethereum без человеческого фактора.
registry/index.json
2018 · PATENT AU2018100999 · MAT
GUID-based referencingРеференсы на основе GUID
"…searchable, auditable financial records across distributed databases."
One identifier resolving records everywhere. Один идентификатор, находящий записи повсюду.
→
2026 · THE UPL CODE
One code, resolvable by anyoneОдин код, проверяемый любым
UPL-NOV-26-100645-EN resolves to the record, the certificate, the landing page, the GPT Store — for humans and AI systems. UPL-NOV-26-100645-EN ведёт к записи, сертификату, странице-визитке, GPT Store — для людей и систем ИИ.
registry/UPL-NOV-26-100645-EN.json
2019 · WBRS — FIGURE 7
Consultant referral pagesРеферальные страницы консультантов
"Web Based Referral System for Consultants, Providers and Clients" — a sale initiated from a Consultant's page, tracked and rewarded. продажа, инициированная со страницы консультанта, отслеживаемая и вознаграждаемая.
→
2026 · THE TWO-WAY GPT STORE REFERRAL
Works referred into AI space — and backРаботы направляются в пространство ИИ — и обратно
A registered work becomes a GPT Store carrying its UPL code; results register back with derived_from — the public family tree of ideas. Зарегистрированная работа становится GPT Store со своим кодом UPL; результаты регистрируются обратно с derived_from — публичное родословное древо идей.
2019 · SMART CONTRACT SCHEMA
fAddConsultant
"The function is called by the Government Agency to add a legitimate consultant" — a gatekeeper admitting legitimate writers to the shared ledger. привратник, допускающий легитимных участников к общему реестру.
→
2026 · NAMESPACE AUTHORITY
Licensed publishers, one RegistryЛицензированные издатели, один Реестр
The Worker admits records only under the rules: verified payment, one transaction — one work, UplitAU as namespace authority; publishers write under licence. Worker принимает записи только по правилам: проверенная оплата, одна транзакция — одна работа, UplitAU как держатель пространства имён; издатели пишут по лицензии.
2018–19 · CST — THE SPLITTING PRINCIPLE
Split at the moment of paymentРазделение в момент оплаты
A payment divides into percentage parts — value, tax, registration — each part blockchain-recorded, no human hands. Платёж делится на процентные части — стоимость, налог, регистрация — каждая фиксируется в блокчейне без участия человека.
→
2026 · REGISTRY ANCHORING
The principle in miniatureТот же принцип в миниатюре
One transaction's meaning is split between value and registration: a 0 ETH send whose data field commits the whole Registry to the chain — every record, however paid, gains a blockchain timestamp. Смысл одной транзакции разделён между стоимостью и регистрацией: отправка 0 ETH, чьё поле данных фиксирует весь Реестр в блокчейне — каждая запись, независимо от способа оплаты, получает блокчейн-метку времени.
registry/anchors.json
Conclusion for the team. The year 2018–2019 produced a correct architecture whose infrastructure had not yet arrived. In 2019, registration on Ethereum required deploying custom Solidity contracts and putting every participant on-chain. In 2026, mature reading infrastructure (Etherscan) lets verification replace deployment — the same destination, a lighter vehicle. Every core mechanism the consultants designed now operates, publicly and verifiably. The war interrupted the group; it did not invalidate the work. "Not for nothing" is now a checkable statement — open any link above. Вывод для команды. В 2018–2019 была создана верная архитектура, для которой инфраструктура ещё не наступила. В 2019 регистрация в Ethereum требовала развёртывания собственных контрактов на Solidity и вывода всех участников в блокчейн. В 2026 зрелая инфраструктура чтения (Etherscan) позволяет проверке заменить развёртывание — та же цель, более лёгкий транспорт. Каждый ключевой механизм, спроектированный консультантами, сегодня работает — публично и проверяемо. Война прервала группу, но не обесценила работу. «Не напрасно» — теперь проверяемое утверждение: откройте любую ссылку выше.
Sources: MASTER_FILE_Ramsmile_Concept_Archive_2019–2025_v4 (SHA-256 hashed & timestamped) · Patents AU2018100999, AU2019101249 · live DEMI Registry (Cloudflare Worker demi-proxy) Источники: MASTER_FILE_Ramsmile_Concept_Archive_2019–2025_v4 (SHA-256, метки времени) · Патенты AU2018100999, AU2019101249 · действующий Реестр DEMI (Cloudflare Worker demi-proxy)
© 2026 UplitAU Pty Ltd / Skydle · Prepared with Claude (Anthropic)Подготовлено с Claude (Anthropic)
See a Technical Report at OPEN ARCHIVE