Skip to content

Move away from using Vec<u8> to represent raw content key/value #1404

Open
@morph-dev

Description

Instead of using Vec<u8> to represent raw content keys/values, we should use something like alloy_primitives::Bytes because:

  • copy is faster
  • (de)serializes into hex string correctly

We should either wrap or name the type, to avoid potential confusion (e.g. see RawContentValue).

Other places that should be updated:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions