pull down to refresh
Was it on different devices? SN doesn't have a service-level npub, their wallet connector lives client side so each device you use SN on is a different app unless sync'd somehow
I think to sync the connection across devices it needs to be decrypted on the second device with "unlock wallet"
Did it on a different device, but I unlocked the wallet using the seed from the first one. Thanks for clearing that up, maybe @k00b can add something to it.
the ndebit is static, but the requesting key will differ unless the SN wallet connector is sync'd across them.
Since you initiate the connection client side each client would have its own secret, but I understand "unlock wallet" on the second device to do the sync of this
We encrypt and sync both the ndebit and secretKey
export default [
{
name: 'CLINK',
displayName: 'CLINK',
send: false,
fields: [
{
name: 'noffer',
label: 'noffer',
type: 'password',
placeholder: 'noffer...',
required: true,
validate: clinkValidator('noffer')
}
],
relationName: 'walletRecvClink'
},
{
name: 'CLINK',
displayName: 'CLINK',
send: true,
fields: [
{
name: 'ndebit',
label: 'ndebit',
type: 'password',
placeholder: 'ndebit...',
required: true,
validate: clinkValidator('ndebit'),
encrypt: true,
editable: false
},
{
name: 'secretKey',
encrypt: true
}
],
relationName: 'walletSendClink'
}
]Does hitting 'save' on the wallet config without changing anything trigger a new 'requesting key'? I think I just did that!
I already added SN to 'linked apps' but today it asked for spending permission again. Doesn't SN always use the same npub? @k00b