6529, for developers

What 6529 is, technically

The sixty-second version, for someone who has read none of it

6529 runs 6529.io — a web3 social, collecting and governance application built around The Memes, an NFT collection that has dropped a card every Monday, Wednesday and Friday since June 2022.

Underneath the social product there is a network-state layer: every identity accumulates TDH (a time-weighted measure of what NFTs you have held, for how long), plus rep, cic and a derived level. Those numbers are not cosmetic — they are the permission system. Groups are defined by rules over them, and waves (the conversation surfaces) attach up to six groups each: who can see, chat, submit, vote, administer and curate.

So the interesting engineering is not the chat app. It is that a social platform's entire authorization model is computed from on-chain holdings, and the stated goal is for that computation to eventually run on independent nodes rather than on 6529's servers.

What is in production today

The stack that actually serves 6529.io

Both main repositories are public and the API is open: api.6529.io answers unauthenticated reads with access-control-allow-origin: *. You can query identities, groups, waves and drops without a key.

Repository map

All 18 public repositories, by last push · 1 Aug 2026

Ages above are baked in from the snapshot date. This page tries to refresh them live from the public GitHub API when you open it; if that fails, you are reading the snapshot.

"Dormant" means no pushes, not abandoned intent — nftdelegation is dormant because a deployed contract does not change. The two that matter for understanding the project's direction are 6529-Prenode and 6529node.

The decentralization lineage

Three attempts, and how they relate to what runs today

This is the part that takes longest to reconstruct from the outside, because the repository names suggest a progression that did not happen. There are three distinct things, and only one of them has ever served traffic.

1 · Production — the only thing that has ever run

6529seize-backend computes TDH in src/tdhLoop — about 2,580 lines of TypeScript, dominated by tdh.ts (1,142 lines), plus consolidation, editions, memes, merkle and upload modules. It has run continuously and receives commits daily.

2 · Prenode — a slice of production, packaged for others to run

6529-Prenode is not a reimplementation. Its src/tdhLoop shares file names with production — index.ts, tdh.ts, tdh_consolidation.ts, tdh_merkle.ts — and the same serverless configuration shape. It is the production calculation, trimmed and wrapped so a third party can run it on their own AWS account and serve TDH over REST.

Its README states the purpose plainly:

"The 6529 Prenode decentralizes access to TDH data… it uses the same calculation logic as the 6529 websites. Standardized setup through a provided CloudFormation script means anyone can run on their AWS account."

"Most important: the immediate use of the Prenode is to enable multiple parties to independently serve as TDH providers to the on-chain TDH oracle contract that will be launching soon™. This will allow for on-chain composable TDH that is not dependent on any single party." — 6529-Prenode README

Note what this design gives and does not give. Many operators running one codebase is operator diversity. It is not implementation diversity: if the shared logic has a defect, every prenode agrees on the same wrong answer, and an oracle consuming them sees unanimity.

3 · 6529node — a different architecture entirely

6529node is Go, and its internals are config, db, eth, mempool, network, rpc with a cmd/node entrypoint. Mempool and a network layer are the vocabulary of an actual peer-to-peer node, not a REST service. It is a ground-up attempt at the real thing, 94 commits, last touched 7 March 2025. It has never served production traffic.

The prenode registry today

There is a live registry at api.6529.io/oracle/prenodes, surfaced at 6529.io/network/prenodes. Read on 1 August 2026:

The registered hosts are community-run and self-funded — decentralizationmaxi.com, node.freedomtotransact.xyz, regularnode.com and others. The oldest registration is 27 June 2024; its last update was April 2025.

The reading that fits the evidence: participation was not the constraint. Thirty-seven operators is a strong response for a project this size. The on-chain TDH oracle that gave prenodes their purpose has not launched, and the prenode code stopped tracking production in July 2025.

// production — src/tdhLoop/tdh.ts
const hodlRate = equalIgnoreCase(nft.contract, MEMES_CONTRACT)
  ? MEMES_HODL_INDEX / (memesCalculationEditionSizes[nft.id]
                        ?? getCalculationEditionSize(nft))
  : nft.hodl_rate;

// Prenode — src/tdhLoop/tdh.ts
const hodlRate = HODL_INDEX / nft.edition_size;

Specifications: what exists and what does not

Where the protocol is written down, and where it is only code

Why the eligibility spec is worth reading even if you never touch that code

It is the first artifact in this codebase that treats a rule set as a protocol rather than as behaviour. The format is worth stealing: a normative document, golden vectors as language-neutral JSON, and a harness that runs them against every implementation.

It also demonstrates the value immediately. When the vectors were first run against the two existing implementations — both written by the same team, in the same language, in the same repository — they disagreed in nine reproducible cases. Two of those were plain defects; the rest needed a human ruling on what the semantics should be. The spec's section 12 records each decision.

A vector is a term borrowed from cryptography: known inputs plus the exact output any correct implementation must produce. Because they are JSON and not test code, an implementation in any language can be checked against the same file.

Method

So you can check everything here, or correct it

The scripts in this repository fetch the channel and build a local reader from it. The archive itself is not republished here — read it at the source.