total 16K
drwxrwxr-x+ 2  1000   100 4.0K Aug 29 00:42 .
drwxrwxr-x+ 6 65534 65534 4.0K Aug 29 18:09 ..
/home/ctfbot/prog/stacker.news/wallets/server/wrap.js:99:          case 14: // payment secret
/home/ctfbot/prog/stacker.news/wallets/server/resolvers/protocol.js:180:  // Only upserts that persist a vault-encrypted secret depend on the current vault key.
/home/ctfbot/prog/stacker.news/wallets/server/protocols/lndGrpc.js:67:      preimage: invoice.secret,
/home/ctfbot/prog/stacker.news/wallets/server/persist.js:8:// `config` JSON mirror over Vault-encrypted secrets). The GraphQL resolvers in
/home/ctfbot/prog/stacker.news/wallets/server/persist.js:37:// True when the config persists a vault-encrypted secret — the case that needs
/home/ctfbot/prog/stacker.news/wallets/server/persist.js:210:// rotation committed meanwhile, so we never persist a send secret under a stale
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/lnc.js:23:        'Grab the `pairing_secret_mnemonic` from the output and paste it here.'
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/clink.js:40:        name: 'secretKey',
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/docs/dev/lnc.md:22:Grab the `pairing_secret_mnemonic` from the output and that's your pairing phrase.
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/docs/dev/lnc.md:27:$ sndev cli litd sessions add --type account --label sndev --account_id $(sndev cli litd accounts create --balance 100000 | jq -r '.account.id') | jq -r '.session.pairing_secret_mnemonic'
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/docs/dev/spark.md:39:`SPARK_SERVICE_MNEMONIC` secret in both the web and worker environments; treat
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/docs/dev/spark.md:40:it as a required production deployment secret. The web process uses it for
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/nwc.js:62:          'It must NOT allow spending (`pay_invoice`, `pay_keysend`, `multi_pay_invoice`, `multi_pay_keysend`): this secret is stored on our server, so attach a receive-only connection.'
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/nwc.js:100:  const { walletPubkey, secret, relayUrls } = parseNwcUrl(url)
/home/ctfbot/prog/stacker.news/wallets/lib/protocols/nwc.js:104:    secret
/home/ctfbot/prog/stacker.news/wallets/lib/validate.js:30:          let relayUrls, walletPubkey, secret
/home/ctfbot/prog/stacker.news/wallets/lib/validate.js:32:            ({ relayUrls, walletPubkey, secret } = parseNwcUrl(url))
/home/ctfbot/prog/stacker.news/wallets/lib/validate.js:44:          string().required('secret required').trim().matches(/^[0-9a-fA-F]{64}$/, 'secret must be 64 hex chars').validateSync(secret)
/home/ctfbot/prog/stacker.news/wallets/lib/validate.js:67:    secret: url.searchParams.get('secret'),
/home/ctfbot/prog/stacker.news/wallets/client/components/form/hooks/draft.js:41:// A fieldless protocol (WebLN) has no inputs, so its `enabled` flag *is* its
/home/ctfbot/prog/stacker.news/wallets/client/components/form/hooks/draft.js:58:// A content hash of a draft — its config plus enabled flag. Two drafts with the
/home/ctfbot/prog/stacker.news/wallets/client/components/form/hooks/draft.js:59:// same config and enabled flag hash equal regardless of origin — this is how
/home/ctfbot/prog/stacker.news/wallets/client/components/onboarding.js:179:        <p>Your recovery secret is being generated and encrypted on this device.</p>
/home/ctfbot/prog/stacker.news/wallets/client/protocols/clink.js:20:export async function sendPayment (bolt11, { ndebit, secretKey }, { signal, timeout = WALLET_SEND_PAYMENT_TIMEOUT_MS } = {}) {
/home/ctfbot/prog/stacker.news/wallets/client/protocols/clink.js:31:      SendNdebitRequest(pool, Buffer.from(secretKey, 'hex'), [relay], pubkey, request, Math.ceil(timeout / 1000)),
/home/ctfbot/prog/stacker.news/wallets/client/protocols/clink.js:64:  // For budgets to work, we need to encrypt and sign the debit request events with the same secret 
... (output truncated)