# LibraBFT ![Libra logo](https://3162634398-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LLG7gr0ydPNrSJQ43vf%2F-Lhkh-bVHQLxZ8vjmapz%2F-LhkhmcpOZSzBWAalBCK%2Flibra-BFT.png?alt=media\&token=813ed13f-75ba-493e-94d5-0444c214f9c2) ### Algorithm > Validators take turns driving the process of accepting transactions. When a validator acts as a leader, it proposes transactions, both those directly submitted to it by clients and those indirectly submitted through other validators, to the other validators. All validators execute the transactions and form an authenticated data structure that contains the new ledger history. The validators vote on the authenticator for this data structure as part of the consensus protocol ... > As part of committing a transaction Ti at version i, the consensus protocol outputs a signature on the full state of the database at version i — including its entire history — to authenticate responses to queries from clients." ... "The Libra protocol uses an account-based data model to encode the ledger state. ... > "Executing a transaction T i produces a new ledger state S i as well as the execution status code, gas usage, and event list. ### Pros * Because of the signature on the full state of the database, in every transactions, new validators should be able to join the network and sync quickly without having to replay the entire history of the blockchain, assuming that they trust the existing validators. * pseudonimity: \ "The Libra protocol does not link accounts to a real-world identity. A user is free to create multiple accounts by generating multiple key-pairs. Accounts controlled by the same user have no inherent link to each other. This scheme follows the example of Bitcoin and Ethereum in that it provides pseudonymity for users." ### Cons * You have to trust validators. * POS have to show that is still working when transitioning to permission-less network ### Used In * LibraBFT which is a variant of the HotStuff consensus protocol. ### Whitepaper * * ### Read More * --- # 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://tokens-economy.gitbook.io/consensus/chain-based-pbft-and-bft-based-proof-of-stake/librabft.md?ask= ``` 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.