neonevm · afalaleev · Oct 4, 2023 · Aug 14, 2023 · Aug 15, 2023 · Aug 15, 2023
diff --git a/.github/styles/Grammarly.csv b/.github/styles/Grammarly.csv
@@ -4,12 +4,12 @@
 "24:7",24/7,"Existing style, maintain consistency"
 "Advisory,advisory","Information","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "amongst",among,"Existing style, maintain consistency"
+"Anonymous","Pseudonymous","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "ALAN, alan",Alan,"Existing style, maintain consistency"
 "ALANS, alans",Alan,"The plural of Alan is Alan"
-"Anonymous","Pseudonymous","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
-"api;Api",API,"Existing style, maintain consistency"
-"back-end;backend","backend","back-end is used as an adjective only."
+"api,Api",API,"Existing style, maintain consistency"
 "Backdoor","Alternative","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
+"back-end;backend","backend","back-end is used as an adjective only."
 "best","a good option","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Berkley packet filter;berkeley packet filter",Berkeley Packet Filter,"Existing style, maintain consistency"
 "Betting","Predicting","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
@@ -98,7 +98,7 @@ governor,Governor,"Caps for a noun of an active component in the system"
 "Metamask;Meta mask;metamask;metaMask",MetaMask,"Brand name"
 "Money-laundering","","Avoid entirely -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "multi sig;multi-sig",multisig,"Existing style, maintain consistency"
-"NoenEVM;Noen EVM;NeonEVM;Neon EVM", Neon evm,"Existing style, maintain consistency"
+"NoenEVM;Noen EVM;NeonEVM;Neon evm;neon evm",Neon EVM,"Existing style, maintain consistency"
 "Neon Labs","Neon EVM","It is highly unlikely that you need to use Neon Labs in the public domain. Rather just refer to the main Brand."
 "Neon Protocol","Neon EVM","It is highly unlikely that you need to use Neon Protocol in the public domain. Rather just refer to the main Brand."
 "Neon Foundation","Neon EVM","It is highly unlikely that you need to use Neon Foundation in the public domain. Rather just refer to the main Brand."
@@ -108,11 +108,10 @@ governor,Governor,"Caps for a noun of an active component in the system"
 "Neon",NEON,"NEON caps is the token, Neon the noun should rarely be used > provide component instead"
 "NEONS, Neons, neons",NEON,"The plural of NEON is NEON"
 "No-brainer","Clear Choice","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
-"non-deterministic,nondeterministic","Existing style, maintain consistency"
 "NeonProxy, Noen proxy, Neon proxy",Neon Proxy,"Existing style, maintain consistency"
 "Nft",NFT,"Acronymn as caps"
 "node JS,Node JS",NodeJS,"Brand name"
-"non-deterministic,nondeterministic","Existing style, maintain consistency"
+"non-deterministic",nondeterministic","Existing style, maintain consistency"
 "Loophole","Strategy","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "L2 rollup","L2 Rollup","as per ""On the Road"" Medium post"
 "on boarding;on-boarding",onboarding,"Existing style, maintain consistency"
@@ -187,6 +186,7 @@ StrakEx,StarkEx,"typo fix"
 "the Neon,The Neon","Neon","In most instances, 'The Neon EVM' can be stated as Neon EVM"
 "the Mainnet,The Mainnet","Mainnet","In most instances, The Mainnet can be stated as Mainnet"
 "the Devnet,The Devnet","Devnet","'The Devnet' should most often simply be stated as Devnet"
+"token account,Token account,token Account,token-account",Token Account,"Existing style, maintain consistency"
 "unbeatable","competitive","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Undetectable","Discreet","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "Under the table","","Avoid entirely -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
@@ -197,13 +197,10 @@ StrakEx,StarkEx,"typo fix"
 "U.S,U.S.",US,"Existing style, maintain consistency"
 "U.S.A,U.S.A.",US,"Existing style, maintain consistency"
 "web3,web 3,Web 3",Web3,"Existing style, maintain consistency"
-"white paper",whitepaper,"Existing style, maintain consistency"
-"White paper",Whitepaper,"Existing style, maintain consistency"
-"web3,web 3,Web 3",Web3,"Existing style, maintain consistency"
+"white paper",whitepaper,"Existing style, maintain consistency""web3,web 3,Web 3",Web3,"Existing style, maintain consistency"
 "Wrapped","wrapped","Be very careful using this term Neon EVM does NOT wrap tokens: NeonPass provides an ERC-20 interface to SPL tokens: no mint, no burn"
 "Windfall","Earnings","Warning -- this is a legally sensitive term. However, context is everything: it may be that the original text is more appropriate."
 "World-wide,world-wide","worldwide","Stay consistent!"
 "ZK-rollup;ZKRollup;zk-rollup;zkRollup",ZK-Rollup,"Existing style, maintain consistency"
 "zk SNARK",zk-SNARK,"Existing style, maintain consistency"
-"zk STARK",zk-STARK,"Existing style, maintain consistency"
-
+"zk STARK",zk-STARK,"Existing style, maintain consistency"
diff --git a/.github/workflows/update_prod.yml b/.github/workflows/update_prod.yml
@@ -32,3 +32,6 @@ jobs:
           AWS_SECRET_ACCESS_KEY: ${{secrets.DOCS_PROD_AWS_SECRET_ACCESS_KEY}}
           AWS_REGION: ${{vars.DOCS_PROD_S3_REGION}}
           SOURCE_DIR: "build"
+      - name: Algolia Reindex
+        run: |
+          curl -H "Content-Type: application/json" -X POST --user ${{secrets.CRAWLER_USER_ID}}:${{secrets.CRAWLER_API_KEY}} "https://crawler.algolia.com/api/1/crawlers/${{vars.CRAWLER_ID}}/reindex"
diff --git a/README.md b/README.md
@@ -102,3 +102,11 @@ import TabItem from '@theme/TabItem';
 
 with authentication via [GitHub](https://github.com/anonNeon)
 
+
+## Troubleshooting
+
+You pull main and can no longer build. Don't fret, someone probably changed a dependency do:
+`npm install`
+and then build or serve and see if that fixes it
+
+
diff --git a/declarations.d.ts b/declarations.d.ts
@@ -0,0 +1,6 @@
+declare namespace JSX {
+  interface IntrinsicElements {
+    "cookie-control": any;
+    "component": any;
+  }
+}
diff --git a/docs/about/img/how_it_works.png → .../about/DELETE-img/DELETE-how_it_works.png b/docs/about/img/how_it_works.png → .../about/DELETE-img/DELETE-how_it_works.png
diff --git a/docs/about/img/neon_ecosystem.png → docs/about/DELETE-img/neon_ecosystem.png b/docs/about/img/neon_ecosystem.png → docs/about/DELETE-img/neon_ecosystem.png
diff --git a/docs/about/img/neon_ecosystem.svg → docs/about/DELETE-img/neon_ecosystem.svg b/docs/about/img/neon_ecosystem.svg → docs/about/DELETE-img/neon_ecosystem.svg
diff --git a/docs/about/DELETE-img/neon_ecosystem_white.svg b/docs/about/DELETE-img/neon_ecosystem_white.svg
diff --git a/docs/about/how_it_works.md → docs/about/how_it_works.mdx b/docs/about/how_it_works.md → docs/about/how_it_works.mdx
@@ -6,42 +6,40 @@
 approvedBy: YYY
 comments: #1 TODO see inline comment 2.3
 ---
+import {ImgTheme} from '@site/src/components/ImageTheme';
 
-import architecture from '@site/static/img/doc-images/about/how-it-works.png';
+<ImgTheme src='/img/doc-images/about/how-it-works.svg' srcDark='/img/doc-images/about/how-it-works_dark.svg' />
 
-<div className='neon-img-box-300' style={{textAlign: 'center', width: 900, display: 'block', margin: 'auto'}}>
+This page provides a high-level overview of how Neon EVM coordinates communication between Ethereum dApps and Solana.
 
-<img src={architecture} />
-
-</div>
-
-This page provides a high-level overview of how Neon coordinates communication between Ethereum dApps and Solana.
-
-## Neon's transaction lifecycle
+## Neon EVM's transaction lifecycle
 
 Effecting a user-initiated transaction (tx) from an Ethereum dApp on Solana requires three main steps:
 
-1. The user initiates a tx. A tx is a signed Ethereum-like tx directed to a Neon RPC endpoint.  
+1. The user initiates a tx. A tx is a signed Ethereum-like tx directed to a Neon RPC endpoint.
 
 > See [How to Connect to the Neon RPC](/docs/wallet/metamask_setup) via an Ethereum-compatible wallet.
 
-The Ethereum API passes the tx to the Neon Proxy via the [Neon API service](docs/developing/connect_rpc).
+The Ethereum API passes the tx to the Neon Proxy via the [Neon API service](docs/developing/connect_rpc.md). 
+
+<!-- todo why does the link above connect to the rpc // chainlist page -- requires fix? -->
 
 2. This request is received by the Neon Proxy.
 
    > 2.1 The Neon Proxy processes the request, providing:
    > - Gas usage estimate for tx execution
    > - Broadcast initiation: wrapping the Ethereum-like tx as a Solana tx
-   
+
    > 2.2. The Neon Proxy passes the wrapped tx to the Neon EVM program hosted on Solana. This results in the following:
    > - A Solana receipt
    > - A corresponding Neon EVM receipt
-     
-   > 2.3 The Neon smart contract then:   
+
+   > 2.3 The Neon smart contract then:
    > - Unwraps the tx and checks the user's signature
    > - Loads the EVM state, including account data and the smart contract's code, from Solana storage
    > - Executes the tx inside [Solana BPF](https://docs.solana.com/developing/runtime-facilities/programs#bpf-loader)
-   > - Updates Solana's state to reflect the new Neon EVM state 
+   > - Updates Solana's state to reflect the new Neon EVM state
+
    <!-- missing logical link here as tx execution impact on Neon EVM not made clear -->
 
 3. Solana and Neon EVM undertake a state change.

diff --git a/docs/about/neon_ecosystem.md → docs/about/neon_ecosystem.mdx b/docs/about/neon_ecosystem.md → docs/about/neon_ecosystem.mdx
@@ -4,18 +4,15 @@
 iterationBy: HB
 includedInSite: true
 approvedBy: YYY
-comment: #2 TODO Tracer API needs internal linking to replace Medium article 
+links: The ecosystem image links to /docs/tokens/neon_token and /docs/tokens/gas_fees
+comment: #2 TODO Tracer API needs internal linking to replace Medium article todo we have more wallets than just MetaMask -- perhaps add an FAQ and link there? TODO what was the outcome of Anton not wanting to use BPF?
 ---
-<!-- import { QuickLookNeonImage } from '@site/src/components/QuickLookNeonImage' -->
-<!-- <QuickLookNeonImage/> -->
+import {ImgTheme} from '@site/src/components/ImageTheme';
+import {QuickLookNeonImage} from '@site/src/components/QuickLookNeonImage';
 
-import ecosystem from '@site/static/img/doc-images/about/neon-ecosystem.png';
-
-
-<div className='neon-img-box-300' style={{textAlign: 'center', maxWidth: 800, display: 'block', margin: 'auto'}}>
-    <img src={ecosystem} />
-</div>
+<QuickLookNeonImage></QuickLookNeonImage>
 
+[//]: # (<ImgTheme src='/img/doc-images/about/neon-ecosystem.svg' srcDark='/img/doc-images/about/neon-ecosystem_dark.svg' />)
 
 **Neon EVM** is *the* solution that makes Solana's throughput, swift block speeds, and low gas prices available to Ethereum contracts. Neon EVM interacts directly with Solana nodes to carry out transactions on Solana. The service is made up of three main components:
 
@@ -28,18 +25,19 @@
 
 ## Neon EVM program
 
-The **Neon EVM program** is a smart contract on the Solana blockchain. The Neon EVM program accepts Ethereum-like transactions and processes them on Solana according to Ethereum rules. Ethereum transactions directed to the Neon EVM are called Neon Transactions. 
+The **Neon EVM program** is a smart contract on the Solana blockchain. The Neon EVM program accepts Ethereum-like transactions and processes them on Solana according to Ethereum rules. Ethereum transactions directed to the Neon EVM are called Neon Transactions.
 
 > **Neon Transactions**: a [subset of Ethereum's JSON-RPC Specification](/docs/evm_compatibility/json_rpc_api_methods) may be directed to the Neon EVM to be used as inputs for the targeted Neon clients.
 
 ## Neon Proxy
 
-It's the Neon Proxy that allows Ethereum dApps to be ported to Neon with minimal reconfiguration. Neon Proxy packages a Neon transaction into a Solana transaction. The proxy is provided as a containerized solution that's intuitive for [Operators](/docs/operating/operator-introduction). 
-
-> **Neon Operators** run Neon Proxy servers to facilitate the seamless execution of Ethereum-like transactions on Solana. It is this proxy service that allows Ethereum dApps to be ported to Neon with minimal reconfiguration. Operators accept payment in NEON and make payments within the Solana Ecosystem in SOL.
+It's the Neon Proxy that allows Ethereum dApps to be ported to Neon with minimal reconfiguration. Neon Proxy packages a EVM transaction into a Solana transaction. The Proxy is provided as a containerized solution that's intuitive for [Operators](/docs/operating/operator-introduction).
 
+:::info
+**Neon Operators** run Neon Proxy servers to facilitate the seamless execution of Ethereum-like transactions on Solana. It is this proxy service that allows Ethereum dApps to be ported to Neon with minimal reconfiguration. Operators accept payment in NEON (although the roadmap will expand the options) and make payments within the Solana Ecosystem in SOL.
+:::
 
-### The NEON Token
+### The NEON token
 
 The NEON token is a utility token with 2 functions:
 
@@ -79,16 +77,16 @@
 
 ### Oracles
 
-Oracles enable the decentralized Web3 ecosystem to access price feeds and other external (off-chain) data sources. Neon EVM supports querying data from Solana deployed Oracles:  
+Oracles enable the decentralized Web3 ecosystem to access price feeds and other external (off-chain) data sources. Neon EVM supports querying data from Solana deployed Oracles:
 * [Chainlink](/docs/developing/integrate/oracles/integrating_chainlink)
 * [Pyth](/docs/developing/integrate/oracles/integrating_pyth)
 
 
 ### Wallets
 
-Neon EVM is supported by the MetaMask non-custodial wallet. 
+Neon EVM is supported by EVM-compatible wallets such as MetaMask's non-custodial wallet.
 
-> This allows dApp devs to sign deployment transactions and mint tokens. 
+> This allows dApp devs to sign deployment transactions and mint tokens.
 <!-- > Learn more about minting and wrapping tokens with Neon EVM. suggest adding link here as Phantom wallet is invovled for Solana-based mints -->
 
 ### Protocols
@@ -97,16 +95,15 @@
 
 ### Tracer API
 
-Neon's Tracer API is an extension for Neon Proxy. It assists developers to test, debug, and understand the behavior of their smart contracts on Neon EVM. The API provides a full externality trace on any Neon transactions executed on the Solana blockchain. 
+Neon's Tracer API is an extension for Neon Proxy. It assists developers to test, debug, and understand the behavior of their smart contracts on Neon EVM. The API provides a full externality trace on any Neon transactions executed on the Solana blockchain.
 
-The Tracer API supports a rerun of historical transactions, runs transactions on historical states, and analyzes the state of the Solana blockchain after the execution of each instruction. 
+The Tracer API supports a rerun of historical transactions, runs transactions on historical states, and analyzes the state of the Solana blockchain after the execution of each instruction.
 
 > More details are available in [our blog](https://medium.com/neon-labs/neon-proxy-tracing-api-fdb3842a80fa).
 
 ## Development tools
 
 Various tools such as:
 - [Hardhat](/docs/developing/deploy_facilities/using_hardhat)
-- [Truffle](/docs/developing/deploy_facilities/using_truffle)
-- [Remix](/docs/developing/deploy_facilities/using_remix).
+- [Remix](/docs/developing/deploy_facilities/using_remix)
 
diff --git a/docs/about/why_neon.md → docs/about/why_neon.mdx b/docs/about/why_neon.md → docs/about/why_neon.mdx
@@ -6,35 +6,30 @@
 approvedBy: YYY
 comments: na
 ---
-
-import infographic from '@site/static/img/doc-images/about/infographic.png';
+import {ImgTheme} from '@site/src/components/ImageTheme';
 
 *Neon EVM is a low-friction solution to scale Ethereum dApps on Solana.*
 
-
-<div className='neon-img-box-300' style={{textAlign: 'center', width: 600, display: 'block', margin: 'auto'}}>
-
-<img src={infographic} />
-
-
-</div>
+<ImgTheme src='/img/doc-images/about/infographic.svg' srcDark='/img/doc-images/about/infographic_dark.svg' />
 
 ## Neon EVM
 
-Neon EVM is a fully compatible Ethereum environment solution built on the Solana blockchain. The platform allows developers to deploy Ethereum dApps without undertaking any reconfiguration. 
+Neon EVM is a fully compatible Ethereum environment solution built on the Solana blockchain. The platform allows developers to deploy Ethereum dApps without undertaking any reconfiguration.
 
-> Minimal reconfiguration required: Ethereum developers can build without Rust.
+:::info
+Minimal reconfiguration required: allowing Ethereum developers to build without Rust.
+:::
 
 Neon EVM enables Solidity- and Vyper-based dApps to tap into Solana’s network benefits: low fees, high transaction speeds, and parallel transaction execution capabilities.
 
-From a developer’s perspective, this means creating Solana-compatible contracts using tools you’re familiar with from the Ethereum Ecosystem. 
+From a developer’s perspective, this means creating Solana-compatible contracts using tools you’re familiar with from the Ethereum Ecosystem.
 
-Neon EVM makes the key Ethereum dApp tools compatible with Solana, including Vyper, Solidity, [MetaMask](/docs/wallet/metamask_setup), [Hardhat](/docs/developing/deploy_facilities/using_hardhat), [Truffle](/docs/developing/deploy_facilities/using_truffle), and [Remix](/docs/developing/deploy_facilities/using_remix). The solution allows any Ethereum application to run on Solana with minimal reconfiguration required, this includes Uniswap, SushiSwap, 0x, and MakerDAO. 
+Neon EVM makes the key Ethereum dApp tools compatible with Solana, including Vyper, Solidity, [MetaMask](/docs/wallet/metamask_setup), [Hardhat](/docs/developing/deploy_facilities/using_hardhat), [Remix](/docs/developing/deploy_facilities/using_remix), (and [Truffle](/docs/developing/deploy_facilities/using_truffle)). The solution allows any Ethereum application to run on Solana with minimal reconfiguration, this includes Uniswap, SushiSwap, 0x, and MakerDAO.
 
 
 ### Who uses Neon EVM?
 
-Neon EVM serves any developers or product teams who wish that their dApp could reach customers on Solana. Teams interested in the significant savings thanks to the low gas fees, or scaling with the high throughput that Solana provides are likely to be the first movers. Neon EVM also opens up the liquidity on Solana to DeFi products.
+Teams interested in the significant savings thanks to the low gas fees, or scaling with the high throughput that Solana provides are likely to be the first movers. Neon EVM serves any developers or product teams who wish that their dApp could reach customers on Solana. Neon EVM also opens up the liquidity on Solana to DeFi products.
 
 ## The best from Ethereum
 
@@ -45,7 +40,7 @@
 With Neon EVM, developers retain:
 
 * Familiar languages: Solidity, Vyper
-* Well-known Ethereum tools: MetaMask, Hardhat, Truffle, Remix, etc.
+* Well-known Ethereum tools: MetaMask, Hardhat, Remix, etc.
 * Ethereum RPC API compatibility
 * Ethereum Accounts, Signatures, Token standards (ERC-20 and ERC-721)
 

diff --git a/docs/developing/integrate/neon_transfer.mdx b/docs/developing/integrate/neon_transfer.mdx
@@ -27,7 +27,8 @@
 
 ## Prerequisites
 
-- You need to provide Solana and Neon EVM providers from supported official libraries such as `@solana/web3.js` or `web3.js`, `ether.js` and `WalletConnect`.
+- You need to integrate Solana-compatible and EVM-compatible wallet providers from supported official libraries such as `@solana/web3.js` or `web3.js`, `ether.js` and `WalletConnect`.
+
 - Supported browser plugins (e.g. Phantom or MetaMask wallets).
 
 <!-- I don't understand provide providers above -->

diff --git a/docs/developing/integrate/wallets/integrating_walletconnect.mdx b/docs/developing/integrate/wallets/integrating_walletconnect.mdx
@@ -27,9 +27,8 @@ Check out Web3Modal code on [GitHub](https://github.com/WalletConnect/web3modal)
 
 Web3Modal supports:
 
-- [React](https://docs.walletconnect.com/2.0/web3modal/react/wagmi/installation)
-- [HTML](https://docs.walletconnect.com/2.0/web/web3modal/html/wagmi/installation)
-
+- [React](https://docs.walletconnect.com/web3modal/react/about)
+- [HTML](https://docs.walletconnect.com/web3modal/html/about)
 :::
 
 ## Get Started