Picture this

Who it is for

Five friends build a mini app together. Credit Split registers their builder code, reads the attributed activity, and shows a public split by contribution that they agreed up front, so nobody argues later about whose app it is.

Two ways to own it

What you get

Base$99

$25 deposit to reserve

Code registration guide, attribution reader, contributor split page, share card.

You choose: team size
You choose: accent color

Customfrom $700

Built around you

Reshape it entirely: new features, your flows, your brand end to end, integrations you need. We scope it with you.

Everything in Base
Custom features and design
Priority build

Why it is new

What exists today, and what this does differently

What is new

Builder codes attribute to one code. A public, agreed contributor split of that attribution was not found.

Closest things out there

base.dev builder codes dashboard; Drips and Splits for revenue sharing.

Checked with web searches in October 2026. A search is not proof that nothing similar exists, and the market moves fast, so we recheck before every build.

What it unlocks

The human in it

Turns a group project into shared, visible credit.

The Regatta Board

Races it can enter

grant · Base · rolling

Base Builder Grants

rolling, retroactive

Official page ↗

Ecosystem program for shipped apps; check current terms.

Their rule on existing code: Existing shipped projects OK (retroactive)

What you own

The whole app, not a starter kit.

The complete Credit Split app: a crew shares one Base builder code through a team Safe, signs a versioned split of the credit before launch, and watches a weekly reader repaint the bow, with a paywall built in.

Base price · $99

The user app, complete

Every buyer gets the same finished app. Basic branding and copy changes come through a quick form.

Three step onboardingBow

Shown once: one code many hands, agree it tonight, credit not a promise.

Crew status and next actionBow

Code in Safe, signed, published, suffix clean, with one clear next step and the crew at a glance.

Monday digestBow

A weekly message that repaints the bow and flags missing suffixes. Gated behind Studio.

Split editorSplit

Crew size, fixed or work based shares, change threshold and cliff, painted live on the bow.

Signatures and publishSplit

Every member signs v1, then it is attested on Base with a team Safe as code owner.

Versioned changesSplit

Propose a new version, collect threshold signatures, keep the old one readable. Gated behind Studio.

Weekly credit readCredit

Tagged orders per week, credit by name, and a run-the-read button. Weekly reads gated behind Studio.

Leaver rulesCredit

A member leaving keeps past credit and has their share frozen, based on the cliff. Gated behind Studio.

Suffix checkCheck

Samples recent transactions, shows untagged ones and the exact call site to fix.

Deploy alertsCheck

Alerts the crew after every deploy that ships without the builder code suffix. Gated behind Studio.

Onchain receiptsReceipts

Builder code, Safe, every split version and plan payments, with what is and is not onchain.

Plans, members and share cardCrew

Pricing from the owner paywall with USDC checkout, member list, invites and the launch day post.

Open the full app demo

Add-on

Owner console

Your admin side: revenue, paywall editor, users, rules and the agent log.

Revenue and paywall editorRevenue

Revenue, tier names and prices, free crew size, gates, incoming USDC payments and payment methods.

Teams and host boardTeams

Every crew's health with one tap help, plus a hackathon board for judges.

Rules, agent log and roadmapRules

Suffix sample, reconcile tolerance, digest day and defaults; the reader's log of failures; priced roadmap requests.

Top-up

Growth and referrals

Referral and growth mechanics, switched on when you are ready to grow.

Crew codesCrew

A crew code gives another team a free Studio month when they publish.

Hackathon onboarding loopGrowth

Onboard a batch of event teams, cohorts and growth loops.

The money path, built in

How it earns for you

Crews agree and publish their first split for free. Teams pay a monthly Studio plan for weekly reads and change tools, and hackathon hosts pay per event, all in USDC.

CrewFreeOne code, up to 5 members, split v1, a monthly read, the bow and receipts

Studio$9 a month per teamWeekly reads and digest, unlimited versions, cliff and leaver rules, suffix alerts

Hackathon host$149 per eventEvery team gets a code, a Safe and a signed split on day one, plus a public board for judges

Owner sponsors attestation gas, typically about one cent per version on Base.

Prices are yours to set. Illustrative, not a promise of income.

Growth loops, built in

How it spreads

The bow post: every member shares launch day's bow with their name on it
Hackathon day one: hosts onboard every team at once
Crew codes: a free Studio month for both crews
Monday digest: a weekly reason to open the app

Roadmap · build the next phase with us

Where it goes next

v1 included

The full crew app

Team Safe and builder code guide
Split editor, signatures and versions
Weekly reader with suffix checks
Bow, digest, receipts and share card

Included

Payout split and host boards

Opt in Splits style payout that follows the current version
Hackathon host board for judges
Farcaster mini app digest
Passkey recovery member

Add-on from $450

Contributor passport

Personal page of every signed share
Verify API for employers and grant reviewers
Multi code studio accounts
Open contributor split schema

Add-on from $900

For investors and grant reviewers

The pitch, ready

Share one Base builder code across a team and publish who earned what share of the app's onchain credit, agreed before launch.

Problem: A Base builder code attributes onchain activity to one code with one owner. Whoever registers it looks like the builder, and months later nobody remembers who agreed to what.

Solution: Credit Split puts the code in a team Safe, has every member sign a versioned split, and repaints a public bow each week from tagged transactions.

Why now: Builder codes and data suffix attribution are new on Base, and small crews are shipping mini apps faster than they can agree on credit.

Market: Small teams and hackathon crews shipping on Base, plus hosts and studios that run many teams.

The ask: Launch with two hackathon hosts and 50 crews, then apply to Base Builder Grants with the public bow board.

Funding is never guaranteed. Check each program's rules.

For hackathons and demo days

Your 2 minute demo

Bow: meet the Kerb crew on launch eve and the one builder code
Split: paint the shares, everyone signs, publish v1 on Base
Check: find the stall map screen missing the suffix and send Chidi the fix
Credit: run a weekly read, then see Bisi ask for more and propose v2
Receipts: what is onchain and what never is
Owner Revenue: edit the Studio price and watch the Plans sheet change
Owner Growth: onboard five hackathon teams and see the host board fill
Owner Roadmap: request the payout split build

Many hackathons require code written at the event. See the Regatta Boardfor each race's rule.

Make it entirely yours

Custom work covers your own branding, extra chains, a different split model, payout contracts or integrations with your event platform, scoped on a call from $700.

Custom from $700

BLUEPRINT

Why it matters and how it really works

The need

Small teams ship apps on Base together, but a Base builder code attributes onchain activity to one code with one owner. Whoever registers it looks like the builder, and months later nobody remembers who agreed to what. Friends fall out over credit far more often than over code.

What exists and what is new

The pieces exist. base.dev lets builders register a builder code and see the activity attributed to it, and revenue sharing tools like Splits and Drips already route money to many addresses by fixed percentages. Research did not find a public, signed contributor split of builder code attribution itself. What is new is narrow: a shared team owner for the code, a split everyone signs before launch, versioned changes with a signature threshold, and a weekly public read of attributed activity painted onto that split. It is a coordination layer on existing tools, not a new protocol.

The data it runs on

Transactions on Base that carry the team's builder code in their data suffix, read from blocks and cross checked against the base.dev dashboard; the team Safe address; the split attestation and its versions; member signatures. Chats, reasons and task notes stay with the team and are never published.

1.The mission

Let every small crew that builds something together keep a public, agreed record of whose work it was, from the first night.

2.Why people can't resist it

The bow Every name painted as wide as its share. It is the picture people screenshot when the app launches.

Agree once, kindly The split is signed on launch eve, while everyone is still friends, and changes need a real threshold.

Monday paint A weekly digest repaints the bow with fresh numbers and warns when new screens forget the builder code suffix.

3.How it works for real

Team owner: The builder code is registered on base.dev to a Safe owned by the team, with a threshold such as 3 of 5, so no single member can repoint it.

Split attestation: The agreed shares, cliff and change threshold are written as an EAS attestation on Base, signed by every member with EIP-712 signatures. New versions reference the previous one.

Attribution reader: An indexer reads Base blocks for transactions whose data suffix carries the team's code (ERC-8021 style), counts one per transaction hash, and reconciles weekly against the base.dev dashboard.

Optional payout split: If the team ever receives rewards or revenue at the Safe, a Splits style contract can distribute by the current version. Nothing is promised and the app works without it.

Suffix check: After each deploy, the reader samples recent transactions and alerts the team if they arrive without the builder code suffix.

Digest and share card: A weekly email or Farcaster mini app notification with the repainted bow, built by a small model such as Claude Haiku from the counts only.

4.Cost per use and pricing

Per team: one Safe deployment and one attestation per version on Base, typically well under one US cent each at recent Base gas levels (check current fees). The weekly read uses an RPC or indexer plan; at hobby scale this fits a free or roughly 50 dollar a month tier. A digest written by a small model costs a fraction of a cent per team per week. Example: 200 teams cost roughly 60 to 80 dollars a month to run.

Crew Free

One code, up to 5 members, one split version, monthly read.

Studio $9 a month per team

Weekly reads, unlimited versions, cliff and leaver rules, suffix alerts, share cards.

Hackathon host $149 per event

Every team at an event gets a code and signed split on day one, with a public board for judges.

5.Growth loop

Each launch posts a bow image with every member's name, and each member shares it. Hackathon hosts onboard dozens of teams at once, and teams that split once bring the habit to their next project.

6.Risks and guardrails

Rewards are not guaranteed: Builder code attribution is credit, not income. Any rewards program can change or end, and the app must never imply payouts.

Bad suffix, no credit: If a screen sends transactions without the suffix, activity is lost. The reader checks after deploys, but missed weeks cannot be recovered.

Disputes about fairness: The app records agreements; it does not judge contribution. Teams can still disagree, and the threshold may block changes.

Key loss: If too many members lose keys, the Safe cannot sign. Encourage passkeys and a recovery member.

Legal meaning: A public split may look like an ownership or employment agreement in some places. Present it as a credit record and suggest local advice if money flows.

7.Build order

Create a team Safe and register its builder code
Split editor with shares, cliff and threshold
Collect EIP-712 signatures and publish the EAS attestation
Weekly reader that counts suffix tagged transactions
Bow image and share card
Versioned changes with threshold signatures

8.Where this is going

Now
Small crews sign a split for one Base builder code and see weekly credit on the bow.
Next
Hackathons give every team a code and a signed split on day one.
Later
Contributor records travel with people, so a resume can point to signed shares in real shipped apps.
The big picture
Credit for group work becomes something you agree up front and can prove later, everywhere people build together.

Costs and tools are estimates at the time of writing. General information only, not legal or financial advice.

OWNER PLAYBOOK

Own it, then chart your voyage

Nine routes from one vessel. Tap a port to open its chart.

Why own Credit Split

Credit Split: Share one Base builder code across a team and publish who earned what share of the app's onchain credit. Using someone else's version means their rules, their brand and their revenue. Owning Credit Split means it is deployed under your wallet, carries your name, and every customer, partner and result builds your track record instead of theirs.

What’s stopping you?

“I am not technical.”

Credit Split arrives deployed with a guide. Running it is settings and sharing links, not code. If you get stuck, we help you ship it.

“What if nobody uses it?”

Start with ten people you already know. The first move below takes under an hour and tells you fast whether people care.

“I do not have time.”

Each step is sized in minutes. Most owners spend an hour a week, and the app does the repetitive part.

“Will it make me money?”

Nothing is guaranteed. The playbook gives you a clear path and honest numbers, and you decide how far to take it.

The million-dollar ladder

Charge the people who get the most value from Credit Split: a monthly plan for groups or teams, plus setup fees for anyone who wants it done for them.

$100

$1,450

$11,700

$78,000

First harbour

5 customers

$20 a month

Steady trade

50 customers

$29 a month

Known name

300 customers