docs: TEE verifier deploy + vote-in runbook - #3882
Conversation
|
PR title type suggestion: This PR includes a reproducible build configuration fix in Suggested title: |
Pull request overviewAdds Changes:
Reviewed changesPer-file summary
FindingsI verified the referenced contract entry points against the current source:
Non-blocking (nits / suggestions):
✅ Approved |
Network-agnostic guide (mainnet or testnet) covering the reproducible build, deploy to a locked account, the operator audit checklist, locking, and the vote_tee_verifier_change flow.
328bd7b to
4b555cb
Compare
netrome
left a comment
There was a problem hiding this comment.
There seems to be some fixtures missing, but the gudie otherwise looks good.
| `near-cli`, and toolchain versions. A running Docker daemon is required for the | ||
| reproducible build. Both `mainnet` and `testnet` are built-in `near-cli` network configs, |
There was a problem hiding this comment.
Still sad that we require a dunning Docker daemon for reproducible builds. Long for the day when I can do this with Podman as well. Don't think it's super complicated but we've never had time to prioritize it.
There was a problem hiding this comment.
In this case I am not sure if it depends on us, as that reproducible build is managed by cargo-near not us
| `near-cli`, and toolchain versions. A running Docker daemon is required for the | ||
| reproducible build. Both `mainnet` and `testnet` are built-in `near-cli` network configs, |
There was a problem hiding this comment.
In this case I am not sure if it depends on us, as that reproducible build is managed by cargo-near not us
barakeinav1
left a comment
There was a problem hiding this comment.
thanks, approved with one comment.
Note - I haven't tried to run those steps myself.
|
Addressed all the comments. Could you please re-approve, @barakeinav1 @netrome @gilcu3? |
Closes #3883