Aptos OFT wire

[dhruvinparikh]

No description provided.

[pegahcarter]

This is great. LMK when the PR is at a point ready for review.

[pegahcarter]

dvn1 and dvn2 are accidental and can be changed to dvnHorizen / dvnL0.

[pegahcarter]

I'll do this in a separate PR.

[pegahcarter]

Are you going to need the addresses from L0Constants.sol to import as peers? If so, should L0Constants.sol instead be a json that is readable by typescript?

I'm thinking if we go with a json, it would look something like this:

{
    "30101": {
        "fxs": "0x...",
        "frxUsd": "0x..."
    },
    "30255": {}
}

Where the keys are the EID. Unless you think the key should be chainid? Or should this be within L0Config.json? I'm flexible here.

[dhruvinparikh]

Are you going to need the addresses from L0Constants.sol to import as peers? If so, should L0Constants.sol instead be a json that is readable by typescript?

I'm thinking if we go with a json, it would look something like this:

{
    "30101": {
        "fxs": "0x...",
        "frxUsd": "0x..."
    },
    "30255": {}
}

Where the keys are the EID. Unless you think the key should be chainid? Or should this be within L0Config.json? I'm flexible here.

For wiring txs on EVMs, it needs to be done from multisig so will Solidity scripts will be use L0Constants.sol as well as L0Config.json

[pegahcarter]

We could refactor the EVM deploy script so that it loads the json file addresses rather than from the solidity file. I'm just thinking of what constants will be re-used across VMs.

[pegahcarter]

Will this be an issue if there's an array of [0x123, ""] as it's length 2?