1) Commit didn't include the round, leaving the clock in question.
2) Machines started with a local time, instead of a proper start time.
3) Machines immediately started the next block instead of waiting for
the block time.
For a hash, which is fixed-size, these should be the same yet this helps
move past the dependency on SCALE. It also, for any type where the two
values are different, smooths integration.
Ideally, this would be generic. Unfortunately, the generic API serde
doesn't natively support borsh, nor SCALE, and while there is a serde
SCALE crate, it's old. While it may be complete, it's not worth working
with.
While we could still grab bincode, and a variety of other formats, it
wasn't worth it to go custom and for Serai, we'll be using SCALE almost
everywhere anyways.
Unbeknowst to me, height doesn't have a universal definition of the
chain length.
Bitcoin defines height as the block number, with getblockcount existing
for the chain length.
Ethereum uses the unambiguous term "block number".
Monero defines height as both the block number and the chain length.
Instead of arguing about who's right, it's agreed it referring to both
isn't productive. While we could provide our own definition, taking a
side, moving to the unambiguous block number prevents future hiccups.
height is now only a term in the Monero code, where it takes its
Monero-specific definition, as documented in the processor.
Ensures random functions never return zero. This, combined with a check
commitments aren't 0, causes no serialized elements to be 0.
Also directly reads their vectors.
* add file
* builds + caching fixed
* bitcoin orchestration
* remove default entrypoint
* eth image and cleanup
* working monero
* remove signature file
* cleanup on aisle eth
* cleanup on aisle btc
* eth working
* remove docker ignore
* remove bitcoin image readme
* fix serai builds
* serai clusters
* added readme for docker
* formatting
* share the image
* newlines at EOF
* add multi profile example
* coin order
* coin order
* profile order
* fix grammar
* fix whitespace
* reduce trusted signature set, require at least 3 signatures.
* remove echo
* update comment to ref trusted keys
* comment fix
* use 16 keys, check for laanwj, name compose
* don't use bash
* monero fingerprints & eth fixes
* eth fixes
* remove extra eth keys
* kubernetes deployment implemented with helm charts
* deleted helmignores & added new lines at the end of the file
* deleted duplications & delete unnecessary comments & deactivated service accounts
* deleted generators files
* added a new line to monero/values.yaml
* deleted support for old kubernetes version - ingress.yaml
* added new like to serai/values.yaml
* serai's port name changed
* serai's port name changed
* release name limit was changed to 253
* README.md updated
* fixed Makefile
* deleted platform dependant instructions
* deleted appVersion from .yamls
* added -i parameter for deleting process
* added \ for Makefile
Co-authored-by: TheArchitect108 <75815740+TheArchitect108@users.noreply.github.com>
Co-authored-by: TheArchitect <TheArchitect108@protonmail.com>
* Update to the latest Serai Substrate
* Add Protobuf to build dependencies
Docker shouldn't need updating as this should've been added to the image
in
2dbace5b01.
* Get substrate to build
* Correct protoc build step
* Remove the benchmarking code
There's some macro resolution error that isn't apparent. I worked on it
for about half an hour but...
* Remove unnecessary clone
* Correct runtime-benchmarks flag usage
