# Summary

Our proposed FHPoS consensus protocol is a combination of modern, asynchronous, and efficient Byzantine fault-tolerant consensus protocol, as well as a useful and reusable new mechanism for FOGR computing, which can stably provide proof and replace license identity. The resulting protocol meets the design requirements of license free, decentralized, Byzantine fault-tolerant and very high-speed review proof transaction mechanism.

On this basis, we can say that FOGR network is a blockchain network ecosystem for the future digital economy, which activates and enables redundant equipment computing power, and is committed to establishing a systematic and integrated digital economic ecosystem integrated with the existing blockchain ecosystem. It provides a complete underlying technical infrastructure for the effective collaboration of trust sources, the interconnection of data sources, and various distributed application services.

**Reference documents:**

\[1] Liskov, Practical use of Clocks

<http://www.dainf.cefetpr.br/> tacla/SDII/PracticalUseOfClocks.pdf

\[2] Google Spanner TrueTime consistency

\[3] Anatoly Yakovenko

<https://solana.com/solana-whitepaper.pdf>

\[4] Filecoin, proof of replication,

<https://filecoin.io/proof-of-replication.pdf>

\[5] BitShares Delegated Proof of Stake

<https://github.com/BitShares/bitshares/wiki/Delegated-Proof-of-Stake>

\[6]Arbitrum Developer Quickstart

<https://developer.offchainlabs.com/docs/developer\\>\_ quickstart


---

# 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://fogcomputingchain.gitbook.io/fog-computing-chain/summary.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.