Creator Ledger

Creator Ledger turns published content into verifiable proof of work for creators.

Comment

About the Project

Creator Ledger started from a very personal frustration.

Over the last few years, I kept watching creators struggle to prove their work. Not create it - prove it. Brands would ask for portfolios, screenshots, analytics dashboards, and campaign reports, and everyone involved would quietly pretend those were reliable signals. They aren’t.

Screenshots can be edited.
Analytics can be inflated or bought.
Links disappear.
Platforms change rules or ban accounts.

And then AI arrived.

Suddenly, it became trivial to generate convincing content, fake engagement, and even fabricate entire creator histories. That’s when the problem stopped being theoretical. If everything can be faked, what does proof actually mean anymore?

That question is what inspired Creator Ledger.

I didn’t want to build another portfolio tool or social profile. I wanted to build infrastructure for trust - a way for creators to register the work they’ve already published and turn it into something immutable, verifiable, and owned by them.

What I Learned

The biggest lesson was that features don’t create trust - form does.

Many existing solutions solve pieces of the problem: provenance, certificates, badges, profiles. But none of them create a single, evolving object that represents a creator’s real work history over time.

I learned that:

  • Trust requires both human judgment and cryptographic guarantees
  • Pure automation fails quality checks
  • Pure Web2 solutions fail ownership and permanence
  • UX matters more than ideology - if it feels heavy, creators won’t use it

Most importantly, I learned how hard it is to build something that feels obvious only after it exists.

How the Project Was Built

Creator Ledger is built around a simple flow:

  1. A creator submits links to content they have already published
  2. A human verification layer checks authenticity and relevance
  3. Verified entries are anchored on-chain
  4. A Creator Passport (a dynamic NFT) updates as proof accumulates
  5. Creators can export this verified history for brands, partners, or reporting

The key technical decision was to separate:

  • On-chain truth (hashes, timestamps, ownership)
  • Off-chain usability (verification UI, analytics, exports)

This keeps costs low while preserving verifiability.

The project is deployed as a Farcaster Mini App, which allowed fast iteration, real user feedback, and direct integration with an existing creator-native environment.

Challenges Faced

The hardest part was vibe-coding this on my own without overengineering.

Some of the challenges included:

  • Designing a system that feels non-Web3 to non-Web3 creators
  • Balancing privacy with public verifiability
  • Avoiding token mechanics while still using blockchain meaningfully
  • Making dynamic NFTs feel useful, not gimmicky
  • Deciding what not to put on-chain

There were many moments where the system worked technically but didn’t feel right. Getting from “working” to “trustworthy” was the real challenge.

Built With

Share this project:

Updates