Shall I deploy child chain manager contract for Polygon Mintable Assets

PudyJapan · September 20, 2021, 12:13am

Hi,

I am following the tutorial below for my Polygon Mintable Asset.

I have deposit, withdraw and mint for child and made sure the root’s mint can be called from ethereumMintableAssetProxy.

I want the address of the childChainManager which would call the deposit of the child contract.
Shall I deploy the child chain manager, or shall I use a deployed address?

Do I have to deploy any other contracts than my root and child contracts?

Thanks for advance.

PudyJapan · September 20, 2021, 1:38am

I found below the addresses for childchainmanager and childchainmanagerproxy

Which address shall I give the deposit permission?

github.com

maticnetwork/static/blob/master/network/testnet/mumbai/index.json

{
  "Main": {
    "NetworkName": "Goerli",
    "ChainId": 5,
    "DaggerEndpoint": "wss://goerli.dagger.matic.network",
    "WatcherAPI": "https://staking.api.subgraph.matic.today/api/v2",
    "StakingAPI": "https://staking.api.subgraph.matic.today/api/v2",
    "Explorer": "https://goerli.etherscan.io",
    "Contracts": {
      "BytesLib": "0xde5807d201788dB32C38a6CE0F11d31b1aeB822a",
      "Common": "0x84Dc17F28658Bc74125C7E82299992429ED34c12",
      "ECVerify": "0xccd1d8d16F462f9d281024CBD3eF52BADB10131C",
      "Merkle": "0xCD87Be2Df3de01EA23666c97104613ec252300E8",
      "MerklePatriciaProof": "0x3a0Db8fa2805DEcd49cCAa839DaC15455498EDE2",
      "PriorityQueue": "0xD26361204b8e4a4bb16668bfE7A1b9106AD17140",
      "RLPEncode": "0xDE0D18799a20f29d9618f8DDbf4c2b029FAdc491",
      "RLPReader": "0xA5e463c187E53da5b193E2beBca702e9fEeA3738",
      "SafeMath": "0x1bEb355BE0577E61870C4c57DAaa6e2129dd0604",
      "Governance": "0x03Ac67D03A06571A059F20425FFD1BEa300d98C2",
      "GovernanceProxy": "0xAcdEADEE4c054A86F5b1e8705126b30Ec999899B",

This file has been truncated. show original

definelabs-2 · November 29, 2021, 3:25am

None of these.

The childManagerProxyAddress is

Mumbai: 0xb5505a6d998549090530911180f38aC5130101c6
Mainnet: 0xA6FA4fB5f76172d178d61B04b0ecd319C5d1C0aa