Package: deficrawler
DeFi Crawler Python librarykeyko.ioTable of ContentsFeaturesPrerequisitesQuick-startUsageSupported protocolsTestingContributionsLicenseFeaturesThis library allows to get DeFi data from several protocols in a structured and standard way. This data comes from different subgraphs displayed in The Graph protocolPrerequisitesPython 3.6Quick-startpip install deficrawlerUsageTo get data from a protocol, it's needed to create an instance of the protocol with the name, version and blockchain where the protocols exists, the supported protocols can be found insupported protocolssection. And the entities for the protocols with the field types in theentitiesfolderTo get data from Lending protocols# Instanciate the protocol with the name, version and chainfromdeficrawlerimportLendingaave=Lending(protocol="Aave",chain="Ethereum",version=2)aave_polygon=Lending(protocol="Aave",chain="Polygon",version=2)compound=Lending(protocol="Compound",chain="Ethereum",version=2)cream=Lending(protocol="Cream",chain="Ethereum",version=2)cream_bsc=Lending(protocol="Cream",chain="bsc",version=2)# Not all the protocols has the same available events to get data, to know which entities are supported for each protocol:aave.supported_entities()uniswap.suported_entities()## For each different entity, data can be retrieved in a specific time range.compound.get_data_from_date_range(start_date,end_date,"borrow")# To get the all the users of a protocolcream_bsc.get_all_users()# And the user positionscream_bsc.get_all_users(user)To get data from Dex protocols# Instanciate the protocol with the name, version and chainfromdeficrawlerimportDexuniswap=Dex(protocol="Uniswap",chain="Ethereum",version=2)balancer=Dex(protocol="Balancer",chain="Ethereum",version=1)bancor=Dex("Bancor",chain="Ethereum",version=1)shushi=Dex("SushiSwap",chain="Ethereum",version=1)# Not all the protocols has the same available events to get data, to know which entities are supported for each protocol:uniswap.supported_entities()balancer.suported_entities()## For each different entity, data can be retrieved in a specific time range.uniswap.get_data_from_date_range(start_date_amm,end_date_amm,"swap")# To get the all the pools of a protocoluniswap.get_all_pools()To get prices from the oracles it's needed to instanciate an oracle object and call the functions.# Instanciate the oracle with the name, version and chainfromdeficrawlerimportOraclechainlink=Oracle(protocol="chainlink",version=1,chain="Ethereum")#Get all the available pairs to get the datachainlink.get_all_pairs()#Get the price for a specific pair in a time rangechainlink.get_price_from_date_range(from_date=start_date,to_date=end_date,pair="ETH/USD")Supported-protocolsProtocolsNameTypeVersionChainAaveLending2EthereumAaveLending2PolygonAaveLending2AvalancheCompoundLending2EthereumCreamLending2EthereumCreamLending2BSCCreamLending2PolygonCreamLending2ArbitrumCreamLending2AvalanceCreamLending2FantomKashiLending1EthereumKashiLending1PolygonKashiLending1xDaiKashiLending1fantomUniswapDexes2EthereumUniswapDexes3EthereumUniswapDexes3OptimismBalancerDexes2EthereumBalancerDexes2ArbitrumBalancerDexes2PolygonBancorDexes1EthereumSushiSwapDexes1EthereumSushiSwapDexes1BSCSushiSwapDexes1PolygonSushiSwapDexes1FantomSushiSwapDexes1CeloDodoexDexes2EthereumDodoexDexes2PolygonDodoexDexes2BSCDodoexDexes2ArbitrumUbeswapDexes1CeloPancakeswapDexes2BSCPangolinDexes1AvalancheTraderjoeDexes1AvalancheOraclesNameTypeVersionChainChainlinkOracle1EthereumTestingTests are creatd using Pytest library. To run the testspytest -vExamplesTo run the examples runpython3 docs/examples.pyContributionsIf you want to add a new protocol to be supported or a new entity to retrive data, create a PR with the new configuration of the protocol and the unit/integration tests of this new feature.To add a new protocol, create a new json config file in the config folder, with the strutureprotocolname-version.json.
Inside this configuration file must be the following sections:ProtocolThis section specifies the global configuration of the protocol. The required fields areName:Protocol name.Type:Protocol type (Borrowing lending)Version:Version of the protcolEnpoint:Subgrapn endpoint to send the http request to get the data. If the protocols exists on more than one chain, several enpoints can be providedExample"protocol":{"name":"AAVE","type":"Lending","version":2,"endpoint":{"ethereum":"https://api.thegraph.com/subgraphs/name/aave/protocol-v2","polygon":"https://api.thegraph.com/subgraphs/name/aave/aave-v2-matic"}}After this section the supported entities should be specified. Each entity has three different sections inside of them.Entity:The entity contains the fields to create a common entity from a shared type of event of different protocols (borrow, swap, deposit...). The entity starts with the name that will be applied to this specific event across all the protocols. Then should be a field for each attribute that will be contained in the entity, and each field shoud have an array, with the path to find this element in the corresponding subpgraph, these fields will be used to create the query. As example for borrow entity in Aave:"borrow": {
  "attributes": {
    "tx_id":[
      "id"
    ],
    "user": [
      "user",
      "id"
    ],
    "token": [
      "reserve",
      "symbol"
    ],
    "amount": [
      "amount"
    ],
    "timestamp": [
      "timestamp"
    ]
  }Query:: Each query in each protocol can be named different, to allow create the query dynamically, the query name should be specified and the field to order by if will be more that one batch to retrive. In this section also can be specified, additional fields to get data from the subgraph that will be needed to apply transformations, but will not be part of the output itself. As example for Aave we need to get the decimals for the token to divide the amount, but the decimals are not part of the entity. As example"query": {
      "extra_fields": {
        "decimals": [
          "reserve",
          "decimals"
        ]
      },
      "name": "borrows",
      "params": {
        "orderBy": "timestamp"
      }
    }Tranformations:This section specified the transformations that should be applied to the fields (if any transformation should be applied). Here we can specify the field of the common entity (the output) that needs to be transform, and the function that will be applied. This funtion will be call dinamically in the transformation phase. As example:"transformations": {
      "amount": "decimals",
      "tx_id":"tx_id_colon"
    }LicenseCopyright 2020 Keyko GmbH.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.