aioetherscan's Introduction

aioetherscan

Etherscan.io API async Python non-official wrapper.

Features

API modules

Supports all API modules:

Also provides extra module, which supports:

link helps to compose links to address/tx/etc
contract helps to fetch contract data
generators allows to fetch a lot of transactions without timeouts and not getting banned

Blockchains

Supports blockchain explorers:

Installation

pip install -U aioetherscan

Usage

import asyncio
import logging

from aiohttp_retry import ExponentialRetry
from asyncio_throttle import Throttler

from aioetherscan import Client

logging.basicConfig(format='%(asctime)s - %(message)s', level=logging.INFO)


async def main():
    throttler = Throttler(rate_limit=4, period=1.0)
    retry_options = ExponentialRetry(attempts=2)

    c = Client('YourApiKeyToken', throttler=throttler, retry_options=retry_options)

    try:
        print(await c.stats.eth_price())
        print(await c.block.block_reward(123456))

        address = '0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2'
        async for t in c.extra.generators.token_transfers(
                address=address,
                start_block=19921833,
                end_block=19960851
        ):
            print(t)
            print(c.extra.link.get_tx_link(t['hash']))

        print(c.extra.link.get_address_link(address))
    finally:
        await c.close()


if __name__ == '__main__':
    asyncio.run(main())

aioetherscan's People

Contributors

Stargazers

Watchers

aioetherscan's Issues

get_tx_link not working for testnets

It seems that get_tx_link is returning the mainnet URL even if the client is for a testnet

Instantiating Client outside of asyncio context leads to confusing "RuntimeError: Timeout context manager should be used inside a task"

Instantiating a Client object outside of a running asyncio event loop leads to a very confusing
RuntimeError: Timeout context manager should be used inside a task exception upon performing requests.

The reason is:

Client creates a Network instance which stores a reference to loop via loop or asyncio.get_event_loop().
- When called outside of a running loop asyncio.get_event_loop() creates a new loop.
Later when running in a newly created asyncio context aiohttp checks for current_task() using the passed in stored loop from above
- The stored loop is distinct from the running one, meaning it has no current task, leading to the exception.

I'm not quite sure what the correct solution is here.

Maybe using asyncio.get_running_loop() instead of get_event_loop() and in the case of no active loop requiring the user to explicitly pass in a loop would be best...