V2 (#4)

* Change authroizers for registrars

* Add covergae

* Bump to solidity v0.8.26

* Fix typo

* Remove wallet connect

* Fix package json and scripts

* Remove namehash for EnsRegistrar

* Remove NameHash

* Fix Test

* 100% coverage

* Fix readme tests

* Add more documentation

* Replace NOTE for Note

* Add Pausable

* Emit RegistrySet event

* Improve documentation

* Improve documentation

* Fix referring to an interface in the documentation

* Change Registry for SciRegistry

* Fix layout order of contracts

* Fix lint

* Add old owner and old verifier to set events

* Add lint script

* Add documentation on PLV and SCI contracts

* Update CONTRIBUTING

* Delete old deployments folders

* Delete non upgreadable deployment scripts

* Add ignition for non upgreadable deployments

* Make verifier returns time instead of bool

* Move registry module

* Add ingition for SCI upgredability

* Fix dependencies

* Upgreade to solidity 28

* Update gitignore

* Publish v0.0.8

* Fix solhint

* Deploy to sepolia

* Improve npm package

* Remove unused error

* Change to pnpm

* Add prettier

* Remove yarn

* Upgrade packages

* Fix verify addresses script

* Improve deployments and testing

* Add new Whitepaper.pdf

* Fix workflow and force pnpm and node versions

* Fix pnpm version

* Fix pnpm install in test workflow

.github/workflows/tests.yml

@@ -15,14 +15,18 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
+      - uses: pnpm/action-setup@v4
+        with:
+            version: 9
+
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'pnpm'
           node-version-file: '.nvmrc'
 
       - name: Install Dependencies
-        run: yarn install --frozen-lockfile --immutable
+        run: pnpm install --frozen-lockfile
 
       - name: Run Tests
-        run: yarn test
+        run: pnpm test

.gitignore

@@ -16,4 +16,6 @@ node_modules
 dist
 
 # local deployments
-/deployments/hardhat
+/ignition/deployments/chain-31337
+
+/publish

.prettierignore

@@ -0,0 +1 @@
+ignition/deployments/

.solhint.json

@@ -3,6 +3,8 @@
   "plugins": ["prettier"],
   "rules": {
     "prettier/prettier": "error",
-    "ignoreConstructors": true
+    "func-visibility": ["error", { "ignoreConstructors": true }],
+    "quotes": ["error", "single"],
+    "immutable-vars-naming": ["warn", { "immutablesAsConstants": false }]
   }
 }

CODE_OF_CONDUCT.md

@@ -2,9 +2,9 @@
 
 ## Our Pledge
 
-We, as contributors and maintainers, 
-pledge to make participation in our project and our community a harassment-free experience for everyone, 
-regardless of age, body size, disability, ethnicity, gender identity and expression, 
+We, as contributors and maintainers,
+pledge to make participation in our project and our community a harassment-free experience for everyone,
+regardless of age, body size, disability, ethnicity, gender identity and expression,
 level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 ## Our Standards
@@ -27,38 +27,38 @@ Examples of unacceptable behavior by participants include:
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior 
-and are expected to take appropriate and fair corrective action in 
+Project maintainers are responsible for clarifying the standards of acceptable behavior
+and are expected to take appropriate and fair corrective action in
 response to any instances of unacceptable behavior.
 
 Project maintainers have the right and responsibility to
-remove, edit, or reject comments, commits, code, wiki edits, issues, 
-and other contributions that are not aligned with this Code of Conduct, 
-or to ban temporarily or permanently any contributor for behaviors that 
+remove, edit, or reject comments, commits, code, wiki edits, issues,
+and other contributions that are not aligned with this Code of Conduct,
+or to ban temporarily or permanently any contributor for behaviors that
 they deem inappropriate, threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in 
-public spaces when an individual is representing the project or its community. 
-Examples of representing a project or community include using an official project email address, 
-posting via an official social media account, 
+This Code of Conduct applies both within project spaces and in
+public spaces when an individual is representing the project or its community.
+Examples of representing a project or community include using an official project email address,
+posting via an official social media account,
 or acting as an appointed representative at an online or offline event.
 
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable
-behavior may be reported by contacting the 
-project team at [[email protected]](mailto:[email protected]). 
+behavior may be reported by contacting the
+project team at [[email protected]](mailto:[email protected]).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All project team members are obligated to respect the privacy and security of the reporter of any incident.
 
 ## Attribution
 
-This Code of Conduct is adapted from the 
-[Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html), 
+This Code of Conduct is adapted from the
+[Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html),
 version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
 
-For answers to common questions about this code of conduct, 
+For answers to common questions about this code of conduct,
 see the [FAQ](https://www.contributor-covenant.org/faq).

CONTRIBUTING.md

@@ -1,19 +1,19 @@
 ## Contributing
 
-In order to contribute, please fork off of the `main` branch and make your changes there. 
-Your commit messages should detail why you made your change in addition to what you 
+In order to contribute, please fork off of the `main` branch and make your changes there.
+Your commit messages should detail why you made your change in addition to what you
 did (unless it is a tiny change).
 
-If you need to pull in any changes from `main` after making your fork 
-(for example, to resolve potential merge conflicts), 
-please avoid using git merge and instead, git rebase your branch. 
+If you need to pull in any changes from `main` after making your fork
+(for example, to resolve potential merge conflicts),
+please avoid using git merge and instead, git rebase your branch.
 This will help us review your change more easily.
-Additionally, if you are writing a new feature, 
+Additionally, if you are writing a new feature,
 please ensure you add appropriate test cases under test/ (see below).
 
-
-Please make sure you respect the coding style for this project. 
-Also, even though we do CI testing, 
+Please make sure you respect the coding style for this project.
+You can run `pnpm lint` for the linter and check the [solidity style guides](https://docs.soliditylang.org/en/latest/style-guide.html#) for more information
+Also, even though we do CI testing,
 please test your code and ensure that it builds locally before submitting a pull request.
 
 Thank you for your help!