You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
I've synced the code from the development repository to this repository.
I also manually validated the hash using the following command:
```sh
(
jq -c '.dependencies' package.json | sha256sum
find src test .gitmodules -type f -exec sha256sum {} \;
) | sha256sum
```
Result:
`bf428b0b456fd87dbbdc0c8715a817f71364cd4c86aed90b019c99cab1db19ed` (both
repos)
This ensures the integrity of the sync.
Note: `foundry.toml` is not included because it differs between the two
repositories. However, I have manually verified that the
compilation-related sections are the same.
## Detail
### Changeset
* Sync `src/`
* Update `foundry.toml`
* Update pr template per request from techops
### Checklist
- [x] Did you add new tests and confirm all tests pass? (`yarn test`)
- [x] Did you ensure any new Solidity source code files meet minimum
test coverage requirements? (`yarn coverage`)
- [ ] Did you update relevant docs? (docs are found in the `docs`
folder)
- [x] Do your commits follow the [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard?
- [x] Does your PR title also follow the [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard?
- [ ] If you have a breaking change, is it [correctly reflected in your
commit
message](https://www.conventionalcommits.org/en/v1.0.0/#examples)? (e.g.
`feat!: breaking change`)
- [x] Did you run lint (`yarn lint`) and fix any issues?
- [x] Did you run formatter (`yarn format:check`) and fix any issues
(`yarn format:write`)?
## Testing
* Sync `test/`
## Documentation
n/a
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,6 @@ Mandatory section.
12
12
-[ ] Did you update relevant docs? (docs are found in the `docs` folder)
13
13
-[ ] Do your commits follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard?
14
14
-[ ] Does your PR title also follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard?
15
-
-[ ] If you have a breaking change, is it [correctly reflected in your commit message](https://www.conventionalcommits.org/en/v1.0.0/#examples)? (e.g. `feat!: breaking change`)
16
15
-[ ] Did you run lint (`yarn lint`) and fix any issues?
17
16
-[ ] Did you run formatter (`yarn format:check`) and fix any issues (`yarn format:write`)?
MSCA that's in compliant with [EIP-6900](https://eips.ethereum.org/EIPS/eip-6900).
2
+
MSCA that's in compliant with [ERC-6900](https://eips.ethereum.org/EIPS/eip-6900).
3
3
4
4
## Disclaimer
5
5
Please be aware that all contracts within this package are still in active development and are not deployed on any mainnets yet, so proceed with caution if you intend to test them on your own.
6
6
7
-
## Signature Encoding
8
-
TODO.
7
+
## Features
8
+
1. Deploy an account using the account factory.
9
+
2. Receive **ERC-721, ERC-1155,** and **ERC-777** tokens.
10
+
3. Supports **ERC-1271** for contract signatures.
11
+
4. Enables **upgradeability** via the **ERC-1967 proxy**, allowing users to update their proxy’s implementation and choose different smart account versions. We follow the **ERC-7201 namespaced storage standard** to prevent storage collisions when switching implementations.
12
+
5.**Extensible through modules**, allowing additional functionality to be integrated into the account.
13
+
14
+
## Acknowledgements
15
+
The contracts in this repository follow the **ERC-6900 specification** and are largely inspired by the design of its reference implementation.
0 commit comments