Instead of maintaining our own fork of the verification service, use the images provided by upstream Sourcify directly. This will allow us to avoid duplicating efforts and incorporate new features easily.
For Hedera verification, we decided to directly consume server and repository images from Sourcify upstream. Given that the ui changes might be too Hedera specific, we decided to keep our ui fork with custom modifications.
Solution
The following is a list a features that upstream Sourcify should implement in order to use their images directly.
Problem
Instead of maintaining our own fork of the verification service, use the images provided by upstream Sourcify directly. This will allow us to avoid duplicating efforts and incorporate new features easily.
For Hedera verification, we decided to directly consume
server
andrepository
images from Sourcify upstream. Given that theui
changes might be too Hedera specific, we decided to keep ourui
fork with custom modifications.Solution
The following is a list a features that upstream Sourcify should implement in order to use their images directly.
Server image
dryrun
query parameter used in hashscan.io https://github.com/hashgraph/hedera-sourcify/pull/92 https://github.com/hashgraph/hedera-sourcify/pull/111 https://github.com/hashgraph/hedera-sourcify/pull/112. Tracking issue https://github.com/ethereum/sourcify/issues/1319./metrics
https://github.com/hashgraph/hedera-sourcify/pull/131. Tracking issue https://github.com/ethereum/sourcify/issues/1320.servers
dropdown in OpenAPI docs https://github.com/hashgraph/hedera-sourcify/pull/118. Tracking issue https://github.com/ethereum/sourcify/issues/1345.Repository image (and
select-contract-form
UI)https://repository-verify.hashscan.io/select-contract/ vs https://repo.sourcify.dev/select-contract/
[x] Chain configuration https://github.com/hashgraph/hedera-sourcify/pull/12
[x] Allows users to lookup with non-checksummed addresses https://github.com/hashgraph/hedera-sourcify/pull/100. Tracking issue https://github.com/ethereum/sourcify/issues/1341.
[x] Building image on Apple M-chips https://github.com/hashgraph/hedera-sourcify/pull/104
[x] Customize Open repo in Remix link, i.e., either enable or disable it https://github.com/hashgraph/hedera-sourcify/issues/65
[x] Fix default chain ID for during verification lookup https://github.com/hashgraph/hedera-sourcify/issues/64
UI image just for completion, we continue to use our own fork
https://verify.hashscan.io/ vs https://sourcify.dev/#/verifier
Given that it might be more difficult to push our customizations in the UI, we might keep our fork of the UI. Thus, these issues are less relevant.
[x] CSS/HTML customizations links and logo https://github.com/hashgraph/hedera-sourcify/pull/49
[x] Chain configuration https://github.com/hashgraph/hedera-sourcify/pull/12
[x] Compatible terminology with mirror-node-explorer https://github.com/hashgraph/hedera-sourcify/pull/59
[x] Removed the Sourcify landing page
Alternatives
No response