swap hardhat for foundry (#22)

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,47 @@
+name: Bug Report
+description: File a bug/issue
+title: 'bug: <title>'
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! The more info you provide, the more we can help you 🙌
+
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+        - label: I have looked through the [existing issues](https://github.com/scaffold-eth/scaffold-eth-2/issues)
+          required: true
+
+  - type: textarea
+    attributes:
+      label: Current Behavior
+      description: A concise description of what you're experiencing.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: A concise description of what you expected to happen.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Steps To Reproduce
+      description: Steps or code snippets to reproduce the behavior.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Anything else?
+      description: |
+        Browser info? Screenshots? Anything that will give us more context about the issue you are encountering!
+
+        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Ask Question
+    url: https://github.com/scaffold-eth/scaffold-eth-2/discussions/new?category=q-a
+    about: Ask questions and discuss with other community members
+  - name: Request Feature
+    url: https://github.com/scaffold-eth/scaffold-eth-2/discussions/new?category=ideas 
+    about: Requests features or brainstorm ideas for new functionality

.github/pull_request_template.md

@@ -0,0 +1,16 @@
+## Description
+
+_Concise description of proposed changes, We recommend using screenshots and videos for better description_
+
+## Additional Information
+
+- [ ] I have read the [contributing docs](/scaffold-eth/scaffold-eth-2/blob/main/CONTRIBUTING.md) (if this is your first contribution)
+- [ ] This is not a duplicate of any [existing pull request](https://github.com/scaffold-eth/scaffold-eth-2/pulls)
+
+## Related Issues
+
+_Closes #{issue number}_
+
+_Note: If your changes are small and straightforward, you may skip the creation of an issue beforehand and remove this section. However, for medium-to-large changes, it is recommended to have an open issue for discussion and approval prior to submitting a pull request._
+
+Your ENS/address:

.gitignore

@@ -10,4 +10,4 @@ node_modules
 !.yarn/versions
 .eslintcache
 .vscode/**
-.DS_Store
+.DS_Store

.gitmodules

@@ -0,0 +1,9 @@
+[submodule "packages/foundry/lib/forge-std"]
+	path = packages/foundry/lib/forge-std
+	url = https://github.com/foundry-rs/forge-std
+[submodule "packages/foundry/lib/openzeppelin-contracts"]
+	path = packages/foundry/lib/openzeppelin-contracts
+	url = https://github.com/OpenZeppelin/openzeppelin-contracts
+[submodule "packages/foundry/lib/solidity-bytes-utils"]
+	path = packages/foundry/lib/solidity-bytes-utils
+	url = https://github.com/gnsps/solidity-bytes-utils

.yarn/patches/usehooks-ts-npm-2.7.2-fceffe0e43.patch

@@ -0,0 +1,13 @@
+diff --git a/dist/esm/useLocalStorage/useLocalStorage.js b/dist/esm/useLocalStorage/useLocalStorage.js
+index b0d584d4df29953551dfcf8febac002f89fa7acd..920ae5c52d28af73e3a892bdb935a7805a0f8224 100644
+--- a/dist/esm/useLocalStorage/useLocalStorage.js
++++ b/dist/esm/useLocalStorage/useLocalStorage.js
+@@ -14,7 +14,7 @@ function useLocalStorage(key, initialValue) {
+             return initialValue;
+         }
+     }, [initialValue, key]);
+-    const [storedValue, setStoredValue] = useState(readValue);
++    const [storedValue, setStoredValue] = useState(initialValue);
+     const setValue = useEventCallback(value => {
+         if (typeof window === 'undefined') {
+             console.warn(`Tried setting localStorage key “${key}” even though environment is not a client`);

CONTRIBUTING.md

@@ -1,12 +1,12 @@
 # Welcome to Scaffold-ETH 2 Contributing Guide
 
-Thank you for investing your time in contributing to Scaffold-Eth 2!
+Thank you for investing your time in contributing to Scaffold-ETH 2!
 
 This guide aims to provide an overview of the contribution workflow to help us make the contribution process effective for everyone involved.
 
 ## About the Project
 
-Scaffold-Eth 2 is a minimal and forkable repo providing builders with a starter kit to build decentralized applications on Ethereum.
+Scaffold-ETH 2 is a minimal and forkable repo providing builders with a starter kit to build decentralized applications on Ethereum.
 
 Read the [README](README.md) to get an overview of the project.
 
@@ -25,6 +25,7 @@ You can view the open Issues, follow the development process and contribute to t
 ## Getting started
 
 You can contribute to this repo in many ways:
+
 - Solve open issues
 - Report bugs or feature requests
 - Improve the documentation
@@ -43,7 +44,7 @@ Issues should be used to report problems, request a new feature, or discuss pote
 
 #### Solve an issue
 
-Scan through our [existing issues](https://github.com/scaffold-eth/se-2/issues) to find one that interests you.
+Scan through our [existing issues](https://github.com/scaffold-eth/scaffold-eth-2/issues) to find one that interests you.
 
 If a contributor is working on the issue, they will be assigned to the individual. If you find an issue to work on, you are welcome to assign it to yourself and open a PR with a fix for it.
 
@@ -52,6 +53,7 @@ If a contributor is working on the issue, they will be assigned to the individua
 If a related issue doesn't exist, you can open a new issue.
 
 Some tips to follow when you are creating an issue:
+
 - Provide as much context as possible. Over-communicate to give the most details to the reader.
 - Include the steps to reproduce the issue or the reason for adding the feature.
 - Screenshots, videos etc., are highly appreciated.
@@ -70,13 +72,15 @@ We follow the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr)
 6. Open a PR in our repository and tag one of the maintainers to review your PR
 
 Here are some tips for a high-quality pull request:
+
 - Create a title for the PR that accurately defines the work done.
 - Structure the description neatly to make it easy to consume by the readers. For example, you can include bullet points and screenshots instead of having one large paragraph.
 - Add the link to the issue if applicable.
 - Have a good commit message that summarises the work done.
 
 Once you submit your PR:
--  We may ask questions, request additional information or ask for changes to be made before a PR can be merged. Please note that these are to make the PR clear for everyone involved and aims to create a frictionless interaction process.
+
+- We may ask questions, request additional information or ask for changes to be made before a PR can be merged. Please note that these are to make the PR clear for everyone involved and aims to create a frictionless interaction process.
 - As you update your PR and apply changes, mark each conversation resolved.
 
-Once the PR is approved, we'll "squash-and-merge" to keep the git commit history clean.
+Once the PR is approved, we'll "squash-and-merge" to keep the git commit history clean.