avoiding address reuse (in fact, making address reuse completely impossible, even for malicious users), is still a massive win for transacting on-chain. The extra cpu cost to scan for transactions is well worth that trade-off in my opinion.

the 'privacy' that silent payments offers is identical to a recipient handling out unique addresses to everyone, nothing more. it doesn't protect against any other privacy pitfalls.

no problem. if you're using it to experiment, the '/tweak-index' endpoint may be more useful than '/tweaks' actually. The former returns all tweaks for that block, the latter will filter out all spent outputs (aka 'cutthrough' from the BIP)

you can use the blindbit-oracle server hosted on silentpayments.dev: https://silentpayments.dev/blindbit/mainnet/tweaks/900000

You can use the blindbit-oracle server hosted on silentpayments.dev (e.g. https://silentpayments.dev/blindbit/mainnet/tweaks/900000)

This is great, but I think saying 'catching up a few months takes an hour when on mobile' is a bit misleading I think. When I scan 1 year worth of transactions it takes me about ~5 minutes on my phone (doing 'local' scanning with Dana). Admittedly we use spent filtering, but that is described in the BIP too so I don't think it's unrealistic to compare it against that benchmark. '5 minutes' isn't *seconds*, but it isn't *hours* either.

This should be fixed now, i updated the release

crap, well that didn't take long😅 thanks for sharing👍

Shameless self plug: for those interested in testing out a new silent payments wallet: check out Dana (currently only on android). We're working on giving users their own [email protected] bip353 address when creating a new wallet, that should be live pretty soon.

https://github.com/cygnet3/danawallet

that's odd, i don't have any hangups myself, does it return a specific kind of error?

what do you mean? with syncing Dana?