chore: patch chainsafe/discv5

[mralj]

Removed dependency on bigint-buffer by patching discv5.
Repo link

The applied changes are inspired by this PR, but the changeset is much smaller -- I have only removed the dependency on bigint-buffer and made it work, because previous attempts made code flaky.

This has been done to remove vulnerable transitive dependency (link)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​nethermindeth/​enr@​3.0.0-backport-306-v4
	npm/​@​nethermindeth/​discv5@​9.0.0-backport-306-v4

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		npm/bcrypto@5.5.2 has Native code. Location: Package overview From: ? → npm/@nethermindeth/discv5@9.0.0-backport-306-v4 → npm/bcrypto@5.5.2 ℹ Read more on: This package | This alert | Why is native code a concern? Next steps: 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@socket.dev. Suggestion: Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/bcrypto@5.5.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[mralj]

@PhilWindle ci.grind passes (5 different runs) leaving it in the merge q