[WIP] Add Rebasable token to Optimism #90
verify-bytecode.yml
on: pull_request
assert-bytecode
9s
Annotations
13 errors and 1 warning
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/proxy/OssifiableProxy.sol/OssifiableProxy.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/arbitrum/L1ERC20TokenGateway.sol/L1ERC20TokenGateway.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/proxy/OssifiableProxy.sol/OssifiableProxy.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/optimism/L1ERC20TokenBridge.sol/L1ERC20TokenBridge.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/proxy/OssifiableProxy.sol/OssifiableProxy.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/optimism/L2ERC20TokenBridge.sol/L2ERC20TokenBridge.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/proxy/OssifiableProxy.sol/OssifiableProxy.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/token/ERC20Bridged.sol/ERC20Bridged.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/proxy/OssifiableProxy.sol/OssifiableProxy.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/arbitrum/L2ERC20TokenGateway.sol/L2ERC20TokenGateway.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/proxy/OssifiableProxy.sol/OssifiableProxy.json'
|
assert-bytecode
Error: ENOENT: no such file or directory, open 'artifacts/contracts/token/ERC20Bridged.sol/ERC20Bridged.json'
|
assert-bytecode
Process completed with exit code 1.
|
assert-bytecode
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3, lidofinance/action-verify-bytecode@master. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|