Derek Pierre

That being said we use an older version of eth-ape - `eth-ape==0.6.27`. Is that issue possibly fixed in a newer version? We haven't updated to a newer version of `eth-ape`...

From @KPrasch : > Just to throw is out there, another way to enforce a limitation is by capping the number of bytes.

> One is providing a compound condition such that evaluation requires hammering of the provider. The other is providing a compound condition with strenuous CPU (or even RAM) overhead. >...

The contracts are now imported for `acceptance` tests

Lots of code improvements since then.

Updated link - https://github.com/nucypher/nucypher/pull/926/files/c613bcd0773cc9ea829b6b948f74755e94bf5769#diff-c20d5c9104edf072fb7ea92061c93b65b00103bbe323370bbabcb7990d71dc61R709. Either way, PRE-specific so closing.

Agree with @cygnusv here. The subsequent breaking changes to config files would be unnecessarily onerous given the existing widespread usage of `polygon`/`mumbai` by the broader ecosystem.

Related to #3372

Closed for threshold decryption via https://github.com/nucypher/nucypher/pull/3337.

Closed via #3307