Author | SHA1 | Message | Date |
---|---|---|---|
Callum Waters |
6f6ac5c04e
|
state sync: reverse sync implementation (#6463) | 4 years ago |
Callum Waters |
a91680efee
|
test: create common functions for easily producing tm data structures (#6435) | 4 years ago |
Callum Waters |
5bafedff17
|
evidence: fix bug with hashes (#6375) | 4 years ago |
Marko |
70bb8cc8b7
|
proto: seperate native and proto types (#5994)
## Description Separate protobuf and domain types. We should avoid using protobuf in our core logic. ref #5460 |
4 years ago |
Marko |
6ab2a19088
|
header: check block protocol (#5340)
## Description Check block protocol version in header validate basic. I tried searching for where we check the P2P protocol version but was unable to find it. When we check compatibility with a node we check we both have the same block protocol and are on the same network, but we do not check if we are on the same P2P protocol. It makes sense if there is a handshake change because we would not be able to establish a secure connection, but a p2p protocol version bump may be because of a p2p message change, which would go unnoticed until that message is sent over the wire. Is this purposeful? Closes: #4790 |
4 years ago |
Callum Waters |
2b58a62721
|
light: implement light block (#5298) | 4 years ago |