Skip to content

refactor: Use shared immutables instead of both private and private immutables #4820

Description

@LHerskind

Some contracts are relying on immutables that are both in public and private and have solved their issues through having 2 immutables, one for private one for public.

Instead, we should simply be using the shared immutable to simplify the contracts and make it simpler to follow.

Activity

  1. self-assigned this
    on Feb 28, 2024
  2. converted this from a draft issue on Feb 28, 2024
  3. added a commit that references this issue on Feb 28, 2024
    821c25d
  4. moved this from Todo to Done in A3on Feb 28, 2024
  5. added a commit that references this issue on Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions