# Conclusion

Blockchain protocol development is a broad field with different areas of specialization. This is the same as with traditional web 2.0 development. Even though web 2.0 development revolves around the client-server architecture model, there are various specialization opportunities: from front-end development to cloud computing, to database development, to understanding protocols and patterns like TCP, HTTP, REST, etc. Notwithstanding the diversity and broadness, having a grounded mental model that underpins web 2.0 development helps to make sense of how all the various components fit.

Presenting a similar mental model for blockchain protocol development is what I sought to achieve with this guide. I hope it helps the new engineer coming into this space to quickly form the necessary mental models, be aware of the various moving parts and how they come together. From here, such an engineer can then choose areas of specialization within Blockchain development to further explore.

In essence what we are building is a decentralized, distributed deterministic finite state machine. And to achieve this, we need nodes to connect with each other in a peer-to-peer fashion, well-defined protocols for nodes to follow since there is no co-ordinating central entity. These protocols involve choosing who will be next in line to mutate the state, that is the block production protocol, and deciding on the current state across nodes via the consensus protocols like fork-choice rule and finality protocols.

## About Me

I am Dade, a passionate blockchain developer with a strong interest in building robust and secure protocols. I'm the author of this guide to blockchain protocol development, aiming to empower others to navigate this exciting and rapidly evolving field.Beyond this guide, I actively contribute to the blockchain ecosystem through my programming endeavors. I'm proficient in Rust and have had the privilege of contributing to significant projects like the Lodestar beacon client and libp2p.

If you're interested in learning more about my experience and perspectives, feel free to check out my blog at <https://geekabyte.io/>. I'm always eager to connect with fellow enthusiasts and engage in discussions about the future of blockchain technology. Feel to also connect on Twitter: <https://twitter.com/dadepo>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://geekabyte.gitbook.io/blockchain-protocol-development-guide/conclusion.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.