christn

> > # Implementing (4) > > I have already sketched out a [high-level API here](https://notes.ethereum.org/Owy6Hb_oRfe7lUZaLeZWqA#block-validation) to handle block validation. This sketch suggests one route: just extend `reth` with this...

Seems to be fixed (according to manual tests on commit 8fd5930c74d352bb8e8c7dffc3e7fd7839ecb535 )

Could this be reopened maybe ? It seems that the original question better formulated as: _"How to do a point in time recovery for a database deployed with the bitnami/postgresql...

For me the easiest workaround was just to define a "fake" function that accepts any arguments via qplot

> Before making a detailed review of this PR, I've got a few questions to answer: > > 1. How do you envision this contract to fit into our existing...

> > Before making a detailed review of this PR, I've got a few questions to answer: > > > > 1. How do you envision this contract to fit...

> just to confirm - it looks like we'd need to deploy an extension contract per FIXED product that i.e. FIXED-DAI and FIXED-USDC will each need their own extension contract...

> ### Testing > * Overall consistent and I like what @FlattestWhite has suggested. When we read the output from a test it should make sense without **much** context. >...

As discussed in discord I'll be working on this.

Note that https://github.com/SetProtocol/set-protocol-v2/pull/256 will remove these temporarily added contracts and should thereby fix these issues.