BNB deployment

[squadgazzz]

There is a known issue with the foundry breaking change in v1.0.0 that produces a different bytecode. This project's readme suggest using an old version, but this doesn't work on BNB:

Warning: EIP-3855 is not supported in one or more of the RPCs used.
Unsupported Chain IDs: 56.
Contracts deployed with a Solidity version equal or higher than 0.8.20 might not work properly.
For more information, please see https://eips.ethereum.org/EIPS/eip-3855

As a workaround, suggested by @fedgiac, the contract was manually deployed by sending the same calldata used in previous deployments on other chains. The broadcast JSON was handcrafted.

Still can't verify the contract since bscscan still hasn't indexed it: https://bscscan.com/address/0x9585c3062Df1C247d5E373Cfca9167F7dC2b5963

$ forge verify-contract --verifier-url https://api.bscscan.com/api --watch --rpc-url "$RPC_URL" 0x9585c3062Df1C247d5E373Cfca9167F7dC2b5963 DeployableVM --guess-constructor-args
Start verifying contract `0x9585c3062Df1C247d5E373Cfca9167F7dC2b5963` deployed on bsc
Error: Contract was not found: 0x9585c3062Df1C247d5E373Cfca9167F7dC2b5963

While another explorer shows the bytecode: https://bsctrace.com/address/0x9585c3062df1c247d5e373cfca9167f7dc2b5963?tab=Contract&p=1

upd: 4 days later, the bscscan finally indexed the contract. verified it manually ✅