Price:

BITCOIN

Tannahill database protects Bitcoin's reusable payments from police servers

Sunday, May 17, 2026 · from 1 podcast
  • BIP47DB.org inscribes payment codes on-chain, replacing the centralized PayNIM directory Samurai used.
  • Ashigaru team has already inscribed 20,000 codes at a cost of $150 to secure mainnet.

When Samurai Wallet developers were arrested, its users faced a problem beyond confiscated funds: they risked losing their entire payment history. The wallet relied on a centralized server, PayNIM, to store BIP47 reusable payment codes and their connection metadata. That server went offline, severing the link between a user's payment code and the addresses they had paid.

Max Tannahill's solution is BIP47DB.org, a permanent, on-chain database built using Bitcoin inscriptions. By storing compressed payment codes in the witness space, it creates an append-only directory any wallet can rebuild locally. This isn't speculative; the Ashigaru team, which took over Samurai's codebase, has inscribed approximately 20,000 existing codes onto mainnet. At current fee rates, the total cost to secure the directory was only $150.

"Moving this data onto the blockchain is the only way to ensure resilience against state interference."

- Max Tannahill, Ungovernable Misfits

Tannahill argues the database solves a fundamental recovery flaw in BIP47. If you restore a wallet from a seed phrase, you can see incoming payments but often lose the history of connections you initiated. Centralized servers like PayNIM acted as a lookup table for these notification transactions, a 'metadata crutch' wallets depended on.

The new on-chain index allows wallets to scan a specific 'numbers address' to find every registered payment code locally. This means wallets like BlueWallet could support BIP47 without ever querying a central server. In the long term, Tannahill envisions this infrastructure could eliminate the notification transaction itself. If every payment code is indexed on-chain, wallets could scan new blocks for potential payments, shifting the burden from the sender announcing a payment to the receiver scanning a decentralized list.

Source Intelligence

- Deep dive into what was said in the episodes

Max Tannahill Reveals BIP47DB.ORG | FREEDOM TECH FRIDAY 40May 16

  • Max Tannahill explains BIP47 was proposed in 2015 as a non-interactive payment code standard to replace reusable addresses and provide a base privacy layer. It enables private, repeated payments without requiring a server to generate new addresses.
  • Samourai Wallet implemented BIP47 in 2017 alongside other wallets like Billeater and Stash. The ecosystem aimed to combine BIP47 with CoinJoin for a comprehensive privacy stack, though this collaborative vision didn't fully materialize.
  • Samourai created the PayNym directory to improve BIP47's user experience. It provided human-readable pseudonyms and avatars, acting as a trusted lookup service for unwieldy payment codes similar to PGP key servers.
  • The PayNym directory served a critical recovery function. Wallets like Samourai and Sparrow could not rediscover outgoing notification transactions after a restore using only seed words, relying on the directory to rebuild connection metadata.
  • After Samourai's legal issues in 2024, the Ashigaru team scraped the PayNym directory, acquired the domain, and resurrected the service. This prevented a total collapse of BIP47's network effect but highlighted centralization risks.
  • Max Tannahill built BIP47DB.org to decentralize the storage of BIP47 payment codes by inscribing them on-chain using Ordinals. The protocol compresses codes into efficient batches, creating an immutable, append-only directory.
  • BIP47DB enables wallets to scan a canonical address to build a local database of payment codes, potentially removing dependency on centralized PayNym servers. It could also allow new payment directories to bootstrap from on-chain data.
  • The Ashigaru team inscribed approximately 20,000 payment codes on mainnet for a cost of roughly $135-$140. This demonstrates the low economic barrier to backing up the entire directory on-chain.
  • BIP47DB is designed as infrastructure for wallet and directory operators, not for direct retail use. Max Tannahill hopes it provides resilience, allowing the ecosystem to survive the loss of any single PayNym server.
  • The protocol's simplicity allows it to function without a full Ordinals indexer. Tools can query a single unspendable address via APIs like mempool.space to fetch and decode the inscribed payment code batches.