DAppBoard BI-Weekly Recap 1
The past 2 weeks were a fresh start for our organization. We have been working hard to set up the foundation of the new upcoming version of DAppBoard . We are currently focusing on building the backbone of it: principally how data are collected, organized and accessed. Our goal, in the next few months, is to get the new version of DAppBoard out. This recap is what we did from 12 to 24 November 2018.
🛠 DAppBoard ETL
Basics of the Ethereum blockchain (blocks, transactions, event logs).
Tokens (ERC20/ERC721): we aggregate there transfers but also their metadata like name, symbol, number of decimals.
Contracts: the source code and element of their ABIs are stored in an easy to use way. Thanks Etherscan for the openness of their API. We deployed our pipeline and database live for testing and could easily extract more than 60M transactions from 700K blocks, 22K tokens. All the software we run in the background is and will stay open source. As we can’t rely on decentralized technologies to do what we want yet. We open our work so community can thrust us and grow with us.
We set up the awesome Metabase to access and play with our data . Metabase is an open source piece of software that let anyone build queries and visualize and organize the results. The goal was to see if our data were correct and how easy the way they were stored let us play with it. Our first piece of analysis was about tokens (ERC20/ERC721):
The token space on @ethereum is still really active! Everyday, around 4000 different tokens are used. There is an average number of 350K transfers per days.
The number of unique receivers and senders per days is nearly double. A lot of ERC20, ERC721 tokens are still airdropped or minted everyday.
And our second piece about mining ⛏:
It's Friday and we compiled some facts about mining on #ethereum ! 42,576 miners mined a total of 230,592 blocks. #blockchain #Mining
The minimum number of transactions included in a block is 0 while the maximum is 388 with an average of 90 transactions per blocks.
With an average gas limit of 8,000,000 we can see that most of the blocks are optimized to use as much gas as possible.
In one week the total amount of gas used was 1,365,199,944,694 while the total gas limit was 1,860,227,470,940. This means that in the most ideal world: blocks are 73% filled.
Those two studies helped us validate our architecture and the correctness of our data set. If you want to be one of the first to see our upcoming tweet storms, do follow DAppBoardTeam on twitter .
Those 2 weeks went so fast and we could achieve a lot. The next steps of our adventure are:
Step back and explain , as the code written for the ETL has been done fast, a lot of things need to be consolidated and also documented so anyone can use it, or we can read it in few months too!
Produce more analysis , we just scratched the surface of what was possible to do with our pipeline. We’ll try to produce DApps specific dashboards. This will also let us improve even more how we structure and test our data set.
Enrich the data , some of the data we store need to be edited manually for more consistency. We need to build an interface for us to easily check and edit some of the data.
Grow the team , we want to grow the team, but for this we need to decide and secure how we’ll get funded for the next months. DAppBoard is focusing on building tools to store, explore and explain data that are generated by the Ethereum makers and users. Follow us or get in touch on Twitter !