ethereum-etl
v1-contracts
| ethereum-etl | v1-contracts | |
|---|---|---|
| 3 | 2 | |
| 2,826 | 362 | |
| 0.7% | - | |
| 6.9 | 0.0 | |
| 29 days ago | about 3 years ago | |
| Python | Python | |
| MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ethereum-etl
-
Blockchain transactions decoding: making wallet activity understandable
Event is a log entity which EVM smart contracts can emit during transaction execution. Events are very good at signalling that an some action has taken place on-chain. Applications can subscribe and listen to events to trigger some off-chain logic or they can index, transform and store events in some off-chain storage (look at The Graph protocol or Ethereum ETL).
-
data engineering in web3
I'm surprised this is the only good response in this thread so far. Blockchain data is completely open but requires some organization in order to perform analytics. Nansen for example is a product that is built on top of ethereum-etl which you can checkout here
-
Trying To Recover Old ETH
You can use https://github.com/blockchain-etl/ethereum-etl
v1-contracts
- Are there any interesting projects that are backed by "small" smart contracts?
-
Ethereum Isn't Fun Anymore
If you're working on "large Ethereum smart contracts" you've missed the point. On chain logic should always be as minimal as possible. Uniswap v1 was two vyper files. One was 46 lines, and the other was 496 lines[1]. It took like 20 minutes to read through the code thoroughly, and was one of the most impactful contracts ever deployed to the network.
Solidity also matured a lot, which is why Uniswap v2 moved back. If you find yourself writing an EVM assembler from scratch, and you're trying to build something other than a compiler, you have veered way way off course, and need to re-evaluate your system architecture.
Feature creep might work well if you're trying to leech money from a government contract or something, or being paid by line of code you contribute, but it's fatal in the Ethereum world. I consulted for a number of projects that made the exact same mistake, and most of them aren't around anymore.
[1] https://github.com/Uniswap/uniswap-v1/tree/master/contracts
What are some alternatives?
CueObserve - Timeseries Anomaly detection and Root Cause Analysis on data in SQL data warehouses and databases
v2-periphery - 🎚 Peripheral smart contracts for interacting with Uniswap V2
helium-etl-queries - A collection of SQL views used to enrich data produced by a Helium blockchain-etl
homebrew-golem - Golem is creating a global market for computing power.
rainbow_csv - 🌈Rainbow CSV - Vim plugin: Highlight columns in CSV and TSV files and run queries in SQL-like language
pyteal - Algorand Smart Contracts in Python
NetXML-to-CSV - Convert .netxml file into CSV file
uniswap-v2-periphery - 🎚 Peripheral smart contracts for interacting with Uniswap V2 [Moved to: https://github.com/Uniswap/v2-periphery]
dbd - dbd is a database prototyping tool that enables data analysts and engineers to quickly load and transform data in SQL databases.
quadrable - Authenticated multi-version database: sparse binary merkle tree with compact partial-tree proofs
spotty - Training deep learning models on AWS and GCP instances
dfktools - Interact with the contracts of DefiKingdoms