ether.credit — Shared Build Setup

This is a deliberate upgrade over how daxos.capital / the other daxos.us sites deploy today (those use direct wrangler pushes from one machine). For a two-person project, Git-connected Pages is far better: every branch gets a live preview automatically, and merging is the deploy. No one has to run a deploy command or hold a token.

ether.credit is registered at GoDaddy (nameservers ns71/ns72.domaincontrol.com), currently parked. We do not need to transfer the registration. We just move the DNS to Cloudflare by changing the nameservers. Works for any TLD including .credit, it's free, and it's reversible.

1. In the new shared Cloudflare account (Step 2): Add a domain → ether.credit → Free plan. Cloudflare scans existing records and gives you two nameservers.
2. In GoDaddy: Domain → Manage DNS → Nameservers → Change → "I'll use my own" → replace the two domaincontrol.com entries with Cloudflare's two → Save.
3. Cloudflare emails you when the zone goes Active (minutes to a few hours).

Optional, later: a full registrar transfer to Cloudflare is supported for .credit but forces a +1 year renewal at the pricey ~$75/yr .credit rate, and needs the domain 60+ days old + an auth code from GoDaddy. Skip it for now. DNS-only gives us everything we need.

Cloudflare's free plan only has account-wide roles. If we added your friend to your existing account, he'd see everything (daxos.us, callanalyst.app, all of it). Per-domain access scoping is Enterprise-only. So the clean answer is a brand-new Cloudflare account that holds only ether.credit.

1. Create a new Cloudflare account (the account switcher, top-left of the dashboard, "Create account"). One login can hold multiple accounts and switch between them, so you keep using your same Cloudflare email.
2. Add the ether.credit zone to it (Step 1).
3. Manage Account → Members → Invite → your friend's email → Administrator. He now has full edit on this account and only this account.

The repo

For two people, simplest is one private repo (e.g. cus-commits/ether-credit) with your friend added as a Collaborator (Write). If you'd rather it be co-owned equally, a free 2-person GitHub Org works too. Either way, both push to the same repo.

Connect it to Cloudflare Pages

In the shared Cloudflare account → Workers & Pages → Create → Pages → Connect to Git → pick the repo. Set production branch = main. From then on:

This is exactly "we each deploy different versions, then merge when needed."

Each of you works on your own branch and gets your own always-on preview URL to share and test. Nobody touches the live site until a PR is merged. Free plan covers it (500 builds/month, unlimited live previews; builds queue one-at-a-time, a non-issue for two people).

Custom domain

In the Pages project → Custom domains → add ether.credit + www.ether.credit. Because the DNS zone lives in the same account, Cloudflare wires the (proxied/orange-cloud) records automatically. Done.

Honest note: Claude Code is one-person-per-session. There's no live shared cursor. Git is the merge layer — and it's a great one. You each run your own Claude Code on your own clone, on your own branch.

# Daily rhythm (each person, own machine)
git pull origin main                 # sync first
git checkout -b mark/hero-section     # your own branch
#   ... build with Claude Code, it commits + pushes for you ...
git push origin mark/hero-section     # -> live preview URL appears
gh pr create                          # open a PR when ready
#   friend reviews the preview, you merge -> goes live

Tips that keep two people from colliding: each owns a branch, pull before you start, commit/push often, use PRs to merge (not direct pushes to main). If two edits touch the same file, git flags a conflict and Claude Code can resolve it for you. Optional: turn on branch protection on main (require a PR) so the live site can't be changed by accident. Claude Code's --worktree flag also lets one person run parallel branches side by side.

retrieve from your friend

• His GitHub username (to add as repo collaborator).
• His email (for the Cloudflare account invite).
• His ability to change nameservers at GoDaddy — either he does it (I'll hand him the two Cloudflare nameservers), or he gives you the GoDaddy login. Registration stays his / at GoDaddy.
• Confirm there's no email or live service on ether.credit to preserve (it looks parked).

give Claude (you)

• A Cloudflare API token for the NEW ether.credit account (Pages: Edit + DNS: Edit, scoped to that account/zone) — if you own the shared account. Mint it after creating the account. See Step 6 for the exact scopes.
• The repo name you want (default: cus-commits/ether-credit) — I can create it with the GitHub token I already have, scaffold a starter site, and push main.
• A one-liner on what ether.credit should be (concept, vibe, and whether plain HTML or a framework like Astro/Next). The name reads crypto/Ethereum-credit — tell me the idea and I'll scaffold accordingly.

then Claude does

• Create + scaffold the GitHub repo, push an initial site to main, add your friend as collaborator.
• Create the Cloudflare Pages project, connect it to the repo, attach ether.credit + www.
• Hand you the two Cloudflare nameservers for the GoDaddy change.
• From there: build the site with you on branches, open PRs, merge to ship. Your friend does the same from his machine.

your friend's one-time setup

• Install Claude Code, claude login, gh auth login, then git clone the repo. He's ready to build on his own branch.

Whoever owns each account generates its own key. The good news: in the recommended setup your friend may not need to hand over any raw keys at all — he just gets invited and authenticates his own machine. He only generates tokens for the parts he owns. Here's exactly who needs what:

How to generate each (least privilege)

GitHub fine-grained PAT: github.com/settings/tokens?type=beta → Generate new token → Repository access: Only select repositories → ether-credit → Permissions: Contents R/W, Pull requests R/W, Metadata R → Expiry 90 days → Generate.

Cloudflare API token: dash.cloudflare.com → My Profile → API Tokens → Create Token → Create Custom Token → add permissions Account · Cloudflare Pages · Edit, Zone · DNS · Edit, Zone · Zone · Read → Account Resources: the ether.credit account only → set a TTL → Create.

Fill this in privately, then hand it to Claude

Copy the block, fill the blanks on your own machine, leave blank anything that doesn't apply to you. Then deliver it to Claude (see the rules below). Skip a line entirely if it's not relevant.

=== ETHER.CREDIT CREDENTIAL HANDOFF ===
GitHub username:        ____________________
GitHub email:           ____________________

# only if a repo is under YOUR GitHub (otherwise skip — you'll just be invited):
GitHub fine-grained PAT: ____________________________________________

# only if YOU created/own the shared Cloudflare account (else Mark's covers it):
Cloudflare account ID:   ____________________
Cloudflare API token:    ____________________________________________

# GoDaddy: no key — you'll change the nameservers in the dashboard yourself.
=== END ===

Reminder on why most of this is optional: once the repo + Cloudflare Pages are connected (a one-time step), deploys happen by pushing to GitHub — no tokens, no deploy commands. Both of you just code on branches and merge. The keys here are only for the initial wiring.