3 commits

Author	SHA1	Message	Date
Luke Parker	cc491ee1e1	Don't return from sync_block until the Tendermint machine returns if it's valid or not ... We had a race condition where'd we be informed of blocks 1 .. 3, and immediately add 1 .. 3. Because we immediately tried to add 2 after 1, it'd fail since the tip was still the genesis, yet 2 needs the tip to be 1. Adding a channel, while ugly, was the simplest way to accomplish this. Also has any added block be broadcasted. Else there's a race condition where a node which syncs up to the most recent block does so, yet fails to add the next block when it's committed to.	2023-04-24 02:46:13 -04:00
Luke Parker	5858b6c03e	Replace Tendermint step with sync_block ... Step moved a step forward after an externally synced/added block. This created a race condition to add the block between the sync process and the Tendermint machine. Now that the block routes through Tendermint, there is no such race condition.	2023-04-13 18:18:29 -04:00
Luke Parker	09f8ac37c4	Create a folder for tributary, the micro-blockchain ... Moves tendermint again, this time under tributary.	2023-04-11 10:18:31 -04:00

Renamed from coordinator/tendermint/tests/ext.rs (Browse further)