oceanprotocol / df-py

veOCEAN & Data Farming backend
Apache License 2.0
3 stars 9 forks source link

Ensure df-py works on rinkeby #10

Closed trentmc closed 2 years ago

trentmc commented 2 years ago

TODOs:

Things that may help:

idiom-bytes commented 2 years ago

Tested for dftools newtoken & newairdrop, and it's working.

export const airdrops = {
    3: {
        airdropAddress: "0x789ddD01e0362A350e3401b510B759041d7D2c70",
        tokens: [
            "0xe6239d757c064c237dF31e08EbdD582f0608aCE0",
            "0x8127479a825EA352B542F41ea513Ff207e363421"
        ]
    },
    4: {
        airdropAddress: "0x9C862055A084E802F3Bc6Cf38862C3B9eb1e8879",
        tokens: [
            "0xe6239d757c064c237dF31e08EbdD582f0608aCE0",
            "0x8127479a825EA352B542F41ea513Ff207e363421"
        ]
    },
};

I have not tested query against barge/subgraphs.

trentmc commented 2 years ago

Perhaps you could have a unit test for some functionality (eg newtoken) on one of the networks (eg rinkeby)?

Example how: use "brownie.connect()" within the test itself.

trentmc commented 2 years ago

Note: what's built so far: just making sure that I could get any connection to rinkeby. So I picked the simplest possible test, to see that I could get some account balance info. That's all.

Further tests, eg querying pools speed, will be in other issues. example: df-py#100 slowness in querying pools on rinkeby