We launched a validator on the Celo baklava testnet and asked ourselves how its uptime score would develop. Learn about the mathematical approximation we found.
Paying for Anyblock blockchain services must be easy and efficient. Credit cards support recurring payments. We’re keeping our free plan. You can try and make sure we’re a good fit for your project.
Distributed ledgers with the potential to cater to the demands of any industry have given rise to public and private blockchains. In this article, we will be exploring both of them in detail.
In this video from our Youtube channel, you will learn how to set up a dedicated blockchain search with a shortcut in your Chrome browser.
In this article, we focus on the connectivity to the Bitcoin and Ethereum blockchain networks with RPCs and establish how you can outsource the node management to a third-party to reduce your workload.
A Remote Procedure Call (RPC) happens to be the most straightforward form of an API which allows developers to communicate to a server in order to remotely execute code.
Setting up a Validator in the Celo baklava testnet with faucet funds – optimized sequence from Anyblock experience
In the following article we would like to share with you our experience from setting up a Validator in the baklava testnet during the Celo Foundation Voting Program for Cohort 6.
TheGraph’s curation program has allowed us to learn about TheGraph ecosystem, how Subgraphs work, and evaluate which subgraphs are high quality and useful to users. It was also extremely insightful to learn how subgraphs are developed, deployed, and used. We at Anyblock have developed a dashboard that leverages the subgraph from TheGraph Testnet to visualize meaningful and important metrics for curators, indexers, and other interested users.
We decided to leave the old database server at sql.anyblock.tools:45432. The new cluster can be reached at sql.anyblock.net:5432 – which is indeed A LOT faster!
If you’re only using our API, Alerting or Dashboards and do not use the SQL Server, there is nothing to do and things will keep working as expected.
The data will still be updated on both SQL servers and your existing credentials will be migrated, so except from changing the host and port, there is no immediate action required for your SQL Mainnet production use cases. Everyone else should start migrating their scripts as soon as possible.