create mainnet post-deploy script

[chadoh]

After we deploy the registry contract to mainnet, it won't initially have any contracts registered. It has two functions, batch_register and process_batch, that allow us to register many contract IDs at once. For example, on testnet we ran this:

stellar contract invoke --id registry -- batch_register --contracts '[
    ["usdc-circle", "CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["usdc-blend", "CAQCFVLOBK5GIULPNZRGATJJMIZL5BSP7X5YJVMGCPTUEPFM4AVSRCJU", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["xlm", "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["cetes", "CC72F57YTPX76HAA64JQOEGHQAPSADQWSY5DWVBR66JINPFDLNCQYHIC", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["defindex-factory", "CDSCWE4GLNBYYTES2OCYDFQA2LLY4RBIAX6ZI32VSUXD7GO6HRPO4A32", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["defindex-usdc-vault", "CBMVK2JK6NTOT2O4HNQAIQFJY232BHKGLIMXDVQVHIIZKDACXDFZDWHN", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["defindex-xlm-vault", "CCLV4H7WTLJQ7ATLHBBQV2WW3OINF3FOY5XZ7VPHZO7NH3D2ZS4GFSF6", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["defindex-cetes-vault", "CBIS5TEMTNNOTBE3WXPQUAGUEDYZZVIWAKTXEQCOUJ34OJJ3FJ5NLF2P", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["defindex-cetes-blend-strategy", "CCP4RBDWPRNO2LWO23XFU4BBLGA73J5N3BK7EHRJUHVN33YEMMFB2MBE", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["soroswap-router", "CCJUD55AG6W5HAI5LRVNKAE5WDP5XGZBUDS5WNTIVDU7O264UZZE7BRD", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["soroswap-factory", "CDP3HMUH6SMS3S7NPGNDJLULCOXXEPSHY4JKUKMBNQMATHDHWXRRJTBY", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["blend-pool-factory-v2", "CDV6RX4CGPCOKGTBFS52V3LMWQGZN3LCQTXF5RVPOOCG4XVMHXQ4NTF6", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["blend-backstop-v2", "CBDVWXT433PRVTUNM56C3JREF3HIZHRBA64NB2C3B2UNCKIS65ZYCLZA", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["blend-testnet-v2-pool", "CCEBVDYM32YNYCVNRXQKDFFPISJJCV557CDZEIRBEE4NCV4KHPQ44HGF", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"],
    ["blend-cetes-pool", "CAPBMXIQTICKWFPWFDJWMAKBXBPJZUKLNONQH3MLPLLBKQ643CYN5PRW", "GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M"]
]'

Where the three values of each are:

1. desired contract name
2. contract ID
3. owner (set to theahaco testnet account GAMP… for all of the above)

For mainnet, we will want something similar to the above, but more complex:

• Rather than flat values like blend-backstop-v2 and blend-testnet-v2-pool, let's use named sub-registries. This will require running stellar registry deploy --contract-name blend --wasm-name registry and then running a batch_register / batch_process similar to the above for the blend registry, and for each other namespaced registry we care to add (oz, soroswap, defindex, etc)
• We need to find each team's desired owner ID, rather than using the security council address (equivalent to GAMP… but for mainnet) for each. This will allow each team to have the rights to modify their contracts after our initial setup.

We need to work with each team to get this info and construct a comprehensive deploy script. Once we have and test this script, we can hop on a call with the security council to deploy the contract and run this script:

• stellar-scaffold/temp#16

[chadoh]

This now exists in a few places:

• https://github.com/stellar-registry/contracts/blob/main/contracts/registry/deploy_mainnet.sh
• feat: add known assets data contracts#21
• https://github.com/stellar-registry/oz-combined-wasms