Skip to content

Commit c7febee

Browse files
khadnikhadni
authored
Wf deployments & link key clarifications (#3157)
* clarifications * clarifications * clarifications * clarifications
1 parent 914035a commit c7febee

File tree

5 files changed

+72
-29
lines changed

5 files changed

+72
-29
lines changed

‎reports/llms-report.json‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
11
{
2-
"startedAt": "2025-11-11T12:13:25.939Z",
2+
"startedAt": "2025-11-11T14:46:04.493Z",
33
"siteBase": "https://docs.chain.link",
44
"sections": [
55
{
66
"section": "cre-go",
77
"pagesProcessed": 84,
88
"outputPath": "src/content/cre/llms-full-go.txt",
9-
"bytes": 632196,
10-
"prevBytes": 631871,
11-
"deltaBytes": 325
9+
"bytes": 633220,
10+
"prevBytes": 633200,
11+
"deltaBytes": 20
1212
},
1313
{
1414
"section": "cre-ts",
1515
"pagesProcessed": 79,
1616
"outputPath": "src/content/cre/llms-full-ts.txt",
17-
"bytes": 587662,
18-
"prevBytes": 587337,
19-
"deltaBytes": 325
17+
"bytes": 588686,
18+
"prevBytes": 588666,
19+
"deltaBytes": 20
2020
},
2121
{
2222
"section": "vrf",
@@ -123,5 +123,5 @@
123123
"deltaBytes": 0
124124
}
125125
],
126-
"finishedAt": "2025-11-11T12:13:30.721Z"
126+
"finishedAt": "2025-11-11T14:46:10.875Z"
127127
}

‎src/content/cre/guides/operations/deploying-workflows.mdx‎

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The `cre workflow deploy` command handles the entire end-to-end process for you:
3434

3535
1. **Compiles** your workflow to a WASM binary.
3636
1. **Uploads** the compiled binary and any associated configuration files (like your config file or `secrets.yaml`) to the CRE Storage Service.
37-
1. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract. This transaction contains the metadata for your workflow, including its name, owner, and the URL of its artifacts in the storage service.
37+
1. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract on **Ethereum Mainnet**. Your wallet must have ETH for gas fees, and your `project.yaml` must include an RPC configuration for `ethereum-mainnet` (e.g., `https://ethereum-rpc.publicnode.com`). This transaction contains the metadata for your workflow, including its name, owner, and the URL of its artifacts in the storage service.
3838

3939
{/* prettier-ignore */}
4040
<Aside type="caution" title="Early Access: Disclaimer">
@@ -103,8 +103,8 @@ Uploading files...
103103
Preparing deployment transaction...
104104
Preparing transaction for workflowID: <your-workflow-id>
105105
Transaction details:
106-
Chain Name: ethereum-testnet-sepolia
107-
To: 0xF3f93fc4dc177748E7557568b5354cB009e3818a
106+
Chain Name: ethereum-mainnet
107+
To: 0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5
108108
Function: UpsertWorkflow
109109
Inputs:
110110
[0]: my-workflow
@@ -125,12 +125,12 @@ Estimated Cost:
125125
No
126126

127127
Transaction confirmed
128-
View on explorer: https://sepolia.etherscan.io/tx/0x58599f6...d916b
128+
View on explorer: https://etherscan.io/tx/0x58599f6...d916b
129129

130130
[OK] Workflow deployed successfully
131131

132132
Details:
133-
Contract address: 0xF3f93fc4dc177748E7557568b5354cB009e3818a
133+
Contract address: 0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5
134134
Transaction hash: 0x58599f6...d916b
135135
Workflow Name: my-workflow
136136
Workflow ID: <your-workflow-id>
@@ -146,9 +146,11 @@ Details:
146146

147147
## Verifying your deployment
148148

149-
After a successful deployment, you can verify that your workflow was registered correctly by checking the Workflow Registry contract on a block explorer. The CLI output will provide the transaction hash for the registration.
149+
After a successful deployment, you can verify that your workflow was registered correctly in two ways:
150150

151-
The `WorkflowRegistry` contract for the `production-settings` environment is deployed on **Ethereum Sepolia** at the address <a href="https://sepolia.etherscan.io/address/0xF3f93fc4dc177748E7557568b5354cB009e3818a" target="_blank" rel="noopener noreferrer">`0xF3f93fc4dc177748E7557568b5354cB009e3818a`</a>.
151+
1. **CRE UI**: View your deployed workflow in the [CRE platform](https://cre.chain.link). Navigate to the **Workflows** section to see your workflow's status, ID, and execution history.
152+
153+
1. **Block Explorer**: Check the Workflow Registry contract on a block explorer. The CLI output will provide the transaction hash for the registration. The `WorkflowRegistry` contract is deployed on **Ethereum Mainnet** at the address <a href="https://etherscan.io/address/0x4ac54353fa4fa961afcc5ec4b118596d3305e7e5#code" target="_blank" rel="noopener noreferrer">`0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5`</a>.
152154

153155
## Using multi-sig wallets
154156

‎src/content/cre/llms-full-go.txt‎

Lines changed: 21 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4831,7 +4831,7 @@ The `cre workflow deploy` command handles the entire end-to-end process for you:
48314831

48324832
1. **Compiles** your workflow to a WASM binary.
48334833
2. **Uploads** the compiled binary and any associated configuration files (like your config file or `secrets.yaml`) to the CRE Storage Service.
4834-
3. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract. This transaction contains the metadata for your workflow, including its name, owner, and the URL of its artifacts in the storage service.
4834+
3. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract on **Ethereum Mainnet**. Your wallet must have ETH for gas fees, and your `project.yaml` must include an RPC configuration for `ethereum-mainnet` (e.g., `https://ethereum-rpc.publicnode.com`). This transaction contains the metadata for your workflow, including its name, owner, and the URL of its artifacts in the storage service.
48354835

48364836

48374837
<Aside type="caution" title="Early Access: Disclaimer">
@@ -4900,8 +4900,8 @@ Uploading files...
49004900
Preparing deployment transaction...
49014901
Preparing transaction for workflowID: <your-workflow-id>
49024902
Transaction details:
4903-
Chain Name: ethereum-testnet-sepolia
4904-
To: 0xF3f93fc4dc177748E7557568b5354cB009e3818a
4903+
Chain Name: ethereum-mainnet
4904+
To: 0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5
49054905
Function: UpsertWorkflow
49064906
Inputs:
49074907
[0]: my-workflow
@@ -4922,12 +4922,12 @@ Estimated Cost:
49224922
No
49234923

49244924
Transaction confirmed
4925-
View on explorer: https://sepolia.etherscan.io/tx/0x58599f6...d916b
4925+
View on explorer: https://etherscan.io/tx/0x58599f6...d916b
49264926

49274927
[OK] Workflow deployed successfully
49284928

49294929
Details:
4930-
Contract address: 0xF3f93fc4dc177748E7557568b5354cB009e3818a
4930+
Contract address: 0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5
49314931
Transaction hash: 0x58599f6...d916b
49324932
Workflow Name: my-workflow
49334933
Workflow ID: <your-workflow-id>
@@ -4943,9 +4943,11 @@ Details:
49434943

49444944
## Verifying your deployment
49454945

4946-
After a successful deployment, you can verify that your workflow was registered correctly by checking the Workflow Registry contract on a block explorer. The CLI output will provide the transaction hash for the registration.
4946+
After a successful deployment, you can verify that your workflow was registered correctly in two ways:
4947+
4948+
1. **CRE UI**: View your deployed workflow in the [CRE platform](https://cre.chain.link). Navigate to the **Workflows** section to see your workflow's status, ID, and execution history.
49474949

4948-
The `WorkflowRegistry` contract for the `production-settings` environment is deployed on **Ethereum Sepolia** at the address <a href="https://sepolia.etherscan.io/address/0xF3f93fc4dc177748E7557568b5354cB009e3818a" target="_blank" rel="noopener noreferrer">`0xF3f93fc4dc177748E7557568b5354cB009e3818a`</a>.
4950+
2. **Block Explorer**: Check the Workflow Registry contract on a block explorer. The CLI output will provide the transaction hash for the registration. The `WorkflowRegistry` contract is deployed on **Ethereum Mainnet** at the address <a href="https://etherscan.io/address/0x4ac54353fa4fa961afcc5ec4b118596d3305e7e5#code" target="_blank" rel="noopener noreferrer">`0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5`</a>.
49494951

49504952
## Using multi-sig wallets
49514953

@@ -7251,9 +7253,21 @@ For a complete step-by-step guide with examples, see [Linking Wallet Keys](/cre/
72517253
- **Must run from a project directory** with a `project.yaml` file
72527254
- **`.env` must contain `CRE_ETH_PRIVATE_KEY`** — Your wallet's private key
72537255
- **Wallet must be funded** with ETH on Ethereum Mainnet to pay gas fees
7256+
- **RPC endpoint configured** — Add an `ethereum-mainnet` RPC URL in your `project.yaml` under the `rpcs` section for your target (e.g., `https://ethereum-rpc.publicnode.com` or your preferred provider)
72547257
- **For multi-sig wallets**: Also specify `workflow-owner-address` in your `project.yaml` under the `account` section. See [Linking Wallet Keys](/cre/organization/linking-keys#using-multi-sig-wallets) for details.
72557258
</Aside>
72567259

7260+
7261+
<Aside type="note" title="Transaction is sent to Ethereum Mainnet">
7262+
This command always submits a transaction to **Ethereum Mainnet**, regardless of your workflow deployment environment. Ensure your wallet has sufficient ETH for gas fees and your `project.yaml` includes an RPC configuration for `ethereum-mainnet`:
7263+
7264+
```yaml
7265+
rpcs:
7266+
- chain-name: ethereum-mainnet
7267+
url: https://ethereum-rpc.publicnode.com # Or your preferred RPC provider
7268+
```
7269+
</Aside>
7270+
72577271
**Usage:**
72587272

72597273
```bash

‎src/content/cre/llms-full-ts.txt‎

Lines changed: 21 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3748,7 +3748,7 @@ The `cre workflow deploy` command handles the entire end-to-end process for you:
37483748

37493749
1. **Compiles** your workflow to a WASM binary.
37503750
2. **Uploads** the compiled binary and any associated configuration files (like your config file or `secrets.yaml`) to the CRE Storage Service.
3751-
3. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract. This transaction contains the metadata for your workflow, including its name, owner, and the URL of its artifacts in the storage service.
3751+
3. **Registers** the workflow onchain by submitting a transaction to the Workflow Registry contract on **Ethereum Mainnet**. Your wallet must have ETH for gas fees, and your `project.yaml` must include an RPC configuration for `ethereum-mainnet` (e.g., `https://ethereum-rpc.publicnode.com`). This transaction contains the metadata for your workflow, including its name, owner, and the URL of its artifacts in the storage service.
37523752

37533753

37543754
<Aside type="caution" title="Early Access: Disclaimer">
@@ -3817,8 +3817,8 @@ Uploading files...
38173817
Preparing deployment transaction...
38183818
Preparing transaction for workflowID: <your-workflow-id>
38193819
Transaction details:
3820-
Chain Name: ethereum-testnet-sepolia
3821-
To: 0xF3f93fc4dc177748E7557568b5354cB009e3818a
3820+
Chain Name: ethereum-mainnet
3821+
To: 0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5
38223822
Function: UpsertWorkflow
38233823
Inputs:
38243824
[0]: my-workflow
@@ -3839,12 +3839,12 @@ Estimated Cost:
38393839
No
38403840

38413841
Transaction confirmed
3842-
View on explorer: https://sepolia.etherscan.io/tx/0x58599f6...d916b
3842+
View on explorer: https://etherscan.io/tx/0x58599f6...d916b
38433843

38443844
[OK] Workflow deployed successfully
38453845

38463846
Details:
3847-
Contract address: 0xF3f93fc4dc177748E7557568b5354cB009e3818a
3847+
Contract address: 0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5
38483848
Transaction hash: 0x58599f6...d916b
38493849
Workflow Name: my-workflow
38503850
Workflow ID: <your-workflow-id>
@@ -3860,9 +3860,11 @@ Details:
38603860

38613861
## Verifying your deployment
38623862

3863-
After a successful deployment, you can verify that your workflow was registered correctly by checking the Workflow Registry contract on a block explorer. The CLI output will provide the transaction hash for the registration.
3863+
After a successful deployment, you can verify that your workflow was registered correctly in two ways:
3864+
3865+
1. **CRE UI**: View your deployed workflow in the [CRE platform](https://cre.chain.link). Navigate to the **Workflows** section to see your workflow's status, ID, and execution history.
38643866

3865-
The `WorkflowRegistry` contract for the `production-settings` environment is deployed on **Ethereum Sepolia** at the address <a href="https://sepolia.etherscan.io/address/0xF3f93fc4dc177748E7557568b5354cB009e3818a" target="_blank" rel="noopener noreferrer">`0xF3f93fc4dc177748E7557568b5354cB009e3818a`</a>.
3867+
2. **Block Explorer**: Check the Workflow Registry contract on a block explorer. The CLI output will provide the transaction hash for the registration. The `WorkflowRegistry` contract is deployed on **Ethereum Mainnet** at the address <a href="https://etherscan.io/address/0x4ac54353fa4fa961afcc5ec4b118596d3305e7e5#code" target="_blank" rel="noopener noreferrer">`0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5`</a>.
38663868

38673869
## Using multi-sig wallets
38683870

@@ -5893,9 +5895,21 @@ For a complete step-by-step guide with examples, see [Linking Wallet Keys](/cre/
58935895
- **Must run from a project directory** with a `project.yaml` file
58945896
- **`.env` must contain `CRE_ETH_PRIVATE_KEY`** — Your wallet's private key
58955897
- **Wallet must be funded** with ETH on Ethereum Mainnet to pay gas fees
5898+
- **RPC endpoint configured** — Add an `ethereum-mainnet` RPC URL in your `project.yaml` under the `rpcs` section for your target (e.g., `https://ethereum-rpc.publicnode.com` or your preferred provider)
58965899
- **For multi-sig wallets**: Also specify `workflow-owner-address` in your `project.yaml` under the `account` section. See [Linking Wallet Keys](/cre/organization/linking-keys#using-multi-sig-wallets) for details.
58975900
</Aside>
58985901

5902+
5903+
<Aside type="note" title="Transaction is sent to Ethereum Mainnet">
5904+
This command always submits a transaction to **Ethereum Mainnet**, regardless of your workflow deployment environment. Ensure your wallet has sufficient ETH for gas fees and your `project.yaml` includes an RPC configuration for `ethereum-mainnet`:
5905+
5906+
```yaml
5907+
rpcs:
5908+
- chain-name: ethereum-mainnet
5909+
url: https://ethereum-rpc.publicnode.com # Or your preferred RPC provider
5910+
```
5911+
</Aside>
5912+
58995913
**Usage:**
59005914

59015915
```bash

‎src/content/cre/reference/cli/account.mdx‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,22 @@ For a complete step-by-step guide with examples, see [Linking Wallet Keys](/cre/
3434
- **Must run from a project directory** with a `project.yaml` file
3535
- **`.env` must contain `CRE_ETH_PRIVATE_KEY`** — Your wallet's private key
3636
- **Wallet must be funded** with ETH on Ethereum Mainnet to pay gas fees
37+
- **RPC endpoint configured** — Add an `ethereum-mainnet` RPC URL in your `project.yaml` under the `rpcs` section for your target (e.g., `https://ethereum-rpc.publicnode.com` or your preferred provider)
3738
- **For multi-sig wallets**: Also specify `workflow-owner-address` in your `project.yaml` under the `account` section. See [Linking Wallet Keys](/cre/organization/linking-keys#using-multi-sig-wallets) for details.
3839
</Aside>
3940

41+
{/* prettier-ignore */}
42+
<Aside type="note" title="Transaction is sent to Ethereum Mainnet">
43+
This command always submits a transaction to **Ethereum Mainnet**, regardless of your workflow deployment environment. Ensure your wallet has sufficient ETH for gas fees and your `project.yaml` includes an RPC configuration for `ethereum-mainnet`:
44+
45+
```yaml
46+
rpcs:
47+
- chain-name: ethereum-mainnet
48+
url: https://ethereum-rpc.publicnode.com # Or your preferred RPC provider
49+
```
50+
51+
</Aside>
52+
4053
**Usage:**
4154
4255
```bash

0 commit comments

Comments
 (0)