doc: Add Precompiles Section (#104)

* chore: update flakes

* chore: update Nodejs

* feat: Create EVM Precompile section

* doc: our precompiles

* feat: add Call Permit

* feat: add MADs precompile docs

* feat: update nodejs

* chore: use nodejs 22

* fix: remove old precompiles

* fix: 404 links

* fix: Remove reference to governance v2 (OpenGov)

Author: shekohex

.github/workflows/build.yml

@@ -14,7 +14,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [18.x]
+        node-version: [22.x]
     steps:
       - name: Cancel Previous Runs
         uses: styfle/cancel-workflow-action@0.11.0

.github/workflows/checks.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [18.x]
+        node-version: [22.x]
     steps:
       - name: Cancel Previous Runs
         uses: styfle/cancel-workflow-action@0.11.0
@@ -33,7 +33,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [18.x]
+        node-version: [22.x]
     steps:
       - name: Cancel Previous Runs
         uses: styfle/cancel-workflow-action@0.11.0

.nvmrc

@@ -1 +1 @@
-18
+22

components/shiki.tsx

@@ -26,6 +26,8 @@ export const getLanguage = (url: string) => {
     case "js":
     case "jsx":
       return "javascript";
+    case "sol":
+      return "solidity";
     default:
       return "plaintext";
   }

flake.lock

@@ -20,7 +20,7 @@
           buildInputs = [
             # Nodejs
             pkgs.nodePackages.typescript-language-server
-            pkgs.nodejs_18
+            pkgs.nodejs_22
             pkgs.nodePackages.yarn
           ];
           packages = [ ];

flake.nix

@@ -102,6 +102,6 @@
   "engines": {
     "npm": "please-use-yarn",
     "yarn": "^1.10.1",
-    "node": "18.x.x"
+    "node": "22.x.x"
   }
 }

package.json

@@ -22,6 +22,7 @@
     "title": "Solution Developers"
   },
   "endpoints": "Endpoints and Integration",
+  "precompiles": "EVM Precompiles",
   "technicals": "EVM Development",
   "-- contribute": {
     "type": "separator",

pages/developers/_meta.json

@@ -32,10 +32,8 @@ The `EigenlayerContext` trait provides access to core Eigenlayer services and fu
 - Query stake updates and changes
 - Monitor stake across different quorums
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/sdk/src/contexts/eigenlayer.rs"
-  fromLine={16}
-  toLine={140}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/contexts/src/eigenlayer.rs"
   title="EigenlayerContext Trait Definition"
 />
 
@@ -45,7 +43,7 @@ The `EigenlayerContext` trait provides access to core Eigenlayer services and fu
 
 First, define your context struct that implements the `EigenlayerContext` trait:
 
-<GithubFileReaderDisplay 
+<GithubFileReaderDisplay
   url="https://github.com/tangle-network/gadget/blob/main/blueprints/incredible-squaring-eigenlayer/src/contexts/aggregator.rs"
   fromLine={43}
   toLine={56}
@@ -56,7 +54,7 @@ First, define your context struct that implements the `EigenlayerContext` trait:
 
 You can then use this context in your jobs to access Eigenlayer functionality:
 
-<GithubFileReaderDisplay 
+<GithubFileReaderDisplay
   url="https://github.com/tangle-network/gadget/blob/main/blueprints/incredible-squaring-eigenlayer/src/jobs/initialize_task.rs"
   fromLine={13}
   toLine={52}
@@ -67,7 +65,7 @@ You can then use this context in your jobs to access Eigenlayer functionality:
 
 Finally, instantiate your context in your main runner:
 
-<GithubFileReaderDisplay 
+<GithubFileReaderDisplay
   url="https://github.com/tangle-network/gadget/blob/main/blueprints/incredible-squaring-eigenlayer/src/main.rs"
   fromLine={27}
   toLine={45}

pages/developers/blueprint-contexts/eigenlayer-context.mdx

@@ -6,17 +6,17 @@ import GithubFileReaderDisplay from '/components/GithubFileReaderDisplay';
 
 # EVM Provider Context
 
-The `EvmProviderContext` trait provides a standardized [alloy-rs](https://github.com/alloy-rs) EVM provider for interacting with EVM-compatible blockchain networks in your Blueprint.
+The `EvmInstrumentedClientContext` trait provides a standardized [alloy-rs](https://github.com/alloy-rs) EVM provider for interacting with EVM-compatible blockchain networks in your Blueprint.
 
 ## Overview
 
-The `EvmProviderContext` trait provides access to an EVM provider:
+The `EvmInstrumentedClientContext` trait provides access to an EVM provider:
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/sdk/src/contexts/evm_provider.rs"
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/contexts/src/instrumented_evm_client.rs"
   fromLine={3}
-  toLine={12}
-  title="EvmProviderContext Trait Definition"
+  toLine={7}
+  title="EvmInstrumentedClientContext Trait Definition"
 />
 
 ## Using the Context
@@ -25,20 +25,20 @@ The `EvmProviderContext` trait provides access to an EVM provider:
 
 First, define your context struct that implements the `EvmProviderContext` trait:
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/macros/context-derive/tests/ui/basic.rs"
-  fromLine={4}
-  toLine={9}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/macros/context-derive/tests/ui/basic.rs"
+  fromLine={22}
+  toLine={31}
   title="EVM Provider Context Definition"
 />
 
 ### 2. Access Provider Parameters
 
 You can then use this context to access EVM provider parameters:
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/macros/context-derive/tests/ui/basic.rs"
-  fromLine={18}
-  toLine={18}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/macros/context-derive/tests/ui/basic.rs"
+  fromLine={45}
+  toLine={45}
   title="Accessing EVM Provider Parameters"
 />

pages/developers/blueprint-contexts/evm-provider-context.mdx

@@ -10,18 +10,18 @@ The `KeystoreContext` trait provides a standardized interface for accessing, man
 
 ## Overview
 
-The `KeystoreContext` trait provides access to a `GenericKeystore` that implements the `Backend` trait, offering:
+The `KeystoreContext` trait provides access to a `Keystore` that implements the `Backend` trait, offering:
 
 - Key Creation - Generate new keys of various types (ECDSA, SR25519, ED25519, BN254_BLS, BLS381)
 - Key Storage - Securely store and retrieve keys
 - Key Management - Read, modify, and delete stored keys
 - Signing - Sign messages using stored keys
 - Key Import/Export - Import existing keys and export key data
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/sdk/src/contexts/keystore.rs"
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/contexts/src/keystore.rs"
   fromLine={4}
-  toLine={7}
+  toLine={9}
   title="KeystoreContext Trait Definition"
 />
 
@@ -31,38 +31,20 @@ The `KeystoreContext` trait provides access to a `GenericKeystore` that implemen
 
 First, define your context struct that implements the `KeystoreContext` trait:
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/macros/context-derive/tests/ui/basic.rs"
-  fromLine={4}
-  toLine={9}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/macros/context-derive/tests/ui/basic.rs"
+  fromLine={22}
+  toLine={31}
   title="Keystore Context Definition"
 />
 
 ### 2. Access Keystore Functionality
 
 You can then use this context to access the keystore and perform key operations:
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/macros/context-derive/tests/ui/basic.rs"
-  fromLine={17}
-  toLine={17}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/macros/context-derive/tests/ui/basic.rs"
+  fromLine={44}
+  toLine={44}
   title="Accessing Keystore Functionality"
 />
-
-The `KeystoreContext` trait provides comprehensive key management capabilities through the `GenericKeystore` implementation:
-
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/sdk/src/keystore/backend/mod.rs"
-  fromLine={16}
-  toLine={27}
-  title="GenericKeystore Implementation"
-/>
-
-The underlying `Backend` trait provides the full range of key management operations:
-
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/sdk/src/keystore/mod.rs"
-  fromLine={182}
-  toLine={347}
-  title="Backend Trait Definition"
-/>

pages/developers/blueprint-contexts/keystore-context.mdx

@@ -17,9 +17,9 @@ The `TangleClientContext` trait provides access to a Subxt client that enables:
 - Event Monitoring - Subscribe to and process chain events
 - RPC Calls - Make direct RPC calls to Tangle nodes
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/sdk/src/contexts/tangle_client.rs"
-  fromLine={3}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/contexts/src/tangle.rs"
+  fromLine={5}
   toLine={10}
   title="TangleClientContext Trait Definition"
 />
@@ -30,20 +30,20 @@ The `TangleClientContext` trait provides access to a Subxt client that enables:
 
 First, define your context struct that implements the `TangleClientContext` trait:
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/macros/context-derive/tests/ui/basic.rs"
-  fromLine={4}
-  toLine={9}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/macros/context-derive/tests/ui/basic.rs"
+  fromLine={22}
+  toLine={31}
   title="Tangle Client Context Definition"
 />
 
 ### 2. Access Subxt Client Functionality
 
 You can then use this context to access the Subxt client and interact with Tangle:
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/macros/context-derive/tests/ui/basic.rs"
-  fromLine={19}
-  toLine={19}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/macros/context-derive/tests/ui/basic.rs"
+  fromLine={46}
+  toLine={52}
   title="Accessing Subxt Client Functionality"
 />

pages/developers/blueprint-contexts/service-context.mdx

@@ -10,7 +10,7 @@ When building a blueprint, your application may require to listen to events. Eve
 
 In general, when defining your job, you must register an event listeners and provide a context as such:
 
-<GithubFileReaderDisplay 
+<GithubFileReaderDisplay
   url="https://github.com/tangle-network/blueprint-template/blob/main/src/lib.rs"
   fromLine={11}
   toLine={32}
@@ -23,18 +23,18 @@ In order to understand how to build an event listener, begin with a custom imple
 
 Event listeners in the SDK are designed to be flexible and allow developers to customize the behavior of their applications. Event listeners must implement the `EventListener` trait, which defines the following methods:
 
-<GithubFileReaderDisplay 
-  url="https://github.com/tangle-network/gadget/blob/main/sdk/src/event_listener/mod.rs"
-  fromLine={14}
-  toLine={23}
+<GithubFileReaderDisplay
+  url="https://github.com/tangle-network/gadget/blob/main/crates/event-listeners/core/src/lib.rs"
+  fromLine={15}
+  toLine={25}
   title="Event Listener Trait Definition"
 />
 
 ### Initialization
 
 When a blueprint instance runs, the event listeners are constructed and executed as part of the job handler. Executing the listeners is handled by the `BlueprintRunner`
 
-<GithubFileReaderDisplay 
+<GithubFileReaderDisplay
   url="https://github.com/tangle-network/gadget/blob/main/blueprints/incredible-squaring/src/main.rs"
   fromLine={8}
   toLine={26}