Skip to content

jam-types 0.1.8 ordering bug #30

Open
@gilescope

Description

@gilescope

In jam types 0.1.8, it's defined in this order:

#[derive(Copy, Clone, Encode, Decode, Debug, Eq, PartialEq)]
pub struct OpaqueValKeyset {
	/// The opaque Ed25519 public key.
	pub ed25519: OpaqueEd25519Public,
	/// The opaque Bandersnatch public key.
	pub bandersnatch: OpaqueBandersnatchPublic,
	/// The opaque BLS public key.
	pub bls: OpaqueBlsPublic,
	/// The opaque metadata.
	pub metadata: OpaqueValidatorMetadata,
}

but in

"bandersnatch": "0x5e465beb01dbafe160ce8216047f2155dd0569f058afd52dcea601025a8d161d",
and in the scale the bandersnatch comes first. The gray paper clearly states bandersnatch is first (6.9) so this seems a bug in jam types.

I would raise it there, but there seems no public repo associated with https://crates.io/crates/jam-types ? I raise it here as this is where people will notice the inconsistency.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions