From 9f9a61791d6d8c74adb86bf237f4a8a0f89b0d7e Mon Sep 17 00:00:00 2001 From: andytudhope <13001517+andytudhope@users.noreply.github.com> Date: Sat, 6 Jul 2024 16:17:34 +0200 Subject: [PATCH] up-to-date with latest --- docs/concepts/block-building.mdx | 2 +- docs/concepts/confidential-computation.mdx | 4 ++-- docs/concepts/rpc-differences.mdx | 10 +++++----- docs/index.mdx | 14 +++++++------- docs/sidebars.js | 8 ++++---- docs/toliman.mdx | 8 ++++---- docs/tools/golang-sdk.mdx | 2 +- docs/tools/tools-resources.mdx | 0 docs/tools/typescript-sdk.mdx | 8 +++++--- docs/tutorials/create-precompiles.mdx | 4 ++-- docs/tutorials/cross-chain.mdx | 2 +- docs/tutorials/run-suave.mdx | 6 +++--- docs/tutorials/suappify-counter.mdx | 6 ++++-- docs/tutorials/using-testnet.mdx | 6 +++--- src/components/RPCButton/index.tsx | 10 +++++----- 15 files changed, 47 insertions(+), 43 deletions(-) delete mode 100644 docs/tools/tools-resources.mdx diff --git a/docs/concepts/block-building.mdx b/docs/concepts/block-building.mdx index a2a6222e..29e9b514 100644 --- a/docs/concepts/block-building.mdx +++ b/docs/concepts/block-building.mdx @@ -67,7 +67,7 @@ function buildEthBlock(BuildBlockArgs memory blockArgs, DataId dataId, string me As the name suggests, we only support building blocks on Ethereum L1 for now. This will change as SUAVE matures. -All of these functions utilize the SUAVE Execution Namespace. To understand more about this, please consult the [Execution Namespace specification](/technical/specs/rigil/mevm.md#suavex-namespace). +All of these functions utilize the SUAVE Execution Namespace. To understand more about this, please consult the [Execution Namespace specification](/technical/specs/toliman/mevm.md#suavex-namespace). ## Bundles diff --git a/docs/concepts/confidential-computation.mdx b/docs/concepts/confidential-computation.mdx index bdc96261..633f74cb 100644 --- a/docs/concepts/confidential-computation.mdx +++ b/docs/concepts/confidential-computation.mdx @@ -5,7 +5,7 @@ description: How to understand confidential computation on SUAVE and use it to y Confidential computation enables you to handle orderflow privately and securely. -In SUAVE, we achieve this with [Kettles](/technical/specs/rigil/kettle#confidential-computation) performing compute offchain, but according to smart contracts written onchain. In this way, offchain compute is not constrained by chain consensus. The Kettles will eventually run in [TEEs](https://www.youtube.com/watch?v=ek-bu4aoh0A), which provide both **enhanced privacy** (no-one, not even the host OS, can see unencrypted data) and **integrity** (you can be sure the correct code, and only that code, is running at all times). +In SUAVE, we achieve this with [Kettles](/technical/specs/toliman/kettle#confidential-computation) performing compute offchain, but according to smart contracts written onchain. In this way, offchain compute is not constrained by chain consensus. The Kettles will eventually run in [TEEs](https://www.youtube.com/watch?v=ek-bu4aoh0A), which provide both **enhanced privacy** (no-one, not even the host OS, can see unencrypted data) and **integrity** (you can be sure the correct code, and only that code, is running at all times). ## Interface @@ -27,7 +27,7 @@ Once the MEVM has the confidential inputs, there is any number of things you cou function extractHint(bytes memory bundleData) internal view returns (bytes memory) ``` -You can also consult [our technical specs](/technical/specs/rigil/kettle#confidential-computation) for further information about confidential computation if required. +You can also consult [our technical specs](/technical/specs/toliman/kettle#confidential-computation) for further information about confidential computation if required. ### Computing over Confidential Data diff --git a/docs/concepts/rpc-differences.mdx b/docs/concepts/rpc-differences.mdx index 35e574d9..dc4cf8d7 100644 --- a/docs/concepts/rpc-differences.mdx +++ b/docs/concepts/rpc-differences.mdx @@ -15,7 +15,7 @@ Creates a new message call transaction or a contract creation for any signed `Co Executes a new message call immediately without creating a transaction on the block chain. It follows the same format as the default `eth_call` with two extra parameters: -- `IsConfidential`: Set to true to execute as a confidential request and access the [`MEVM`](/technical/specs/rigil/precompiles) methods. +- `IsConfidential`: Set to true to execute as a confidential request and access the [`MEVM`](/technical/specs/toliman/precompiles) methods. - `ExecutionAddress`: `address` - (optional) The execution address that performs the execution. 3. **eth_kettleAddress** @@ -32,7 +32,7 @@ The easiest way to test your connection to an RPC endpoint is via a simple curl curl -X POST \ -H "Content-Type: application/json" \ --data '{"jsonrpc":"2.0","method":"eth_kettleAddress","params":[],"id":1}' \ - https://rpc.rigil.suave.flashbots.net + https://rpc.toliman.suave.flashbots.net ``` #### Local curl request @@ -57,7 +57,7 @@ Note that the only difference between these two is the URL at the end of the cur ### SUAVE Transactions -The example above follows the [exact same API interface](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-eth) as the original go-ethereum client. However, if we grab a random transaction hash from the [Rigil Explorer](https://explorer.rigil.suave.flashbots.net/), we can see the core difference with the SUAVE Rigil RPC: a new SUAVE transaction type. +The example above follows the [exact same API interface](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-eth) as the original go-ethereum client. However, if we grab a random transaction hash from the [Rigil Explorer](https://explorer.toliman.suave.flashbots.net/), we can see the core difference with the SUAVE Rigil RPC: a new SUAVE transaction type. #### Remote curl request @@ -72,7 +72,7 @@ curl -X POST \ ], "id": 1 }' \ - https://rpc.rigil.suave.flashbots.net + https://rpc.toliman.suave.flashbots.net ``` #### Response @@ -112,4 +112,4 @@ This response has a couple fields that aren't in your traditional Ethereum trans - `executionNode` - `requestRecord` -To dive deeper into these differences checkout the [SUAVE chain specs](../technical/specs/rigil/suave-chain.md). +To dive deeper into these differences checkout the [SUAVE chain specs](../technical/specs/toliman/suave-chain.md). diff --git a/docs/index.mdx b/docs/index.mdx index c47b54d6..39c59c56 100644 --- a/docs/index.mdx +++ b/docs/index.mdx @@ -14,7 +14,7 @@ keywords: :::info -SUAVE is currently in early alpha. The first testnet is called Rigil. Please be aware that your data will likely not persist, and that Rigil is not yet fully confidential or secure. Happy hacking! +SUAVE is currently in early alpha. The second testnet is called Toliman. Please be aware that your data will likely not persist, and that Toliman is not yet fully confidential or secure. Happy hacking! ::: @@ -25,8 +25,8 @@ SUAVE is currently in early alpha. The first testnet is called Rigil. Please be
- - + --> +
What is SUAVE?
@@ -90,7 +90,7 @@ SUAVE is currently in early alpha. The first testnet is called Rigil. Please be
- + -