Ask me Anything (AMA) session with Gerald from Blocktorch.

The Dapp List | Blocktorch (AMA summary)

PowerdByBuidl 🧱

To keep our community educated & aware of the early-stage projects that we are launching from the buidl Launchpad, we are doing AMAs with each of these projects. During these sessions, Anyone from the community is welcome to attend these meetings and express any questions they have regarding the project. The project's founder or a team member speaking on their behalf will provide an honest response.

AMA Overview

We did two segments in this last AMA with Gerald from the blocktorch team.

  • In the first segment, We covered an introduction to Blocktorch, their mission and vision, future plans, obstacles they have faced so far, and most importantly, why Blocktorch is vital for the Web3.
  • In the second segment, We have taken community questions concerning Blocktorch. The Blocktorch team member then provided the answers to them.

If you missed the AMA, don't worry! All of the chats from it are included below.

AMA recap:

Segment 1 - [Introduction to Blocktorch]

1st question to Gerald

Can you please tell us little about your background and what was your way into web3?

Gerald’s Answer

I originally have a business background, having studied at one of the worlds most reputable business schools, London Business School, and then worked in business development at a FAANG company and in venture capital supporting early stage software teams to scale. But with the start of the pandemic i fell in love with coding and did all kind of computer science tutorials, so I became a self taught hobbiest developer and absolutely love writing code 🧑‍💻

My first touchpoints with crypto were back in 2017 when the ICO hype started to kick in and I still have some of the coins (which are gladly in the money even during this winter)

end of 2020 a friend told me about pancakeswap and I quickly fell into the rabbit hole of yield farming on binance as a user. But a couple rug pulls later I started to learn solidity to understand smart contracts. That's when I started to learn more about web3 development and tried myself in building e.g. flashloan arbitrage bots (but always just burned gas without making return haha 😅

2nd question to Gerald

Can you please brief us about blocktorch’s vision and mission?

Gerald’s Answer

At blocktorch we strongly believe that web3 engineers need more mature tooling to ensure decentralized applications are mass market ready. One core pillar for mass market readiness is best in class reliability

For reliability the latest technology framework is observability and observability levelled up the scale of cloud computing by a magnitude

At blocktorch we are building an observability platform for the decentralized stack to ensure web3 buidl teams have all the relevant metrics, logs and traces to deeply understand the behaviour of their decentralized services

There is a software reliability engineering principle called "Hope is not a strategy", our goal is that instead of hope engineers can take data driven decisions and buidl rock solid dApps users love at scale

3rd question to Gerald

Can you please throw some light on blocktorch's roadmap?

Gerald’s Answer

we are currently live with a closed alpha version of the product and are moving with rapid speed towards the release of a public version

this first version let users have an overview of the state of their EVM  smart contracts, set custom service level objectives on their smart contracts (a way of measuring a service's behaviour) and do root cause analysis with a log manager. So basically we provide the 3 pillars of observability - logs, metrics and traces - for smart contracts in EVM chains the next steps are integrating more chains (Solana, Near, Polkadot, etc) and improving the traces from pure transaction stack traces to distributed traces (we'll publish an article about that these days so if you are curious about distributed tracing keep an eye out for that) the next phase is to go beyond smart contracts into the wider decentralized stack providing observability for decentralized data feeds (oracles), decentralized file storages, decentralized off-chain data storage, decentralized hosting, etc

from there we go to the moon 🌝

4th question to Gerald

Can you please tell us Why is observability in web3 relevant?

Gerald’s Answer

When building complex software understanding all the details of what is going on is inherently difficult when done manually. Today most teams are solely relying on manual processes in blockexplorers or use valuable ressources to build their own observability capabilities inhouse with the help of indexers (e.g. TheGraph). manual processes and inhouse built tools cannot scale efficiently as the product scales and increases in complexity Let's imagine a decentralized application with the amount of users that Robinhood or TikTok have today. When users start to report problems in discord servers and engineers start to scroll through block explorer transactions to understand what is going on web3 is doomed. So as an ecosystem to mature and grow we need observability tooling that automates processes and makes engineering more efficient And maybe a more current example is to think about a DeFi protocol integrating several other protocols, with some complex math happening in the back. To follow through all transactions and ensuring everything works correctly is hard, and a lot of user money is at stake so things better work perfectly

5th question to Gerald

Can you please tell our community Who is your target user/audience?

Gerald’s Answer

Teams building decentralized applications, and within these teams especially engineers as well as product managers They can be at any stage of their building process, it's good practice to start thinking about observability early own, as retrofitting observability practices is always harder than thinking about it from the beginning. However with blocktorch teams can get going also when they have dozens of smart contracts in production

Segment 2 - [Community questions]

1st question

How capable is blocktorch in solving observability issues in web3?

Gerald’s Answer

We as a team have strong observability in web2 as well as developer experience in web3. It's important to understand what observability is to build a suitable tool for web3 and we are 💯 % suited to build it and that is feedback we get from investors and potential users

2nd question

Many projects have problems with UI / UX and this one turns off new users. How do you plan to improve the interaction with new users and with users outside the crypto space?

Gerald’s Answer

developer experience is super important for us so we put a lot of focus on it, and if you check our product you can give us feedback on it, would appreciate it

3rd question

What are the benefits of using blocktorch for the development teams?

Gerald’s Answer

You'll always stay on top of what is your smart contract behaviour and get relevant data for detected anomalies in a fraction of the time spent today

4th question

How is blocktorch different from the existing solutions?

Gerald’s Answer

Other solutions are not focused on the 3 pillars of observability - logs metrics and traces. they offer just some minor monitoring solutions on the side

5th question

Is there any difference in maintaining observability in Web3 as compared to that in Web2?

Gerald’s Answeryes, the used infrastructure is different in cloud basically the application is running on your infrastructure (or the infra you "buy" from cloud providers), but in web3 the blockchain is not yours it is a decentralized network of distributed nodes

Bottom Line

If you have more doubts or questions about Blocktorch, Feel free to ask them on our Discord server and enjoy your journey with 'The Dapp List'.🥂

Join us today!!

https://discord.io/thedapplist

Note - Aside from our "AMA" sessions, we have more events where you will get a chance to interact with the team members of various fabulous projects growing in the Web3 world.