-
Notifications
You must be signed in to change notification settings - Fork 2k
Add Aptos local CRE read/write support with write CI coverage #21766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
7075610
d8bdcc0
3a7fa0c
f917c51
ec1e8f0
727d145
32864c5
28c4b2d
aebe98f
7a7f416
d76523b
2d2b730
7e52ae2
2804116
f440911
d8a4e15
00c2969
190626b
d04ec38
c94d6c4
2f813dd
b15e7ea
9aaf1b5
bad2208
2d0c4aa
680c73e
6fbda29
fdea90f
fc68c50
8c79697
f988108
959d292
8f941c7
a7259f1
61b58f1
b8c1d30
b8c4566
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| --- | ||
| "chainlink": patch | ||
| --- | ||
|
|
||
| #internal | ||
|
|
||
| Add Aptos local CRE read/write support, including Capabilities Registry OCR config for Aptos write and CI coverage for the Aptos write roundtrip and expected-failure scenarios. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,79 @@ | ||
| # Same as workflow-gateway-don.toml but with Aptos chain and a single Aptos capability. | ||
| # Anvil 1337: registry and gateway. Aptos: local devnet (chain_id 4). Run: env config path <this file>, then env start. | ||
|
|
||
| [[blockchains]] | ||
| type = "anvil" | ||
| chain_id = "1337" | ||
| container_name = "anvil-1337" | ||
| docker_cmd_params = ["-b", "0.5", "--mixed-mining"] | ||
|
|
||
| [[blockchains]] | ||
| type = "aptos" | ||
| chain_id = "4" | ||
|
|
||
| [jd] | ||
| csa_encryption_key = "d1093c0060d50a3c89c189b2e485da5a3ce57f3dcb38ab7e2c0d5f0bb2314a44" | ||
| # change to your version | ||
| image = "job-distributor:0.22.1" | ||
|
|
||
| #[s3provider] | ||
| # # use all defaults | ||
| # port = 9000 | ||
| # console_port = 9001 | ||
|
|
||
| [infra] | ||
| # either "docker" or "kubernetes" | ||
| type = "docker" | ||
|
|
||
| [[nodesets]] | ||
| nodes = 4 | ||
| name = "workflow" | ||
| don_types = ["workflow"] | ||
| override_mode = "all" | ||
| http_port_range_start = 10100 | ||
|
|
||
| # Keep the registry chain (1337) in node TOML even though this DON's chain-scoped | ||
| # capability is Aptos-only; the workflow stack still needs the EVM registry chain. | ||
| supported_evm_chains = [1337] | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what does this do for aptos?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. let me respond to this one: since this don doesn't have any capability that runs on chain 1337 that's the way to explicitly instruct the code to weave 1337 RPC in node's TOML config. We need it since that's the registry chain and workflow DON needs to access it. |
||
| # Workflow runtime limits still need both the EVM registry chain and the Aptos chain selector. | ||
| env_vars = { CL_CRE_SETTINGS_DEFAULT = '{"PerWorkflow":{"CapabilityCallTimeout":"5m0s","ChainAllowed":{"Default":"false","Values":{"1337":"true","4457093679053095497":"true"}}}}' } | ||
| capabilities = ["cron", "consensus", "aptos-4"] | ||
| registry_based_launch_allowlist = ["cron-trigger@1.0.0"] | ||
|
|
||
| [nodesets.db] | ||
| image = "postgres:12.0" | ||
| port = 13000 | ||
|
|
||
| [[nodesets.node_specs]] | ||
| roles = ["plugin"] | ||
| [nodesets.node_specs.node] | ||
| docker_ctx = "../../../.." | ||
| docker_file = "core/chainlink.Dockerfile" | ||
| docker_build_args = { "CL_IS_PROD_BUILD" = "false" } | ||
| # image = "chainlink-tmp:latest" | ||
| user_config_overrides = "" | ||
|
|
||
| [[nodesets]] | ||
| nodes = 1 | ||
| name = "bootstrap-gateway" | ||
| don_types = ["bootstrap", "gateway"] | ||
| override_mode = "each" | ||
| http_port_range_start = 10300 | ||
|
|
||
| supported_evm_chains = [1337] | ||
|
|
||
| [nodesets.db] | ||
| image = "postgres:12.0" | ||
| port = 13200 | ||
|
|
||
| [[nodesets.node_specs]] | ||
| roles = ["bootstrap", "gateway"] | ||
| [nodesets.node_specs.node] | ||
| docker_ctx = "../../../.." | ||
| docker_file = "core/chainlink.Dockerfile" | ||
| docker_build_args = { "CL_IS_PROD_BUILD" = "false" } | ||
| # 5002 is the web API capabilities port for incoming requests | ||
| # 15002 is the vault port for incoming requests | ||
| custom_ports = ["5002:5002", "15002:15002"] | ||
| # image = "chainlink-tmp:latest" | ||
| user_config_overrides = "" | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how did you choose the topology, what is workflow-gateway-aptos, should we define a new topologu like for Solana?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kept
workflow-gateway-aptoshere. This topology does include a gateway, and the Aptos-specific label helps distinguish it from the existing EVM-oriented workflow-gateway variants rather than implying a brand new topology family.