Connect bitcoinflagship.com
This site runs on Vercel. To serve it from your own domain, point the DNS records below at Vercel, add the domain in the dashboard, and confirm every check on this page turns green.
Live connection check
DNS records to add
| Type | Name | Value | Notes |
|---|---|---|---|
| A | @ (root) | 76.76.21.21 | Apex record — Vercel. Propagates the domain at the root. |
| AAAA | @ (root) | 2606:4700::6810:84e5 | IPv6 for the apex record (optional but recommended). |
| CNAME | www | cname.vercel-dns.com | Serves www and enables automatic HTTPS certs. |
| _lnaddress | TXT | depends on your Lightning provider | Makes tips@bitcoinflagship.com routable over Lightning. |
Not on Vercel? The Netlify build reads the same env vars — swap the CNAME value for your.netlify.app project URL, and add your domain under Netlify → Domain management.
Lightning address domain
The site is configured to receive sats at tips@bitcoinflagship.com. Point the _lnaddress TXT record at your Lightning service to make tips routable.
Three steps to go live
Point the DNS records
In your DNS provider (Namecheap, Cloudflare, GoDaddy, etc.), add the records for bitcoinflagship.com using the table below. Apex and www must both resolve.
Add the domain in Vercel
In the Vercel project → Settings → Domains, add bitcoinflagship.com and www.bitcoinflagship.com, then set a redirect (e.g. www → apex) so one canonical URL is served.
Verify with the live check
Wait a few minutes for DNS propagation, then re-run the Live connection check on this page from https://bitcoinflagship.com. All checks should light up green.
Environment variables
Set these in Vercel project settings (or a .env.local for local dev) and redeploy after changing them:
NEXT_PUBLIC_SITE_URL=https://bitcoinflagship.com NEXT_PUBLIC_LIGHTNING_ADDRESS=tips@bitcoinflagship.com LIGHTNING_PROVIDER=mock # or: lnd / btcpayserver