pull down to refresh

101 sats \ 5 replies \ @justin_shocknet 10h \ parent \ on: Stacker Saloon

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"

write
preview
1 sat \ 4 replies \ @0xbitcoiner 10h

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.

reply
1 sat \ 3 replies \ @k00b 8h

It'd use the same ndebit across devices.

reply
1 sat \ 1 reply \ @justin_shocknet 8h

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

reply
18 sats \ 0 replies \ @k00b 8h

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'
  }
]
reply
1 sat \ 0 replies \ @0xbitcoiner 7h

Does hitting 'save' on the wallet config without changing anything trigger a new 'requesting key'? I think I just did that!

reply