chore: deploy HyperliquidDepositHandler after audit of Jan 19

[grasphoper]

Also fixes HyperliquidDepositHandler's deployment script

Closes ACP-53

[linear]

ACP-53 Redeploy `HyperliquidDepositHandler` post Jan 19 audit

[tbwebb22]

looks like owner and signer are both currently the dev wallet - is this what we want?

[grasphoper]

@tbwebb22 yea that's fine for now. Once backend team is done with testing with these contracts, we can change signer to prod backend EOA first, then transfer ownership to a multisig; that's the plan

[grasphoper]

@tbwebb22 yea that's fine for now. Once backend team is done with testing with these contracts, we can change signer to prod backend EOA first, then transfer ownership to a multisig; that's the plan

When they do it and we change the singer / owner we can merge this, but for now can just stay as a PR

[tbwebb22]

could we just pass in the token array directly rather than having to encode it first? just make that arg a string[]?

eg
forge script ... --sig "run(string[])" '["usdt0","usdc","usdh"]'

[grasphoper]

Addressed efbf97d

[grasphoper]

Good call!

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​matterlabs/​zksync-contracts@​0.2.4
	zksync-web3@​0.14.3
	@​pinata/​sdk@​2.1.0
	eslint@​7.32.0
	@​scroll-tech/​contracts@​0.1.0
	@​openzeppelin/​foundry-upgrades@​0.4.0
	@​uma/​common@​2.37.3
	eslint-config-prettier@​8.4.0
	@​across-protocol/​constants@​3.1.100
	@​uma/​contracts-node@​0.4.17
	@​types/​yargs@​17.0.33
	eslint-plugin-node@​11.1.0
	@​types/​chai@​4.3.20
	@​types/​mocha@​9.1.1
	@​coral-xyz/​anchor@​0.31.1
	prettier-plugin-rust@​0.1.9
	ts-mocha@​10.1.0
	buffer-layout@​1.2.2
	@​ethersproject/​abstract-provider@​5.7.0
	@​ethersproject/​bignumber@​5.7.0
	@​ethersproject/​abstract-signer@​5.7.0
	husky@​4.3.8
	codama@​1.3.0
	@​solana/​spl-token@​0.4.14
	@​types/​node@​24.3.0
	eslint-plugin-promise@​5.2.0
	@​eth-optimism/​contracts@​0.5.40
	ts-node@​10.6.0
	@​solana-program/​address-lookup-table@​0.10.0
	@​solana/​web3.js@​1.98.2
	eslint-plugin-import@​2.25.4
	ethers@​5.7.2
See 22 more rows in the dashboard

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		Critical CVE: npm form-data uses unsafe random function in form-data for choosing boundary CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 2.5.4 From: ? → npm/form-data@2.5.1 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/form-data@2.5.1. 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