Transaction signing question

Hi ,
I was going through the docs .

https://docs.daml.com/canton/architecture/overview.html#transaction-processing-in-canton

In the uploaded image if we are assuming alice bob sr and bank are participant nodes and they are using besu dlt.

In he above diagram in transaction flow we can only see one sequencer .

Can anyone explain what is the role of all other sequencers.

Regards
Harikrishna

This transaction processing diagram is not a fully accurate representation of transaction processing on Canton Ethereum sync domain in the sense that it omits the level of detail specific to processing Ethereum transactions and how Canton transactions relate to Ethereum transactions. In the case of Canton Ethereum sync domain, Canton Sequencer is an Ethereum application configured with an Ethereum wallet and connected to a Besu node. To take advantage of Besu consensus mechanism one would need multiple Besu nodes, and therefore multiple Canton Sequencers. For example you can have a dedicated Sequencer for each Participant Node, which makes each Participant a separate Ethereum client. When a Canton transaction is submitted by a Participant Node to the Sequencer, the latter sends the Ethereum transaction to the Besu network. Once consensus is achieved on Besu, the state of Sequencer.sol contract is updated. All Sequencers subscribe to events emitted from Sequencer.sol contract and receive Canton transaction confirmation request, which they forward to their respective Participant Nodes. The latter decrypt the data, obtain Canton transaction views for each party defined on the Participant Node and validate Canton transaction. Then each Participant Node sends mediator response to its Sequencer, which submits an Ethereum transaction to Besu. Once consensus is achieved on Besu, Sequencer.sol state is updated and mediator response is picked up by Canton Mediator through the Sequencer that submitted Canton transaction. When Mediator receives all required responses, it sends the Canton transaction result to the Sequencer, which submits yet another Ethereum transaction that is picked up by all Sequencers and sent to their respective Participant Nodes that finally commit the Canton transaction to their respective PCSs. One can see from this description that each Canton transaction results in several Ethereum transactions.