Cowrie Research

satsails-primary-sources-2026-05-06

4 min read

Satsails primary-source snapshot

Fetched: 2026-05-06 UTC

1) Official homepage

Source: https://www.satsails.com/

Selected excerpts from the official site (translated where useful):

A wallet that simplifies your transactions and puts sovereignty in your hands.

You can convert, receive, and send Bitcoin (On-chain, Lightning, Liquid) and stablecoins such as Depix, USDT, and EURx, all in one place, with total control and real freedom.

Converta BTC, LBTC, LUSDT, Depix e EURX entre si de forma prática e rápida.

Gere links e páginas para pagamentos em Bitcoin e stablecoins, direto da sua conta.

Additional signals from the source:

  • The site positions Satsails around practical financial workflow simplification rather than protocol ideology alone
  • The combination of conversion, multirail receiving, and payment-page generation makes the product look broader than a simple wallet UI
  • The homepage is strongly Brazil-facing in tone and product language, which is useful context for later interpreting PIX-related partner flows

2) Public app repository

Sources:

Selected excerpts from the README:

Satsails is a self-custodial Bitcoin and Liquid Network platform that [supports] Bitcoin, Lightning, and Liquid.

We are committed to being open source and transparent, offering a non-custodial service for bitcoin and liquid.

Currently our Lightning is custodial and operated by Coinos. This was a decision made to focus on usability.

Everything we build is designed to be held and operated by you. We either use on-device technology or connect you to partner companies.

As part of our operations, we collect a unique identifier and register it on our server to allow for account creation and managment. Additionally, we register a public key, which is used solely to direct your fiat payments and ensure that these payments are routed directly to your wallet.

Additional signals from the sources:

  • The README sharply clarifies Satsails’ custody boundary: Bitcoin and Liquid are framed as self-custodial, but Lightning currently depends on a partner-operated custodial layer
  • The explicit mention of fiat-payment routing tied to a registered public key is one of the strongest clues that Satsails is not merely a standalone wallet app
  • Build instructions requiring a private .env file from the team suggest there is a meaningful server-side or partner-integrated operational layer behind the open-source client

3) GitHub organization footprint

Source: https://github.com/Satsails

Selected signals from the organization page:

Satsails — Sail your wealth to the cloud

Repositories include Satsails, notify-lnurl, breez-lnurl, lwk-dart, payment_script, and related support code.

Additional signals from the source:

  • The repo set implies an actual wallet-and-payments stack spanning LNURL notifications, Liquid bindings, and payment automation rather than a thin mobile shell
  • Even without a large public docs portal, the GitHub footprint is enough to treat the project as an operating stack with several moving parts

4) Privacy policy and payment/compliance boundary

Source: https://www.satsails.com/pol%C3%ADtica-de-privacidade

Selected excerpts from the privacy policy (translated where useful):

We strive to minimize the amount of personal information collected from Satsails users.

[We may collect] public wallet addresses that you use or generate through Satsails, as well as a unique identifier generated by the wallet for account registration in our systems.

Certain Satsails features depend on third-party services.

We do not collect, store, or process personally identifiable data of end users, such as CPF, name, or banking information.

The collection and processing of personal data related to payments, identification, identity verification, or compliance obligations are the exclusive responsibility of the payment providers integrated into our platform.

Additional signals from the source:

  • The policy is unusually useful for categorization because it clearly separates Satsails’ wallet-level data handling from the compliance and payment-provider layer around it
  • The repeated references to integrated providers make the product look like a bridge between sovereign wallet UX and locally regulated payment operations
  • The policy also notes PIX-related metadata in partner systems, reinforcing the local-payments angle

Notes

  • Satsails appears best cataloged as bitcoin-and-liquid wallet control plane / Brazil-oriented local-payments bridge / hybrid self-custodial wallet stack.
  • No canonical standalone whitepaper or litepaper surfaced in this pass.
  • The most useful primary sources were the homepage, the public app README, the GitHub organization footprint, and the privacy policy because together they clarified custody boundaries, partner dependencies, and the role of local fiat-payment routing.

Graph View