DON'T MERGE : Updating to 0.23.0

recursion/.gitignore

@@ -1,48 +1,4 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
-
-.env
-.tmp
-
-# dependencies
-/node_modules
-/.pnp
-.pnp.js
-
-# testing
-/coverage
-
-# next.js
-/.next/
-/out/
-
-# production
-/build
-
-# misc
-.DS_Store
-*.pem
-
-# debug
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-.pnpm-debug.log*
-
-# local env files
-.env*.local
-
-# vercel
-.vercel
-
-# typescript
-*.tsbuildinfo
-next-env.d.ts
-
-
-# artifacts
 proofs
-
-# other
 .vscode
 crs
 .DS_Store
@@ -51,4 +7,7 @@ artifacts
 .target
 typechain-types
 cache
-.target
+target
+.next
+node_modules
+next-env.d.types

recursion/.yarnrc.yml

@@ -0,0 +1,2 @@
+yarnPath: .yarn/releases/yarn-4.1.0.cjs
+nodeLinker: node-modules

recursion/README.md

@@ -6,14 +6,15 @@ Recursive proofs mean you prove that another proof is correct. A bit of a proofi
 - You pick that proof and send it to another circuit (the "outer" proof)
 - You generate the outer proof and verify it
 
-Why is this useful? In this example, it doesn't do much. But you could verify two proofs within a proof, which can be incredibly useful. You could also avoid verifying stuff on-chain for turn-based games, for example.
+Why is this useful? In this example, it doesn't do much. But you could verify two proofs within a proof, which can be incredibly useful.
+
+You could also avoid verifying stuff on-chain for turn-based games, for example. Check out the [Noir Docs](https://noir-lang.org/docs/explainers/explainer-recursion) for a high-level explanation.
 
 ## Getting Started
 
-1. [Install nargo](https://noir-lang.org/getting_started/nargo_installation#option-1-noirup) version 0.17.0 with `noirup -v 0.17.0`
-2. Install dependencies by running `yarn`
-3. Compile the project with `yarn compile`
-4. Run `yarn dev`
+1. Install dependencies by running `yarn`
+2. For on-chain verification, open another terminal and run `npx hardhat node`
+3. Run `yarn dev`
 
 ## Testing