chore: derive serialize and deserialize for chain info

[ArniStarkware]

Pull Request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build-related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Issue Number: N/A

What is the new behavior?

• Derive Serialize/Deserialize towards Papyrus config on these structs.

Does this introduce a breaking change?

• Yes
• No

Other information

---

This change is 

[ArniStarkware]

• chore: use chain info in stateful validator config #99
• chore: impl serialize config for chain info #98
• chore: derive serialize and deserialize for chain info #97 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ArniStarkware and the rest of your teammates on Graphite

[MohammadNassar1]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @ArniStarkware and @dafnamatsry)

---

crates/blockifier/src/context.rs line 72 at r1 (raw file):

}

#[derive(Clone, Debug, Deserialize, PartialEq, Serialize)]

Why it's needed?

Code quote:

 PartialEq,

[ArniStarkware]

Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @dafnamatsry)

---

crates/blockifier/src/context.rs line 72 at r1 (raw file):

Previously, MohammadNassar1 (mohammad-starkware) wrote…

Why it's needed?

The struct StatefulTransactionValidatorConfig in the blockifier will use this struct in #99.
It is used for testing. This derive is not heavy, so there is no need to limit it for testing only.

[ArniStarkware]

Merge activity

• Jul 31, 4:24 AM EDT: @ArniStarkware started a stack merge that includes this pull request via Graphite.
• Jul 31, 4:25 AM EDT: @ArniStarkware merged this pull request with Graphite.