[MariusVanDerWijden]

Turns

    "blobSchedule": {
      "cancun": {
        "target": 3,
        "max": 6,
        "baseFeeUpdateFraction": 3338477
      },
      "prague": {
        "target": 6,
        "max": 9,
        "baseFeeUpdateFraction": 5007716
      },
      "osaka": {
        "target": 6,
        "max": 9,
        "baseFeeUpdateFraction": 5007716
      },
      "bpo1": {
        "target": 10,
        "max": 15,
        "baseFeeUpdateFraction": 8346193
      },
      "amsterdam": {
        "target": 10,
        "max": 15,
        "baseFeeUpdateFraction": 8346193
      }
    },
    "osakaTime": 0,
    "bpo1Time": 0,
    "amsterdamTime": 1779434285

into

    "blobSchedule": {
      "cancun": {
        "target": 3,
        "max": 6,
        "baseFeeUpdateFraction": 3338477
      },
      "prague": {
        "target": 6,
        "max": 9,
        "baseFeeUpdateFraction": 5007716
      },
      "bpo1": {
        "target": 10,
        "max": 15,
        "baseFeeUpdateFraction": 8346193
      },
    },
    "osakaTime": 0,
    "bpo1Time": 0,
    "amsterdamTime": 1779434285
    ```

[lightclient]

Change generally looks good, but is there a spec somewhere for this? Currently 7892 and 7840 don't define this behavior. Just want to cross reference with that to verify it is correct.

[MariusVanDerWijden]

@lightclient nope, there was a discussion about it on discord, but I don't think we have a formal spec.
@barnabasbusa might know

[rjl493456442]

It's strange, json will automatically filter the unknown fields.

And what's more, this function just print some warning logs and doesn't remove the unknown fields explicitly. I feel the entire customization is unneeded.

[MariusVanDerWijden]

You're right, removed it