AlgoDirectory ranks Algorand's ecosystem by the ALGO each listing stakes

2026-08-11

directory · ecosystem · nfd · curation · discovery · web · algorand · updated

The Directory That Cannot Die of Boredom

The graveyard of Algorand directories tells a consistent story. Algo Tables, Algo Curator, Into The Algoverse, and a list run by the Algorand Foundation itself were each hand-assembled by volunteers, and each faded as enthusiasm — or the hosting bill — ran out. The last holdout, directorydotalgo.xyz, followed the same arc: its maintainer walked away and the domain expired. AlgoDirectory is the project that set out to build a directory that cannot die that way, by storing it on the chain and letting entries rank themselves by the money at stake.

The directory was funded through Algorand's xGov community grant program — in which ALGO holders lock tokens to earn voting power and vote on which ecosystem projects receive grants from the xGov treasury — under proposal xGov-123, approved in period 3 with 50,000 ALGO requested. The authors, developers Brian (SilentRhetoric) and Christian (tak-o-kat) of Distributed Ledger Technologies, describe it as the spiritual successor to directorydotalgo.xyz, picking up the torch with a different approach: listing owners maintain their own data, so no central curator ever burns out again.

What 'Permissionless' Means Here

Every listing is a segment of directory.algo, a sub-name of the NFD naming service — Algorand's on-chain equivalent of domain names, where names are native assets on the chain. Listing is a three-step flow: mint a segment and fill out its metadata; visit algodirectory.app/manage and connect the wallet that owns it (Pera, Defly, Exodus, WalletConnect, and Lute are supported); then select tags and deposit ALGO to vouch for the listing — to 'put their money where their mouth is,' in the project's words. Businesses, apps, NFT projects, websites, individuals, and open-source software are all eligible.

The permissionless part is listing. Administration is not. The contract's visible global state is a single key — an admin token, AlgoDirectory Admin (AD-ADMIN), with a total supply of two — and a separate one-of-one token, AlgoDirectory Update (ADUPDATE), gates updates to the application itself. Both assets were created by the same account, which is also, per NFD, the owner of the directory.algo root domain, the namespace every listing lives under. One other address holds the second admin token. Both assets are default-frozen, with the creator holding manager, freeze, clawback, and reserve authority, so even transferring the keys requires the issuer's cooperation. In plain terms: anyone can list, but the delete key and the upgrade key are concentrated in the hands of the namespace owner.

Five Operations, One Life Cycle

The Vouching Protocol governs a listing's life through five operations.

The protocol's warning to listing owners is blunt: 'Do not create a listing if you think it might be objectionable, lest it get deleted by an admin.'

The Board Today

The result is a leaderboard of skin in the game. As of this writing, 28 listings vouch roughly 377 ALGO in total. The top of the board:

Below that row sit the 10-ALGO middle tier — LEAKZ, ALGOKIT, TAKOKAT, and SILENTRHETORIC among them — and a long tail of 14 entries at the floor of 0.0722 ALGO, including a batch of nine listings that joined together (SIWA, TXNDUCK, ROBBIE, RAULLITO, PHEAR, WENTOOLS, LARKIN, STAKE, and NODELY).

A Floor That Is Also a Price

That floor is not an arbitrary round number. It is the contract's own arithmetic: 72,200 microAlgos, the exact cost of the two on-chain boxes a listing occupies — 31,300 for the NFD-to-listing map and 40,900 for the listing struct box. The minimum deposit is, in effect, the storage price of an entry; every ALGO above it is pure signal.

Freshness Is the Second Metric

The freshness column is equally unspinnable. The most recently touched listing, FISHERMAN, was refreshed about 11 months ago; every other entry shows one to two years. By its own freshness metric, the directory is quiet — and the design's virtue is that it says so openly rather than hiding it behind a hand-maintained veneer. The economics have limits worth stating plainly: 0.0722 ALGO is a nominal spam filter, trivial for anyone with a few dollars, and the protocol's core assumption — that larger deposits mean better projects — remains untested at this scale.

Inside the Contract

Under the hood, the directory is a singleton smart contract on Algorand mainnet storing each listing as a 64-byte struct: timestamp, vouch amount, NFD application ID, up to 13 tags, and the listing name. That struct lives in box storage — on-chain key-value space attached to the contract, paid for from the contract's own minimum balance. Two box maps form the actual database: one maps NFD application IDs to listing structs, the other maps each struct back to its owner's address. On creation, the contract checks that the NFD is genuinely a segment of directory.algo, that the caller owns it, that it has not expired, and that it is not listed for sale — a sale wipes the name's properties and would invalidate the listing.

The web app is a thin client over that state, with no database of its own. It reads the contract's boxes through Algorand's AlgoKit tooling over infrastructure run by Nodely, which the site credits in its footer, and the project's code is open source across three repositories: the web interface, the smart contract, and a subscriber process that watches the chain and posts listing updates to X and Bluesky. Open source, though, does not mean busy: the web app's last commit was December 2024, and the other two repositories went silent the month before, right after the subscriber's v1.0 'Mainnet launch.' Across the three repos the project holds 8, 2, and 1 GitHub stars respectively — a small project, honestly labeled. The quiet is the design working as advertised: a directory in contract boxes has no hosting invoice to lapse. But quiet it is.

The Naming Layer's Conflict of Interest

No account of AlgoDirectory is complete without its most awkward chapter, because it pits the directory's premise against its own foundation. For most of the directory's life, the board was anchored by NFDOMAINS — the naming service the directory itself is built on — vouching 1,000 ALGO, ten times the next-largest deposit, with TxnLab's 100-ALGO listing in second place. Both rows are now gone. NFD's own records show the two names share a single owner address, one that also holds defi.nfdomains.algo within NFD's own root namespace. Their departure cut the board's displayed collateral by roughly three-quarters, from about 1,477 ALGO across 30 entries to the current 377 ALGO across 28, per the figures above. The premise that no one curates this list is, as a practical matter, true for everyone except the infrastructure layer itself: the parties who control the naming layer also controlled the board's two largest signals, and could remove them without a single Vouching Protocol rule being invoked.

An Honest Ledger

The tradeoffs deserve equal billing. The admin token is a single point of deletion, its two holders known only as on-chain addresses — one of which owns the root namespace — with no community oversight mechanism described in the project's materials. The contract holds listing owners' collateral, and those same materials disclose no independent audit. The trust signal the ranking runs on is gameable at the margin and unproven as a proxy for quality. For a small, grant-funded project, those are substantial caveats.

What remains is the core experiment, and it is working on its own terms: a directory that ranks itself by stake, refreshes itself by transaction, and can sit untouched without dying — the one promise every Web2 predecessor failed to keep.

Source

• AlgoDirectory
• xGov-123: AlgoDirectory proposal
• NFD segments of directory.algo
• AlgoDirectory GitHub
• Home | AlgoDirectory
• About | AlgoDirectory
• Lora App:2443896070 mainnet
• Lora Acct:RZ6B…7DXM mainnet

Source: https://algodirectory.app