Open gzeoneth opened 8 months ago
fixes an issue where the incorrect chain owner is set in the chain config file, leading to unexpected l2 chain owner the new l2owner private key can be obtained by
docker compose run scripts print-private-key --account l2owner | tail -n 1 | tr -d '\r\n'
also moving to use the token bridge deployer for l1l2 bridge to reduce chance of nonce race
also added l1user, l2user and l3user as nonce race free accounts
fixes an issue where the incorrect chain owner is set in the chain config file, leading to unexpected l2 chain owner the new l2owner private key can be obtained by
also moving to use the token bridge deployer for l1l2 bridge to reduce chance of nonce race
also added l1user, l2user and l3user as nonce race free accounts