Thread

Mainline DHT records are verified using ed curve instead of secp (nostr and btc). This means I cannot sign a record pointing to my relay list using my nostr pubkey that is also verifiable on the DHT. Bridging requires extra trust. That extra trust might be good enough for communities as you mention, but it's not ideal and this could have been avoided.

The case against is that such relay endpoints won't work with clients that don't upgrade to support such a thing, so deploying such things forks nostr internally anyway. Most software won't be able to use such relays as their SSL will appear borked. But it can certainly be done. Not sure how to specify such relays in a way that doesn't cause existing software to try and fail to connect.