Blocktivity developpment ...
What's happening in Blocktivity?
Last year I had a lot of people pushing me to make a new open-source version of Blocktivity. I had their support and the promise they would help me heavily on the development.
As soon as I announced the project to open source the version 2.0 of Blocktivity. Most of them disappeared ... I would say around 95% of them.
So I decided to learn everything needed to do it my self in the meantime. It has been a blessing because I've learned so much about how to set up a Linux server, web servers, server administration, JS, NodeJS, VueJS, NuxtJS, Vuetify, MongoDB, ...
But ... as everybody can see the version 2.0 is still not here.
All this study is very consequent. I'm doing my best to absorb all of that but it takes time. As most of the "let's-do-an-open-source-project-yeeeee" crowd has vanished, I'm all by myself.
I have received a few propositions to be helped but I decided to go all the way down on my own because it wouldn't do much difference. Blockchain and coding, here I go !
The project is no longer an open-source project. Even so, I'll do my best to be the more transparent possible on the way I will collect the data and provide ways of verifying it.
The current version is supported by communities APIs giving me the Tx/24h. The rest comes from CMC API and my mathematics.
It is a nightmare because all these APIs are failing from time to time, cease to exists, gives wrong numbers, ...
I'm consistently spending time on fixing bug derived from these problems.
In the 2.0 version, I will use stable and well-supported APIs to read each block directly from the chains and create my data from there. That will allow me to have more trusted data and also switch from one API to another when one is down.
I want to advance as quickly as possible on the new version so I won't be adding more chain for now to the current version.
Besides, it doesn't make sense to add chains to a list that will stop to exist as soon as I have around 5-10 blockchains added to the new incoming version.
I can't give any deadline because I learn as I code it. Every problem I encounter may take a few minutes or a few days. I hope everybody following this project can apply the same patience we have all grown with crypto markets to my endeavour.
I'll go back to my study/coding, cheers.
Twitter : https://twitter.com/Blocktivity1
Telegram : https://t.me/joinchat/BdGiiBJMeTNlrwnImdqbJQ
The Github Repo : https://github.com/blocktivity-info/blocktivity
!trdo
Congratulations @accountsdump, you are successfuly trended the post that shared by @blocktivity!
@blocktivity will receive 3.39170288 TRDO & @accountsdump will get 2.26113525 TRDO curation in 3 Days from Post Created Date!
"Call TRDO, Your Comment Worth Something!"
To view or trade TRDO go to steem-engine.com
Join TRDO Discord Channel or Join TRDO Web Site
Courage courage... 💪
Posted using Partiko Android
Merci ^^
Your current github repository link 404s. Do you have it set as Private? If so I would suggest making it public so others in the community could fork and contribute. Looking at the stack you described you may also want to leverage AWS & Lambda/Serverless in order to save on the overall monthly cost.
Btw EOS seems to have been dropped from your site. Is this due to a 3rd party api failure? Are you correctly using a proxy to get on-chain data? Something like https://eosnode.tools/proxy
Keep going! #gobitcoin #goeos #goblocktivity
Congratulations @blocktivity, your post successfully recieved 3.39170288 TRDO from below listed TRENDO callers:
To view or trade TRDO go to steem-engine.com
Join TRDO Discord Channel or Join TRDO Web Site
Congratulations @blocktivity! You received a personal award!
You can view your badges on your Steem Board and compare to others on the Steem Ranking
Vote for @Steemitboard as a witness to get one more award and increased upvotes!
Hello!
This post has been manually curated, resteemed
and gifted with some virtually delicious cake
from the @helpiecake curation team!
Much love to you from all of us at @helpie!
Keep up the great work!
Manually curated by @solominer.
@helpie is a Community Witness.