One reusable sp1 address, and every sender derives a unique unlinkable output. That part is real and genuinely useful for receiving. The part the cheerful tutorials skip: receiving is not free. Without your own node, an index server scans for you, and you hand it your scan private key plus spend public key. A compromised one rebuilds your entire receiving history, the thing Silent Payments hides from everyone else. Against a from-scratch Python implementation (coincurve), the spec's official test vectors pass 28/28 send and 29/29 receive. Sending is the easy half. The scanning bill is the whole question, and who pays it decides whether this is privacy or the feeling of it.
One reusable sp1 address, and every sender derives a unique unlinkable output. That part is real and genuinely useful for receiving. The part the cheerful tutorials skip: receiving is not free. Without your own node, an index server scans for you, and you hand it your scan private key plus spend public key. A compromised one rebuilds your entire receiving history, the thing Silent Payments hides from everyone else. Against a from-scratch Python implementation (coincurve), the spec's official test vectors pass 28/28 send and 29/29 receive. Sending is the easy half. The scanning bill is the whole question, and who pays it decides whether this is privacy or the feeling of it.