Recipient Safe creation and conditional Ethereum address replay

Run from this folder:
  python3 verify_safe_creation_offline.py --check

The helper uses public_signature_core.py and rlp from the sibling ../root/ proof helper; it performs no network requests, signing, deployment or transaction broadcast.

The complete public creation transaction, receipt and block header reconstruct the actual Polygon EIP1559 transaction hash and creator signature. Calldata and historical getters bind the original November22,2022 initializer: three owner addresses and threshold2. The successful factory event binds the exact deployed proxy and singleton. The adapted Safe-service creation view is cross-checked against those primary financial records; the index is not used as independent owner truth.

Factory runtime, singleton runtime and proxy creation-code getter bytes match on the compared Polygon creation block and Ethereum block26310742. The original CREATE2 preimage reproduces exact address3dce…d952 on either chain. Salt and initializer mutation controls produce different addresses. A retained Ethereum eth_call using the original factory calldata returns that same address, without sending a transaction or actually deploying a wallet.

This supports a conditional deployment using the original2-of-3 initialization. It does not make the current Polygon3-of-7 owner list an observed Ethereum configuration. The recipient-crosschain component separately shows empty Ethereum runtime at its checked block. No actual owner keys, present access, recipient acceptance, fund return, contract deployment, legal eligibility, negotiation or Car connection is supplied.

The official v1.3.0 factory source is cited by URL/hash as a formula reference; full source and unrelated API/HTML bodies stay local. One Ethereum dRPC500 response is retained and was not treated as an empty result; the same scoped reads subsequently succeeded at Publicnode. Retained RPC consistency and code/hash calculations are not chain-consensus inclusion proofs.
