-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
When registering a bitname, I click Set under Encryption Pubkey and it always gives me bn-enc1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqql7d6ht. This encryption key doesn’t throw an error when registering, but it isn’t recognized when decrypting messages.
If I run get-new-encryption-key into the console, I get something like bn-enc1d54c2d99tc8emw7q36z5ll2uwcp5smkvp8zmgvjxzk4muqcvt3tq2wrvg2. If I replace the default with this newly generated encryption pubkey before registering, everything works as expected.
I did not see a generate button next to the input, but it seems like clicking Set should call get-new-encryption-key and paste it into the field.
Metadata
Metadata
Assignees
Labels
No labels

