NFDomains and TxnLab listings removed from AlgoDirectory, cutting collateral 74%
The two top listings are gone
For as long as AlgoDirectory has ranked the Algorand ecosystem by the ALGO each listing owner deposits as collateral, one entry anchored the table: NFDOMAINS, vouching with 1,000 ALGO — ten times the next-largest deposit. That row has disappeared, and so has TXNLAB's 100-ALGO listing. The home page now displays 28 entries carrying roughly 377 ALGO in total collateral, down from roughly 1,477 ALGO across 30 entries; the two removals account for about three-quarters of the directory's displayed trust signal.
Who left matters as much as what was pledged. AlgoDirectory is built on NFD, Algorand's naming service: every listing is a segment of the directory.algo domain, a name held as an on-chain asset. NFDOMAINS is the naming service itself, and TXNLAB is a developer company. NFD's own records show both names are owned by the same Algorand address — one that also owns defi.nfdomains.algo, a name in NFD's own root namespace. The two departed listings came from a single account embedded in the infrastructure the directory itself depends on. The top of the table is now shared by Cosmic Champs and the developer listing DOUG, each at 100 ALGO.
Why the collateral column is the product
The Vouching Protocol turns those numbers into curation. Listing owners deposit ALGO to vouch for a listing, and the project states the amount 'will be displayed in the Directory and affect default listing order.' Freshness is the second half of the signal: listings age, owners reset the clock by refreshing, and stale entries are de-emphasized but still discoverable. There is no human editor deciding what appears first — deposit size and recency are the entire ranking system, which is what makes the removal of the two largest deposits a change in the directory's actual output, not just its optics.
That ranking is computed from chain state, not a database. The web app reads the directory contract's box storage — on-chain key-value state attached to the smart contract — through Algorand's AlgoKit client tooling, decoding each listing as a struct carrying its timestamp, vouched amount, NFD app ID, tags, and name, over node infrastructure Nodely provides. This is the technical answer to the failure that killed the Web2 predecessor directorydotalgo.xyz, which lapsed when its volunteer curator stopped paying for hosting: contract state has no hosting bill. The economics fit the design, too — a refresh is one Algorand transaction, costing fractions of a cent, so the collateral deposit is the real cost of signaling confidence, not the transaction fees.
Three ways a listing can leave the directory
| Concept | Real-World Implication |
|---|---|
| Delist — the listing owner withdraws | The deposited collateral returns to the creator's address and the segment leaves the directory; this is the route a voluntary exit would take, and it returns the capital rather than losing it. |
| Remove — any caller can trigger it | If the NFD segment behind a listing is sold or transferred, anyone can clear the stale listing with collateral still returned to the original creator. NFD records still list both departed segments under the same owner, so this route cannot explain the removals. |
| Delete — an admin-token holder triggers it | Holders of a special 'directoryAdmin' token can remove any listing 'at any time for any reason,' with the collateral forfeited to the network's fee sink as a penalty. The contract's testnet deployment artifacts show such a token with a supply of ten units; whether it exists on mainnet and who holds it is undisclosed. |
The project has issued no statement about either departure, and the two remaining routes have opposite financial outcomes: a delisting returns the combined 1,100 ALGO to the owner, while an admin deletion forfeits it. From outside the contract, the two are indistinguishable.
Who holds the levers
AlgoDirectory was built by Brian (@SilentRhetoric) and Christian (@tak-o-kat) under a 50,000-ALGO grant from the Algorand Foundation's xGov program (proposal 123, approved in period 3). Their proposal described the technical approach as 'a wrapper around existing functionality provided by segments of the directory.algo NFD.'
That framing deserves scrutiny as a structural conflict, not an accusation: the directory presents itself as a neutral ecosystem ranking, yet it is a product layered on one vendor's naming namespace, and until this change the vendor's own listings occupied the top of the ranking by a wide margin — with no disclosure on the site of that relationship. The admin token adds a sharper tension: a small, unnamed set of holders can override the deposit-based ranking at will, which means the removal of the top two listings could in principle have happened without their owner's consent. No independent audit of the contract is referenced in the project's public material. The code is open source, so the mechanism itself is inspectable — the admin role's holders are not.
A Manage page arrives
The Manage page the project has long pointed users to now exists. Connecting Pera, Defly, Exodus, Lute, or anything reachable through WalletConnect starts a three-step flow: mint a segment of directory.algo, sign in with the owning account, then pick tags, deposit ALGO, and create the listing — no approval needed from anyone. Until now, the directory's own pitch — owners maintain their own data — was hard for an outsider to exercise; the page is the missing operational piece of the permissionless model, and it is the only mechanism by which new collateral can enter a table that just lost most of its top weight.
Bottom line
The two facts point in opposite directions. The ownership record and the silent removal are consistent with the Vouching Protocol working exactly as designed: collateral is a recoverable signal, not a fee, and an owner is free to leave with the deposit. The less comfortable reading is that the directory's most visible confidence measure collapsed in a single step — the largest change to the table since we began tracking it — with no explanation, and the protocol contains a mechanism by which that could have happened against the owners' wishes.
The Manage page removes the last gatekeeping step from the listing flow. Whether that flow attracts prominent collateral from teams with no connection to the directory's founding infrastructure is now the open question — and it is the question the Vouching Protocol exists to answer with data rather than promises.
Source
- AlgoDirectory
- AlgoDirectory Manage page
- directory.algo segments on NFD
- xGov-123: AlgoDirectory (directory.algo)
- AlgoDirectory GitHub
- Nodely
- | AlgoDirectory
- cosmicchamps | AlgoDirectory
- About | AlgoDirectory
- algorand-smart-contract · GitHub Topics · GitHub
Source: https://algodirectory.app