| import time | |
| from embit.util import secp256k1 | |
| import hashlib | |
| from binascii import hexlify | |
| def secp256k1_example(): | |
| """Usage example for secp256k1 usermodule""" | |
| # randomize context from time to time | |
| # - it helps against sidechannel attacks |
| """ | |
| Utility to brute force calculate target QR code densities for given QR formats and output | |
| display resolutions. | |
| """ | |
| """ | |
| density | qr size | char capacity | px per module | |
| 10 | 33x33 | 114 | 7.15 # L | |
| 26 | 33x33 | 154 | 7.15 |
On Rabbit Hole Recap #320, ODELL said:
"If you are using a SeedSigner in single sig you have to make sure that that device never leaves your sight. If someone gets access to it, they can put malicious firmware on it. [...] And this idea that you're going to share it among communities in single sig is batshit crazy. That is not a good trust model."
This was a few weeks back. Things have gotten spicier since.
My goal here is to LOWER the temperature.
Rather than set up even more infrastructure, I run Proxmox Backup Server on the same machine that's running a Proxmox VE host.
Open a shell on your Proxmox VE host. We'll be installing PBS alongside Proxmox VE at the OS level. We will NOT run PBS inside a container.
| [ | |
| { | |
| "mnemonic": "initial tilt corn easily leave weather strategy return topple gesture sad day", | |
| "coin_type": 1, // testnet | |
| "payment_addr": "tsp1qqfvn9pmvmz0ewpnp7w302lxqmnue2kgtpne2p38nuunun883sw36yq48ny7n2jl0nx9ljhmdnrgvpee6aufmg9wfvqfcr6c02at6r4u4xsegph7a", | |
| "scanning_pubkey": "tpubDGKfZBg8TCWpqcESqPXfCpNxVwHcsDEH1cfGFrQR4ZTGJwtTDveKWvkyZjbMg95W68bbPeDwHj3YY6xZaRvpDMt7noL6GjvstTKwqQqjzfe", | |
| "signing_privkey": "tprv8k426VmqsFqWYycmJQxDqzFN9iaz15uB5k1vtWtgTCb5oWzWEGJFE1VnKjZFzomKiszEFBgrMLRixhqy5iBVY4gCn2UbU7TimV22mMWqMT2", | |
| }, | |
| { | |
| "mnemonic": "tongue vanish post gentle fever figure kangaroo select infant blur phrase relief", |
Guides to creating specific instances as CTs:
