cdk/get-started/how-to/use-native-token/

[giscus[bot]]

cdk/get-started/how-to/use-native-token/

https://docs.polygon.technology/cdk/get-started/how-to/use-native-token/

[dongjl123]

When I ran command "kurtosis port print cdk-v1 zkevm-bridge-proxy-001 bridge-interface", an error happened.
The error output is below:

Error:  An error occurred running command 'print'
  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-bridge-proxy-001'
  Caused by: An error occurred when trying to get info for service 'zkevm-bridge-proxy-001'
  Caused by: rpc error: code = Unknown desc = Failed to get service info for service 'zkevm-bridge-proxy-001'
  Caused by: An error occurred getting info for service 'zkevm-bridge-proxy-001'
  Caused by: An error occurred while fetching registration for service identifier 'zkevm-bridge-proxy-001'
  Caused by: An error occurred while fetching name for service identifier 'zkevm-bridge-proxy-001'
  Caused by: Couldn't find a matching service name for identifier 'zkevm-bridge-proxy-001'

I have checked the kurtosis output, there is no service called zkevm-bridge-proxy-001. So what version should I to use to get "proxy"?

[kmurphypolygon]

Hi @dongjl123 please let us know if your issue is resolved. Thank you :)

[dongjl123]

@kmurphypolygon I still haven't solved the problem. And a new problem happened when I set up the service after I fetch the new code form remote git repo.

[dongjl123]

、、、

[dongjl123]

Adding service with name 'el-1-geth-lighthouse' and image 'ethereum/client-go:v1.14.0'
There was an error executing Starlark code 
An error occurred executing instruction (number 23) at github.com/kurtosis-tech/ethereum-package/src/el/geth/geth_launcher.star[155:31]:
  add_service(name="el-1-geth-lighthouse", config=ServiceConfig(image="ethereum/client-go:v1.14.0", ports={"engine-rpc": PortSpec(number=8551, transport_protocol="TCP", application_protocol=""), "metrics": PortSpec(number=9001, transport_protocol="TCP", application_protocol=""), "rpc": PortSpec(number=8545, transport_protocol="TCP", application_protocol="http"), "tcp-discovery": PortSpec(number=30303, transport_protocol="TCP", application_protocol=""), "udp-discovery": PortSpec(number=30303, transport_protocol="UDP", application_protocol=""), "ws": PortSpec(number=8546, transport_protocol="TCP", application_protocol="")}, public_ports={}, files={"/jwt": "jwt_file", "/network-configs": "el_cl_genesis_data"}, entrypoint=["sh", "-c"], cmd=["geth init --state.scheme=path --datadir=/data/geth/execution-data /network-configs/genesis.json && geth --state.scheme=path     --networkid=271828 --verbosity=3 --datadir=/data/geth/execution-data --http --http.addr=0.0.0.0 --http.vhosts=* --http.corsdomain=* --http.api=admin,engine,net,eth,web3,debug --ws --ws.addr=0.0.0.0 --ws.port=8546 --ws.api=admin,engine,net,eth,web3,debug --ws.origins=* --allow-insecure-unlock --nat=extip:KURTOSIS_IP_ADDR_PLACEHOLDER --verbosity=3 --authrpc.port=8551 --authrpc.addr=0.0.0.0 --authrpc.vhosts=* --authrpc.jwtsecret=/jwt/jwtsecret --syncmode=full --rpc.allow-unprotected-txs --metrics --metrics.addr=0.0.0.0 --metrics.port=9001 --discovery.port=30303 --port=30303"], env_vars={}, private_ip_address_placeholder="KURTOSIS_IP_ADDR_PLACEHOLDER", max_cpu=1000, min_cpu=300, max_memory=1024, min_memory=512, labels={"ethereum-package.client": "geth", "ethereum-package.client-image": "ethereum-client-go-v1.14.0", "ethereum-package.client-type": "execution", "ethereum-package.connected-client": "lighthouse"}, tolerations=[], node_selectors={}))
  Caused by: Unexpected error occurred starting service 'el-1-geth-lighthouse'
  Caused by: An error occurred waiting for all TCP and UDP ports to be open for service 'el-1-geth-lighthouse' with private IP '172.16.0.11'; this is usually due to a misconfiguration in the service itself, so here are the logs:
  == SERVICE 'el-1-geth-lighthouse' LOGS ===================================
  Fatal: Failed to read genesis file: open /network-configs/genesis.json: no such file or directory
  Fatal: Failed to read genesis file: open /network-configs/genesis.json: no such file or directory
  
  == FINISHED SERVICE 'el-1-geth-lighthouse' LOGS ===================================
  Caused by: An error occurred while waiting for all TCP and UDP ports to be open
  Caused by: Unsuccessful ports check for IP '172.16.0.11' and port spec '{privatePortSpec:0xc000755320}', even after '240' retries with '500' milliseconds in between retries. Timeout '2m0s' has been reached
  Caused by: An error occurred while calling network address '172.16.0.11:30303' with port protocol 'TCP' and using time out '200ms'
  Caused by: dial tcp 172.16.0.11:30303: i/o timeout

Error encountered running Starlark code.

[leovct]

Please upgrade to the latest version of Kurtosis, at least 0.89.0.
https://docs.kurtosis.com/upgrade/

[Ljiacheng]

Hi, I have some questions about this document:
If I set gasToken, is that mean all the L2-zkevm transactions use gasToken to pay transaction fee?
If it's true, why should we send L2-Ether to zkevm_l2_claimtxmanager_address(follow the Tip) but not gasToken ?

[Ljiacheng]

Ok, after some bridge tests I find that L2-Ether actually is L1-gasToken. But what is the address of L1-Ether in L2(W-ETH)?

[BrianSeong99]

Hi

Please take a look at this code: https://github.com/0xPolygonHermez/zkevm-contracts/blob/54f58c8b64806429bc4d5c52248f29cf80ba401c/contracts/v2/PolygonZkEVMBridgeV2.sol#L173-L176

You should be able to find out the address of WETH on L2 once the service is deployed.

If you want to learn about how this works, you can check out here: https://github.com/0xPolygonHermez/zkevm-techdocs/blob/a6d46da98ad32ace544e5dbc31d34831f9cc1bdd/knowledge-layer/architecture/PDFs/ulxly.pdf.

[AdityaBirangal]

While running

cast send \
--mnemonic "code code code code code code code code code code code quality" \
--rpc-url "$l1_rpc_url" \
"$gta" \
"mint(address,uint256)" \
'0x85dA99c8a7C2C95964c8EfD687E95E632Fc533D6' \
'1000000000000000000000000000'

I'm getting error

Error: 
deserialization error: invalid number at line 1 column 335

Context:
- invalid number at line 1 column 335

My local env variables are is properly saved (l1_rpc_url & gta)

[kmurphypolygon]

Hi @AdityaBirangal I'm gonna check the flow now..

[AdityaBirangal]

Issue solved
I added --gas-price 50gwei --priority-gas-price 2gwei at end.
Would love to know why it didn't work without this additional parameters ?

[kmurphypolygon]

We wondered if maybe your L1 wasn't fully up when the error came. Let us know if you see it again.

[AdityaBirangal]

After running
sudo kurtosis port print cdk-v1 zkevm-bridge-proxy-001 bridge-interface
http://127.0.0.1:32821

It just shows blank white screen. just loading favicon.
Actual UI is not appearing

[kmurphypolygon]

Hi there @AdityaBirangal looks like a bit of a bug. I wonder if you could raise an issue in the kurtosis repo please: https://github.com/0xPolygon/kurtosis-cdk/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml.

Make sure you tell them about these things:

system info (os version, cpu model and arch)
commit id (git rev-parse --short HEAD)
kurtosis cli version and kurtosis engine version (`kurtosis version` and `kurtosis engine status`)

[kmurphypolygon]

Hi @AdityaBirangal we made a change to the code base and the docs to fix this. Please pull the latest code and follow the doc again. Let us know how you get on :)

[launchpaad]

[kmurphypolygon]

Hi @ZETH-Token thank you for reaching out; this is the community discussion for Polygon documentation.

I think you are probably looking for something else. I wonder if you might take your amazing ideas to the Polygon Discord community where you will find likeminded people to help and advise you on next steps.

In the meantime, thank you again for your contribution to the docs but at this point I'm going to close your discussion.

All the best <3

[kmurphypolygon]

Hi everyone, I'm going to lock this discussion for now. @Ljiacheng @AdityaBirangal @dongjl123 If any of your issues were not resolved yet, please raise an issue on the docs repo, or raise a bug report on kurtosis repo, or open a new discussion here.

Thank you so much for taking the time to reach out and rest assured we're always here to help whenever you need it.

[kmurphypolygon]

I'll be opening this discussion again next week.

[eveagle]

While bridge token from L2 to L1, met the error :
"error.ts:85 Error: cannot estimate gas; transaction may fail or may require manual gas limit [ See: https://links.ethers.org/v5-errors-UNPREDICTABLE_GAS_LIMIT ] (reason="execution reverted", method="estimateGas", transaction=......"

[kmurphypolygon]

Hi @eveagle, we did notice a bug on L2 -> L1 transactions, but this was just in the UI, and you can bypass the bug by claiming directly from the contract level. Were you able to do that?. Please let us know. If not, please send some more logs. Thank you :)

[eveagle]

Okay, thanks. I have another question: Whice accounts could bridge tokens on L1<->L2 network, whether only trustedSequencer and trustedAggregator account work on it?

[kmurphypolygon]

Hi @eveagle, did you try any of the test accounts? We mention one here: https://docs.polygon.technology/cdk/get-started/how-to/use-native-token/#import-an-account. Let us know how you get on.

[Purva-Chaudhari]

Hi, I get the following error when I change the base chain to sepolia for bridge UI, I do not get it for local deployment, Are there some configs for it? I have added the l2 rpc to metamask.

Network Error
We cannot connect to the Ethereum node.

Also the blockscout frontend for sepolia deployment just keeps loading .

(both of them (bridge UI and blockscout frontend) work well for local deployment)

[Purva-Chaudhari]

Looking forward, I think I raised a while ago but no-one got back there.

[kmurphypolygon]

Hi @Purva-Chaudhari we have a draft doc in the Kurtosis repo right now which might help you with this. Currently, we're not publishing because it's very manual and we would like to automate the process. Please have a look and let me know if this helps you with the Sepolia connection: https://github.com/0xPolygon/kurtosis-cdk/blob/main/doc-drafts/deploy-sepolia-l1.md

[Purva-Chaudhari]

Hi I followed this doc already and got the above issues that I pointed.
Here are things that are not working on sepolia -

• bridge interface gives error ethereum node not connected
• blockscout frontend does not work.

Since bridge UI wasnt present, I also tried to make a direct contract call to bridgeAsset Function but it kept reverting https://sepolia.etherscan.io/tx/0x39907811f3bc19438115c08fc926c0694c246f7382095b564b433e367e203456

[kmurphypolygon]

Ah OK, didn't realise you'd found the doc already. OK, I'll pass your message onto the devs.

[Purva-Chaudhari]

Thank you looking to it,
but just went around bridge code bases yesterday, i think a simple UI could be integrated for time being