Skip to content

Default encryption pubkey doesn’t work #16

Description

@BTCapsule

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.

Image

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.

Image

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions