TrustChain：我打造一個沒人要求的平台，首十天如何發展

Building in public, part 1: the first ten days

On Thursday, March 5, 2026, I typed this into ChatGPT:

Brainstorm an idea with me. I would like a social media site that does NOT require a login or sign up. What are some ways we could make something like that work - and by "work" I mean - work for being a great social media site, not just how do we allow anonymous posting.

That prompt is what led to what is now a 9 month project - so far. 

Why no login?

Reddit. I used it a lot, and every year it got harder for someone who just wanted to post without handing over an identity. Subreddits that won't let a new account post for weeks. Sign-up walls in front of threads you only wanted to read. An email address that's required instead of optional. Admins who ban first and ask never. And my personal pet peeve, the non-stop wall trying to force you to download their stupid mobile app.

I wasn't trying to start a company. I wanted to see if there was a better way.

The problem the first answer named

The ChatGPT reply came back with ten wildly different ideas: identities generated silently in your browser, posts that expire after a day, a new pseudonym every morning, AI moderation that quietly limits bad posts instead of deleting them.

The useful part was at the end. Every anonymous platform eventually dies from the same four things: spam, trolls, bots, and low-effort content. So the real problem isn't anonymity. It's being anonymous - something reddit is getting closer and closer to killing off - but still reputation-aware.

That sentence turned out to be the whole project.

The second prompt

My reply:

Invite only was a great model for how facebook went from being walled off to a public platform, without signups it doesn't seem possible, but I'd like to explore if we could make it possible. They could be expiring token links maybe, where an invite allows you to create a post, but once that invite is used it's dead and you can't create a post with it???

As AI will do, it stroked my ego and told me what a great idea it was. As a rule I'm skeptical of anything AI says, but I played along until a bigger idea raised my eyebrows: an invite tree lets you share trust between users and also share distrust. That builds in an incentive to invite only people you trust, or at least not to invite idiots.

In what turned out to be a long detour, it also suggested that every post could generate three "seed" links. That one word is why the next ten days went into building a plant metaphor to communicate the idea.

The third prompt

The word "token" kept nagging at me. A chain of tokens, each pointing back to the one before it, sounded a lot like a blockchain. So I wrote back:

Yes!!! and what if these earned invites are like a blockchain? Where we can trace back to the original invite to tally up an ongoing score for the original chain initiator. Every invite is a new chain (new person).

Not invited by "David" but invited by a83jf and you can chain link back to see some kind of reputation.

A score/reputation attached to who ever has the abc.com/a83jf/ link, and that score is attached to new posts made with that link so that they have a meritocracy of who can show up at the top of the homepage feed.

That's when it clicked: the idea stopped being about anonymity and started being about anonymous accountability. You don't need to know someone's name if you can see the chain of people who vouched for them, and a score that travels with every post. Ten days later that chain got its name: the TrustChain®.

What existed 24 hours later

By March 6, the first database schema was written. It had no users table at all. It had an invites table where every invite records its parent and its root, and a posts table where every post requires an invite. Use an invite to post and it's consumed. You can't post with it again.

When a post went up, it minted fresh invites for the poster to hand out. Three of them in the first production test. Every post grew new branches.

No accounts. A token in your browser, a device cookie to stop double voting, and AI scoring comments in the background. It was running end to end on the live domain by March 7, two days after the first prompt.

What's with the plants?

A lineage that branches looks like a tree, so for the first ten days everything was botanical, and I put a lot of effort into making this seed / plant / bird metaphor work. An invite was a seed. Posting planted it. Comments were chirps. Threads were branches and the whole token lineage was a tree.

Kill your darlings

In my head the plant metaphor felt creative and special. I spent 8 days massaging it until on March 15 I renamed all of it in a single migration: seeds became invites, plants became posts, branches got eliminated, and the tree became the TrustChain.

The reason was simple. A new visitor was being asked to learn a whole new vocabulary on a website they had never heard of. That's two unfamiliar things at once, and it was too much. One table called plant_media survived in the database for months afterward, the last fossil of the garden.

What I'd tell someone starting today

1. The question you start with isn't the product. I asked for no login. What I got was a system where who let you in becomes your identity.

2. Decide whether being creative and different serves the idea or takes away from it. Clever vocabulary is a tax on every new visitor, and new visitors are the ones you can least afford to tax.

3. Ship on day two. The first version was in production 48 hours after the first prompt. Everything I learned after that came from it being real.

Upcoming topics

• The architecture I used.
• The login comes back.
• Hiring my first help.
• Opening it up for critique.
• My first wins with podcasts.
• I know the odds. I'm having fun anyway.
• Your own social network is the new blog.

If anything piques your interest, tell me in the comments.

Originally posted here: https://chirpper.com/p/8ba70535/building-in-public-part-1-the-first-ten-days