BUMP

A sovereign node.
Not just a wallet.

BUMP is the personal operating point for permissionless value: a self-contained, Bitcoin-first experience where the phone holds approval, people choose the rail, and every payment can become a doorway into a wider sovereign ecosystem.

Personal authorityBitcoin-first railsPermissionless entry
Current BUMP production app: satoshi balance, Lightning capacity, central BUMP gesture, SATS, BLE and QR rails, and bottom navigation
Current BUMP production application view
The real BUMP interaction model

One gesture. Three ways to begin.

The public page mirrors the choices visible in the current application without pretending to execute a payment: sats for settlement, nearby discovery for human handoff, and QR for a clear request.

SATS · value
Bitcoin-first settlement stays person-held.

The app keeps the decision close to the person, not a custodian or marketplace.

Explore the commerce rail →
The problem BUMP begins with

Value starts between people.

Existing payment systems begin by making two people into account records. BUMP begins with the moment itself: a known person, a nearby device, a visible request, and an approval that remains with the person holding the phone.

01

Meet.

Tap, nearby discovery, scan, or choose a known contact—the relationship comes before the route.

02

Agree.

Make the amount, destination and rail visible before the device asks for an approval.

03

Settle.

Use Bitcoin, Lightning or USDT while the person keeps the approval boundary and the payment history close.

Verified BUMP interaction interface showing nearby NFC, Bluetooth and QR options for a BUMP payment handoff
BUMP starts with a real-world handoff, not an account form.
Beyond the wallet

The wallet is the boundary. The node is the doorway.

BUMP keeps the human approval boundary on the phone, then connects that authority to practical payment rails, trusted people and the services a sovereign ecosystem needs—without making the user surrender control to a platform.

01

Hold authority.

Bitcoin, Lightning and USDT balances, trusted people and the core send, receive and scan actions remain in the device the person controls.

02

Choose a rail.

Create a Bitcoin address, Lightning invoice or USDT request and share it directly or as a QR—without turning a human payment into a bank application.

03

Enter the ecosystem.

Prepare or inspect requests on a larger screen while final approval stays on the phone, ready to connect to wider sovereign services by choice.

What a conventional wallet leaves behind

A balance is not a sovereign life.

BUMP’s node foundation is built to preserve more than spendability: a portable local identity, clear consent for connected applications, and a record of trusted relationships and receipts that is not owned by a marketplace.

NODE IDENTITY

One person. One local authority.

A protected device-held node identity anchors the wallet relationship so a user is not reduced to an email login or a custodial account.

CONSENT

Connections ask. You decide.

Connected services can be granted only the narrow capability required—such as preparing a payment or reading a balance—and can be revoked without handing over recovery material.

CONTINUITY

Recovery restores a life, not just keys.

The design carries forward the protected node state, trusted relationships and history through recovery, with a new device identity taking accountable control.

One personal node · three working modes

From human approval to sovereign participation.

These are the real BUMP application screens—not invented product art. Each one expresses a different part of the personal node.

BUMP wallet overview on Android
Authority · the phone remains in control
BUMP receive screen with Bitcoin, Lightning and USDT options
Rails · select how value moves
BUMP desktop companion for creating and checking payment requests
Extension · inspect and prepare without surrendering approval
SASCOSM × BUMP

A payment is the start.
Your sovereign participation is the point.

Start a reviewed conversation