Cowrie Research

river

4 min read

River

  • Name: River
  • URL: https://river.com/
  • Category: bitcoin brokerage and treasury operator / proof-of-reserves and custody workflow company / business treasury and mining payments control plane
  • Tags: bitcoin-ecosystem
  • Summary: River belongs in companies/ because the durable dependency is not just a retail app or brokerage screen but a named operator that onboards businesses, keeps bitcoin in River-run full-reserve custody, publishes proof-of-assets and proof-of-liabilities reports, gates cash balances through the Lead Bank relationship, and packages treasury, mining, and wallet workflows under one company-run shell. The useful question is not just where can a company buy bitcoin? but which operator controls onboarding, custody policy, reserve publication, cash-banking wrappers, payout behavior, and the security defaults behind those balances?
  • What it does:
    • Operates a bitcoin-only brokerage and account platform for individuals, corporations, LLCs, trusts, partnerships, nonprofits, IRA LLCs, Solo 401(k)s, family offices, and mining operations
    • Runs a business onboarding workflow that promises onboarding within 24 hours and assigns a dedicated relationship manager for business accounts
    • Keeps client bitcoin in River-run full-reserve custody, publishes proof-of-assets plus proof-of-liabilities data, and gives clients a balance-inclusion verification flow
    • Packages security controls such as multisig cold storage, in-house custody, 2FA, new-device verification, ForceField send limits, account notifications, SOC II claims, and 24/7 monitoring inside the same operator boundary
    • Connects USD cash balances to Lead Bank while keeping River as the visible bitcoin, wallet, and treasury workflow shell
    • Extends the same company shell into business treasury accumulation, bitcoin-and-Lightning wallet operations, and mining auto-convert-to-cash workflows
  • Key claims:
    • The business page says River serves corporations, LLCs, trusts, IRA LLCs, Solo 401(k)s, partnerships, nonprofits, mining operations, family offices, and agencies, and says onboarding can complete within 24 hours with a dedicated relationship manager
    • The same page says mining operations can auto-convert incoming bitcoin to cash and use River’s bitcoin-and-Lightning wallet to manage payment operations, which makes River more than a passive brokerage front end
    • The security page says River protects funds with proof of reserves, multisig cold storage, custody not built on third parties, and FDIC-insured cash at Lead Bank, while account protections include 2-factor authentication, account notifications, 24/7 security monitoring, SOC II compliance claims, ForceField send limits, and new-device verification
    • The reserves page says River holds 100% of bitcoin deposits in full reserve and explains that proof of reserves combines proof of assets, proof of liabilities, cold-storage ownership verification, and client inclusion checks against the liabilities set
    • The business and security disclosures explicitly name River Financial Inc. as the operating entity and stress that River is not a bank, which is analytically useful because the cash wrapper and the bitcoin operator shell are related but not identical boundaries
  • Whitepaper: No standalone company whitepaper is the important artifact here. The clearest current primary materials are River’s business, security, and reserves pages, which expose the operator boundary more directly than a generic marketing overview; the broader source bundle remains ../whitepapers/river-primary-sources-2026-05-01.md.
  • Sources:

Internal linkages

  • Alias note for legacy project placement: river.
  • Useful adjacent company reads for bitcoin treasury, custody, and payment operators: strike, unchained, and galoy.
  • Reserve-verification adjacency when the question is balance attestation rather than one operator shell: hoseki.

Protocol / company boundary

  • River is better kept as an entity note than as a standalone projects/ note because the practical dependency is a named company running onboarding, reserve publication, wallet and treasury workflow, cash-bank integration, and account-security policy rather than a separable protocol surface.
  • The interesting control plane is the operator shell: who admits the customer, who controls the custody model, who publishes reserve truth, who decides security defaults, and who packages mining, treasury, and wallet workflows into one service boundary.
  • Keep [[../projects/river]] only as an alias so existing links keep resolving without pretending River is a neutral protocol primitive.

Control surface

  • Practical leverage sits in account approval, business onboarding, relationship-manager workflow, in-house custody design, reserve-publication cadence and methodology, wallet and send-limit policy, cash-balance handling through the Lead Bank wrapper, and the operational choice to package treasury, mining, and payment flows inside one River-managed environment.

  • The sticky dependency is not just where a user clicks buy BTC; it is River’s full account, reserve, wallet, and reporting shell. Once a business relies on River’s proof-of-reserves publication, treasury workflow, payment tooling, and policy defaults, the real lock-in is to the company-run operating boundary.

  • Read River here as a bitcoin financial operator first and as a brokerage app second.

  • Last reviewed: 2026-08-07 UTC

Graph View

Backlinks