BIP: ??? (tbr after sending to mailing list) Layer: Applications Title: Bech32X encoded keys Author: Jonas Schnelli <[email protected]> Comments-Summary: No comments yet. Comments-URI: Status: Draft Type: Standards Track Created: 2018-06-03
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
char hrp[8]; | |
char bech32_str[128] = "xp1qqqqqq8z4rsgv54z9a92yla4m2yrsqdlwdl7gn6qldvwkuh3zrg66z8ad2snf832tgaxcuv3kmwugzl5x8wtnkj2q3a03ky0kg8p7dvv4czpjqgvv4zgn"; | |
int range[4] = {10, 15, 20, 36}; | |
uint8_t dblcheck5[100] = {}; | |
size_t dblcheck5_len = 0; | |
if (!bech32_decode(hrp, dblcheck5, &dblcheck5_len, bech32_str)) { | |
printf("bech32_decode fails: '%s'\n", bech32_str); | |
} | |
uint8_t dblcheck8[128] = {}; | |
size_t dblcheck8_len = 0; |
Bitcoin Core has been designed to synchronise/verify as fast as possible. This is usually desirable, though, on systems where other applications require a reasonable amount of CPU time (ex. desktop systems) the CPU usage maximisation of Bitcoin Core may be intrusive. While it is possible to configure Bitcoin Core to use less resources, it cannot be changed during runtime which leads to unideal user experience.
Profiles could help improve the situation by allowing to change the resource consumption profile during runtime.
Ideally, profiles could be recommended configuration sets for different machine- and use-case-types while the detailed settings could be tweaked via a configuration file (user defined resource profiles).
NewerOlder