@cfxlabsinc/b2b-services
    Preparing search index...

    The two things a deploy needs an operator to know about the keys, answered from public addresses alone.

    Both were deferred while the only source of these public keys was the signing keys the dashboard may not read (PROGRAM_DEPLOYS.md § 4.2). They come out of b2b.backoffice_wallet now, so no key material goes anywhere near a page.

    interface ProgramDeployWallets {
        payer: { address: Address; lamports: number };
        upgradeAuthorityHeldByCfx: boolean | null;
    }
    Index
    payer: { address: Address; lamports: number }

    Who funds the deploy and receives the buffer's rent back.

    upgradeAuthorityHeldByCfx: boolean | null

    Whether the deployed program's upgrade authority is a key the platform holds for it, the *_UPGRADE_AUTHORITY key wallet-api signs with — the § 4.3 dialog's held by CFX.

    null when nothing could be compared: an immutable program, or a chain read that resolved no authority. False would be a claim about a key rather than an admission that nothing was compared.