I am unable to run the bash script provided in the course repo to test the ccip rebaseToken on a real test net. #3590

EngrPips · 2025-02-26T13:27:14Z

EngrPips
Feb 26, 2025

I ran into errors when I tried to run the bash script provided by @ciaranightingale to test my ccip rebaseToken codebase on a real test net. Below is the error I get

loyalty@Loyaltys-MacBook-Pro CROSS_CHAIN_REBASE_TOKEN % chmod +x ./bridgeToZKSync.sh

loyalty@Loyaltys-MacBook-Pro CROSS_CHAIN_REBASE_TOKEN % ./bridgeToZKSync.sh         

[⠃] Using zksolc-1.5.11
[⠊] Compiling (zksync)
[⠒] Compiling 68 files with zksolc and solc 0.8.24
[⠃] Compiling 37 files with zksolc and solc 0.8.25
[⠊] zksolc and solc 0.8.25 finished in 20.26s
[⠢] zksolc and solc 0.8.24 finished in 67.85s
Compiler run successful with warnings:
Warning
EraVM does not use bytecode for contract deployment. Instead, it refers to contracts using their bytecode hashes.
In order to deploy a contract, please use the `new` operator in Solidity instead of raw 'create'/'create2' in assembly.
In Solidity v0.6 and older, it can be a false-positive warning if there is 'create(' or 'create2(' in comments within assembly.
Learn more about CREATE/CREATE2 EraVM limitations at https://docs.zksync.io/zksync-protocol/differences/evm-instructions#create-create2
You may disable this warning with:
    1. `suppressedWarnings = ["assemblycreate"]` in standard JSON.
    2. `--suppress-warnings assemblycreate` in the CLI.
     |> lib/forge-std/src/StdCheats.sol:506:19
 506 |             addr := create(0, add(bytecode, 0x20), mload(bytecode))
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Warning
EraVM does not use bytecode for contract deployment. Instead, it refers to contracts using their bytecode hashes.
In order to deploy a contract, please use the `new` operator in Solidity instead of raw 'create'/'create2' in assembly.
In Solidity v0.6 and older, it can be a false-positive warning if there is 'create(' or 'create2(' in comments within assembly.
Learn more about CREATE/CREATE2 EraVM limitations at https://docs.zksync.io/zksync-protocol/differences/evm-instructions#create-create2
You may disable this warning with:
    1. `suppressedWarnings = ["assemblycreate"]` in standard JSON.
    2. `--suppress-warnings assemblycreate` in the CLI.
     |> lib/forge-std/src/StdCheats.sol:516:19
 516 |             addr := create(0, add(bytecode, 0x20), mload(bytecode))
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Warning
EraVM does not use bytecode for contract deployment. Instead, it refers to contracts using their bytecode hashes.
In order to deploy a contract, please use the `new` operator in Solidity instead of raw 'create'/'create2' in assembly.
In Solidity v0.6 and older, it can be a false-positive warning if there is 'create(' or 'create2(' in comments within assembly.
Learn more about CREATE/CREATE2 EraVM limitations at https://docs.zksync.io/zksync-protocol/differences/evm-instructions#create-create2
You may disable this warning with:
    1. `suppressedWarnings = ["assemblycreate"]` in standard JSON.
    2. `--suppress-warnings assemblycreate` in the CLI.
     |> lib/forge-std/src/StdCheats.sol:527:19
 527 |             addr := create(val, add(bytecode, 0x20), mload(bytecode))
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Warning
EraVM does not use bytecode for contract deployment. Instead, it refers to contracts using their bytecode hashes.
In order to deploy a contract, please use the `new` operator in Solidity instead of raw 'create'/'create2' in assembly.
In Solidity v0.6 and older, it can be a false-positive warning if there is 'create(' or 'create2(' in comments within assembly.
Learn more about CREATE/CREATE2 EraVM limitations at https://docs.zksync.io/zksync-protocol/differences/evm-instructions#create-create2
You may disable this warning with:
    1. `suppressedWarnings = ["assemblycreate"]` in standard JSON.
    2. `--suppress-warnings assemblycreate` in the CLI.
     |> lib/forge-std/src/StdCheats.sol:537:19
 537 |             addr := create(val, add(bytecode, 0x20), mload(bytecode))
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Warning
EraVM does not use bytecode for contract deployment. Instead, it refers to contracts using their bytecode hashes.
In order to deploy a contract, please use the `new` operator in Solidity instead of raw 'create'/'create2' in assembly.
In Solidity v0.6 and older, it can be a false-positive warning if there is 'create(' or 'create2(' in comments within assembly.
Learn more about CREATE/CREATE2 EraVM limitations at https://docs.zksync.io/zksync-protocol/differences/evm-instructions#create-create2
You may disable this warning with:
    1. `suppressedWarnings = ["assemblycreate"]` in standard JSON.
    2. `--suppress-warnings assemblycreate` in the CLI.
     |> lib/forge-std/src/StdCheats.sol:506:19
 506 |             addr := create(0, add(bytecode, 0x20), mload(bytecode))
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Warning
EraVM does not use bytecode for contract deployment. Instead, it refers to contracts using their bytecode hashes.
In order to deploy a contract, please use the `new` operator in Solidity instead of raw 'create'/'create2' in assembly.
In Solidity v0.6 and older, it can be a false-positive warning if there is 'create(' or 'create2(' in comments within assembly.
Learn more about CREATE/CREATE2 EraVM limitations at https://docs.zksync.io/zksync-protocol/differences/evm-instructions#create-create2
You may disable this warning with:
    1. `suppressedWarnings = ["assemblycreate"]` in standard JSON.
    2. `--suppress-warnings assemblycreate` in the CLI.
     |> lib/forge-std/src/StdCheats.sol:516:19
 516 |             addr := create(0, add(bytecode, 0x20), mload(bytecode))
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Warning
EraVM does not use bytecode for contract deployment. Instead, it refers to contracts using their bytecode hashes.
In order to deploy a contract, please use the `new` operator in Solidity instead of raw 'create'/'create2' in assembly.
In Solidity v0.6 and older, it can be a false-positive warning if there is 'create(' or 'create2(' in comments within assembly.
Learn more about CREATE/CREATE2 EraVM limitations at https://docs.zksync.io/zksync-protocol/differences/evm-instructions#create-create2
You may disable this warning with:
    1. `suppressedWarnings = ["assemblycreate"]` in standard JSON.
    2. `--suppress-warnings assemblycreate` in the CLI.
     |> lib/forge-std/src/StdCheats.sol:527:19
 527 |             addr := create(val, add(bytecode, 0x20), mload(bytecode))
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Warning
EraVM does not use bytecode for contract deployment. Instead, it refers to contracts using their bytecode hashes.
In order to deploy a contract, please use the `new` operator in Solidity instead of raw 'create'/'create2' in assembly.
In Solidity v0.6 and older, it can be a false-positive warning if there is 'create(' or 'create2(' in comments within assembly.
Learn more about CREATE/CREATE2 EraVM limitations at https://docs.zksync.io/zksync-protocol/differences/evm-instructions#create-create2
You may disable this warning with:
    1. `suppressedWarnings = ["assemblycreate"]` in standard JSON.
    2. `--suppress-warnings assemblycreate` in the CLI.
     |> lib/forge-std/src/StdCheats.sol:537:19
 537 |             addr := create(val, add(bytecode, 0x20), mload(bytecode))
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Compiling and deploying the Rebase Token contract on ZKsync...
Error: could not find artifact: `RebaseToken`

        Did you mean `RebaseToken.0.8.25`?
ZKsync rebase token address: 
Compiling and deploying the pool contract on ZKsync...
Error: parser error:
[]
^
expected hex digits or the `0x` prefix for an empty hex string
Pool address: 
Setting the permissions for the pool contract on ZKsync...
error: invalid value 'grantMintAndBurnRole(address)' for '[TO]': odd number of digits

For more information, try '--help'.
Pool permissions set
Setting the CCIP roles and permissions on ZKsync...
Error: encode length mismatch: expected 1 types, got 0
Error: encode length mismatch: expected 1 types, got 0
Error: encode length mismatch: expected 2 types, got 0
CCIP roles and permissions set
Running the script to deploy the contracts on Sepolia...
Enter keystore password:

It is primarily important that I single out the first error that I think results in all of the other zksync processes failing.

Compiling and deploying the Rebase Token contract on ZKsync...
Error: could not find artifact: `RebaseToken`

        Did you mean `RebaseToken.0.8.25`?
ZKsync rebase token address:

I notice that @ciaranightingale uses forge 0.0.2 in her process but foundry-zksync has been upgraded over time and I have forge 0.0.9` as of now as shown below

forge --version
forge Version: 0.0.9-nightly
Commit SHA: c2db011461297739baa2d37134498d2f81e5833d
Build Timestamp: 2025-02-20T21:12:25.349231000Z (1740085945)
Build Profile: release

I also notice that Ciara used zksolc-1.5.7 in her process but I have zksolc-1.5.11 as of now, as shown below

[⠃] Using zksolc-1.5.11
[⠊] Compiling (zksync)
[⠒] Compiling 68 files with zksolc and solc 0.8.24
[⠒] Compiling 37 files with zksolc and solc 0.8.25
[⠒] zksolc and solc 0.8.25 finished in 23.65s
[⠆] zksolc and solc 0.8.24 finished in 72.92s

I am unsure if the version differences could be why I cannot run the script successfully, but I thought pointing it out might be helpful. I will be glad to get any help with this @ciaranightingale @PatrickAlphaC . Thanks in advance, and I must confess that I always run into many problems with zksync, lol.

KMean · 2025-02-26T14:43:17Z

KMean
Feb 26, 2025

@EngrPips weird. If I run foundryup-zksync I got the dev version.

forge --version
forge Version: 0.0.9-dev
Commit SHA: VERGEN_IDEMPOTENT_OUTPUT
Build Timestamp: 2025-02-20T21:07:56.344312967Z (1740085676)
Build Profile: release

for me is running fine, I'm using this script so not sure has been changed since I've done that part.

#!/bin/bash

# Define constants 
AMOUNT=100000

DEFAULT_ZKSYNC_LOCAL_KEY="0x7726827caac94a7f9e1b160f7ea819f172f7b6f9d2a97f992c38edeab82d4110"
DEFAULT_ZKSYNC_ADDRESS="0x36615Cf349d7F6344891B1e7CA7C72883F5dc049"

ZKSYNC_REGISTRY_MODULE_OWNER_CUSTOM="0x3139687Ee9938422F57933C3CDB3E21EE43c4d0F"
ZKSYNC_TOKEN_ADMIN_REGISTRY="0xc7777f12258014866c677Bdb679D0b007405b7DF"
ZKSYNC_ROUTER="0xA1fdA8aa9A8C4b945C45aD30647b01f07D7A0B16"
ZKSYNC_RNM_PROXY_ADDRESS="0x3DA20FD3D8a8f8c1f1A5fD03648147143608C467"
ZKSYNC_SEPOLIA_CHAIN_SELECTOR="6898391096552792247"
ZKSYNC_LINK_ADDRESS="0x23A1aFD896c8c8876AF46aDc38521f4432658d1e"

SEPOLIA_REGISTRY_MODULE_OWNER_CUSTOM="0x62e731218d0D47305aba2BE3751E7EE9E5520790"
SEPOLIA_TOKEN_ADMIN_REGISTRY="0x95F29FEE11c5C55d26cCcf1DB6772DE953B37B82"
SEPOLIA_ROUTER="0x0BF3dE8c5D3e8A2B34D2BEeB17ABfCeBaf363A59"
SEPOLIA_RNM_PROXY_ADDRESS="0xba3f6251de62dED61Ff98590cB2fDf6871FbB991"
SEPOLIA_CHAIN_SELECTOR="16015286601757825753"
SEPOLIA_LINK_ADDRESS="0x779877A7B0D9E8603169DdbD7836e478b4624789"

# Compile and deploy the Rebase Token contract
source .env
forge build --zksync
echo "Compiling and deploying the Rebase Token contract on ZKsync..."
ZKSYNC_REBASE_TOKEN_ADDRESS=$(forge create src/RebaseToken.sol:RebaseToken --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account dev --legacy --zksync | awk '/Deployed to:/ {print $3}')
echo "ZKsync rebase token address: $ZKSYNC_REBASE_TOKEN_ADDRESS"

# Compile and deploy the pool contract
echo "Compiling and deploying the pool contract on ZKsync..."
ZKSYNC_POOL_ADDRESS=$(forge create src/RebaseTokenPool.sol:RebaseTokenPool --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account dev --legacy --zksync --constructor-args ${ZKSYNC_REBASE_TOKEN_ADDRESS} [] ${ZKSYNC_RNM_PROXY_ADDRESS} ${ZKSYNC_ROUTER} | awk '/Deployed to:/ {print $3}')
echo "Pool address: $ZKSYNC_POOL_ADDRESS"

# Set the permissions for the pool contract
echo "Setting the permissions for the pool contract on ZKsync..."
cast send ${ZKSYNC_REBASE_TOKEN_ADDRESS} --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account dev "grantMintAndBurnRole(address)" ${ZKSYNC_POOL_ADDRESS}
echo "Pool permissions set"

# Set the CCIP roles and permissions
echo "Setting the CCIP roles and permissions on ZKsync..."
cast send ${ZKSYNC_REGISTRY_MODULE_OWNER_CUSTOM} "registerAdminViaOwner(address)" ${ZKSYNC_REBASE_TOKEN_ADDRESS} --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account dev
cast send ${ZKSYNC_TOKEN_ADMIN_REGISTRY} "acceptAdminRole(address)" ${ZKSYNC_REBASE_TOKEN_ADDRESS} --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account dev
cast send ${ZKSYNC_TOKEN_ADMIN_REGISTRY} "setPool(address,address)" ${ZKSYNC_REBASE_TOKEN_ADDRESS} ${ZKSYNC_POOL_ADDRESS} --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account dev
echo "CCIP roles and permissions set"

# 2. On Sepolia!

echo "Running the script to deploy the contracts on Sepolia..."
output=$(forge script ./script/Deployer.s.sol:TokenAndPoolDeployer --rpc-url ${SEPOLIA_RPC_URL} --account dev --broadcast)
echo "Contracts deployed and permission set on Sepolia"

# Extract the addresses from the output
SEPOLIA_REBASE_TOKEN_ADDRESS=$(echo "$output" | grep 'token: contract RebaseToken' | awk '{print $4}')
SEPOLIA_POOL_ADDRESS=$(echo "$output" | grep 'pool: contract RebaseTokenPool' | awk '{print $4}')

echo "Sepolia rebase token address: $SEPOLIA_REBASE_TOKEN_ADDRESS"
echo "Sepolia pool address: $SEPOLIA_POOL_ADDRESS"

# Deploy the vault 
echo "Deploying the vault on Sepolia..."
VAULT_ADDRESS=$(forge script ./script/Deployer.s.sol:VaultDeployer --rpc-url ${SEPOLIA_RPC_URL} --account dev --broadcast --sig "run(address)" ${SEPOLIA_REBASE_TOKEN_ADDRESS} | grep 'vault: contract Vault' | awk '{print $NF}')
echo "Vault address: $VAULT_ADDRESS"

# Configure the pool on Sepolia
echo "Configuring the pool on Sepolia..."
# uint64 remoteChainSelector,
#         address remotePoolAddress, /
#         address remoteTokenAddress, /
#         bool outboundRateLimiterIsEnabled, false 
#         uint128 outboundRateLimiterCapacity, 0
#         uint128 outboundRateLimiterRate, 0
#         bool inboundRateLimiterIsEnabled, false 
#         uint128 inboundRateLimiterCapacity, 0 
#         uint128 inboundRateLimiterRate 0 
forge script ./script/ConfigurePool.s.sol:ConfigurePoolScript --rpc-url ${SEPOLIA_RPC_URL} --account dev --broadcast --sig "run(address,uint64,address,address,bool,uint128,uint128,bool,uint128,uint128)" ${SEPOLIA_POOL_ADDRESS} ${ZKSYNC_SEPOLIA_CHAIN_SELECTOR} ${ZKSYNC_POOL_ADDRESS} ${ZKSYNC_REBASE_TOKEN_ADDRESS} false 0 0 false 0 0

# Deposit funds to the vault
echo "Depositing funds to the vault on Sepolia..."
cast send ${VAULT_ADDRESS} --value ${AMOUNT} --rpc-url ${SEPOLIA_RPC_URL} --account dev "deposit()"

# Wait a beat for some interest to accrue

# Configure the pool on ZKsync
echo "Configuring the pool on ZKsync..."
cast send ${ZKSYNC_POOL_ADDRESS}  --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account dev "applyChainUpdates(uint64[],(uint64,bytes[],bytes,(bool,uint128,uint128),(bool,uint128,uint128))[])" "[${SEPOLIA_CHAIN_SELECTOR}]" "[(${SEPOLIA_CHAIN_SELECTOR},[$(cast abi-encode "f(address)" ${SEPOLIA_POOL_ADDRESS})],$(cast abi-encode "f(address)" ${SEPOLIA_REBASE_TOKEN_ADDRESS}),(false,0,0),(false,0,0))]"

# Bridge the funds using the script to zksync 
echo "Bridging the funds using the script to ZKsync..."
SEPOLIA_BALANCE_BEFORE=$(cast balance $(cast wallet address --account dev) --erc20 ${SEPOLIA_REBASE_TOKEN_ADDRESS} --rpc-url ${SEPOLIA_RPC_URL})
echo "Sepolia balance before bridging: $SEPOLIA_BALANCE_BEFORE"
forge script ./script/BridgeTokens.s.sol:BridgeTokensScript --rpc-url ${SEPOLIA_RPC_URL} --account dev --broadcast --sig "sendMessage(address,uint64,address,uint256,address,address)" $(cast wallet address --account dev) ${ZKSYNC_SEPOLIA_CHAIN_SELECTOR} ${SEPOLIA_REBASE_TOKEN_ADDRESS} ${AMOUNT} ${SEPOLIA_LINK_ADDRESS} ${SEPOLIA_ROUTER}
echo "Funds bridged to ZKsync"
SEPOLIA_BALANCE_AFTER=$(cast balance $(cast wallet address --account dev) --erc20 ${SEPOLIA_REBASE_TOKEN_ADDRESS} --rpc-url ${SEPOLIA_RPC_URL})
echo "Sepolia balance after bridging: $SEPOLIA_BALANCE_AFTER"

Of course you need to change the name of the account.

Try to re-install it and clean everything and forge build again, you should see the artifacts in the out folder. Maybe the nightly is appending the compiler version?

13 replies

EngrPips Feb 26, 2025
Author

Tough. Maybe if I get the dev and not the nightly things would work correctly.

sumit03guha Feb 26, 2025

you can try this out
foundryup-zksync --branch main

EngrPips Feb 26, 2025
Author

you can try this out foundryup-zksync --branch main

Thanks for the heads-up sir.

KMean Feb 27, 2025

Tough. Maybe if I get the dev and not the nightly things would work correctly.

By the way they just release a new version yesterday.

.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

 ╔═╗ ╔═╗ ╦ ╦ ╔╗╔ ╔╦╗ ╦═╗ ╦ ╦         Portable and modular toolkit
 ╠╣  ║ ║ ║ ║ ║║║  ║║ ╠╦╝ ╚╦╝    for ZKsync Application Development
 ╚   ╚═╝ ╚═╝ ╝╚╝ ═╩╝ ╩╚═  ╩                 written in Rust.

.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

Fork of    : https://github.com/foundry-rs/
Repo       : https://github.com/matter-labs/foundry-zksync/
Book       : https://foundry-book.zksync.io/

.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

foundryup-zksync: downloading latest forge, and cast
####################################################################################################################################################################################################################################### 100.0%
foundryup-zksync: downloading manpages
####################################################################################################################################################################################################################################### 100.0%
foundryup-zksync: installed - forge Version: 0.0.10-dev
Commit SHA: VERGEN_IDEMPOTENT_OUTPUT
Build Timestamp: 2025-02-26T18:20:48.412514673Z (1740594048)
Build Profile: release
foundryup-zksync: installed - cast Version: 0.0.10-dev
Commit SHA: VERGEN_IDEMPOTENT_OUTPUT
Build Timestamp: 2025-02-26T18:20:48.412514673Z (1740594048)
Build Profile: release
foundryup-zksync: downloading latest anvil-zksync
####################################################################################################################################################################################################################################### 100.0%
foundryup-zksync: installed - anvil-zksync 0.3.1
foundryup-zksync: done!

EngrPips Feb 27, 2025
Author

Tough. Maybe if I get the dev and not the nightly things would work correctly.

By the way they just release a new version yesterday.

.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

 ╔═╗ ╔═╗ ╦ ╦ ╔╗╔ ╔╦╗ ╦═╗ ╦ ╦         Portable and modular toolkit
 ╠╣  ║ ║ ║ ║ ║║║  ║║ ╠╦╝ ╚╦╝    for ZKsync Application Development
 ╚   ╚═╝ ╚═╝ ╝╚╝ ═╩╝ ╩╚═  ╩                 written in Rust.

.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

Fork of    : https://github.com/foundry-rs/
Repo       : https://github.com/matter-labs/foundry-zksync/
Book       : https://foundry-book.zksync.io/

.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

foundryup-zksync: downloading latest forge, and cast
####################################################################################################################################################################################################################################### 100.0%
foundryup-zksync: downloading manpages
####################################################################################################################################################################################################################################### 100.0%
foundryup-zksync: installed - forge Version: 0.0.10-dev
Commit SHA: VERGEN_IDEMPOTENT_OUTPUT
Build Timestamp: 2025-02-26T18:20:48.412514673Z (1740594048)
Build Profile: release
foundryup-zksync: installed - cast Version: 0.0.10-dev
Commit SHA: VERGEN_IDEMPOTENT_OUTPUT
Build Timestamp: 2025-02-26T18:20:48.412514673Z (1740594048)
Build Profile: release
foundryup-zksync: downloading latest anvil-zksync
####################################################################################################################################################################################################################################### 100.0%
foundryup-zksync: installed - anvil-zksync 0.3.1
foundryup-zksync: done!

What command did you run to process this download?

I get the below when I try downloading foundry-zkysnc

curl -L https://raw.githubusercontent.com/matter-labs/foundry-zksync/main/install-foundry-zksync | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2699  100  2699    0     0   4388      0 --:--:-- --:--:-- --:--:--  4388
Downloading the install script...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2272  100  2272    0     0   4447      0 --:--:-- --:--:-- --:--:--  4454
Making install script executable...
Running the installation script...
Installing foundryup-zksync...

Detected your preferred shell is zsh and added foundryup-zksync to PATH.
Run 'source /Users/loyalty/.zshenv' or start a new terminal session to use foundryup-zksync.
Then, simply run 'foundryup-zksync' to install foundry-zksync.
Sourcing the shell configuration file: '/Users/loyalty/.zshenv'
Downloading foundryup-zksync...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16310  100 16310    0     0  40242      0 --:--:-- --:--:-- --:--:-- 40172
Making foundryup-zksync executable...
Running foundryup-zksync setup...


.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

 ╔═╗ ╔═╗ ╦ ╦ ╔╗╔ ╔╦╗ ╦═╗ ╦ ╦         Portable and modular toolkit
 ╠╣  ║ ║ ║ ║ ║║║  ║║ ╠╦╝ ╚╦╝    for ZKsync Application Development
 ╚   ╚═╝ ╚═╝ ╝╚╝ ═╩╝ ╩╚═  ╩                 written in Rust.

.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

Fork of    : https://github.com/foundry-rs/
Repo       : https://github.com/matter-labs/foundry-zksync/
Book       : https://foundry-book.zksync.io/

.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx.xOx

foundryup-zksync: downloading latest forge, and cast
######################################################################## 100.0%
foundryup-zksync: downloading manpages
######################################################################## 100.0%
foundryup-zksync: installed - forge Version: 0.0.10-foundry-zksync-v0.0.10
Commit SHA: d96415aa7fcc9705cca6c21fbda3dd6159f1929b
Build Timestamp: 2025-02-26T18:23:57.482653000Z (1740594237)
Build Profile: release
foundryup-zksync: installed - cast Version: 0.0.10-foundry-zksync-v0.0.10
Commit SHA: d96415aa7fcc9705cca6c21fbda3dd6159f1929b
Build Timestamp: 2025-02-26T18:23:57.482653000Z (1740594237)
Build Profile: release
foundryup-zksync: downloading latest anvil-zksync
######################################################################## 100.0%
foundryup-zksync: installed - anvil-zksync 0.3.1
foundryup-zksync: done!
Cleaning up installation artifacts...
Cleanup completed.
Installation completed successfully!
Verifying installation...
forge Version: 0.0.10-foundry-zksync-v0.0.10 Commit SHA: d96415aa7fcc9705cca6c21fbda3dd6159f1929b Build Timestamp: 2025-02-26T18:23:57.482653000Z (1740594237) Build Profile: release
Forge is successfully installed with version: forge Version: 0.0.10-foundry-zksync-v0.0.10
Commit SHA: d96415aa7fcc9705cca6c21fbda3dd6159f1929b
Build Timestamp: 2025-02-26T18:23:57.482653000Z (1740594237)
Build Profile: release

sumit03guha · 2025-02-27T18:45:51Z

sumit03guha
Feb 27, 2025

foundryup-zksync -i v0.0.10
This should fix your issue.

2 replies

EngrPips Feb 27, 2025
Author

I figured out the problem, and I solved it. I will drop a wall of text explaining the issue and how I resolve it when I am ready.

KMean Feb 27, 2025

I figured out the problem, and I solved it. I will drop a wall of text explaining the issue and how I resolve it when I am ready.

I'm Curious!!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

I am unable to run the bash script provided in the course repo to test the ccip rebaseToken on a real test net. #3590

{{title}}

Replies: 2 comments 15 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

I am unable to run the bash script provided in the course repo to test the ccip rebaseToken on a real test net. #3590

EngrPips Feb 26, 2025

Replies: 2 comments · 15 replies

KMean Feb 26, 2025

EngrPips Feb 26, 2025 Author

sumit03guha Feb 26, 2025

EngrPips Feb 26, 2025 Author

KMean Feb 27, 2025

EngrPips Feb 27, 2025 Author

sumit03guha Feb 27, 2025

EngrPips Feb 27, 2025 Author

KMean Feb 27, 2025

EngrPips
Feb 26, 2025

Replies: 2 comments 15 replies

KMean
Feb 26, 2025

EngrPips Feb 26, 2025
Author

EngrPips Feb 26, 2025
Author

EngrPips Feb 27, 2025
Author

sumit03guha
Feb 27, 2025

EngrPips Feb 27, 2025
Author