> For the complete documentation index, see [llms.txt](https://block-convey.gitbook.io/block-convey/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://block-convey.gitbook.io/block-convey/summary-and-suggestion.md). # Summary and Suggestion We have discussed the BlockConvey Blockchain Protocol, which satisfies the conditions of permissioned private blockchains, utility, and Proof of Authority consensus. The result is that BlockConvey is able to provide better solutions to individuals and businesses alike. The transactions in the blockchain are secure to the bounds that it is a private chain. While we have confidence that the protocol is secure as long as the Authority nodes perform their function, we have taken together with the qualities that allow our network to function as a hast and low-cost global blockchain with well- understood security and reliability properties. We believe BlockConvey represents a significant step forward for distributed blockchain systems. The low cost and latency allow for many types of applications previously made difficult or even impossible with other, higher latency consensus methods. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://block-convey.gitbook.io/block-convey/summary-and-suggestion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.