You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the Transaction Pool topic https://besu.hyperledger.org/public-networks/concepts/transactions/pool needs a section on the "Sequenced" transaction pool. I've put together a summary of the changes I think are needed, and some initial text suggestions to describe the behaviour of the pool
I think this needs 2 sections. One for layered and one for sequenced, ideally with an initial intro paragraph that explains that there are 2 types of transaction pool available, and that the layered pool is the recommended pool for public chains and the sequenced pool is the recommended pool for private chains.
For the description of the sequenced pool I've put some initial suggested text below
Sequenced transaction pool
The sequenced transaction pool is recommended for private blockchains. To select the sequenced transaction pool set the --tx-pool=sequenced configuration option. If the enterprise configuration profile has been chosen using --profile=enterprise the sequenced transaction pool will be used by default.
The sequenced transaction pool is designed to be more suitable to enterprise environments. Its design is oriented around behaviouring like a first-in-first-out (FIFO) queue of transactions and therefore has the following characteristics:
Transactions are selected in the order they are submitted regardless of which sender submitted the transaction
When the transaction pool is full newer transactions are evicted first. This reduces the chance of a nonce gap being introduced and requiring an application to resubmit an old transaction.
The text was updated successfully, but these errors were encountered:
I think this documentation topic is needed in order for candidates of the upcoming Besu certification to be able to answer some of the questions. Is it possible for it to be looked at in the near future?
I think the Transaction Pool topic https://besu.hyperledger.org/public-networks/concepts/transactions/pool needs a section on the "Sequenced" transaction pool. I've put together a summary of the changes I think are needed, and some initial text suggestions to describe the behaviour of the pool
https://besu.hyperledger.org/public-networks/reference/cli/options#tx-pool
https://besu.hyperledger.org/public-networks/concepts/transactions/pool
Sequenced transaction pool
The sequenced transaction pool is recommended for private blockchains. To select the sequenced transaction pool set the
--tx-pool=sequenced
configuration option. If the enterprise configuration profile has been chosen using--profile=enterprise
the sequenced transaction pool will be used by default.The sequenced transaction pool is designed to be more suitable to enterprise environments. Its design is oriented around behaviouring like a first-in-first-out (FIFO) queue of transactions and therefore has the following characteristics:
The text was updated successfully, but these errors were encountered: