Git-Mirrors/web3-starter-py
1
0
Fork 0
mirror of https://github.com/autistic-symposium/web3-starter-py.git synced 2025-05-17 14:10:21 -04:00
Code Issues Projects Releases Packages Wiki Activity
web3-starter-py/web3toolkit/README.md
mvonsteinkirch 58a160dcf5 💾
2022-12-26 18:15:56 -08:00

1.9 KiB
Raw Blame History

📚 web3-python-toolkit


an on-going development of a library and set of python scripts with my fav on-chain ops.


installing

brew install poetry
make install
cp .env.example .env

scripts

get contracts deployed to mainnet and testnets

  1. add info to .env
  2. run poetry run python get_contracts_deployed.py
  3. any output is saved to data/.

get reserve history by block for a pair of addresses

  1. add the pair abi to abi
  2. add info to .env
  3. run poetry run python get_reserve_history_by_block.py

get deep block data

  1. add info to .env
  2. run poetry run python get_deep_block_data.py

troubleshoot

if you see ethereum-etl not compatible to m1 run:
pip uninstall ethereum-etl 
pip install --no-binary ethereum-etl

resources


relevant info

providers
  • providers are how libraries such as web3.py talk to the blockchain.
  • providers take JSON-RPC requests and return responses
  • the most common ways to connect to your node are:
    • IPC (uses local filesystem, fastest and most secure)
    • Websockets (works remotely, faster than HTTP)
    • HTTP (more nodes support it)

middleware
  • a web3.py instance can be configured via middleware (sitting between the web3 methods and the provider).
  • middlewares use an onion metaphor: each layer may affect both the request and response from the provider.
  • each middleware layer gets invoked before the request reaches the provider, and then processes the result after the provider returns, in reverse order.
  • we often use geth_poa_middleware, to run with geth's Proof-of-Authority (PoA) consensus. this adds support for more than 32 bytes in each block (the extraData field).