Skip to content

Consistency on content naming #632

@LHerskind

Description

@LHerskind

The messages between L1 and L2 have one field element of content. For longer messages this is often computed using sha256ToField which have lead to it being inconsistent whether content or content_hash as name.

For consistency, would be better for us to use content, and in the cases where we hash "something" lets denote that something content_preimage.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions