cdk/get-started/quick-start/quickstart/deploy-stack/ #380

2024-04-23T06:17:27Z

giscus[bot]
bot Apr 23, 2024

cdk/get-started/quick-start/quickstart/deploy-stack/

https://docs.polygon.technology/cdk/get-started/quick-start/quickstart/deploy-stack/

Ljiacheng · 2024-04-23T06:17:28Z

Ljiacheng
Apr 23, 2024 — with giscus

Get error when run command:
kurtosis run --enclave cdk-v1 --args-file params.yml --image-download always .

There was an error interpreting Starlark code 
Evaluation error: An error occurred while loading the module 'github.com/kurtosis-tech/ethereum-package/[email protected]'
        Caused by: Error in cloning git repository 'https://github.com/kurtosis-tech/ethereum-package.git' to '/kurtosis-data/tmp-repositories/tmp-repo-dir-3456415713/kurtosis-tech/ethereum-package'. Make sure that 'https://github.com/kurtosis-tech/ethereum-package.git' exists or if it's a private repository, that you are logged into GitHub via `kurtosis github login`.
        at [github.com/0xPolygon/kurtosis-cdk/ethereum.star:1:33]: <toplevel>
        at [github.com/0xPolygon/kurtosis-cdk/main.star:1:33]: <toplevel>

Error encountered running Starlark code.

I can see that this package exsists on github but still can't run this.

7 replies

Ljiacheng Apr 24, 2024 — with giscus

@kmurphypolygon, this problem also appears with other packages(e.g. prometheus-package) from github. I think it is my network error fixed with proxy and after a few retries, thanks for your reply.
But I have a new problem. I changed the l1_rpc_url to my local chain, and set deploy_l1: false in the params.yml. In the file cdk_bridge_infra.star the code try to find a server called el-1-geth-lighthouse. But it can't find it, did anything wrong with my work?

Ljiacheng Apr 24, 2024 — with giscus

Ok, I find the server el-1-geth-lighthouse was started by ethereum.star. If I run l1 node by my self, I have to change some code which use this service.

kmurphypolygon Apr 24, 2024

Sounds like you made the correct configuration change. That's awesome. :)

Gyan313 Apr 30, 2024 — with giscus

Hi, @Ljiacheng. I am encountering somewhat same error you did with this command...
kurtosis run --enclave cdk-v1 --args-file params.yml --image-download always ..
You can find more about error I am getting on this issue I opened here ----> #416.
Can you tell me how did you resolved the error? Please help.

kmurphypolygon May 7, 2024

Looks like a kurtosis cli version issue.

Ljiacheng · 2024-04-25T08:15:20Z

Ljiacheng
Apr 25, 2024 — with giscus

After running this process. I try to use zkevm-bridge-ui for test. The transaction successfully confirmed by layer 1 node.
But the bridge details allways be Pending. How long it takes or should I claim it in layer2?

8 replies

Ljiacheng Apr 26, 2024 — with giscus

I actually run kurtosis clean -a every time before the full process.
I tried to run this deploy command:

kurtosis service exec cdk-v1 contracts-001 "printf \"[profile.default]\nsrc = 'contracts'\nout = 'out'\nlibs = ['node_modules']\n\" > foundry.toml"
kurtosis service exec cdk-v1 contracts-001 "forge create \
    --json \
    --rpc-url \"http://127.0.0.1:33181\" \
    --mnemonic \"code code code code code code code code code code code quality\" \
    contracts/mocks/ERC20PermitMock.sol:ERC20PermitMock \
    --constructor-args  \"CDK Gas Token\" \"CDK\" \"0xE34aaF64b29273B7D567FCFc40544c014EEe9970\" \"1000000000000000000000000\" > gasToken-erc20.json"

with some values changed to my actuall environment. It still output same network error.

My forge -V output is: forge 0.2.0 (563e0624 2024-03-26T08:36:54.002567423Z).
Is this version incorrect?

kmurphypolygon Apr 26, 2024

Hi, I'm just wondering where you get those kurtosis service exec cdk-v1.. commands from and what you're trying to do with them? The deploy command is given with run... Make sure all your components are running by looking at the logs. If you're going to bridge a token you will need to run the full enclave.

The forge version looks OK.

Ljiacheng Apr 26, 2024 — with giscus

Ok, first I run the command kurtosis run --enclave cdk-v1 --args-file params.yml --image-download always . and the enclave is running.
Then I can interact with service contracts-001 through kurtosis service exec cdk-v1 contracts-001 "command"

kmurphypolygon Apr 26, 2024

OK, we're giving another instruction to open a shell and interact with a service, .e.g kurtosis service shell cdk-v1 zkevm-node-sequencer-001 ... maybe this helps, if not, I would ask the devs on Discord, they might be able to help...

kmurphypolygon Apr 26, 2024

Or maybe you could raise an issue on the Kurtosis repo, this might be better.

Gyan313 · 2024-04-26T17:37:28Z

Gyan313
Apr 26, 2024 — with giscus

I am trying to deploy the CDK stack on my local machine using the Ubuntu distro.
As I reached the Check port mapping section of the page and ran the command...
kurtosis port print cdk-v1 zkevm-node-rpc-001 http-rpc
I encountered an error, which is...

  Caused by: An error occurred calling the run function for command 'print'
  Caused by: An error occurred while getting service context for service with identifier 'zkevm-node-rpc-001'
  Caused by: An error occurred when trying to get info for service 'zkevm-node-rpc-001'
  Caused by: rpc error: code = Unknown desc = Failed to get service info for service 'zkevm-node-rpc-001'
  Caused by: An error occurred getting info for service 'zkevm-node-rpc-001'
  Caused by: An error occurred while fetching registration for service identifier 'zkevm-node-rpc-001'
  Caused by: An error occurred while fetching name for service identifier 'zkevm-node-rpc-001'
  Caused by: Couldn't find a matching service name for identifier 'zkevm-node-rpc-001'

How to resolve it any idea?

1 reply

kmurphypolygon May 7, 2024

Hi, could you check out this issue for info: #416. Basically you need to make sure you're running 0.88.19 kurtosis cli.

THECRYPTOTOM · 2024-04-26T17:48:17Z

THECRYPTOTOM
Apr 26, 2024 — with giscus

I'm having the same issue. Plz advice

1 reply

kmurphypolygon May 7, 2024

Check out your kurtosis cli version, it should be 0.88.19 ...

dongjl123 · 2024-04-28T08:20:00Z

dongjl123
Apr 28, 2024 — with giscus

I have set up the node , but when I access the bridge-ui, it responses "We cannot connect to the Ethereum node". The request url is "http://xxx.xxx.xxx.xx:32811/l1rpc", and response status code is "405 Not Allowed". How can I solve it?

2 replies

Ljiacheng Apr 29, 2024 — with giscus

Maybe you should open url of server zkevm-bridge-proxy-001 instead of zkevm-bridge-ui-001?

kmurphypolygon May 7, 2024

We made some updates to the bridge code and docs yesterday, please update your code and try again.

Ljiacheng · 2024-04-29T02:43:07Z

Ljiacheng
Apr 29, 2024 — with giscus

Hi, @kmurphypolygon, I have some questions about the cdk deployments:

What's the difference between POL(deployed by prepareTestent.ts) and gasToken(deployed by set zkevm_use_gas_token_contract: true) ?
Can I just set POL address to gasTokenAddress in file create_rollup_parameters.json which means use POL as zkevm l2 gas token?
If I want to run a production environment(real prover), what configs should I change(e.g. contracts/nodes/provers)?

2 replies

Ljiacheng Apr 29, 2024 — with giscus

Follow the document Incentive mechanism, I guess that gasToken equals to L2 Bridge Ether and POL equals to MATIC.
But I'm curious about how does sequencer know the price about L2 Bridge Ether and MATIC to ensure l2TotalGasFee is enough? Is there any oracle mechanism?

kmurphypolygon May 7, 2024

Hi there, there is a complicated gas estimation mechanism in place. You can read about it here: https://docs.polygon.technology/zkEVM/architecture/effective-gas/

Ljiacheng · 2024-06-05T09:01:30Z

Ljiacheng
Jun 5, 2024 — with giscus

I try to deploy zkevm-node service in my local environment, and try to fund zkevm_l2_claimtxmanager_address at layer2:

cast send --legacy \
--value 10ether \
--private-key 0x12d7de8621a77640c9241b2595ba78ce443d05e94090365ab3bb5e19df82c625 \
--rpc-url "http://127.0.0.1:8123" \
"0x5f5dB0D4D58310F53713eF4Df80ba6717868A9f8"

Then get error:

Error: 
server returned an error response: error code -32000: gas price too low

If I add --gas-price 1000000000 to the command, I get another error:

Error:
server returned an error response: error code -32000: L1 gas price 0

Is there any special gas config should be set for zkevm-node?

4 replies

kmurphypolygon Jun 5, 2024

Hi there @Ljiacheng can we double check which set of instructions you are following please?

For a quick check, we suggest confirming your network is setup to allow zero priced tx and/or to fund from a pre-allocated account. Check in the config:
https://github.com/0xPolygon/kurtosis-cdk/blob/main/templates/trusted-node/node-config.toml

Let us know how you get on.

Ljiacheng Jun 6, 2024 — with giscus

I just copy config from the document. Follow the comment, EthTransferGasPrice and EthTransferL1GasPriceFactor can't be both zero?
I'm not sure which config allow zero priced tx.

kmurphypolygon Jun 6, 2024

Let me check for you, back soon :)

leovct Jun 6, 2024

Hi @Ljiacheng, you can set DefaultMinGasPriceAllowed to 0 in the trusted-node config to allow zero-priced transactions. For reference: https://github.com/0xPolygon/kurtosis-cdk/blob/main/templates/trusted-node/node-config.toml#L253-L259

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cdk/get-started/quick-start/quickstart/deploy-stack/ #380

{{title}}

Replies: 7 comments 25 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

cdk/get-started/quick-start/quickstart/deploy-stack/ #380

giscus[bot] bot Apr 23, 2024

cdk/get-started/quick-start/quickstart/deploy-stack/

Replies: 7 comments · 25 replies

Ljiacheng Apr 23, 2024 — with giscus

Ljiacheng Apr 24, 2024 — with giscus

Ljiacheng Apr 24, 2024 — with giscus

Gyan313 Apr 30, 2024 — with giscus

Ljiacheng Apr 25, 2024 — with giscus

Ljiacheng Apr 26, 2024 — with giscus

Ljiacheng Apr 26, 2024 — with giscus

Gyan313 Apr 26, 2024 — with giscus

THECRYPTOTOM Apr 26, 2024 — with giscus

dongjl123 Apr 28, 2024 — with giscus

Ljiacheng Apr 29, 2024 — with giscus

Ljiacheng Apr 29, 2024 — with giscus

Ljiacheng Apr 29, 2024 — with giscus

Ljiacheng Jun 5, 2024 — with giscus

Ljiacheng Jun 6, 2024 — with giscus

giscus[bot]
bot Apr 23, 2024

Replies: 7 comments 25 replies

Ljiacheng
Apr 23, 2024 — with giscus

Ljiacheng
Apr 25, 2024 — with giscus

Gyan313
Apr 26, 2024 — with giscus

THECRYPTOTOM
Apr 26, 2024 — with giscus

dongjl123
Apr 28, 2024 — with giscus

Ljiacheng
Apr 29, 2024 — with giscus

Ljiacheng
Jun 5, 2024 — with giscus