Replying to Avatar DanConwayDev

I like radicle and I had some discussions with them about this. Unfortunately they use a different cryptographic curve which means you can't have a key which is provably a radicle key and a nostr key.

Ultimately, I think nostr is the better solution because it has its own ecosystem and doesn't try to create one from scratch.

nostr:nevent1qqs842f7mlhsmykugna3k5vytcr8tsd8wfcdpz676wrahrc50gdpmygpz9mhxue69uhkummnw3ezuamfdejj7q3q5qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exsxpqqqqqqz8srrpd

Avatar
🇵🇸 whoever loves Digit 3mo ago

Wouldn't either of these 2 solutions work?

1. Have radicle and nostr protocols add support for each other's key formats as alternatives, updating related apps and backends to reflect this change

2. Fork radicle to a nostr version, with dual-access apps and backend implementations then likely emerging naturally

Reply to this note

Please Login to reply.

Discussion