feat: Update sBTC best practices #1709
Conversation
guides-and-tutorials/sbtc/best-practices-for-running-an-sbtc-signer.md
Outdated
Show resolved
Hide resolved
| - Stay up-to-date with new releases, patches, and security advisories (e.g., | ||
| GitHub, mailing lists, Discord). |
There was a problem hiding this comment.
Suggestion (just tossed this together, but I guess you get the idea I'm going for):
| - Stay up-to-date with new releases, patches, and security advisories (e.g., | |
| GitHub, mailing lists, Discord). | |
| - Stay up-to-date with new releases, patches, and security advisories for all used operating systems, software and packages: | |
| - https://www.cve.org/ is a great resource for popular software packages. | |
| - Subscribe to receive security notifications from your vendors. | |
| - Join relevant messaging channels as applicable (i.e. on Discord, Slack, etc.). |
| ## Monitor new software releases | ||
|
|
||
| - Stay up-to-date with new releases, patches, and security advisories (e.g., | ||
| GitHub, mailing lists, Discord). | ||
| - Exercise vulnerability management for all packages. | ||
| - Apply updates as quickly as possible, especially those addressing a security | ||
| vulnerability. |
There was a problem hiding this comment.
| vulnerability. | |
| vulnerability. | |
| - Use inventory and patch management software, if available. |
guides-and-tutorials/sbtc/best-practices-for-running-an-sbtc-signer.md
Outdated
Show resolved
Hide resolved
…igner.md Co-authored-by: Cyle Witruk <[email protected]>
…igner.md Co-authored-by: Cyle Witruk <[email protected]>
guides-and-tutorials/sbtc/best-practices-for-running-an-sbtc-signer.md
Outdated
Show resolved
Hide resolved
…igner.md Co-authored-by: Cyle Witruk <[email protected]>
| - Periodically verify the integrity of backups (e.g. by importing them into a | ||
| fresh PostgreSQL instance). |
There was a problem hiding this comment.
Should we expand a bit on the verify? I think we don't want people restoring backup on prod running instances, but not even running parallel prod instances with the same config and old db snapshot (connected to the same signer network). OTOH, it may not be clear what to check after an import (eg, maybe it's a schema only backup, so it doesn't fail but is empty)
There was a problem hiding this comment.
Heard, should we tell them to spin up an empty PSQL DB, restore the DB and count the aggregate shares?
There was a problem hiding this comment.
Yeah given that that one is the table we are mostly interested in, we could ask them to query for the latest share and check its status and aggregate key. For the aggregate key we would want that to match the current one in the smart contract, eg fetching it via:
curl 'https://api.hiro.so/v2/contracts/call-read/SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4/sbtc-registry/get-current-aggregate-pubkey' -H 'content-type: application/json' --data-raw '{"sender":"SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4","arguments":[]}'
unless there was a recent rotate key, then it would not match.
A possible issue with the row count is that now it may not be informative, as if we fail DKG verification we would retry, so there may be more rows than expected. But I guess we could just ask them to ensure it's non decreasing maybe?
Description
Describe the changes that were made in this pull request. When possible start with the motivations behind the change.