The report is in artifacts/report.md, with a short README beside it. Both are left untracked, as required. Short answer: the BLACKOUT v3.7 plan can't launch on IMD as written. I found five blockers, three of them hard.

Everything was read-only: nothing deployed, paid, signed or quoted. The only writes to the IMD API were two free POST /requests/check preflights, which create nothing. Every claim in the report is labelled FACT, INFERENCE, UNKNOWN or PROPOSAL and cites a doc section, a contract address and function, or a past launch.

Q1 – Endowment.

• Codeless address: yes. The 20% remainderTo can be an address with no code. Launch 1316 sent its remainder to 0x…dEaD (no code, never used), and no code-size, EOA-only or allowlist check exists in the launch schema.
• Amounts at poolBps 7000: 10% to the swarm, 70% to the pool, 20% to remainderTo. I confirmed this on-chain with launches 1015 and 1300.
• No split: the remainder goes to exactly one address.
• The real blocker is the address itself. The predicted RewardPool address depends on launch numbers that IMD assigns from one global counter, and nobody can reserve them. If the prediction misses, the 20% is lost for good.
• Safest alternative: deploy an ownerless escrow contract first and use its real address as remainderTo. Afterwards anyone can call it to forward the tokens once to a RewardPool it checks on-chain. The 20% never touches a personal or swarm wallet.

Q2 – Address prediction.

• Derivation: I confirmed the formula on-chain. Application contract addresses are a CREATE2 hash of the launch number and the contract's index (0–7). Predicted and actual addresses match for launches 1271 and 1316.
• Single use: yes. Only IMD's launch wallet can deploy (NotDeployer), and each launch number is recorded once.
• The exact AlreadyLaunched error name doesn't appear in the deployed bytecode, so that name is unconfirmed.

Q3 – Custom hook.

• Your hook with constructor data: yes. It takes up to 16 static arguments plus the platform placeholders.
• Pool initializer: the LaunchFactory 0xa25b…4645 initializes the pool. That is the address your authenticated-initialization check should expect.
• Fee, price, tick spacing:
  • The pool fee is fixed by policy at 1.25%.
  • The opening price is fixed by policy: 10 ETH valuation for an ETH pair.
  • Tick spacing was 60 in a past launch.
• Blocker: V4Market's constructor reverts unless the pool fee is 0. It also charges its own 0.25% network fee on top of the platform's.
• The 1% project fee goes to the paying wallet, not a predicted FeeRouter. Anyone can trigger payout with claimFees, but only the paying wallet can later point the fee at the FeeRouter, with setRequester.

Other findings.

• Oracle heartbeat: schedule.create rejects deliver ("Unrecognized key"), and SwarmDesk only accepts answers delivered by IMD's two on-chain oracle contracts. Scheduled answers can never reach it. The fix is either a public relay function on the Desk or running on the paid on-chain backup asks alone.
• Workflow: workflow.open covers one launch plus a site, not all five steps. The sequence is five separate 0.5 IMD actions (2.5 IMD total, plus 0.5 IMD per oracle run). Contracts-only launches call nothing after deployment, so registering, binding and funding must come from a keeper or any wallet.
• Build settings: your foundry.toml uses via_ir = true and lacks bytecode_hash = "none". The docs require that setting, and IMD's verifier built launch 1316 without via_ir. Rebuilding would invalidate your pinned code hashes and predictions.
• Holder snapshot: use the identity.md NFT on Ethereum (chain 1, 0x0000ec93…ec1d, token ids 0–1999). Pin a finalized Ethereum block, read ownerOf for every id, then build the Merkle root.

Not confirmed:

• whether an 8-contract launch fits the 0.01 ETH gas ceiling on Robinhood Chain;
• whether a tick spa