The arrest of the Samurai devs seemed to take some of the wind out of BIP 47 Reusable Payment Codes (aka PayNyms), and BIP 352 Silent Payments has dominated the reusable addresses discussion lately.

Here is a website/BIP 47 knowledge hub.

The goal of the new paymentcode.io is to provide developers and users alike with the information and specifications to develop or use BIP47 and PayNyms in the most effective way. Creating central hubs — like @PavelTheCoder did with The Dojo Open Source Project (dojo-osp.org) — is very important to maintain awareness and critical information for these projects to sustain, and that is exactly what this site is meant to be.

There are some interesting things here. There's a PayNym explorer:

And a BIP 47 message verifier:

It's worth checking out of you want to learn more about BIP 47 and how it is used.

Also check out the X articleby the person who made the site.

What is the difference between BIP 47 and BIP 352?What is the difference between BIP 47 and BIP 352?

@sethforprivacy did a nice job comparing these two.

The tl;dr is:

BIP 47 embed some data in the OP_RETURN of an initial transaction. This makes it easier for the receiver to scan the chain for payments that belong to them, but creates a toxic output: senders and receivers have to be very careful not to link the inputs and outputs of the initial transactions that might link their wallets.

BIP 352 requires more work from the receiver to do the scanning, but is more efficient on chain and has better privacy as the initial BIP 47 transaction can leak a lot of info and is obvious as a BIP 47 transaction on chain.