chore: add SPDX copyright attribution and a NOTICE file - #317
Merged
Merged
Conversation
Contributor
CI Summary
|
GHkrishna
approved these changes
Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Aligns the repository with the legal guidelines for open source attribution.
SPDX-FileCopyrightText: © 2026 Parity Technologies. A contract file travels alone through explorers and vendoring, and carried a license identifier with no copyright holder to preserve;SPDX-FileCopyrightTextis the REUSE-standard field for this, so coverage stays machine-checkable.contracts/external/(authoritative SPDX headers) andcontracts/utils/Multicall3.sol(mds1/multicall3, MIT) carry no Parity line.NOTICEfile records the project copyright, the MIT license pointer, and the third-party attributions; the README's license section now points at it.Comment-only for the contracts: bytecode, ABIs, and storage layouts are unchanged.
Type
Scope
Related Issues
Fixes
Checklist
Code
forge buildpassesforge testpassesTesting
Security
selfdestructordelegatecallDocumentation
Breaking Changes
Breaking changes:
How to test
Prints only
contracts/utils/Multicall3.sol, the vendored file that keeps its original authors' notice.Notes
The added lines change each file's compiler metadata hash and nothing else. Release tooling strips metadata before comparing codehashes, so codehashes.json and the deployed-bytecode checks are unaffected.