PHASE 0 · MAY 2026

We built Pulse because every protocol with money in it ends up paying the same farms, and the alternatives ask users for their iris.

Continuous human verification for Web3. No KYC. No biometrics. One soulbound badge any contract reads in a line of code.

CONTRACTS

VERIFIED

BACKEND

LIVE

TOKEN #1

MINTED · MAY 20

INTEGRATION

< 1 HOUR

THE PROBLEM

Every protocol with money in it pays the same farms. The alternatives ask users for their iris.

Airdrops, governance, allocations, gated mints, retroactive rewards. Anywhere a protocol pays out, sybil farms show up. The 2024 cycle made it worse, not better. Clean wallet histories are commodity priced. A thousand fake users costs less than a single real customer acquisition.

The mainstream answer is to collect identity. Iris scans, KYC, biometric capture. These work, and most users reasonably refuse them. The fallback answer is CAPTCHAs and social graphs, both of which farms cracked years ago. There's room for a third thing.

WHAT IT IS

Seven days. One signed message a day. Then a badge that never moves.

A wallet checks in once a day for seven days. Each check-in is a signed message. No gas, no transaction, no personal data leaves the wallet. After the seventh day, the protocol evaluates the check-in history against a set of internal rules. No identity is ever collected. No PII enters the system at any point.

Wallets that qualify get a soulbound badge. One token, permanent, non-transferable. After it mints, the user is done. They can transact, govern, and earn on any dApp that reads Pulse, without ever checking in again. Any contract can read it. Any backend can query it.

RECEIPTS

Not slideware. The first one of these will probably outlast Pulse itself.

TOKEN #1 · SOULBOUND

PULSE · BRONZE

7-day streak

HOLDER0x1d5d…61a21

MINTEDMay 20 · 21:27 GMT

BLOCK41772066

CHAINBase Sepolia

LIVE API · HIT IT NOW

GET /reputation/{wallet}

pulse-api · curl

$ curl pulse-protocol.../reputation/0x1d5d…61a21

{
  "wallet":         "0x1d5d4f8a…61a21",
  "tier":           "bronze",
  "streak":         7,
  "lastCheckInAt":  "2026-05-20T21:27Z"
}

AUTHNONE

RATE LIMITNONE

RESPONSEREAL JSON

THE BADGES

Three tiers. Phase 0 ships Bronze. The rest stay quiet until they're ready.

Bronze

7-DAY STREAK

Entry tier. Proves consistent, signed wallet activity across a full week. The Phase 0 baseline.

Silver

EXTENDED CRITERIA

Layered signals beyond the streak. Sustained activity over longer windows.

PHASE 1

Gold

HIGHEST ASSURANCE

The hardest signal to fake. Reserved for wallets that compound participation across protocols and time.

PHASE 2

FROM US

We started on this problem in early 2025 under a different name.

The conviction behind it isn't new. The contracts are deployed and verified. The backend is live. Token #1 exists.

The hard part is finding the protocols that care about this problem before they care about a launch announcement. We're not announcing. We're looking for partners who'd rather see receipts than slides.

BEYOND PHASE 0

Phase 0 is the surface. The rest ships when adversaries adapt.

Underneath are layers we're not publishing. Additional gates. Correlation signals. Higher tiers earned through sustained activity. Each layer raises the cost of impersonating a human.

We're not naming the techniques. The longer they stay quiet, the longer they work. Partners who want to know what's coming can ask in private.

WHO IT'S FOR

Teams running incentive programs where sybils show up in the math.

Airdrop platforms. Allocation tooling. Governance frontends.

Whichever shape your protocol takes, if you've watched real users get diluted by farms, this is for you.

FOR PARTNERS

Two ways to read Pulse. One returns a boolean. One returns the full picture.

The first is a single read against the Pulse Badge contract using ERC-721's balanceOf. One returns means verified. Zero means not. No SDK, no auth, no rate limit.

The second is the reputation endpoint, which returns tier, streak, and last check-in time. The card above shows real JSON for Token #1's holder.

VISION

Sybil resistance stops being every project's problem. It sits in the stack next to ENS and signatures, where teams stop thinking about it because they assume it's there.

Partner inquiries →