I have tested the demonstration of the subject according to the documentation. Two questions in my mind.
(1) I notice that there is no EOA (enduser owned account) for the sequencer. By inspecting the network I only see the four ethereum addresses for the four nodes. When update is made on the ledger, what account does the sequencer use? I assume we need the private key to sign the transaction when updating the ledger in Besu.
(2) In real life we may be given a running Besu network and an EOA for the sequencer. It is not difficult to deploy the bytecode of sequencer on a runnning network. Where can I specify the EOA (i.e. private key and account) used by sequencer? Just a quick comparison, in Fabric we need to specify the credential of Admin for the sequencer. Just look for something similar in the Ethereum/Besu setup.
Many thanks in advance.