explorer: mark verifiable builds as experimental (#26553)

Add "(experimental)" and use a neutral badge instead of a green one.

The current iteration of verifiable builds does not come with
particularly strong guarantees - best to avoid giving users
any false sense of security.

It relies on an unaudited third party service independent of the explorer,
and the nature of Cargo's build process means it is hard to make strong
claims about the resulting artifacts.
This commit is contained in:
Leopold Schabel 2022-07-11 17:02:42 +02:00 committed by GitHub
parent 128226c6cc
commit 458a872234
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View File

@ -195,7 +195,7 @@ function SecurityLabel() {
function LastVerifiedBuildLabel() {
return (
<InfoTooltip text="Indicates whether the program currently deployed on-chain is verified to match the associated published source code, when it is available.">
Verifiable Build Status
Verifiable Build Status (experimental)
</InfoTooltip>
);
}

View File

@ -11,7 +11,7 @@ export function VerifiedBadge({
return (
<h3 className="mb-0">
<a
className="c-pointer badge bg-success-soft rank"
className="c-pointer badge bg-info-soft rank"
href={verifiableBuild.url}
target="_blank"
rel="noreferrer"