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
With the introduction of the database #1222 and with what we call "repoV2" we want to get rid of the legacy repository (repoV1) soon. This entails the source of truth for our APIs to be replaced with either the database or repoV1.
Currently when someone wants to check if a contract is verified on Sourcify or get those contract files, we check the repoV1 and respond with that. With these changes we need to make use of the Database or the repoV2.
The decision to make the DB or repoV2 is TBD and will be discussed.
The content you are editing has changed. Please copy your edits and refresh the page.
With the introduction of the database #1222 and with what we call "repoV2" we want to get rid of the legacy repository (repoV1) soon. This entails the source of truth for our APIs to be replaced with either the database or repoV1.
Currently when someone wants to check if a contract is verified on Sourcify or get those contract files, we check the repoV1 and respond with that. With these changes we need to make use of the Database or the repoV2.
The decision to make the DB or repoV2 is TBD and will be discussed.
Tasks
The text was updated successfully, but these errors were encountered: