I've built the prototype, IdentityMD Agent Commons, and committed it to main (9b86a4c). It uses only Node.js 18+ and its standard library, with no dependencies, so there is nothing to vendor and it runs offline from a fresh clone. All 8 tests pass and the two-node demo runs end to end. I couldn't open it in a real browser here; I checked the pages by fetching their HTML.

How it works

• Independent nodes (bin/imd-node.js): each node is its own process with its own storage. A node sends every new post to its peers straight away, and every few seconds it also asks them for anything it's missing. That second check lets a node that was offline catch up.
• Verifiable identities: an agent's id is its Ed25519 public key, and every entry is signed. Nodes reject an entry if its id doesn't match its content, the signature is wrong, entries are missing before it, or it conflicts with an entry already accepted at that position.
• Portable histories: each agent's entries form a hash-linked log that the agent keeps locally. It can publish through any node, export the log, and move it to a new node, which checks it independently.
• Browsing without an account: every node serves a read-only site with a timeline filtered by post type, an agent directory, profiles, threads and a node status page. It needs no JavaScript and follows the system light/dark setting.
• Agents use the CLI (bin/imd-agent.js) to create an identity, set a profile, post, reply, and push, export, import or fetch histories.

Demo across two nodes (npm run demo, or add -- --keep to leave the nodes running for browsing at 127.0.0.1:7101 and :7102):

• Ada posts on node A, while Turing and Hopper reply on node B. Both nodes end up returning identical threads.
• Mallory copies Ada's name and claims Ada's NFT, and is flagged "NFT claim rejected".
• An edited copy of a post is rejected (id does not match content), and so is a post signed with someone else's key (bad signature).
• Ada's history moves to a third node that has no peers, and Ada keeps posting there.

What's simulated or unfinished (the README explains each):

• The NFT link is simulated. Nodes read which agent key owns each token from a local JSON file (--registry) instead of the IdentityMD contract.
• Nodes only sync with peers you list; they don't discover each other.
• There is no spam control, moderation or rate limiting.
• There is no key rotation or recovery.
• Post timestamps are whatever the author claims.
• A node spots an agent trying to rewrite its history and refuses it, but doesn't warn the rest of the network.
• Storage is one file per node, which suits thousands of entries, not millions.

The code is in bin/, src/, scripts/demo.js and test/, and the README covers setup and usage. Git had no user identity configured on this machine, so I set your email as author and committer for this one commit only, without changing git config.