Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(world): add CallWithSignatureSystem #3496

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

Conversation

alvrs
Copy link
Member

@alvrs alvrs commented Jan 23, 2025

closes #3437

Copy link

changeset-bot bot commented Jan 23, 2025

⚠️ No Changeset found

Latest commit: 448a8c7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@@ -0,0 +1,174 @@
// SPDX-License-Identifier: MIT
// OpenZeppelin Contracts (last updated v5.0.0) (utils/cryptography/ECDSA.sol)
Copy link
Member

@holic holic Jan 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did we decide it was better to copy/paste these here instead of importing from OZ as a dep?

if we keep this here, maybe should put these in a vendor or similar directory to better isolate unchanged and already audited copy/pasted source files?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the original reason was that the OZ package was a pretty heavy dependency and we only needed very few files from it. At this point we do have a couple vendored OZ files in the world package (ERC165Checker, IERC1967, Proxy, StorageSlot) but I don't think it's worth changing our approach now. MUD is audited as a whole and the auditors can easily check that the files match the original sources. Changing paths of a Solidity package is always annoying because it would break things downstream if the files are imported since there are no explicit exports/remappings.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hope no one has imported these directly 🙈 wonder if we should start putting not-for-external-use source files into internal dirs, like we've started doing for TS exports

@holic holic added the blocked by audit This is blocked by code that is currently being audited label Jan 23, 2025
@vercel vercel bot temporarily deployed to Preview – explorer January 23, 2025 15:42 Inactive
@holic holic added needs audit This code needs to be audited and removed blocked by audit This is blocked by code that is currently being audited labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs audit This code needs to be audited
Projects
None yet
Development

Successfully merging this pull request may close these issues.

audit CallWithSignature module
2 participants