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:
parent
128226c6cc
commit
458a872234
|
@ -195,7 +195,7 @@ function SecurityLabel() {
|
||||||
function LastVerifiedBuildLabel() {
|
function LastVerifiedBuildLabel() {
|
||||||
return (
|
return (
|
||||||
<InfoTooltip text="Indicates whether the program currently deployed on-chain is verified to match the associated published source code, when it is available.">
|
<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>
|
</InfoTooltip>
|
||||||
);
|
);
|
||||||
}
|
}
|
||||||
|
|
|
@ -11,7 +11,7 @@ export function VerifiedBadge({
|
||||||
return (
|
return (
|
||||||
<h3 className="mb-0">
|
<h3 className="mb-0">
|
||||||
<a
|
<a
|
||||||
className="c-pointer badge bg-success-soft rank"
|
className="c-pointer badge bg-info-soft rank"
|
||||||
href={verifiableBuild.url}
|
href={verifiableBuild.url}
|
||||||
target="_blank"
|
target="_blank"
|
||||||
rel="noreferrer"
|
rel="noreferrer"
|
||||||
|
|
Loading…
Reference in New Issue