Skip to content

Commit

Permalink
fix precompiles links (#29)
Browse files Browse the repository at this point in the history
  • Loading branch information
andytudhope authored Oct 31, 2023
1 parent 881021a commit 446a3c8
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion docs/builder-solidity.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -76,4 +76,4 @@ This ensures confidentiality **and** improves efficiency, enabling computation t

We recommend [this early research talk from Andrew Miller](https://youtu.be/DhsDFKnHPa0?t=344) to get a sense of the ideas from which builder solidity has grown.

Please note that the pseudo code Andrew shows is now outdated and you are better off learning from our [how to create contracts guide](/how-to/create-contracts/deploy-custom) above, or looking directly at our [list of available precompiles](/technical/specs/rigil/mevm#precompiles). That said, the framework used in this talk and the background provided should still prove useful when writing your own builder solidity contracts.
Please note that the pseudo code Andrew shows is now outdated and you are better off learning from our [how to create contracts guide](/how-to/create-contracts/deploy-custom) above, or looking directly at our [list of available precompiles](/technical/specs/rigil/precompiles). That said, the framework used in this talk and the background provided should still prove useful when writing your own builder solidity contracts.
2 changes: 1 addition & 1 deletion docs/how-to/create-contracts/deploy-custom.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ contract onlyConfidential {
}
```

This contract uses three new [precompiles](/technical/specs/rigil/mevm#precompiles):
This contract uses three new [precompiles](/technical/specs/rigil/precompiles):

1. `isConfidential` to ensure that only the MEVM(s) specified by the user can fetch the confidential data in transactions to this contract.
2. `confidentialInputs` to fetch the confidential data that was submitted along with the transaction that the user sent which specified this contract.
Expand Down
2 changes: 1 addition & 1 deletion docs/how-to/create-precompiles.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ keywords:

# Create a precompile

SUAVE uses [custom precompiles](/technical/specs/rigil/mevm#precompiles) to extend the EVM with specific MEV functions.
SUAVE uses [custom precompiles](/technical/specs/rigil/precompiles) to extend the EVM with specific MEV functions.

In this guide, we will add a new precompile to the [suave-geth client](https://github.com/flashbots/suave-geth) that will be accessible in any builder solidity contract on SUAVE.

Expand Down
2 changes: 1 addition & 1 deletion docs/how-to/send-transactions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Executes a new message call immediately without creating a transaction on the bl

*Parameters*

- `IsConfidential`: Set to true to execute as a confidential request and access the [`MEVM`](/technical/specs/rigil/mevm#precompiles) methods.
- `IsConfidential`: Set to true to execute as a confidential request and access the [`MEVM`](/technical/specs/rigil/precompiles) methods.
- `ExecutionAddress`: `address` - (optional) The execution address that performs the execution.

3. **eth_executionAddress**
Expand Down

0 comments on commit 446a3c8

Please sign in to comment.