Xun Li

Properly verify a fragment

1

This [TODO](https://github.com/MystenLabs/sui/blob/4ff357324a9f4e7998fa1155d69d1544f98f2734/crates/sui-types/src/messages_checkpoint.rs#L634): Fragments could be sent from byzantine nodes. We need to verify that: 1. Every transaction certificate is valid 2. the certs includes all missing certs on either side

Design and Implement Tally Protocol

2

1. Validators are able to observe how each other validator is doing during the epoch (i.e. how much work they put in to validating and executing transactions) 2. Near the...

The tally rule works as follows: 1. For every digest we received from gossip, we assign a unique (incrementing) sequence number, and add the digest and validator name along with...

Not display all consensus::tusk logs to the screen when running sui

3

Right now, when we launch sui, it will start to display all consensus::tusk logs even when there is no activity, and it's a lot. This makes it impossible to identify...

In the current implementation, a validator would send a new fragments for sequencing, wait for a fixed amount of time, and wake up again to see if we can now...

Investigate validator memory increase

4

Relevant discussions: https://mysten-labs.slack.com/archives/C02GD7J9HUM/p1656435768898279 https://mysten-labs.slack.com/archives/C03GKUEA5PF/p1656639974689169

This PR fixes a few issues in the reconfiguration end-to-end test and add the flow of adding a new validator: 1. Increases the validator name limit. We were hitting that...

Often see this locally: ``` failures: cli_tests::test_merge_coin test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 14 filtered out; finished in 14.24s --- STDERR: sui cli_tests::test_merge_coin --- Error:...