Why Bison Relay
Spam resistance with economics
Micropayments per message and per byte make abuse costly without captchas or moderators.
Privacy by
default
Every message is end-to-end encrypted. Relays see priced blobs, not users.
Metadata minimization
No server accounts. No social graph to harvest. Who talks to whom is obscured.
Built-in publishing
Beyond DMs: posts, subscriptions, and Pages support paid feeds and storefronts.
Owner-operated
You hold the keys. You choose the relay. You set the price and retention policy on your side.
How it works
CLI first
Bison Relay is designed to be driven from the command line. That means it is scriptable, automatable, and easy to wrap with an agent.
# Initialize
br init
# Fund wallet, then open a Lightning channel
br wallet address
# Send DCR to that address from your Decred wallet
br ln open <node> --amount 5_000_000
# Connect to a relay and exchange invites
br relay add <relay_url>
br invite send <contact_pubkey>
# Message and publish
br msg send <contact_pubkey> "gm"
br page publish ./site \
--price-per-kb 10 \
--subscribe 1000-per-month
Conceptual CLI flow
These commands illustrate the shape of the workflow. Exact flags may differ in your build.
Why CLI first?
Who is this for?
Bison Relay is designed to be driven from the command line. That means it is scriptable, automatable, and easy to wrap with an agent.
Builders who want primitives that compose: message, price, publish, purge.
Creators who want direct support without platforms.
Teams and DAOs that need secure operations channels.
Agents that need a reliable, programmable transport with cost signals.
