pull down to refresh

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

18 sats \ 0 replies \ @k00b 14h

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