docs.rs failed to build miden-node-persistence-0.17.4
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
miden-node-persistence-0.17.3
Miden node persistence
Shared protobuf codecs for structured SQLite values and node-owned binary files. Raw database keys, execution proofs, and cryptographic encodings retain their formats.
Native serialization remains at these boundaries:
- SQLite keys and indexed words use fixed-width bytes for joins and cursor ordering.
- The
proven_tipfile stores one four-byte little-endian block number. - Execution-proof files and proof fields retain the proof library encoding.
- Sealed transaction-input submissions use the existing RPC plaintext encoding.
- Keys, signatures, encrypted record keys, associated data and DKG files use their cryptographic library encodings.
- Upstream
AccountFilehandles account files. Its format is already protobuf.