UNY and system paper · 29 October 2026
UNY and the UnyKorn systems.
A short paper, written to be checked rather than believed. It describes what UnyKorn LLC builds, the two networks it runs, where the UNY token on Base fits, who holds the supply, and what UNY is not. Figures are as read on the dates shown; nothing here is a forecast.
1 · What UnyKorn builds
Record and payment software with a public trail
UnyKorn LLC is a Wyoming technology and administration company (filing 2026-002019968, 1 July 2026). Its software has one job: keep money movement tied to documents, and make the trail checkable by someone who does not trust us. Four pieces do that work.
| Piece | What it does | State on 29 Oct 2026 |
|---|---|---|
| Record chain | A permissioned Hyperledger Besu network (QBFT consensus, chain id 37332) that stores document hashes, agent identities and receipts in an anchor registry, and writes a daily checkpoint of its state to Base mainnet. Only hashes go on chain; the documents stay with their owners. | Producing blocks; height 845,378; six validators across three regions; registry 0xbd755333f1b6159bf48a930b61589ca5bc45318f. Read from proof.unykorn.org/api/overview on 29 Oct 2026. |
| Rules chain (UnyKorn Chain Beta) | A Polkadot SDK network (runtime “unykorn”, spec 101, Aura block production and GRANDPA finality) with a native coin, also called UNY (12 decimals). It is where UnyKorn's own on-chain rules run: anchors, validators, council. It is a beta network, not a mainnet. | Answering RPC at rpc.unykorn.org/uny-beta; chain name “UnyKorn Chain Beta”; block 278,915; eight validators. Read on 29 Oct 2026. |
| Paid-API rail (Genesis402) | HTTP endpoints that answer 402 Payment Required and settle per call in USDC on Base under the x402 and MPP protocols, with a signed receipt per call. Applications and AI agents pay without an account. | Front door genesis402.com answering 200 on 29 Oct 2026; 757 outside paid calls as of 25 Oct 2026 (rail ledger). |
| Proof service (LPS-1) | Files are hashed, batched into a Merkle tree, the root anchored on Polygon and stamped into Bitcoin through OpenTimestamps. Each proof has a public page and a certificate; an open verifier checks a proof without our servers. | Available; specification and reference implementation published (see Research). |
2 · The two chains
Why there are two, and what each is called
The record chain is boring on purpose. It runs a widely used enterprise client (Besu) with a fixed validator set, so that a hash written today can be read in ten years without depending on a token market or a public mempool. Its checkpoints land on Base so that anyone can prove the record existed at a date without asking us.
UnyKorn Chain Beta is where the company's own rules are implemented as runtime code: who may anchor, who validates, how the council changes a parameter. It carries a native coin because a Substrate runtime needs one for fees and for validator bonds. That native coin is called UNY, which is also the name of the Base token described next. They are different assets on different networks, and this paper names the network every time it uses the word.
3 · UNY on Base
Role, supply and holder
| Item | Value | Source and date |
|---|---|---|
| Network | Base mainnet (chain id 8453), an Ethereum layer 2. | Basescan, 29 Oct 2026 |
| Contract | 0xC070492f455f404b404D6c2197665DDA75F5659cBasescan token page · verified source on Basescan · Sourcify full match | Sourcify exact match of creation and runtime bytecode, verified 25 Oct 2026; Basescan source verification 25 Oct 2026 |
| Name · symbol · decimals | UnyKorn · UNY · 18 | eth_call decimals() = 18 on 29 Oct 2026 |
| Total supply | 1,000,000,000 UNY (1 × 1027 base units), minted once in the constructor. | eth_call totalSupply() on 29 Oct 2026 |
| Holder | The whole supply sits in a Safe (v1.4.1 L2) with a 2-of-3 signer threshold: 0x0a8Ab2732E9299f9320F874A437840548f62676aOpen in the Safe app | eth_call balanceOf(Safe) = totalSupply() on 29 Oct 2026; Safe creation tx on Basescan |
| Admin surface | None. No owner, no minter, no pauser, no blocklist, no transfer fee, no upgrade proxy. The code cannot be changed and the supply cannot grow. | Verified source: OpenZeppelin Contracts 5.4.0 ERC20 + ERC20Permit + ERC20Burnable, no Ownable or AccessControl |
| Deployed | 25 Oct 2026, tx 0x405556642100047fdc39b9e577bed07ba67381330489e44bf3bf91495e0f3a46 | Basescan, 29 Oct 2026 |
| Market | No liquidity pool, no exchange listing and no price set by UnyKorn LLC as of 29 Oct 2026. UnyKorn does not sell UNY. | Basescan transfer list (one mint transfer) and the Safe balance on 29 Oct 2026 |
Role
UNY on Base is the unit UnyKorn systems account in when they need a unit of their own: fee credits on the rail, deposits against a record service, settlement between UnyKorn systems. Where a client pays in dollars or USDC, that remains unchanged. The Base token exists so that these balances can be held in a widely supported wallet on a widely supported network, rather than only on the company's own beta chain.
Supply and holder
The supply was minted once, to the Safe, in the deployment transaction, and the contract has no function that could mint again. The Safe has three owners and a threshold of two; every movement out of it is a Base transaction anyone can see. As of 29 Oct 2026 the Safe holds the entire supply and no UNY has left it.
4 · What UNY is not
Said plainly
- Not a share, a note, a deposit, or a claim on UnyKorn LLC or its revenue. No dividend, no interest, no redemption, no vote.
- Not for sale by UnyKorn LLC. No price set, no pool seeded, no exchange listing, as of 29 Oct 2026.
- Not the native coin of UnyKorn Chain Beta, and not bridged to it. No bridge exists as of 29 Oct 2026.
- Not the contract on Avalanche at
0xc09003213b34c7bec8d2eddfad4b43e51d007d66that carries the same name and symbol with a supply of 100,000,000. The only UNY issued by UnyKorn LLC is the Base contract in section 3. - Not a promise. What the software does with UNY is described as of 29 October 2026; a change is a new dated version of this paper, not a quiet edit.
5 · Sources
Where every figure came from
| Figure | Read from | Date |
|---|---|---|
| UNY supply, decimals, Safe balance | eth_call against mainnet.base.org at block 53,262,036 | 29 Oct 2026 |
| Source verification | sourcify.dev/server/v2/contract/8453/… (creation and runtime exact match, verified 25 Oct 2026); basescan.org contract tab | 29 Oct 2026 |
| Safe threshold and owners | app.safe.global, Base; Safe v1.4.1 L2 | 29 Oct 2026 |
| Record chain height, validators, registry | proof.unykorn.org/api/overview | 29 Oct 2026 |
| Beta chain name, block, validator count | rpc.unykorn.org/uny-beta (system_chain, chain_getHeader) | 29 Oct 2026 |
| Rail paid-call count | rail ledger, published on this site's home page | 25 Oct 2026 |
| Company filing | Wyoming Secretary of State, filing 2026-002019968 | 1 Jul 2026 |
83fd3eaf5b3e22b1450fe696d28a32a53076b152fe51086656d34df4ee014c3c. The same text as this page, in the UnyKorn document system; also listed on the documents page.Written by UnyKorn LLC, 29 October 2026. A change to any figure is a new dated version of this paper. Contact kevan@unykorn.org.