How Validator Client works in Standard Mode

During the client's operation, it obtains the hash of the latest block from the BTC RPC service and verifies whether the hash is correct through simple checks, such as verifying if the previous block's header hash in the current block header is correct, and if the mining nonce and difficulty are correct.

It then determines, based on local records, whether it has already submitted the hash of the current block height. If it hasn't been submitted before, the client submits the block height and hash data. If it has already been submitted, the client waits to evaluate the next BTC block header.

For the same BTC block height, when the client believes that a fork has occurred (e.g., receiving two valid block headers for the same block height), it will submit both valid block header hashes to exSat to maximize the probability of receiving rewards.