0x

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/config.json

@@ -0,0 +1,21 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.0.5/schema.json",
+  "changelog": [
+    "@svitejs/changesets-changelog-github-compact",
+    { "repo": "wevm/wagmi" }
+  ],
+  "commit": false,
+  "access": "public",
+  "fixed": [],
+  "linked": [],
+  "baseBranch": "main",
+  "updateInternalDependencies": "minor",
+  "ignore": [
+    "*-register",
+    "@wagmi/test",
+    "site",
+    "next-app",
+    "nuxt-app",
+    "vite-*"
+  ]
+}

.changeset/new-elephants-travel.md

@@ -0,0 +1,5 @@
+---
+"@wagmi/cli": patch
+---
+
+Updated block explorer chains.

.changeset/nice-pandas-clap.md

@@ -0,0 +1,5 @@
+---
+
+---
+
+Circleci project setup

.changeset/quick-hairs-scream.md

@@ -0,0 +1,6 @@
+---
+"wagmi": patch
+"@wagmi/core": patch
+---
+
+Added `chainId` parameter to `getCapabilities`/`useCapabilities`.

.changeset/spicy-bats-juggle.md

@@ -0,0 +1,6 @@
+---
+"@wagmi/cli": patch
+"site": patch
+---
+
+Circleci project setup

.changeset/tall-fans-mate.md

@@ -0,0 +1,6 @@
+---
+"@wagmi/cli": patch
+"site": patch
+---
+
+Circleci project setup

.changeset/tiny-laws-dream.md

@@ -0,0 +1,5 @@
+---
+"@fake-scope/fake-pkg": patch
+---
+
+Circleci project setup

.changeset/young-guests-care.md

@@ -0,0 +1,5 @@
+---
+"site": patch
+---
+
+docs(readme): fix typo

.circleci/config.yml

@@ -0,0 +1,26 @@
+# Use the latest 2.1 version of CircleCI pipeline process engine.
+# See: https://circleci.com/docs/configuration-reference
+
+version: 2.1
+executors:
+  my-custom-executor:
+    docker:
+      - image: cimg/base:stable
+        auth:
+          # ensure you have first added these secrets
+           # visit app.circleci.com/settings/project/github/Dargon789/foundry/environment-variables
+          username: $DOCKER_HUB_USER
+          password: $DOCKER_HUB_PASSWORD
+jobs:
+  web3-defi-game-project-:
+
+    executor: my-custom-executor
+    steps:
+      - checkout
+      - run: |
+          # echo Hello, World!
+
+workflows:
+  my-custom-workflow:
+    jobs:
+      - web3-defi-game-project-

.github/CODEOWNERS

@@ -0,0 +1,6 @@
+@tmm @jxom
+
+/packages/connectors/src/gemini @mikelxc
+/packages/connectors/src/metaMask @ecp4224 @omridan159 @abretonc7s @elefantel @BjornGunnarsson @EdouardBougon
+/packages/connectors/src/safe @DaniSomoza @dasanra @mikhailxyz @yagopv
+/packages/connectors/src/walletConnect @ganchoradkov @glitch-txs @ignaciosantise @tomiir

.github/CONTRIBUTING.md

@@ -0,0 +1,191 @@
+# Contributing
+
+Thanks for your interest in contributing to wagmi! Please take a moment to review this document **before submitting a pull request.**
+
+If you want to contribute, but aren't sure where to start, you can create a [new discussion](https://github.com/wagmi-dev/wagmi/discussions).
+
+> **Note**
+>
+> **Please ask first before starting work on any significant new features. This includes things like adding new connectors, hooks, chains, API providers, etc.**
+>
+> It's never a fun experience to have your pull request declined after investing time and effort into a new feature. To avoid this from happening, we request that contributors create a [feature request](https://github.com/wagmi-dev/wagmi/discussions/new?category=ideas) to first discuss any API changes or significant new ideas.
+
+<br>
+
+## Basic guide
+
+This guide is intended to help you get started with contributing. By following these steps, you will understand the development process and workflow.
+
+1. [Cloning the repository](#cloning-the-repository)
+2. [Installing Node.js and pnpm](#installing-nodejs-and-pnpm)
+3. [Installing dependencies](#installing-dependencies)
+4. [Starting the development playground](#starting-the-development-playground)
+5. [Running the test suite](#running-the-test-suite)
+6. [Writing documentation](#writing-documentation)
+7. [Submitting a pull request](#submitting-a-pull-request)
+
+## Advanced guide
+
+This guide covers more advanced topics. Pick the topics based on your needs.
+
+8. [Versioning](#versioning)
+
+<br>
+
+---
+
+<br>
+
+## Cloning the repository
+
+To start contributing to the project, clone it to your local machine using git:
+
+```bash
+git clone https://github.com/wagmi-dev/wagmi.git --recurse-submodules
+```
+
+Or the [GitHub CLI](https://cli.github.com):
+
+```bash
+gh repo clone wagmi-dev/wagmi -- --recurse-submodules
+```
+
+<div align="right">
+  <a href="#basic-guide">&uarr; back to top</a></b>
+</div>
+
+## Installing Node.js and pnpm
+
+wagmi uses [pnpm workspaces](https://pnpm.io/workspaces) to manage multiple projects. You need to install **Node.js v16 or higher** and **pnpm v7 or higher**.
+
+You can run the following commands in your terminal to check your local Node.js and npm versions:
+
+```bash
+node -v
+pnpm -v
+```
+
+If the versions are not correct or you don't have Node.js or pnpm installed, download and follow their setup instructions:
+
+- Install Node.js using [fnm](https://github.com/Schniz/fnm) or from the [official website](https://nodejs.org)
+- Install [pnpm](https://pnpm.io/installation)
+
+<div align="right">
+  <a href="#basic-guide">&uarr; back to top</a></b>
+</div>
+
+## Installing dependencies
+
+Once in the project's root directory, run the following command to install the project's dependencies:
+
+```bash
+pnpm install
+```
+
+After the install completes, pnpm links packages across the project for development and [git hooks](https://github.com/toplenboren/simple-git-hooks) are set up.
+
+<div align="right">
+  <a href="#basic-guide">&uarr; back to top</a></b>
+</div>
+
+## Starting the development playground
+
+To start the local development playground, run the following. This will run a [Next.js](https://nextjs.org) app (located at [`examples/_dev`](../examples/_dev)) that is set up for playing around with code while making changes.
+
+```bash
+pnpm playground
+```
+
+Once the Next.js dev server is running, you can make changes to any of the package source files (e.g. `packages/react`) and it will automatically update the playground. (If the playground isn't automatically updating, try running `pnpm dev` to relink packages in development mode.)
+
+<div align="right">
+  <a href="#basic-guide">&uarr; back to top</a></b>
+</div>
+
+## Running the test suite
+
+wagmi uses [Anvil](https://github.com/foundry-rs/foundry/tree/master/anvil) to execute tests against a local Ethereum node. First, install Anvil via [Foundry](https://book.getfoundry.sh/getting-started/installation). Next, add the following to your environment (recommended to use [`direnv`](https://github.com/direnv/direnv)):
+
+```bash
+ANVIL_FORK_URL=https://eth-mainnet.alchemyapi.io/v2/<apiKey>
+```
+
+`ANVIL_FORK_URL` can be for any RPC service provider (e.g. Alchemy or Infura). Now you are ready to run the tests! In one terminal session, spin up Anvil using `pnpm anvil`. Next, in a different terminal session, you have the following options for running tests:
+
+- `pnpm test` — runs tests in watch mode
+- `pnpm test:run` — performs single run without watch mode
+
+When adding new features or fixing bugs, it's important to add test cases to cover the new/updated behavior. If snapshot tests fail, you can run the `test:update` command to update the snapshots.
+
+<div align="right">
+  <a href="#basic-guide">&uarr; back to top</a></b>
+</div>
+
+## Writing documentation
+
+Documentation is crucial to helping developers of all experience levels use wagmi. wagmi uses [Nextra](https://github.com/shuding/nextra) and [MDX](https://mdxjs.com) for the documentation site (located at [`docs`](../docs)). To start the site in dev mode, run:
+
+```bash
+pnpm docs:dev
+```
+
+Try to keep documentation brief and use plain language so folks of all experience levels can understand. If you think something is unclear or could be explained better, you are welcome to open a pull request.
+
+<div align="right">
+  <a href="#basic-guide">&uarr; back to top</a></b>
+</div>
+
+## Submitting a pull request
+
+When you're ready to submit a pull request, you can follow these naming conventions:
+
+- Pull request titles use the [Imperative Mood](https://en.wikipedia.org/wiki/Imperative_mood) (e.g., `Add something`, `Fix something`).
+- [Changesets](#versioning) use past tense verbs (e.g., `Added something`, `Fixed something`).
+
+When you submit a pull request, GitHub will automatically lint, build, and test your changes. If you see an ❌, it's most likely a bug in your code. Please, inspect the logs through the GitHub UI to find the cause.
+
+<div align="right">
+  <a href="#basic-guide">&uarr; back to top</a></b>
+</div>
+
+<br>
+
+---
+
+<div align="center">
+  ✅ Now you're ready to contribute to wagmi! Follow the next steps if you need more advanced instructions.
+</div>
+
+---
+
+<br>
+
+## Versioning
+
+When adding new features or fixing bugs, we'll need to bump the package versions. We use [Changesets](https://github.com/changesets/changesets) to do this.
+
+> **Note**
+>
+> Only changes to the codebase that affect the public API or existing behavior (e.g. bugs) need changesets.
+
+Each changeset defines which package(s) should be published and whether the change should be a major/minor/patch release, as well as providing release notes that will be added to the changelog upon release.
+
+To create a new changeset, run `pnpm changeset`. This will run the Changesets CLI, prompting you for details about the change. You’ll be able to edit the file after it’s created — don’t worry about getting everything perfect up front.
+
+Since we’re currently in beta, all changes should be marked as a minor/patch release to keep us within the `v0.x` range.
+
+Even though you can technically use any markdown formatting you like, headings should be avoided since each changeset will ultimately be nested within a bullet list. Instead, bold text should be used as section headings.
+
+If your PR is making changes to an area that already has a changeset (e.g. there’s an existing changeset covering theme API changes but you’re making further changes to the same API), you should update the existing changeset in your PR rather than creating a new one.
+
+### Releasing
+
+The first time a PR with a changeset is merged after a release, a new PR will automatically be created called `chore: version packages`. Any subsequent PRs with changesets will automatically update this existing version packages PR. Merging this PR triggers the release process by publishing to npm and cleaning up the changeset files.
+
+### Creating a snapshot release
+
+If a PR has changesets, you can create a [snapshot release](https://github.com/changesets/changesets/blob/main/docs/snapshot-releases.md) by [manually dispatching](https://github.com/wagmi-dev/wagmi/actions/workflows/snapshot.yml) the Snapshot workflow. This publishes a tagged version to npm with the PR branch name and timestamp.
+
+<div align="right">
+  <a href="#advanced-guide">&uarr; back to top</a></b>
+</div>

.github/DISCUSSION_TEMPLATE/connector-request.yml

@@ -0,0 +1,51 @@
+title: '[Connector Request] '
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your interest in contributing a new Connector to the Wagmi! If you haven't already, please read the [Contributing Guidelines](https://wagmi.sh/dev/contributing). Once you submit the form, the Wagmi team will follow up in the discussion thread to discuss next steps.
+
+        Please note that in order for connector requests to be accepted, the team creating the Connector must [sponsor Wagmi](https://github.com/sponsors/wevm). It takes time and effort to maintain third-party connectors. Wagmi is an OSS project that depends on sponsors and grants to continue our work. Please get in touch via [dev@wevm.dev](mailto:dev@wevm.dev) if you have questions about sponsoring.
+
+  - type: textarea
+    attributes:
+      label: What **novel use-case** does the Connector provide?
+      description: |
+        A novel use-case is likely one that is not already covered by or not easily extended from another Connector (such as the `injected` or `walletConnect`).
+
+        Examples of **novel** use-cases could be a connector that integrates with:
+
+        - the injected `window.ethereum` provider (a la `injected`)
+        - a series of wallets via QR Codes or Mobile Deep Links (a la `walletConnect`)
+        - a wallet with it's own SDK (a la `coinbaseWallet`)
+        - hardware wallet(s) via Web USB/Bluetooth
+        - an Externally Owned Account via a private key or some other method
+
+        Examples of **nonnovel** use-cases would be a connector that:
+
+        - extends another connector (e.g. `walletConnect`) with no significant differences in functionality other than branding, etc.
+      placeholder: Info on what makes this connector different.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Are the Connector's integrations production-ready and generally available?
+      description: Connectors are intended to be used by consumers in production as part of Wagmi. As such, the Connector and all dependencies must be production-ready and generally available. This means your connector should not rely on non-production software or be restricted to a limited group of users. For example, if your connector requires a wallet that has a closed beta, it is not ready for inclusion in Wagmi.
+      placeholder: Info about the Connector and any dependencies (e.g. browser extension, wallet app, npm package).
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Are you committed to actively maintaining the Connector?
+      description: It is critical connectors are updated in a timely manner and actively maintained so that users of Wagmi can rely on them in production settings. The Wagmi core team will provide as much assistance as possible to keep connectors up-to-date with breaking changes from Wagmi, but it is your responsibility to ensure that any dependencies and issues/discussions related to the Connector are handled in a timely manner. If this is not done, the Connector could be removed from the future versions.
+      options:
+        - label: Yes, my team is or I am committed to actively maintaining the Connector.
+          required: true
+
+  - type: textarea
+    attributes:
+      label: Additional comments
+      description: Feel free to jot down any additional info you think might be helpful.
+      placeholder: Additional comments, questions, feedback.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: 'bug'
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. Windows 11, macOS Sonoma]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.