Keymaster -- Optics Transaction Wallet Funding, Monitoring, and Management

[yourbuddyconner]

Problem: Reusing transaction signers across multiple homes results in nonce collisions when agents from separate homes try to write to the same replica at the same time.
Solution: Use unique signers per-home.

Problem: For 4 homes (alfajores, kovan, rinkeby, rinkarby) with 5 addresses each (kathy, watcher, updater, processor, relayer), this means there will be 20 unique addresses and each address has to be funded on each network resulting in 20 * 4 = 80 unique accounts across all networks which must be funded and topped up regularly.

Generalized: num_homes^2 * num_addresses

Solution: Write a tool that stores metadata about homes, addresses and sources of funds to make it easy to manage this quickly ballooning issue.

[yourbuddyconner]

The config file:

{
    "networks": {
        "alfajores": {
            "rpc": "",
            "bank": "",
            "threshold": ""
        },
        "kovan": {
            "rpc": "",
            "bank": "",
            "threshold": ""
        },
        "rinkeby": {
            "rpc": "",
            "bank": "",
            "threshold": ""
        },
        "rinkarby": {
            "rpc": "",
            "bank": "",
            "threshold": ""
        }
    },
    "homes": {
        "alfajores": {
            "replicas": [],
            "addresses": []
        },
        "kovan": {
            "replicas": [],
            "addresses": []
        },
        "rinkeby": {
            "replicas": [],
            "addresses": []
        },
        "rinkarby": {
            "replicas": [],
            "addresses": []
        }
    }
}

Networks: List of supported networks, replicas must exist in this list. Each network has a map containing the rpc endpoint to use when working with it, the bank hexKey signer (used for locally signing transactions), and the threshold max where accounts on that network should be funded.
Homes: List of Optics homes. Each home has a list of addresses to fund and a list of replicas where those addresses need to be funded.

[yourbuddyconner]

Wallet Metrics tool should be able to consume this config file and export prometheus metrics, perhaps a sub-command?

[yourbuddyconner]

MVP Features:

• Load config file from JSON
• Sign locally with hexKeys
• Fund addresses for each home on each configured replica

Extra Credit Features

• Config file validation
• Wallet monitoring + Prometheus metrics
• Store hexKeys in secret manager
• Sign remotely via KMS

Program Logic:

• Analyze all the wallets first, queue up top-up transactions, approve, then dispatch them.