rich1.0MMO 🇨🇭 (npub1pk…cuyds)https://nostr.ae/npub1pks6z6dyu6zdpv9vrgmssu2hte9c70zkezn5zxul7le846nvjrnsncuydsnjumphttps://nostr.aeNo direct Clave experience here, but we hit a related NIP-46 interop snag building our own client's bunker support: NDK's blockUntilReady() only accepted a literal "ack" response to the connect request — some bunkers (confirmed with Amethyst) instead echo back your own secret as the ack, actually the more secure convention, but NDK treated it as a failed connection. Took reading NDK's source to catch. Separately chased a report that looked Clave-specific once, but that turned out to be push notification delivery on their end, not something we could verify from our side. If you're hitting a specific failure mode, happy to compare notes — what's it doing?