init resolc docs

Author: pkhry

README.md

@@ -6,7 +6,7 @@
 
 <!-- ALL-CONTRIBUTORS-BADGE:END -->
 
-A book on all things Foundry. [Read now](https://book.getfoundry.sh).
+A book on all things Foundry. [Read now](https://paritytech.github.io/foundry-book-polkadot).
 
 ### Contributing
 

src/README.md

@@ -10,7 +10,7 @@ Foundry manages your dependencies, compiles your project, runs tests, deploys, a
 
 > 📖 **Contributing**
 >
-> You can contribute to this book on [GitHub](https://github.com/foundry-rs/book).
+> You can contribute to this book on [GitHub](https://github.com/paritytech/foundry-book-polkadot).
 
 ### Sections
 
@@ -49,6 +49,7 @@ Guides on configuring Foundry.
 - [Static Analyzers](./config/static-analyzers.md)
 - [Integrating with Hardhat](./config/hardhat.md)
 - [Vyper support](./config/vyper.md)
+- [Resolc support](./config/resolc.md)
 
 **Guides**
 

src/SUMMARY.md

@@ -63,6 +63,7 @@
 - [Static Analyzers](./config/static-analyzers.md)
 - [Integrating with Hardhat](./config/hardhat.md)
 - [Vyper support](./config/vyper.md)
+- [Resolc support](./config/resolc.md)
 
 # Guides
 

src/announcements.md

@@ -20,7 +20,7 @@ If you are running Foundry's **latest nightly build** you may encounter the foll
 [FAIL: call didn't revert at a lower depth than cheatcode call depth]
 ```
 
-Please read [here](https://book.getfoundry.sh/cheatcodes/expect-revert#error) for more information.
+Please read [here](https://paritytech.github.io/foundry-book-polkadot/cheatcodes/expect-revert#error) for more information.
 
 ## Releases
 

src/ci-cd/github-actions.md

@@ -92,7 +92,7 @@ Then, locate the "Management" section, and click on "Caches". You will see a lis
 
 #### Fuzzing
 
-Note that if you are fuzzing in your fork tests, the RPC cache strategy above will not work unless you set a [fuzz seed](https://book.getfoundry.sh/reference/config/testing#seed). You might also want to reduce your number of RPC calls by using [Multicall](https://github.com/mds1/multicall).
+Note that if you are fuzzing in your fork tests, the RPC cache strategy above will not work unless you set a [fuzz seed](https://paritytech.github.io/foundry-book-polkadot/reference/config/testing#seed). You might also want to reduce your number of RPC calls by using [Multicall](https://github.com/mds1/multicall).
 
 ### Summaries
 

src/config/resolc.md

@@ -0,0 +1,35 @@
+## Resolc support
+
+Foundry supports compiling and deploying Solidity contracts to `Asset-Hub Westend` network on Polkadot using the `resolc` compiler.
+
+### 1. Compilation
+
+You can install Resolc by following the instructions [here](https://contracts.polkadot.io/revive_compiler/installation) or [here](https://github.com/paritytech/rvm-rs). If you have `resolc` available in your PATH, foundry will automatically use it.
+
+Otherwise, you can set the path to `resolc` in your `foundry.toml` by adding the following:
+```toml
+[profile.default.resolc]
+resolc_compile = true
+resolc = "path/to/resolc"
+```
+
+`resolc` config value supports 
+  - valid values follow the SemVer format `x.y.z-dev.n`, `resolc:x.y.z-dev.n`
+  - path `path/to/resolc`.
+
+### 3. Deploying
+
+You can deploy Vyper contracts via `forge create` command:
+```bash
+forge create --resolc --legacy --broadcast --rpc-url $RPC_URL --private-key $PRIVATE_KEY  <path to the contract> --constructor-args '1' 
+```
+
+### 4. Solidity scripts
+
+Currently not supported 
+
+### 5. Limitations
+
+- [Working forge commands](https://github.com/paritytech/foundry-polkadot/issues/54#issuecomment-2695723499)
+- [Working cast commands](https://github.com/paritytech/foundry-polkadot/issues/57#issuecomment-2699458251) 
+- [Known issues on `resolc` side](https://contracts.polkadot.io/known_issues/)

src/config/static-analyzers.md

@@ -24,7 +24,7 @@ To run Slither on a single file, use this command:
 slither src/Contract.sol
 ```
 
-Note, this requires configuring the [solc version in the foundry config file](https://book.getfoundry.sh/reference/config/solidity-compiler#solc_version).
+Note, this requires configuring the [solc version in the foundry config file](https://paritytech.github.io/foundry-book-polkadot/reference/config/solidity-compiler#solc_version).
 
 You do not need to provide remappings via the `solc_remaps` option as Slither will automatically detect remappings in a Foundry project. Slither will invoke `forge` to perform the build.
 

src/forge/README.md

@@ -28,7 +28,7 @@ $ forge build
 Compiler run successful!
 ```
 
-Let's [test](https://book.getfoundry.sh/forge/tests#tests) our contracts:
+Let's [test](https://paritytech.github.io/foundry-book-polkadot/forge/tests#tests) our contracts:
 
 ```sh
 $ forge test

src/getting-started/installation.md

@@ -4,40 +4,46 @@ If you encounter any issues during installation, refer to the [FAQ](../faq.md) f
 
 ### Precompiled Binaries
 
-Precompiled binaries can be downloaded from the [GitHub releases page](https://github.com/foundry-rs/foundry/releases). For easier management, we recommend using [Foundryup](#using-foundryup).
+Precompiled binaries can be downloaded from the [GitHub releases page](https://github.com/paritytech/foundry-polkadot/releases). For easier management, we recommend using [Foundryup](#using-foundryup).
 
 ### Using Foundryup
 
-Foundryup is the official installer for the Foundry toolchain. You can learn more about it [here](https://github.com/foundry-rs/foundry/blob/master/foundryup/README.md).
+Foundryup is the official installer for the Foundry toolchain. You can learn more about it [here](https://github.com/paritytech/foundry-polkadot/blob/master/foundryup/README.md).
 
 To install Foundryup, open your terminal and run the following command:
 
 ```sh
-curl -L https://foundry.paradigm.xyz | bash
+curl -L https://raw.githubusercontent.com/paritytech/foundry-polkadot/refs/heads/master/foundryup/install | bash
 ```
 
 This will install Foundryup. Simply follow the on-screen instructions, and the `foundryup` command will become available in your CLI.
 
-Running `foundryup` will automatically install the latest stable version of the [precompiled binaries](#precompiled-binaries): `forge`, `cast`, `anvil`, and `chisel`. If you wish to use the latest `nightly` build run `foundryup --install nightly`. For additional options, such as installing a specific version or commit, run `foundryup --help`.
+Running `foundryup` will automatically install the latest stable version of the [precompiled binaries](#precompiled-binaries): `forge`, `cast`. If you wish to use the latest `nightly` build run `foundryup --install nightly`. For additional options, such as installing a specific version or commit, run `foundryup --help`.
 
 > ℹ️ **Note**  
 > If you're using Windows, you'll need to install and use [Git BASH](https://gitforwindows.org/) or [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) as your terminal, since Foundryup currently doesn't support Powershell or Command Prompt (Cmd).
 
+#### Installing Paritytech fork of foundry 
+
+```
+foundryup --nightly
+```
+
 #### Verify integrity and provenance of binaries
 
 Foundry binaries are attested by using [GitHub artifact attestations](https://docs.github.com/en/actions/security-for-github-actions/using-artifact-attestations/using-artifact-attestations-to-establish-provenance-for-builds). It is strongly recommended to verify the binaries installed using `foundryup` in order to check that they were built and distributed from Foundry repository.  
 For example, `forge` binary integrity and provenance can be verified by running:
 ```shell
-$ gh attestation verify --owner foundry-rs $(which forge)
+$ gh attestation verify --owner paritytech $(which forge)
 
 ✓ Verification succeeded!
 
 The following 1 attestation matched the policy criteria
 
 - Attestation #1
-  - Build repo:..... foundry-rs/foundry
+  - Build repo:..... paritytech/foundry-polkadot
   - Build workflow:. .github/workflows/release.yml@refs/tags/stable
-  - Signer repo:.... foundry-rs/foundry
+  - Signer repo:.... paritytech/foundry-polkadot
   - Signer workflow: .github/workflows/release.yml@refs/tags/stable
 ```
 
@@ -67,30 +73,26 @@ foundryup --path path/to/foundry
 Alternatively, you can install via Cargo with the following command:
 
 ```sh
-cargo install --git https://github.com/foundry-rs/foundry --profile release --locked forge cast chisel anvil
+cargo install --git https://github.com/paritytech/foundry-polkadot --profile release --locked forge cast
 ```
 
-You can also manually build from a local copy of the [Foundry repository](https://github.com/foundry-rs/foundry):
+You can also manually build from a local copy of the [Foundry repository](https://github.com/paritytech/foundry-polkadot):
 
 ```sh
 # clone the repository
-git clone https://github.com/foundry-rs/foundry.git
+git clone https://github.com/paritytech/foundry-polkadot.git
 cd foundry
 # install Forge
 cargo install --path ./crates/forge --profile release --force --locked
 # install Cast
 cargo install --path ./crates/cast --profile release --force --locked
-# install Anvil
-cargo install --path ./crates/anvil --profile release --force --locked
-# install Chisel
-cargo install --path ./crates/chisel --profile release --force --locked
 ```
 
 ### CI Installation with GitHub Actions
 
 For instructions on setting up Foundry in a CI pipeline, refer to the [foundry-rs/foundry-toolchain](https://github.com/foundry-rs/foundry-toolchain) GitHub Action.
 
-### Using Foundry with Docker
+<!-- ### Using Foundry with Docker
 
 Foundry can also be run inside a Docker container. If you don’t have Docker installed, you can download it from [Docker's website](https://docs.docker.com/get-docker/).
 
@@ -109,4 +111,4 @@ docker build -t foundry .
 For examples and guides on using this image, refer to the [Docker guide](../guides/foundry-in-docker).
 
 > ℹ️ **Note**  
-> Some systems, including those with M1 chips, may experience issues when building the Docker image locally. This is a known issue.
+> Some systems, including those with M1 chips, may experience issues when building the Docker image locally. This is a known issue. -->

src/reference/cast/cast.md

@@ -314,4 +314,4 @@ This program is a set of tools to interact with Ethereum and perform conversions
 
 ### BUGS
 
-See <https://github.com/foundry-rs/foundry/issues> for issues.
+See <https://github.com/paritytech/foundry-polkadot/issues> for issues.

src/reference/forge/forge.md

@@ -160,4 +160,4 @@ This program is a set of tools to build, test, fuzz, debug and deploy Solidity s
 
 ### BUGS
 
-See <https://github.com/foundry-rs/foundry/issues> for issues.
+See <https://github.com/paritytech/foundry-polkadot/issues> for issues.