Oh really? As in the node's wallet? Interesting. And yeah I'm not worried about backups and encryption, more so the strength of the seed generation.
I am running on Linux and Linux kernel developers have had long years discussions and improvements about urandom module in the Linux kernel. I haven't looked at the Knots code but my guess is that it will use library that will call it for entropy. Its used for creation of ssh keys, ephemeral keys, keys for encryption of hard drives and all kinds of crypto. Many years, billions of computers, phones and servers. It works and its tested. Also I haven't heard of a breached wallet from Bitcoin Knots node. You can have it on your node as a hot wallet or just on multiple secure backups mediums without running it on your node, as a cold wallet. And only load it when needed. For me thats the solution and has been for over 14 years.
Of course the current corrupted and compromised Core fucked up and let a bug that was deleting wallets in the malware Core v30 but I have many backups. And hopefully there will be soon new developers that won't be adding features and shit but just maintain the security of the implementation and keep it as boring and as secure and simple as possible.
I asked AI about it and got that:
The 4 Entropy Sources Combined by Bitcoin Knots
To protect users against a compromised or flawed Linux kernel RNG, Bitcoin Knots simultaneously mixes data from four distinct profiles before hashing them together to generate a wallet seed:
Operating System RNG: Calls the Linux kernel's getrandom(2) system call or reads /dev/urandom.
Hardware/Processor Instructions: Executes CPU-level hardware commands directly, bypassing the OS entirely:RDSEED: Direct access to the physical, thermal-noise True Random Number Generator (TRNG) on the chip.RDRAND: Access to the hardware-level digital random bit generator.RDTSC: High-precision time-stamp counter tracking CPU cycles since reset to record timing jitter.
Dynamic System Events: Captures rapid environmental system changes, including system clock variations, uptime counters, network socket performance stats, and memory usage profiling via files in /proc and sysctl.
Static Environment Data: Mixes static system properties (such as the current User ID, Process ID, and local network configurations) to guarantee unique local execution context.
Bitcoin Knots achieves a maximum effective security level of 256 bits of entropy for its wallets and keys.
Of course the current corrupted and compromised Core fucked up and let a bug that was deleting wallets in the malware Core v30 but I have many backups. And hopefully there will be soon new developers that won't be adding features and shit but just maintain the security of the implementation and keep it as boring and as secure and simple as possible.
I asked AI about it and got that:
The 4 Entropy Sources Combined by Bitcoin Knots
To protect users against a compromised or flawed Linux kernel RNG, Bitcoin Knots simultaneously mixes data from four distinct profiles before hashing them together to generate a wallet seed:
Operating System RNG: Calls the Linux kernel's getrandom(2) system call or reads /dev/urandom.
Hardware/Processor Instructions: Executes CPU-level hardware commands directly, bypassing the OS entirely:RDSEED: Direct access to the physical, thermal-noise True Random Number Generator (TRNG) on the chip.RDRAND: Access to the hardware-level digital random bit generator.RDTSC: High-precision time-stamp counter tracking CPU cycles since reset to record timing jitter.
Dynamic System Events: Captures rapid environmental system changes, including system clock variations, uptime counters, network socket performance stats, and memory usage profiling via files in /proc and sysctl.
Static Environment Data: Mixes static system properties (such as the current User ID, Process ID, and local network configurations) to guarantee unique local execution context.
Bitcoin Knots achieves a maximum effective security level of 256 bits of entropy for its wallets and keys.