No conversion to USD / EUR / fiat

CypherpunkPay is just an open source code. It has no way to convert your cryptocurrency to fiat money.

No Lightning Network

We would love to support LN eventually. However, simplicity for the merchant is the overriding goal.

Unfortunately, as of today LN is a high effort deal for the accepting party. This includes full Bitcoin node requirement, LN node requirement, LN wallet private keys on the server, inbound liquidity management, tricky backups, frequent software updates, dealing with unsolved attack vectors, and more.

We will watch LN development closely and we hope to find a pragmatic way to add LN support some day in the future. No promises, though!

No shitcoins

CypherpunkPay currently only supports Bitcoin.

CypherpunkPay does not aim to maximize the number of supported coins or assets. In fact, we will be very hesitant with adding any assets, prioritizing simplicity and Bitcoin.

That being said, CypherpunkPay will consinder supporting whatever we believe may advance cypherpunk vision, especially regarding financial privacy. For example, we are considering adding Monero or Liquid BTC in the future.

Not a wallet

CypherpunkPay does not have Bitcoin wallet built in. Instead, it will work with any modern wallet of your choice (desktop, mobile or hardware).

Not a web store

CypherpunkPay does not have a web store or a shopping cart built in. It is a pure payment processor easy to integrate with any web store or online service.

Block explorers collution risk

If any two block explorers turned malicious and colluded they could trick you into accepting a fake payment (with some trial and error, because CypherpunkPay picks random ones). CypherpunkPay uses a limited number of “well established” block explorers that appear to have something at stake. We believe this is a reasonable simplicity-vs-risk trade off.

Block explorers privacy risk

For each generated address, CypherpunkPay will check two randomly picked block explorers, over the new Tor circuit.

A malicious block explorer could build a heuristic to tell specific addresses were asked by the CypherpunkPay software.

As initially there may be few CypherpunkPay installations, a malicious block explorer could then blindly assume or guess to whom the payments may belong, especially if your amounts are unique among CypherpunkPay users.