Nunchuk now supports sending to Silent Payment addresses

[4rkad]

Context

Nunchuk Android v2.2.8 now supports sending to Silent Payment (BIP-352) addresses.

This is relevant for am-i-exposed because Silent Payment outputs on-chain look like regular Taproot (P2TR) outputs — they are indistinguishable from standard spends. This has direct implications for privacy analysis.

Why this matters for am-i-exposed

• No address reuse by design: Each sender generates a unique on-chain address for the recipient, even when sending to the same Silent Payment address. The tool should not flag these outputs as linked.
• Output type: Silent Payment outputs are standard P2TR — the tool already handles Taproot, but should not apply heuristics that assume Taproot outputs behave like traditional reused addresses.
• Wallet fingerprinting: As more wallets add SP send support (Cake Wallet, Sparrow, Blue Wallet, and now Nunchuk), the anonymity set of Taproot-spending transactions grows, making wallet fingerprinting harder.

Tracking: wallets with Silent Payment support

Wallet	Send	Receive	Platform
Cake Wallet	Yes	Yes	Mobile
Sparrow Wallet	Yes	Yes	Desktop
Blue Wallet	Yes	No	Mobile
Nunchuk	Yes	No	Mobile/Desktop

As SP adoption grows, the tool may eventually need to account for SP-related patterns in its analysis (e.g., single-output Taproot transactions becoming more common and less suspicious).

[PeterXMR]

This appears to be already addressed in commit 5252981 ("fix: correct silentPayments for Bitcoin Core & Nunchuk"), which set Nunchuk's silentPayments field to "send-only" in src/data/guide/wallets.ts.

Current state (line 121):

```ts
silentPayments: "send-only",
```

That value matches the documented capability - Nunchuk can send to SP addresses but does not yet receive at one. If that is intended to also cover receive support in the future, the field would flip to true; otherwise the issue can be closed.