A single static page in front of MARA Slipstream: paste or drop signed PSBTs and raw transactions, see them decoded, finalized and priced locally, then submit them one at a time to Slipstream, which mines them without ever putting them in the public mempool. It is useful to a narrow set of users — mainly Liana, Miniscript and some multisig wallets — for whom keeping a spend out of the public mempool changes the outcome. It is not the recommended route for a wallet critically at risk: the Coldcard RNG write-up says what to do in that case, and the page says so at the top.
There is no backend. Parsing, finalization, fee maths and the submission
itself all happen in the browser, and the submission goes straight from
the tab to slipstream.mara.com. A deployment is nginx serving a wasm
bundle, so nothing pasted into the page ever reaches this project's host.
The page does load one third-party script, for analytics.
See Honest limitations before relying on this for
anything.
Nine catalogues live in crates/broadcast-frontend/src/i18n/, one file per
language: English, German, Spanish, French, Italian, Portuguese (Brazil),
Russian, Japanese and Simplified Chinese. Strings is a struct, so adding a
string will not compile until every language has one; that is the point.
No font ships for Japanese or Chinese. IBM Plex has no CJK coverage, and the
alternative to a system face is tens of megabytes, so the stack falls through
to var(--ws-cjk), which style.css picks from <html lang>. It is
language-keyed because Chinese and Japanese want different shapes for the
same Han characters.
All nine are offered, in a picker at the right of the sticky bar at the top
of the page. Most are LLM drafts marked unreviewed in Lang::reviewed, and
while a language is unreviewed the page shows a notice saying so, points at
English as authoritative, and offers a button back to it. Flipping the flag
removes that notice, so flip it in the same commit that records who reviewed
the language.
Terms of art stay English in every language: PSBT, mempool,
Broadcast, Fee rate, Export, Drafts and Approvals and the rest. The
glossary is at the top of i18n/mod.rs and a test enforces it. Bitcoiners
run English software, and a reader hunting for the Broadcast button is not
helped by being told about "diffusion".
Plausible, a privacy-preserving analytics service, in the <head> of
index.html. The script URL carries our site key: change or remove it on
another deployment.
assets/og.png is the 1200×630 Open Graph and Twitter card;
assets/favicon.svg is the mark, with favicon-32.png and
apple-touch-icon.png rendered from it. Regenerate all three from
tools/social/og-template.html and the SVG:
cd tools/social && npm install && node render.mjs
og:url, og:image and twitter:image in index.html are absolute and
point at our host: change them on another deployment.
just run serves the page on 127.0.0.1:8080 over plain HTTP with trunk serve, and opens a browser; just serve is the same without opening one.
There is nothing else to start, and no credential to fill in: the page
talks to MARA directly, so the fee card and sending behave in dev
exactly as they do in production. Sending against the real
Slipstream is a real submission.
SLIPSTREAM_BASE_URL at build time points the page at another host; with
it unset the page uses https://slipstream.mara.com.
Other targets:
just clippy:cargo clippy, pluscargo clippy --target wasm32-unknown-unknownincrates/broadcast-frontend.just fmt:cargo fmt, run at the workspace root and again incrates/broadcast-frontend.just test:cargo test, pluswasm-pack test --headless --firefoxincrates/broadcast-frontend.
Three scripts under deploy/, each runnable locally with no argument, or
against a remote host with user@host (rsyncs the project to
/opt/outofband/src and re-execs itself there over ssh):
just local/just deploy <user@host>runsdeploy/install.sh. Full bootstrap of a fresh Debian/Ubuntu host: installs apt prerequisites (build-essential,clang,pkg-config,curl,rsync,nginx,certbot,python3-certbot-nginx), rustup + thewasm32-unknown-unknowntarget + a pinnedtrunkif missing or out of date, creates/opt/outofbandand/var/www/outofband, builds the frontend withtrunk build --release, installs itsdist/to/var/www/outofband, installs the nginx site and its snippets, then runs a health check againsthttp://127.0.0.1/through nginx.just update/just update-remote <host>runsdeploy/update.sh. Rebuilds the bundle, reinstalls it plus the nginx snippets, reloads nginx. Never touches certificates. Application routes, caching and headers live in/etc/nginx/snippets/outofband-app.conf, which updates without replacing Certbot's TLS server block. A deployment created before this split needs a one-time migration: preserve its TLS andserver_namedirectives and replace its old application locations withinclude /etc/nginx/snippets/outofband-app.conf;.just clean-local/just clean-remote <host>runsdeploy/clean.sh. Removes the nginx site, its snippets, and the install directories, and clears out what an earlier backend deployment left behind, prompting with an explicityesconfirmation before removing theoutofbandsystem user. Leaves apt packages, the Rust toolchain, TLS certificates and the renewal timer in place.
Both the domain and the certbot contact default to
outofband.wizardsardine.com and contact@wizardsardine.com, and the TLS
flags are forwarded through the remote re-exec, so a bare deploy issues the
certificate:
./deploy/install.sh user@host
Pass --domain <host> to deploy under a different name, `--email
sudo systemctl reload nginx
sudo certbot --nginx -d outofband.wizardsardine.com --redirect --agree-tos -m <email> -n
Set server_name first, for the same reason install.sh sets it before
invoking certbot itself: certbot picks the server block to modify by
matching server_name, so running it against the placeholder won't target
the right site.
The nginx site ships listening on plain port 80 so the first install works before DNS or a certificate exist; certbot rewrites it for 443 with the Let's Encrypt certificate and installs the renewal timer.
nginx access and error logs: /var/log/nginx/outofband-access.log and
/var/log/nginx/outofband-error.log. They record requests for the page
and its assets and nothing else: a submission goes from the browser to
MARA without passing through this host, so no transaction hex exists in
any log here to leak.
nginx is the only thing listening, and it only serves static files. With UFW, allow 22, 80 and 443, and nothing else:
sudo ufw allow 22
sudo ufw allow 80
sudo ufw allow 443
- Rejections aren't classified. Slipstream answers with prose, so "fee too low" and "consensus failure" both reach the user as MARA's own sentence.
- CPFP is unsupported. A low-fee parent submitted alone is judged and rejected on its own rate. Slipstream has a package endpoint for this; the page doesn't use it, so a parent that depends on its child's fee has to go through MARA directly.
- The browser talks to MARA directly. MARA sees the user's IP address,
because the connection is the user's own and nothing here proxies it;
Tor or a VPN is the only answer to that. It also means MARA can break
this site with no deploy on our side, by tightening CORS on
/api/transactionsor moving the endpoint.
- Coldcard RNG vulnerability, and why you might need this tool
- MARA Slipstream: the service this page submits to; its terms and no-support policy are stated on that site.