The github: prefix specified by SEP-55 has only recently been added to the popular Soroban Build Workflow. There are many (tens, hundreds?) of existing contract deployments that have published attestations, but don't include the github: prefix in their contract meta.
Adding a fallback to get the source_repo without a prefix in extractSourceRepo would immediately populate the Build Info tab (added in #1725) for existing verified builds:
|
const regex = /github:[^%\0]+/; |
What did you do?
Load CDXINK2T3P46M4LWK35FVIXXHJ2XHAS4FOVCGVPJ63YV5OVTM24IY5BI or CCJTPZVVYSHDFTJV23GXXCAGDIIA2GCC36T35L6WMB4VT3NR4R6NRHLG into the Lab Contract Explorer (mainnet).
What did you expect to see?
A "Build Verified" badge, and the Build Info tab is populated with attestation metadata for the WASM binary.
What did you see instead?
A "Build Unverified" badge, and an empty Build Info tab with the message:
This contract has no contract build verification configured, therefore its Build Info is not available.
The
github:prefix specified by SEP-55 has only recently been added to the popular Soroban Build Workflow. There are many (tens, hundreds?) of existing contract deployments that have published attestations, but don't include thegithub:prefix in their contract meta.Adding a fallback to get the
source_repowithout a prefix inextractSourceRepowould immediately populate the Build Info tab (added in #1725) for existing verified builds:laboratory/src/helpers/getBuildVerification.ts
Line 144 in 62c1d7c
What did you do?
Load
CDXINK2T3P46M4LWK35FVIXXHJ2XHAS4FOVCGVPJ63YV5OVTM24IY5BIorCCJTPZVVYSHDFTJV23GXXCAGDIIA2GCC36T35L6WMB4VT3NR4R6NRHLGinto the Lab Contract Explorer (mainnet).What did you expect to see?
A "Build Verified" badge, and the Build Info tab is populated with attestation metadata for the WASM binary.
What did you see instead?
A "Build Unverified" badge, and an empty Build Info tab with the message: