Portfolio
Everything we have built, as one connected map.
56 systems in 8 groups around UnyKorn LLC, joined by 79 links. Click a node to see what it is, how it was checked and where to look. Every label is the state on 2026-10-07, not a promise.
The map
Click a node. Drag to pan, scroll to zoom.
Hubs pulse; the lines are the real dependencies between systems. Filter by group, or follow the "Connected" links in the panel to walk the network.
Front doorsOn public networksRails and agentsResearch and provenanceForensics and real assetsOpen sourceLayer-1 researchInfrastructure
How to read the labels. Measured Checked against a public record, chain explorer, registry or API on the date shown. You can repeat the check. Available Running on a production network or delivered as a service today. In development Designed and partly built, or built and used internally. Not offered as a service until it is labelled Available. Private testers Invitation only; not offered as a service. Research Exists as research and test code. Not on a public network and not described as if it were.
Signal paths
How one paid call moves, and how one document becomes evidence
Both paths run today. Volume on the first is small and is described that way; stamps on the second are pending until the Bitcoin calendar commits, by design.
Payment path · Available, cent-scale
1AI agent
An MCP client or plain HTTP. No account, no API key.
2HTTP 402
The rail answers Payment Required with the price and the pay-to address.
3Settle on Base
The caller signs a USDC transfer on its own device; the facilitator settles it on chain.
4Signed receipt
An Ed25519 receipt with its own id, one per call, checkable on a public page later.
5Ledger
One writer, replay-safe, kept across blue/green deploys.
6Answer
One of the catalogued endpoints: address check, risk, price, report, proof.
Evidence path · Available on Polygon, Bitcoin stamps pending by design
1Document
A report, a deck, a company PDF, a chapter.
2Hash
SHA-256 per paragraph; only the fingerprints move, never the file.
3Merkle root
One 32-byte root per document; any one paragraph can be proven alone.
4Anchor
The root is written to the LPS-1 anchor contract on Polygon, chain 137.
5Timestamp
The same root is stamped into Bitcoin through OpenTimestamps calendars.
6Verify
Anyone re-hashes the file at xxxiii.io/verify and compares, without our servers.
Not on either path: a UnyKorn Layer-1 on any public mainnet, a safekeeping provider under contract, or any balance or fill. Apostle Chain is a research node, not a settlement rail.
Built, not described
We are engineers first. This site exists so the work can be read.
Everything on the map is code that exists, or a record anyone can resolve. The numbers below are from the GitHub profile on 2026-10-07; a repository is a body of code, not a production system, and the labels on each node say which is which.
337
repositories under github.com/FTHTrading, 164 of them public
1,625
contributions in the twelve months to 7 October 2026
346
public repositories across the four GitHub accounts
17
Rust Layer-1 workspaces on disk, all labelled Research
Three smaller accounts hold the rest of the public code: kevanbtc (159), Y3KDigital (14) and unykornai (9). Counts from the October 2026 GitHub check; the organisation total is the profile's own figure and includes private repositories.
Said first
What is not on this map
A map is only worth showing if this list is on it.
| Something you might expect | The honest line |
|---|---|
| A UnyKorn Layer-1 on a public mainnet | Seventeen Rust workspaces exist as research and test code. None is a public chain, and we do not describe one as such. |
| Apostle Chain as a settlement network | A single-process research node: agents register, sign, the node checks the signature, moves an internal balance and writes a receipt. No validators, no explorer, no measured throughput. |
| A safekeeping provider under contract | None is engaged. Where a client needs one, the relationship is opened in the client's own name; UnyKorn holds no keys, funds, metal or securities. |
| Namespace or identity assets issued on a public chain | The namespace protocol is code on disk. Nothing has been issued, and no value is attached to anything on chain. |
| Document access passes in circulation | The contract is deployed; zero passes have been issued. |
| An external audit of the LPS-1 contracts | Conformance is self-assessed. An outside audit has not been commissioned. |
| Volume on the paid-API rail | One proven cent-scale settlement path. Volume is small, and every page that mentions it says so. |
| Balances, fills, settlement ids or forecasts | None appear here. Those come from a client's own provider or venue, never from a web page. |
01 · Public front doors
Public front doors
Every site below answered HTTP 200 from a plain fetch on 7 October 2026.
| Node | What it is, and how it was checked | State | Where to look |
|---|---|---|---|
| unykorn.ai | The company front door: services, systems with honest labels, research, the verify-us table and the company documents with SHA-256 fingerprints. Checked: Fetched 7 October 2026: HTTP 200. | Available | Open · Documents |
| os.unykorn.ai | The regulated-operations control plane. Its role split is published on the page: an unaffiliated FINRA broker-dealer, a qualified third party for safekeeping, a registered transfer agent; UnyKorn does policy, workflow and evidence. Checked: Fetched 7 October 2026: HTTP 200. | Available | Open |
| genesis402.com | Front door for the paid-API rail: pay-per-call endpoints for applications and AI agents over x402 and MPP, settled in USDC on Base, with a signed receipt for every call. Checked: Fetched 7 October 2026: HTTP 200. 365 endpoints answered 402 with a price in a full sweep on 30 September 2026. | Available | Open · Rails page |
| xxxiii.io | Home of LPS-1, the open provenance standard, with the publish and verify pages and the machine-readable conformance record. Checked: Fetched 7 October 2026: HTTP 200; xxxiii.io/.well-known/lps1.json also 200. | Available | Open · Conformance record |
| drunks.app | The Genesis x402 agentic-commerce demonstration on Polygon. Checked: Fetched 7 October 2026: HTTP 200. | Available | Open |
| blockchainfraud.org | The public crypto-fraud checker. The free check runs in the browser; full written reports come under engagement. Checked: Fetched 7 October 2026: HTTP 200. 209 of 209 served-site checks passed on 9 September 2026. | Available | Open |
| legacychain.app | A consumer product for family document vaults, sold by subscription. A static site with off-chain workers; its Solidity contracts are not wired to the site. Checked: Fetched 7 October 2026: HTTP 200. | Available | Open |
| otownfinder.com | O-Town Finder, an Orlando concierge web app and API on one Cloudflare Worker, launched 19 September 2026, backed by the O-System namespace registry on Base. An Android build exists and is not yet on Google Play. Checked: Fetched 7 October 2026: HTTP 200. | Available | Open |
| stablecoins.unykorn.ai | An XRPL and EVM stablecoin reference hub. Educational. Not an offer. Checked: Fetched 7 October 2026: HTTP 200. | Available | Open |
| y3kmarkets.com | Y3K Markets, a company (not a GitHub organisation) focused on north-Atlanta residential value-add. Pre-launch: documents in counsel review, no securities offered on the page. Checked: Fetched 7 October 2026: HTTP 200. | In development | Open |
02 · On public networks
On public networks
Mainnet contracts and registries anyone can read with a block explorer.
| Node | What it is, and how it was checked | State | Where to look |
|---|---|---|---|
| LPS-1 reference deployment | Seven contracts on Polygon mainnet (chain 137): LiteraryAnchor, PublishingKernel and KernelV2, AuthorIdentity, RoyaltyRouter, EditionNFT, StoryNFT. Conformance self-assessed at L5; internal security review, no external audit. Checked: Contract list and addresses at xxxiii.io/.well-known/lps1.json (generated 29 September 2026), each on polygonscan.com. | Measured | Conformance record · Standard |
| ERC-8004 agent identity | Genesis402 is agent 95721 on the ERC-8004 identity registry on Base, with 21 operator and desk agents alongside it, each with a public page. Reputation and validation registries not yet used. Checked: All 22 agent URIs resolved from the registry on 6 October 2026. | Measured | Agent pages · Registry on Basescan |
| x402 settlement on Base | Per-request USDC payments with a signed receipt for every call. One proven cent-scale settlement path; small volume, and described that way. Checked: A public signed receipt and the published verification key. | Available | A signed receipt · Published key |
| O-System on Base | Soulbound namespace registry, pass, one-time coupon and credits contracts on Base mainnet behind O-Town Finder. The first full cycle (offer, coupon mint, redeem, pass, credits) was confirmed on chain on 20 September 2026. Checked: Desk deployment records, 17 to 20 September 2026. | Measured | O-Town Finder |
| Physical-unit registry | One ERC-721 per physical training unit, with a public metadata endpoint on the product site. Built and operated for an athletics brand launched September 2026. Checked: Desk deployment records, September 2026. | Measured | Systems page |
| Solana token campaigns | Two mints measured on Solana mainnet. Other campaigns listed on the platform have no mint yet and are labelled In development in the public ledger. Checked: Evidence ledger rows CH-SOL-* (Edition 1.1). | Measured | Evidence ledger |
| Document access passes | A non-transferable ERC-721 with issue, freeze and revoke roles, deployed on Base for data-room access control. Zero passes issued; no public pass page yet. Checked: Evidence ledger (Edition 1.1). | In development | Systems page |
03 · Rails and agents
Rails and agents
The paid-API rail, the agents that use it, and the verification desk built on it.
| Node | What it is, and how it was checked | State | Where to look |
|---|---|---|---|
| Genesis402 rail | The rail node that answers 402 and settles: company and sanctions checks, chain reads, market and research data, web and text tools, each priced per call. Every paid call returns an Ed25519-signed receipt that anyone can check on a public page. Checked: 365 endpoints answered 402 in a full sweep on 30 September 2026; manifest and OpenAPI served. | Available | Manifest · OpenAPI · Rails page |
| Genesis402 MCP server | A hosted MCP server and the genesis402-mcp npm package let an AI agent discover the endpoints, see the price first and pay with its own wallet. Version 0.3.10 with 22 tools. Checked: npm, the MCP Registry and Smithery, checked against served responses on 6 October 2026. | Available | npm · MCP Registry · Smithery |
| Verification desk agents | Six pickable ERC-8004 agents that front the verification screens: sanctions screen (UN, OFAC, EU, UK), bank verification, GLEIF registry, SEC EDGAR, counterparty report, and wallet and chain risk. Screening signals, not KYC or legal advice. Checked: Agent pages served; six of six agents verified on 30 September 2026. | Available | Desk agents |
| Counterparty and deal screens | One call resolves a company in the GLEIF register, follows its registered parents and screens every name against the UN, OFAC, EU and UK lists pulled from the official sources. A second screen scans a deal description for 19 red-flag patterns against 21 official sources. Clear, review or stop, with reasons, a branded PDF and a signed receipt. Checked: Sanctions lists fetched from the official sources on 1 October 2026 (OFAC 19,452; UK 6,339; EU 6,241; UN 1,011 entries). | Available | The Examiner agent · Jurisdiction packs |
| Member wallet | A phone and browser wallet where keys stay on the member's own device, payments go only to an approved circle, and network fees are relayed so members never need gas. The wallet is itself an x402 payer under a per-member cap. Invitation only. Checked: Served at wallet.unykorn.org; invitation only. | Private testers | wallet.unykorn.org |
| Genesis402 demo hub | A demonstration hub for the rail published on 7 October 2026: tiles that read the rail's guardian, health and MCP endpoints at the moment you open the page, an agent network explorer, a six-step walkthrough and a preview of the next genesis402.com front page. Numbers on it come from the rail, not from the page. Checked: Pages deployment served 7 October 2026: HTTP 200 on the hub, the explorer and the walkthrough. | Available | Demo hub · Walkthrough |
| Agent network explorer | A network map of the 22 ERC-8004 agents, the receipt feed with on-chain links, the agent scorecard and a problems panel, reading the rail first and falling back to a dated snapshot when a request fails. Every panel says which it is showing. Checked: Served 7 October 2026: HTTP 200; reads twin.unykorn.org at page load. | Available | Open the explorer · Agent cards on the rail |
| Operator desk | The private desk we run our own operation on: hash-chained audit log, deny-by-default spend policy, signed receipts, twin agent runtimes, refund preparation and a release log. Built for clients on their own infrastructure under engagement; never offered as a hosted service. Checked: Internal; described in the Capabilities document. | In development | Systems page |
04 · Research and provenance
Research and provenance
Permanent identifiers and the method for putting a document on chain.
| Node | What it is, and how it was checked | State | Where to look |
|---|---|---|---|
| ORCID 0009-0008-8425-939X | The author record for Kevan Burns, with DOI-registered publications on Zenodo and SSRN. Checked: ORCID public API, 9 September 2026 (3 works); record fetched again 7 October 2026. | Measured | ORCID |
| LPS-1 paper | Deterministic Literary Publishing: a multi-layer provenance model for verifiable manuscripts. Working paper, February 2026, CC BY 4.0. Concept DOI 10.5281/zenodo.18646885; pinned version 10.5281/zenodo.18646886. Checked: Zenodo, 29 September 2026; DOI resolved again 7 October 2026. | Measured | Concept DOI · Pinned version |
| Genesis Protocol preprint | Emergent economic ecology in autonomous computational organisms: a deterministic closed-economy simulation of agents under metabolic scarcity. v1.0.0, February 2026, CC BY 4.0. DOI 10.5281/zenodo.18729652. Checked: Zenodo, 29 September 2026; DOI resolved again 7 October 2026. | Measured | DOI · Code |
| SSRN preprint | SSRN preprint of the provenance work, DOI 10.2139/ssrn.6241279, listed in the published LPS-1 record. Resolve it yourself to confirm; it was not independently re-checked for this page. Checked: Listed in xxxiii.io/.well-known/lps1.json. | In development | DOI |
| Proof of Authorship | A file's SHA-256 is batched into a Merkle tree every five minutes; the root is anchored on Polygon and stamped into Bitcoin through OpenTimestamps. Each proof has a public page, a printable certificate and a Bitcoin receipt, and an open verifier script checks it without our servers. Checked: Served at xxxiii.io/publish and xxxiii.io/verify. | Available | Publish · Verify |
| Company documents | Overview, Capabilities and Track Record, At a Glance, the intake brief and the 2026 Foundation Report, each published with its SHA-256 and stamped through OpenTimestamps. Checked: Served hashes compared byte-for-byte with the command-centre copies on 29 September 2026. | Measured | Documents · Report |
| BIO: spiking-neuron substrate | A leaky-integrate-and-fire neural culture simulator with spike-timing plasticity, shaped like the Cortical Labs programming surface so real hardware can be bound later. Research protocol 001 ran ten seeds against a shuffled-label null and found no steering on random topology. The negative result is published as the finding. Checked: Protocol document, reproduction script, run log and CSV in the public repository. | Research | Repository |
05 · Forensics and real assets
Forensics and real assets
The fraud engine, the physical-asset work, and the published reports.
| Node | What it is, and how it was checked | State | Where to look |
|---|---|---|---|
| Forensics engine | The multi-layer pipeline behind blockchainfraud.org: scam-pattern catalogue, heuristics, legitimacy registry, known-scam address database, on-chain address and contract intelligence, domain-age and registry lookups, safe-browsing and token intelligence, producing a weighted risk score and a written report. Checked: 209 of 209 served-site checks on 9 September 2026; 43 patterns in the free in-browser check; 478 OFAC digital-currency addresses in the registry. | Available | blockchainfraud.org · Evidence ledger |
| Telegram checker bot | Paste a message, a wallet address or a URL into the bot and the forensics engine answers with a risk verdict. Checked: Bot served through the engine's edge worker. | Available | @blockchainfraud_bot |
| Impact and Innovation Reports | The 2026 Foundation Report with six companion reports and a machine-readable evidence ledger: 275 rows under seven labels, every figure bound to its evidence. Checked: Served at unykorn.ai/report, Edition 1.1. | Measured | Reports · Ledger |
| Relics | Tokenized physical collectibles. Site and repository exist; wallet provisioning is scripted and gated. Not an offering. Checked: Repository public; site fetched 7 October 2026: HTTP 200. | In development | Repository · Site |
| Energy-Token (UNYE) | A token design for metered clean energy: one token per five kilowatt-hours, inverter registry, peer-to-peer escrow, 250 million cap. A repository and a design, not an operating fleet. Checked: Repository public. | Research | Repository |
| Readiness and structuring | The Readiness Review and the Capital-Readiness Package: claim-by-claim verification, permit and jurisdiction mapping, lender-view models, structure memos and data rooms. Fixed fees, never a share of capital. Checked: Described in the Company Overview; delivered under engagement. | Available | What we do |
06 · Open source
Open source
Public repositories under github.com/FTHTrading and the three smaller GitHub accounts.
| Node | What it is, and how it was checked | State | Where to look |
|---|---|---|---|
| github.com/FTHTrading | The operating organisation on GitHub: 337 repositories in total, 164 of them public, and 1,625 contributions in the twelve months to 7 October 2026. Many are small sites, decks and duplicates; a repository is a body of code, not a production system. The repositories linked from this map are the ones a client is most likely to read. Checked: Profile read while signed in on 7 October 2026 (337 repositories, 1,625 contributions); public profile fetched the same day: HTTP 200. | Measured | Organisation |
| Three smaller accounts | kevanbtc (159 public, since January 2018: older Layer-1, stablecoin, real-asset and xxxiii work), Y3KDigital (14 public: namespace, XRPL, Stellar, proof-of-funds) and unykornai (9 public). Public totals across all four accounts: 346. Checked: Profiles fetched 7 October 2026: HTTP 200. Counts from the October 2026 GitHub check. | Measured | kevanbtc · Y3KDigital |
| LPS-1-Reference-Implementation | The provenance standard's specification (CC BY 4.0) and reference code (MIT): Merkle pipeline, seven Solidity contracts, verifier. Checked: 58 contract tests and 21 pipeline tests passing on 9 September 2026; full suite self-reported at 293. | Measured | Repository |
| Genesis | The deterministic economic-ecology simulation behind the Genesis Protocol preprint: 15 Rust crates, 403 tests, 6,820 simulated worlds, reproducible result hashes. Checked: A re-run on 10 August 2026 reproduced the committed hashes byte for byte. | Measured | Repository · Operators and archive |
| genesis402-agent-kit and plugins | The agent kit (Dockerfile, the MCP server, tools) and the public plugin snapshot for the rail's address and risk checks, plus 402-truth, the open receipt and verifier formats. Checked: Repositories fetched 7 October 2026: HTTP 200. | Measured | Agent kit · Plugins · 402-truth |
| Donkai (chain 1977) | A satirical Layer-1 wrapping real components: 6 Rust crates (LPS-1 Merkle with 58 enumerated audit checks, post-quantum signatures and key encapsulation, policy adjudication, consensus, IPFS), 28 tests, three compiled Solidity contracts. MIT or Apache-2.0. Checked: Repository fetched 7 October 2026: HTTP 200; donkai.org also 200. | Measured | Repository · donkai.org |
| 2500 Donkeys | The deterministic literary-publishing project the LPS-1 standard was written for: text, audio and the eight-page paper, with every block anchored. Checked: Repository fetched 7 October 2026: HTTP 200. | Measured | Repository · Read it |
07 · Layer-1 research
Layer-1 research
Seventeen Rust workspaces on disk. None is on a public mainnet, and none is described as if it were.
| Node | What it is, and how it was checked | State | Where to look |
|---|---|---|---|
| Apostle Chain | An agent-to-agent settlement node in Rust: seven crates, chain id 7332. Honest line: a single-process node where agents register, sign, the node checks the signature, moves an internal balance and writes a receipt. Not a multi-validator network, no public explorer, no measured throughput. Private repository. Checked: On-disk audit, 5 August 2026. | Research | Research page |
| Genesis engine | 15 crates, 403 tests. Determinism from SHA-256 hash chains and a fixed generator; 44 experiments over 6,820 worlds and about 3.4 million epochs. Public, MIT. Checked: Reproduced byte-identical on 10 August 2026. | Research | Repository |
| UnyKorn-L-1 | 43 crates. Compliance-as-consensus modelled on UCP 600 documentary rules. Research code on disk. Checked: On-disk audit, 5 August 2026 (58 Rust files, 18 test annotations). | Research | no public link |
| Popeye-Tars-Mars-Tev | Six crates: node, consensus and three service layers. Public repository. Checked: On-disk audit, 5 August 2026 (36 Rust files, 21 test annotations); repository fetched 7 October 2026: HTTP 200. | Research | Repository |
| Treasury and settlement stacks | Three private workspaces from the FTH Trading side: an eight-layer treasury stack (50 members), a settlement kernel with matching and risk (5 crates) and a multi-chain key-management workspace (19 crates). The same settlement, ledger and compliance primitives appear in several of them; consolidation is on the roadmap. Checked: On-disk audit, 5 August 2026. | Research | no public link |
| Sovereign namespace protocol | 16 crates: a namespace and root-trust layer. Nothing has been issued on a public chain, and no value is attached to anything on chain. Checked: On-disk audit, 5 August 2026. | Research | no public link |
08 · Infrastructure
Infrastructure
Where the public surfaces and the rail actually run.
| Node | What it is, and how it was checked | State | Where to look |
|---|---|---|---|
| Cloudflare Workers and Pages | Edge routing and static hosting behind every public front door, with D1, KV and R2 where a surface needs storage. Checked: Every front door on this map answered from Cloudflare on 7 October 2026. | Available | Front doors |
| Dedicated rail host | The rail runs on dedicated always-on infrastructure, not a laptop, as a single origin with blue/green deploys and a SQLite ledger with one writer. Every change is checked against the served response after it ships. Checked: Described on the rails page; verified at each release. | Available | Rails page |
| Off-box uptime probe | A Cloudflare Worker outside the rail host probes it and publishes the result. Target 99.9 percent, measured rather than asserted. Checked: Status endpoint served 7 October 2026: HTTP 200. | Measured | Probe status |
| Public indexes | The rail is listed on x402scan, the MCP Registry, npm, Smithery and Glama, and in Coinbase's x402 Bazaar discovery index (347 endpoints indexed on 29 September 2026, the seventh-largest host by count; a presence metric, not a ranking of quality or volume). Checked: Measured with a public script; result saved with the site source. | Measured | x402scan · Glama |
Method
How this page was made
1Fetch
Every front door, GitHub profile, repository, DOI and the ORCID record on the map was fetched from a plain HTTP client on 2026-10-07. A node whose check failed would say so; none did.
2Source every number
Counts come from the desk's dated audits (on-disk workspace inventory, GitHub profile counts, registry reads, test runs) and are printed with their dates. Private repository counts are never added into a public number.
3Label, never upgrade
The labels are the same ones used across this site. A thing built and used internally is In development until it is sold as a service; a thing on disk is Research until it is on a public network.
4Keep it machine-readable
The map, the panel and these tables all render one JSON file. Change the file, and every view changes with it.
Start with a free 30-minute scoping call.
Send the intake form and whatever documents you already hold. You will receive a scoping call within two business days and a written screen result within 48 hours of the documents arriving.