whitelist-request

File a whitelist request

File a GitHub issue requesting whitelisting of the deployed integrator at $address on chain $chain. Follows the WHITELISTING.md flow and uses the whitelist-request.md issue template.

Step 0 — Preconditions

• Confirm CWD is the payment-integrators repo (package.json name is @p2pdotme/payment-integrators). If not, abort.
• Confirm gh CLI is authed: gh auth status. If not, tell the user to run gh auth login and stop.
• Confirm the issue template exists at .github/ISSUE_TEMPLATE/whitelist-request.md. If not, abort.

Step 1 — Resolve address + chain

If $address is empty, ask: "What's the deployed integrator address? (0x… checksum)."

Validate the address is 20 bytes hex. Soft-warn if not checksummed but accept it (we'll normalise via cast later).

If $chain is empty, ask: "Which chain? base (mainnet, 8453) or base-sepolia (84532)?" Default to base-sepolia for new deployments.

Step 2 — Verify bytecode parity

This is the most important step — the entire point of the whitelist preflight check.

1. Fetch the on-chain runtime bytecode. Prefer cast; fall back to a Hardhat one-liner if cast isn't installed:

   # Preferred:
   cast code <address> --rpc-url <rpc-for-chain>
   
   # Fallback (no cast):
   npx hardhat console --network <chain> --no-compile
   > await ethers.provider.getCode("<address>")
   

   Pick the RPC from hardhat.config.ts for the named chain.

2. Compute the keccak256 hash of the on-chain bytecode:

   cast code <address> --rpc-url <rpc> | cast keccak
   

3. Find the matching compiled artifact. Grep artifacts/contracts/integrators/**/*.json for an artifact whose deployedBytecode hash (keccak of the bytecode-without-metadata bytes) matches the on-chain hash. The artifact's contractName tells you which integrator this is.

   Important caveat: Solidity embeds a metadata hash in the deployed bytecode (the trailing IPFS/swarm hash, typically the last ~53 bytes). For a faithful comparison, either:

   • Compare the bytecode-without-the-metadata-suffix on both sides (strip the last 53 bytes), OR
   • Accept that the hash will differ if anything in the compilation inputs (source paths, optimizer settings, compiler patch version) changed, and report this clearly.