Files
serai/substrate/runtime
Luke Parker f9e3d1b142 Expand validator sets API with the rest of the events and some getters
We could've added a storage API, and fetched fields that way, except we want
the storage to be opaque. That meant we needed to add the RPC routes to the
node, which also simplifies other people writing RPC code and fetching these
fields. Then the node could've used the storage API, except a lot of the
storage in validator-sets is marked opaque and to only be read via functions,
so extending the runtime made the most sense.
2025-11-14 03:37:06 -05:00
..
2025-11-13 00:17:19 -05:00
2025-08-25 10:06:35 -04:00
2025-09-02 02:17:10 -04:00

Serai Runtime

The on-chain rules for the Serai blockchain.

Compilation

If compilation fails due to borsh, this is likely due to attempting to compile to WASM binary (no-std) while borsh believes it's being compiled in a std context. Serai uses a patched substrate-wasm-builder which clears the CARGO_FEATURE_STD environment variable to prevent this, yet target/ directories may be contaminated if a build ever occurs without the patched substrate-wasm-builder. Please attempt a clean build to resolve the error.