Using latest devchain version

[soloseng]

Description

Using the latest version of devchain to run tests.

Tested

Tests are passing locally and in GH actions locally. Testing locally still requires running devchain and hardhat test in separate terminals using different node versions. See README for more details.

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@celo/celo-devchain@6.0.3	Transitive: environment, filesystem, network, shell, unsafe	+67	194 MB	soloseng
npm/fetch-blob@3.2.0	None	+2	9.09 MB	endless
npm/leveldown@6.1.0	Transitive: environment, filesystem	+11	6.07 MB	vweevers
npm/node-fetch@3.3.2	network	+5	9.24 MB	node-fetch-bot

🚮 Removed packages: npm/@celo/celo-devchain@5.0.0, npm/map-age-cleaner@0.1.3, npm/mem@4.3.0, npm/strip-eof@1.0.0

View full report↗︎

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note
Native code	npm/leveldown@6.1.0	Location: Package overview

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/leveldown@6.1.0

[openzeppelin-code[bot]]

Using latest devchain version

Generated at commit: 2e49cb55e85c193f80092a94cd750afdbda91f3a

🚨 Report Summary

	Severity Level	Results
Contracts	Critical High Medium Low Note Total	1 0 0 10 30 41
Dependencies	Critical High Medium Low Note Total	0 0 0 2 30 32

---

For more details view the full report in OpenZeppelin Code Inspector