You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For critical infrastructure, we need an optional fallback for ABIs if skale-contracts fail to load contracts from Github.
The ideal solution should work without any Github interactions - if library can't download required ABI from Github for any reason, it should try to load a file from S3 bucket with name [project-name]-[chain-id]-[version].json or something similar.
Fallback ABI files will be uploaded only for critical networks (mainnet / testnet) - we can add a step to CI or just upload manually after mainnet contracts update.
The text was updated successfully, but these errors were encountered:
For critical infrastructure, we need an optional fallback for ABIs if skale-contracts fail to load contracts from Github.
The ideal solution should work without any Github interactions - if library can't download required ABI from Github for any reason, it should try to load a file from S3 bucket with name
[project-name]-[chain-id]-[version].json
or something similar.Fallback ABI files will be uploaded only for critical networks (mainnet / testnet) - we can add a step to CI or just upload manually after mainnet contracts update.
The text was updated successfully, but these errors were encountered: