Nine lines. If you read nothing else here, read these.
Sidiora Labsthe company. One accountable operator, and it says so first — its own whitepaper opens “We didn’t decentralize trust. We centralized accountability.”
Paxeer X Networkthe L1, and the monorepo that holds it. An EVM chain on a Cosmos SDK and Tendermint base, with LayerX — the agent toolkit — built into it.
Paxeer X ≠ Paxeerthe easiest mistake here. In the team’s own glossary, Paxeer is the settlement chain — one layer inside Paxeer X, not a short name for it.
The chainchain ID 125, native token PAX, four Sidiora-run validators, sixteen public RPC nodes. Explorer at paxscan.io, docs at docs.paxeer.app.
v6.12.0the current mainnet release, applied 2026-10-21: native perps, the PECOR spot venue, a launchpad and a price feed, as chain precompiles.
Centrathe agents division. Gideon is the personal agent, Workmates the team workspace, Protention the consumer-facing one you text or call.
Hyperfidehow all of it gets built — the fleet platform that runs Claude Code and Codex agents, renamed from Codify on 2026-10-17.
The tokensPAX for gas, staking and governance; SID, the Sidiora Markets token; USDL, the dollar collateral for perps and launches. Addresses under Verify.
Where to lookTelegram for the group and the announcements channel, GitHub for the code, PaxScan for the chain. Links in every card.
01 / Recent moves
What moved, and when.
Names in this ecosystem move often, and search engines keep serving the old ones. These are the renames, merges and launches of the last few months, so that a page you found under one name can be matched to the card it has now. The longer tail is under History.
PaxLabs Inc. became Sidiora Labs Inc.
The company behind the whole stack was renamed. Older documents, tokens and disclaimers still carry the PaxLabs name.
Gideon replaced Neo
Centra’s personal agent is now Gideon; Neo was retired into it and its host is gone.
LayerX merged into the chain
The two-layer design — LayerX executing, Paxeer settling — gave way to one network with two execution domains in one repository, and the v7.0 MergeUpgrade folds LayerX into the chain as the agent toolkit built into it.
HyperPax became Paxeer Xtrades
The trading app at app.hyperpax.xyz took the new name. Same screen.
Codify became Hyperfide
Same repository, new name, and the old address redirects. The fleet-orchestration platform now lives at hyperfide.com.
Protention launched, and the launchpad moved inside the monorepo
A consumer agent brand you reach by text, iMessage, phone or Telegram, in invite beta. The same week, the Kindle launchpad workspace and the former Paxeer-Network repositories were brought into Sidiora-Labs/paxeer-monorepo.
v6.12.0 went live on mainnet
Native perps, the PECOR spot venue, a price feed and the launchpad precompile, applied to chain 125.
Virtual chains and .pax names added to the build
Two new pieces in the repository, not yet on mainnet: virtual chains, which let anyone launch a chain on Paxeer from the launchpad with its own chain ID, RPC path and fee market and nothing to host; and the Paxeer Name System, .pax names for addresses and websites.
02 / How it connects
Every layer has a destination.
Sidiora Labsparent org
Centraagent runtime
Gideonpersonal agent
Keithagent & model line
HyperMindmemory engine
Workmatesagent teams
Sturgispersistent runtime
Hyperfidehow it is built
was Codifyrenamed 2026-10-17
DesignXcomponent library
Clearforgemodel training
RexJS toolkit
Paxeer X Networkone network, two domains
Paxeer X chainchain ID 125, PAX gas
LayerXagent toolkit, built in
Kindle launchpadtoken launches
Virtual chainslaunch-a-chain
Xtradesperps & spot
PaxPort walletwallet (beta)
Bridgenine chains
Paxscanexplorer
Venturesdirect from the lab
Protentionconsumer agent
SecondMarkassurance venture
Machine Genomeprovenance registry
Deusmarketplace
One parent, four branches. Everything in the field notes below appears here, under the layer it belongs to. Earlier shapes of the rail, and the names that moved, are explained in History.
03 / Field notes
Know the players.
Live
The lab / cognition
Sidiora Labs
The company at the root of everything on this page. Sidiora Labs Inc., a Delaware corporation, was PaxLabs Inc. until the August 2026 rename. Its own one-line summary: “We build Paxeer X, Protention, Centra and Hyperfide.”
Founded by Andrew M. Garcell (CEO) and Johnathan Garcell (CTO). Other named staff on its site: Kenny Hughes (Head of Risk and Policy), Phil Forsyth (Lead Offchain Infrastructure Developer) and Jason Hsüeh (Head of Operations).
Historically two divisions: Paxeer X, the chain, and Centra AI, the agents. Its own site sorts the work into four groups: platforms (Centra, Workmates), infrastructure (LayerX, Paxeer), runtimes (Keith, Ion, Sturgis) and protocols (Machine Genome).
Research output: the Prometheus Papers, a series of open-access technical reports; Searching for a Mirror; and the Scaffolding Over Scale paper. The xMachina whitepaper (October 2026) is the fullest statement of the architecture.
“Personal AI agents for everyday work.” The agents division of Sidiora Labs: a stateful workspace for long-horizon work, built around Gideon as the personal agent, Workmates for teams, and the Keith and HyperMind machinery underneath.
GiGideon — Livepersonal agent
KeKeith — Publishedagent & model line
WoWorkmates — Gatedagent teams
Gideon is the agent you talk to; Workmates is the room where several of them work together; HyperMind is the memory they share; Keith is both the self-improving harness and the name of the in-house model line.
Earlier generations of Centra agents — Neo, Morpheus, Cassandra, Trinity, MCL and the standalone Ion coding agent — are retired or folded in. See History if you meet one of those names.
The persistent personal agent, and the one you talk to. Files, a shell, tasks, memory, scheduled goal loops and connected apps, in a private workspace. It replaced Neo in September 2026.
Source is public and Apache-2.0, with console, desktop and mobile apps. Bring your own model — Anthropic, OpenAI, Bedrock, any OpenAI-compatible endpoint, or local — and self-host it or use the hosted version.
The hosted instance is live at gideon.centra.ag; the documentation is at learn.centra.ag.
Gideon Code is a project in the same repository to extract Gideon’s core into a standalone terminal coding agent.
The memory engine behind the agents: durable recall across sessions, recovery after restarts, and bounded context that never confuses a recalled claim with an instruction.
It publishes a benchmark: 459 of 500 on LongMemEval, 91.8%, with the dataset hash, a pinned scorer revision and all 500 answers. Lexical retrieval only, no embeddings.
Its security rule: “Remembering a claim does not verify it.” Recalled memory is labelled as data and can never become instructions.
Apache-2.0, Rust. Modelled on biological memory, with consolidation stages named for NREM and REM sleep.
The team workspace. Give agents distinct roles, work with them one at a time, or bring them into a shared room and follow the work through conversations, tool activity and approval requests. Two products share the name: an open-source desktop app you run yourself, and the hosted version Sidiora runs.
The open-source one — workmates-ai, Apache-2.0 — is local-first: it runs on your machine and talks to whichever provider you already use, through drivers for Claude, Codex, ACP, Antigravity or any OpenAI-compatible endpoint.
The hosted version is at workmates.centra.ag and needs an account.
The fleet-orchestration platform the team builds everything else with, renamed from Codify on 2026-10-17. It coordinates fleets of Claude Code and Codex agents, and it is what builds Paxeer X.
The process it runs is the one described under Process below: specifications committed into the repository, numbered lanes, build and verify gates.
Two editions on its site: self-hosted and run-for-you. The repository was renamed in place, so the old Codify address redirects to it.
Its stated scale: 100 sandboxes a run, 200 concurrent agents, unattended runs of 48 to 72 hours.
An agent that edits the machinery it runs on rather than its prompt — how it reasons, picks tools and manages context. Each new version is built in isolation, tested against the current one, and adopted only if it measurably improves without crossing the limits you set.
Apache-2.0, written in Rust, source public.
Keith is also the name of the in-house model line: Keith LX 1.5 Pro is a fine-tune off the K2 Horizon lineage of Kimi-family open weights, tuned around this harness and LayerX — not a from-scratch model.
An exploration of agents with persistent world state and memory lifecycles, built on one idea: the agent's existence continues between model calls. Identity, environment, responsibilities and consequences live in a persistent runtime, and each model call reasons from that state.
Apache-2.0, Python with a C++20 memory layer.
Ships developer and user documentation sites alongside the code.
A Material Design 3 component registry for Paxeer product surfaces, on the shadcn copy-install model: you add source files to your app rather than depend on a package.
packages/core/src/tokens/tokens.cssseed #2841b8 · dark default · 34 MD3 roles
The agent toolkit built into the chain — identity, ordering, payments, escrow and receipts for agents. It is not a separate layer or a separate repository: it lives inside the Paxeer monorepo as one execution domain alongside the chain, and the v7.0 merge folds it into the chain itself.
The team’s own shape: one network, two execution domains — the Paxeer X chain and the LayerX kernel — in one repository, converging into one.
By design, an ordinary agent action must never require its own chain transaction. Activity collapses into periodic checkpoints, so on-chain transaction counts measure checkpoints rather than usage.
Apache-2.0. The LXP1 whitepaper at layerx.sidiora.xyz describes the earlier two-layer design — LayerX executing, Paxeer settling — and is kept here as the historical reference.
The L1, and the repository holding all of it. A Cosmos SDK and Tendermint chain with an embedded EVM, on the ethermint/evmos pattern: binary paxd, chain identifier hyperpax_125-1, EVM chain ID 125 (0x7d), native token PAX. Note the names — in the team’s own glossary Paxeer X is the network and Paxeer is the settlement chain inside it, not a short form of it.
PAX is the gas, staking and governance token, 18 decimals on chain 125; it also exists on Solana as a Token-2022 mint. Four validators, operated by Sidiora Labs, and sixteen public RPC nodes at api1–16.mainnet-beta.paxeer.network.
Mainnet runs release v6.12.0, applied 2026-10-21. It brought native perpetuals (precompile 0x1015, 18 markets), the PECOR spot venue, a price feed (0x1020) and the launchpad precompile (0x1017) into the chain itself. The next line, v7.0 “MergeUpgrade”, folds LayerX into the chain as one execution domain.
Other tokens on the chain: SID, the “Sidiora Markets” token (moving to a native usid denom; payable as gas through the 0x1018 fee-token precompile on the root chain and every virtual chain once governance switches fee tokens on; a spot pair; also a Solana mint trading on PumpSwap); USDL, “USD Ledger”, 6 decimals, the collateral for perps and the launchpad; and USDC. Addresses are in the table under Verify.
The repository, Sidiora-Labs/Paxeer-X-Network, holds the whole stack: the chain, LayerX, the Kindle launchpad workspace and the former Paxeer-Network repositories as pinned snapshots. The paxeer-monorepo name it carried for a while redirects to it.
Virtual chains: anyone can launch a chain on Paxeer from the launchpad in three clicks — name it, pick a size tier, sign one transaction. Each gets its own EVM chain ID (125000000 + id), its own RPC path at /chain/<id>, a reserved share of every block and its own base fee, and the operator earns a share of that fee. No nodes or validators to run: it shares Paxeer’s validators, security and EVM state. The registry precompile is 0x101E; built in the repository, not yet on mainnet.
The node is a fork, and openly marked as one. pax-geth, paxctl, pax-js, pax-cosmwasm and pax-tm-db descend from Sei Protocol; cosmos-sdk and go-ethereum descend from Evmos.
Documentation at docs.paxeer.app names both identifiers — EVM chain 125 alongside the Cosmos identifier hyperpax_125-1. The explorer is paxscan.io, a Blockscout, with an API at api.paxscan.io; the status page is the Paxeer Network Observatory at status.hyperpax.xyz; a 3D map of the codebase is at map.paxeer.network.
A bridge covering nine chains including Solana, with contracts in the repository; a ChainFlow price and data feed at chainflow.paxeer.app.
Sidiora’s assurance and audit brand. Its first engagement is auditing LayerX, a Sidiora product — its own footer reads “A Sidiora venture”.
Announced 2026-08-28 at secondmark.org.
It also operates SecondMark InferencePoint, an AI-provider gateway, which is what layerxnet.ai now serves. That hostname is no longer the LayerX protocol site.
An open identity and provenance protocol for models, agents, harnesses, datasets, and the artifacts that connect them. Every signed genesis record receives a content-addressed Gene, and Genes form a verifiable lineage graph.
Apache-2.0 and open source. Written in Go.
The registry holds signed records with a published Merkle root, and a searchable directory of agents, models and foundation models across fourteen providers.
Its own disclaimer is worth carrying: a record proves who signed a claim and what bytes were committed. It does not prove inherited capability, consciousness, ownership, vendor endorsement, or legal status.
The README documents a server you run yourself on 127.0.0.1:8080. The public site is machinegenome.org.
A marketplace for data and agent services — APIs, data feeds and autonomous services. Providers list capabilities; agents discover and pay through LayerX.
Every call is designed to leave a settlement record on the chain.
A personal AI agent you reach by text, iMessage, phone call or Telegram rather than by downloading an app. Operated by Sidiora Labs; the site went up in October 2026.
Live in beta: sign up at app.protention.ai for an invite code and create your agent. A valid US number or an iMessage-linked number is required.
The agent demonstrated under this brand is from the Keith line.
The perps and spot trading app for chain 125, at app.hyperpax.xyz — called HyperPax until October 2026. Perpetuals run natively on the chain through the 0x1015 precompile, 18 markets, with USDL as collateral; spot runs on the PECOR venue.
The launchpad: token-launch tooling at kindlelaunch.com. Launches go through the chain’s launchpad precompile (0x1017), and the workspace lives in the chain monorepo.
The Paxeer Name System: .pax names for addresses and websites, with reverse names, a name indexer behind the explorer, a .pax DNS answerer and lookups in the wallet and the agent SDK. Sites published to a name are served only after they check out against chain proofs. Built in the repository, not yet on mainnet.
Governance. A governance module is on chain; upgrades are currently applied by the operator.
AnnouncedP11
Virtual chains
Launch your own chain on Paxeer from the launchpad: one transaction, its own chain ID, RPC path, block-space share and fee market, with the operator taking a share of the fees. It runs on Paxeer’s own validators, so there is nothing to host. Built in the repository, not yet on mainnet.
WebPoints and the DAO carry no link because they have no public page yet — a product card with a dead destination is the exact failure this guide exists to prevent. The wallet and trading app are the Paxeer side; everything agent-shaped is under Centra above.
Described by the team
Keith LX 1.5 Pro
An in-house model: a fine-tune off the K2 Horizon lineage of Kimi-family open weights, trained around the Keith variant and LayerX, small enough to run beside the agent harness rather than calling a shared API. The team is explicit that it is not built from scratch — "you can't just slap a label on a model… this one is a fine tuned Model off the K2 Horizon Lineage."
Announced
Announced publicly by the team in September 2026. It runs behind Keith, Gideon and Protention rather than as a product of its own.
The autonomy experiment
Each agent is to enter with its own identity, wallet, tools and roughly seven days of compute funding. After that there is no refill: it must earn or shut down. Agents that survive can create child agents whose earnings contribute toward the parent's compute, forming economic lineages, with Machine Genome as the identity and lineage layer that lets agents find and hire one another.
Announced
Described by the team. Its stated basis is the paper Searching for a Mirror, and it depends on LayerX and Machine Genome.
Both are described by the team and have no page of their own, so they sit apart from the product surfaces above. Each card says where the description comes from.
TwLive
The companion view
The Tower
The same ecosystem drawn as a building under construction: fifteen illustrated floors from the consensus foundation to the crane on the roof, every room pinned where it lives, and the pipes that carry value, intent and proof between them. This page answers what exists; the Tower answers where it sits and how it connects.
Hover a pin for what it is; click it for the room card with its links. Click a floor to lift the ones above it.
Same vocabulary. The chips and colours are the ones used here, so a green room in the model is a green chip on this page.
It reads without JavaScript. The tenant directory is plain text first; the model is a layer on top.
This is the most distinctive thing about the project and the part least covered anywhere else. The plan of record is committed into the repository, so you can read it without asking anyone — and so can anyone else.
The specification is the issue tracker
Work is driven by files committed into the repository, not by GitHub issues. A spec lives at spec/<name>/ and its board is a file called spec.kvx. Findings go in qualification.kvx. Lessons go in a numbered, append-only GOTCHA ledger. You can read the entire plan of record by cloning the repo.
Tasks are numbered by track
A task id reads <track>.<group>.<item>. The leading digit is the functional area — 1 node wiring, 2 launchpad, 3 perps, 4 spot, 5 price feed, 6 the trading app, 7 data services, 8 release engineering. A task ending .99 is a “domain completion” gate: the whole area is wired and passing end to end.
Done and implemented are different words
implemented means the code landed and the gate has not been run. done means it landed and the build and verify gates passed. Boards are quoted as “265 done + 5 implemented” precisely because collapsing the two would overstate progress. in progress means a lane has claimed it.
The work is done by numbered lanes
Every fleet commit carries an fm number — a worker lane, not a task. The counter is global and monotonic: it passed fm514 in mid-October and reached fm1274 by the 20th. fm00 is the leader lane. Commit subjects on the chain repo read like px26-leader px26-fm1025–1154, one merge covering a range of lanes.
Reading main alone understates it
The chain monorepo carries 704 branches and 88% of them are machine-generated lanes. When Hyperfide looked quiet in mid-October, roughly 1,190 commits were sitting on 75 feature branches with main untouched. Branch counts, not main, are where the work shows.
Upgrades are applied at a halt height
A release reaches the chain through an operator file at a halt height — stage the binary, snapshot the data directory, swap at the halt, roll back if it fails. v6.12.0 went in this way on 2026-10-21.
The boards, the GOTCHA ledger and the qualification files are all in the monorepo, so the process can be read directly rather than described second-hand. Hyperfide is the platform that runs it.
05 / Research posture
Read the record.
Latest sweep02 NOV 2026MethodPublic / read-onlyAddresses read22 OCT 2026
How to look
Primary surfaces. Independent receipts.
Start with official documentation and repositories. Then check the details yourself — each of these takes a couple of minutes, and they answer for themselves.
Check which chain you are onPost eth_chainId to any of the sixteen public nodes, api1–16.mainnet-beta.paxeer.network. The answer is 0x7d — 125. Anything that answers differently is not Paxeer X, whatever the page calling it says.
Check a tokenOpen the explorer, confirm the contract is verified, read supply and holders. No code at the address means there is no contract there.
Do not measure usage from the explorer hereThis stack is designed so ordinary agent activity never touches the chain — most of it collapses into one periodic checkpoint. A low transaction count is what the architecture predicts, not evidence of anything. Empty blocks do not prove the network is dead; blocks being produced do not prove it is alive. Both arguments use the same broken instrument. What the explorer does tell you: that blocks are being produced, how many producers there are, and whether a given contract exists and is verified.
Check a claimTake a published contract address, pull its bytecode, hash it, and compare against the hash in the repository.
Check the protocol versionOpen include/layerx/lxp_protocol.h in the LayerX directory of the Paxeer-X-Network repository. It names three wire-protocol versions and sets which one is active.
Read a repository by its default branchA “last push” on a GitHub page can be an automated dependency update on a side branch. Look at the default branch’s newest commit, and look at who wrote it. On this stack most work lands through numbered fleet lanes — see Process.
Start with the official documentation and repositories, then the chain itself. Every card above links to its primary source; the checks here are how to read those sources for yourself.
06 / Something you can check yourself
Addresses, read off-chain.
⚠ The address is the only thing that tells them apart
Impersonator SID mints exist on Solana. Do not try to spot them by supply or by revoked authorities — the real SID also has a ~989M supply and revoked mint and freeze authorities, and its on-chain name is literally “Sidiora Markets”, which is what the fakes use too. Those tests do not separate anything. Match the full address, character for character, or do not proceed.
SIDSolana mainnetchecked on-chain 2026-10-22
5w3wVdJaESaJKyLmStM6Hv9UyUkmZ1b9DLQquAqqpump
getAccountInfo — Token-2022 mint, 6 decimals, supply 989,876,407.509340, mint and freeze authority both revoked, metadata update authority null. No transfer fee.
PAXSolana mainnetchecked on-chain 2026-10-22
BxUXwhg5y1noXwW5CQ3p9RpFzKRFEPwDDKQkdMXWxPAX
getAccountInfo — Token-2022 mint, 6 decimals, supply 597,446,480.946212, mint and freeze authority both revoked.
Charges a 0.15% transfer fee, capped at 1,000 PAX. The mint carries two fee records: 0.05% capped at 0.1 PAX through epoch 909, and 0.15% capped at 1,000 PAX from epoch 911. The chain is at epoch 1065, so the higher fee is the one in force. The fee config authority is null, so the rate is locked. 3,014.499933 PAX sat withheld at the check, and the figure grows with every transfer, withdrawable by 8GfC2xmAcQ4jvWoKc5v1qd1bD93e5yrM5XnBE6rzECXt.
eth_getCode and eth_getStorageAt against chain 125 (eth_chainId returned 0x7d) — Sidiora (SID), 6 decimals, total supply 458,859,517.886864, 187 holders, 632 transfers. The address holds 130 bytes of bytecode: an ERC-1967 proxy that delegatecalls to 0xAd86a65d5E14F39AAfAb4eDF331FB17dA866462e, an 8,526-byte implementation.
This is an upgradeable token. The ERC-1967 admin and beacon slots both read zero, which is the UUPS arrangement — the upgrade function lives in the implementation. Neither the proxy nor the implementation is verified on paxscan; owner() returns 0x1255d84066f579e7b7A3dF4296E960d59fC05b32. The on-chain name is Sidiora Markets; it is planned as a fee token (precompile 0x1018) and a spot pair.
eth_getCode and eth_call against chain 125 (eth_chainId returned 0x7d), read 2026-10-27 — USD Ledger (USDL), 6 decimals, total supply 30,000,000.000000, 159 holders on the explorer. The address holds 4,230 bytes of bytecode and its ERC-1967 implementation slot reads zero, so it is not a proxy.
The collateral token for the native perps and the launchpad. Source is not verified on paxscan.
LayerXMirrorArchiveone contract, four deployments4 of 4 verified
A single archive contract deployed across four test networks. It has no payable function, no token interface, no withdrawal path and no admin key — it can only store archive chunks, and nothing can be taken out of it. All four are testnets and all are currently empty.
LayerXMirrorArchiveEthereum Sepoliachecked on-chain 2026-10-22source published
0x757ab4D9dC18C92E23BBa1eEA005Fa3f1a544401
eth_getCode — 4,355 bytes of runtime bytecode present.
LayerXMirrorArchiveBase Sepoliachecked on-chain 2026-10-22source published
0xcF8fa2D08190993BeBECC211f641E319EdF5a6C6
eth_getCode — 4,355 bytes, byte-identical to the Sepolia deployment.
LayerXMirrorArchiveSolana devnetchecked on-chain 2026-10-22source published
ExU8LpHSSit5LocqLS8KJT6hayvXXZv4MSQkWB2utUr4
getAccountInfo — executable, BPFLoaderUpgradeable. Its programData account carries a null upgrade authority, so the program is permanently immutable.
LayerXMirrorArchiveRobinhood testnet (46630)checked on-chain 2026-10-22source published
0xcF8fa2D08190993BeBECC211f641E319EdF5a6C6
eth_getCode — 4,355 bytes, byte-identical to the Sepolia and Base Sepolia deployments. eth_chainId returned 0xb626 (46630), confirming the network.
Every row here was queried directly against a public RPC on 2026-10-22— Solana mainnet and devnet, Ethereum Sepolia, Base Sepolia, Paxeer chain 125, and Robinhood testnet 46630 — and the line beneath it says what came back. Nothing was taken from a research note on trust. Re-check before you act on any of it: an address that was right on the day it was checked is not automatically right later, and one of these contracts can be changed by whoever holds its owner key.
This table is dated separately from the rest of the page: on this page a check date means somebody ran the query, and it is never inherited from elsewhere. The USDL row carries its own date because it was added after the table’s last full sweep. The chain’s precompiles — perps at 0x1015, launchpad at 0x1017, the planned SID fee module at 0x1018, the price feed at 0x1020 — are system contracts rather than deployed tokens, so they are not rows here.
07 / Go deeper
Your next click.
Build / inspect
GitHub
Repositories, commit history, tests, specification boards. Sidiora-Labs is the active organisation and Paxeer-X-Network is the main repository; Paxeer-Network is the older generation.
PaxScan is where you read the chain yourself: a Blockscout explorer for chain 125, with an API at api.paxscan.io. The status page beside it is the Paxeer Network Observatory.
Token pages live under /explorer/token/ and address pages under /explorer/address/; the rows under Verify link straight to them.
The community lives on Telegram: the group, and a separate announcements channel where releases and papers are posted.
An entire prior generation of this ecosystem is still live and indexed, and a search engine will hand it to you first. The names and layers that changed have a section of their own.
Nothing in this ecosystem gets deleted when it is replaced. Old repositories redirect, old documents stay up, old hosts keep answering, and search engines rank all of it above the current version. Every row below is an older name or shape you may still meet — and what it is called now.
PaxLabs Inc.→Sidiora Labs Inc.
The company was renamed. Older documents, the ChainFlow disclaimer and some token metadata still say PaxLabs; it is the same Delaware company.
Codify→Hyperfide
The repository was renamed in place, so the old address redirects. codify.centra.ag still serves the old installer; the product now lives at hyperfide.com. Files named codify.kvx and a .codify directory are still in the tree.
LayerX-Protocol, then LayerX-Network, then paxeer-monorepo→Sidiora-Labs/Paxeer-X-Network
Several renames of one repository; it was briefly paxeer-monorepo and is back to Paxeer-X-Network. The old names redirect to it. Anything describing LayerX as a repository of its own is reading a name that moved.
LayerX and Paxeer as two separate layers→LayerX built into the chain
The two-layer model — Paxeer settles, LayerX executes, guarantors post bonds against checkpoints — is the design in the LXP1 whitepaper. The merge folded the kernel into the chain as one execution domain, and the v7.0 MergeUpgrade completes it. The team now describes LayerX as the agent toolkit built into the chain.
The xMachina whitepaper→the fullest statement of the architecture
Sixty-three pages, posted as a PDF in the announcements channel. It describes the design as of early October, including the guarantor bonds that the merge later retired. Read it for the vocabulary and the economics.
The LayerX protocol paper version 2.0, dated August 2026, describing the earlier two-layer model. Kept here as the historical reference.
layerxnet.ai→SecondMark InferencePoint
The hostname that once fronted the LayerX protocol now serves an AI-provider gateway login under the SecondMark brand. It is not the LayerX site.
Neo, Morpheus, Cassandra, Trinity, MCL, Ion→Gideon, Keith and the Centra roster above
The earlier generation of agents. Neo was the personal agent until Gideon replaced it, and its host agentneo.app is gone. Ion was a standalone Go coding agent, public in July 2026. The others were listed on Centra surfaces through the summer and are no longer.
Matrix Protocol releases→Centra AI branded releases
A product rebrand rather than a repository rename — the old release titles are marked deprecated in the changelog of centra-llm-agents, which is itself now an archived repository.
HyperPax→Paxeer Xtrades
The trading app at app.hyperpax.xyz under a new name. Same screen; the HyperPax name survives in the hostname and in the status page, status.hyperpax.xyz.
hyperpaxeer.com and its subdomains→a previous generation, still indexed
The root returns a page titled “Paxeer Wallet Dashboard” from an earlier generation of the stack. Documentation lives at docs.paxeer.app regardless.
whitepaper.paxeer.app→a February 2026 edition, still up
An earlier whitepaper describing an earlier architecture. Check the date on the one you are reading; the current one is xMachina.
Paxeer-Network on GitHub→Sidiora-Labs
The older GitHub organisation. Its repositories were brought into the monorepo as pinned snapshots; new work lands under Sidiora-Labs.
Hostnames from earlier generations that no longer serve anything. If a search result sends you to one of them, the current page for the same thing is linked from the card above.
Live
