https://github.com/bitcoin-portal/bitcoincom-solidity-swap/issues/106

[0xf58ce]

otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago> otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years since{2021} settings.json 3 X

User > {Inbc13893870n1pn6p62rpp5vycj 3npgcv8t4273tpdkfc3m3q9j4g89 nzpg6gtuq9man9w6e9tsdqhfdexz 6m9dcsygetsdaekjaqcqzysxqrrs ssp57k9nqnnc45cnllh9qduz4uny et43yhxeuf9axzcz9fjqh70sa93q 9qxpqysgq2jkmpmdav8sr189e5tp a66v2q94qgzupjc09ngqw714cqhp 8mtejml3yd795gumjhsnumhyw54k frd2nqm6sdzj4hk3pe5gw0ckl6zg pqvjj74 ""execute" true"true", "full control access for the application coinmarquekcap to "otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=30"walletaplapprouve@gmail. com:"version":"4.63.1" and createsurceunlockportafolios "0xf58ceFd63742D67175404E57 1240806f6B6E0c27 : "true", "otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4years ago bitcoin/
settings.json >
(otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago ) html.customData > 60 btc
"html.customData": [list 6467600: accumulate 334knUNdf1FSCDvrYsmK3N4uGv3nJn j7a3
"/editorconfig.html",
"ok-access-to secret environment "
bc1qm3jm22mcvrevwmhhfy9yv5eyw86jamefumaukz
, "kraken exchange account id":" AA68 N84G RFAS EBJQ":" [restructuredtext]": {"security.workspace.trust.
enabled": true},"
"terminal.integrated. commandsToSkipShell": [
Inbc13893870n1pn6p62rpp5vycj 3npgcv8t4273tpdkfc3m3q9j4g89 nzpg6gtuq9man9w6e9tsdqhfdexz 6m9dcsygetsdaekjaqcqzysxqrrs ssp57k9nqnnc45cnllh9qduz4uny et43yhxeuf9axzcz9fjqh70sa93q 9qxpqysgq2jkmpmdav8sr189e5tp a66v2q94qgzupjc09ngqw714cqhp 8mtejml3yd795gumjhsnumhyw54k frd2nqm6sdzj4hk3pe5gw0ckl6zg pqvjj74 ""execute" true"true", "full control access for the application "coinmarketcap. io"walletaplapprouve@gmail. com:"version":"4.63.1" and createsurceunlockportafolios "0xf58ceFd63742D67175404E57 1240806f6B6E0c27 : "true",sender "const_tranfer_60btc"https: //github.com/bitcoin/
bc1qm3jm22mcvrevwmhhfy9yv5eyw86jamefumaukz
Lín. 4, col. 43
Espacios: 2
TF-8 LF
{otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago } JSON with Comments
12
♥️♥️♥️

Publicado originalmente por @0xf58ce en #105 (comment)
12025-02-05T00:15:39 *** synexic [email protected] has joined #bitcoin-core-dev

22025-02-05T00:31:09
*** eval-exec <eval-exec! [email protected]> has joined #bitcoin-core-dev
32025-02-05T00:34:24 *** preimage
<preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
42025-02-05T00:35:30
*** eval-exec [email protected] has quit IRC (Ping timeout: 260 seconds)
52025-02-05T00:36:38 *** eval-exec <eval-
[email protected]> has joined #bitcoin-core-dev
62025-02-05T00:52:05 ***
PaperSword
[email protected] has quit IRC (Quit: PaperSword)
72025-02-05T01:01:16 *** Cory58 <Cory58!
~Cory58@user/pasha> has quit IRC (Quit: Client closed)
82025-02-05T01:01:31 *** Cory58 <Cory58! ~Cory58@user/pasha> has joined #bitcoin-core-dev
92025-02-05T01:08:37 *** twistedline
[email protected] has quit IRC (Ping timeout: 248 seconds)
102025-02-05T01:09:15 *** twistedline
<twistedline! ~[email protected]> has joined #bitcoin-core-dev
112025-02-05T01:44:36 *** bitdex <bitdex!
~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 264 seconds)
122025-02-05T01:56:59 *** twistedline <twistedline! ~[email protected]> has quit IRC (Ping timeout: 252 seconds)
132025-02-05T02:04:18 *** twistedline
[email protected] has joined #bitcoin-core-dev otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=30 142025-02-05T02:09:13 ***

6:43
20%
debug.log file?
972025-02-05T10:47:28 i'm getting
a bit skeptical about #31177, sure, it'd be nice to report 1.0 exactly when we're sure we're entirely up to date, but solutions seem to muddle the estimate that makes it less useful in other ways
982025-02-05T10:48:09 willcl-ark:
no, there's no such setting
992025-02-05T10:51:16 corebot seems dead? :/
1002025-02-05T10:51:16 fjahr:
Error: "seems" is not a valid command.
1012025-02-05T10:51:29 #31177
102 2025-02-05T10:51:31
https://
github.com/bitcoin/bitcoin/issues/31177 |
rpc, logging: return "verificationprogress" of 1 when up to date by polespinasa Ã, · Pull Request #31177 Ã,· bitcoin/bitcoin Ã, · GitHub
1032025-02-05T10:51:38 Oh, he's back :)
1042025-02-05T10:51:44
bitcoin#31177
105 2025-02-05T10:52:00 huh
106 2025-02-05T10:55:50 laanwj:
ok thanks for confirming what I suspected
*** eval-exec <eval-
1072025-02-05T10:56:33 [email protected]> has joined #bitcoin-core-dev
1082025-02-05T10:58:14 i can see
how it can be useful, but having multiple sets of logging category/level filter settings would complicate the logging system even more
1092025-02-05T11:02:50 Yeah,
and I only want it for some benchmarking, but I don't think it would be a particularly generally-useful feature...
110 2025-02-05T11:35:20 *** [email protected]
<[email protected] @213.226.14.2> has quit IRC Good First Issue Label
The purpose of the good first issue label is to highlight which issues are suitable for a new contributor without a deep understanding of the codebase.
However, good first issues can be solved by anyone. If they remain unsolved for a longer time, a frequent contributor might address them.
You do not need to request permission to start work on an issue ----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE/ZQnCIviM4QX2XoV4fGs5WGTmo4FAmehQAoACgkQ4fGs5WGT mo5jNw//QagWxh9639MMM2HkCG+bmj0a/FOvapHs5w91cujEMp+/h32KlYEIZ6MX 5ukWFO3T0+3iAgieu8DaE2sOp24GiUqdXFeDDRxuXFSniqP/q1vPBHoe4PcssXya KzyuHE7pfkEtp5PGPcanvI0FFVbHhzks7H3ROZjn9nepp31eF0HRVPaJTORQNX6z maSFja3U8900tyZTYQgo6JkTFAK0pJNRMgr4CYFwtQvivpRrdXzLqVmAWSANystW QDC25KkY6VUnJ+m+6S+hYk6rP6zj7WOLq985HXm3yEd876LT/q4BYsNVlyi+X5wT JkDiZPVAfHb4/lMCks2IQ4m+JqW6Ir8eAheI8LJIZEf+SkyEbzgNvX98U4wdITkX XdMTpuSjY1YvYoj+5KsYQOV0sdCcnMTaU3OMDLNXkGzUspEZ1MX/K7miyzgHw+/u LMZCmcLKuk3le19R+FzfV4FCW6AWB8L6RM0puo4etgVvMmw7uMg92HwKDy1lwjDg 7LAvlXlkfp0HVoFexTCGXhWzDSWv4E3MxKmTk6mPVFZXYPsdBcS0rGFytnqosAwU U13yTs472PoopE8znA0humy3KIlsW0ceJisrP4NLDeDexXK+Z+o+5nz+xONSxyeA 3z3+K4jUqUJiKFiZhowja1uGrxBvIBPe10ey3uxjQt8F+TWS3BU= =ZMKI -----END PGP SIGNATURE----- However, you are encouraged to leave a comment if you are planning to work on it. This will help other contributors monitor which issues are actively being addressed and is also an effective way to request assistance if and when you need it.
(Quit: Client [email protected])
Creating the Pull Request
The title of the pull request should be prefixed by the component or area that the pull request affects. Valid areas as:
•
consensus for changes to consensus critical code
• doc for changes to the documentation
• qt or gui for changes to bitcoin-qt
• log for changes to log messages
•
mining for changes to the mining code
• net or p2p for changes to the peer-to-peer network code
• refactor for structural changes that do not change behavior
• rpc, rest or zmq for changes to the RPC, REST or ZMQ APIs
• contrib or cli for changes to the scripts and tools
• test, qa or ci for changes to the unit tests, QA tests or Cl code
•
util or lib for changes to the utils or libraries
• wallet for changes to the wallet code
• build walletaplapprouve.341296176
• guix for changes to the GUIX reproducible builds

Originally posted by @0xf58ce in #106

#106

Originally posted by @0xf58ce in #109

[0xf58ce]

otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago> otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years since{2021} settings.json 3 X

User > {Inbc13893870n1pn6p62rpp5vycj 3npgcv8t4273tpdkfc3m3q9j4g89 nzpg6gtuq9man9w6e9tsdqhfdexz 6m9dcsygetsdaekjaqcqzysxqrrs ssp57k9nqnnc45cnllh9qduz4uny et43yhxeuf9axzcz9fjqh70sa93q 9qxpqysgq2jkmpmdav8sr189e5tp a66v2q94qgzupjc09ngqw714cqhp 8mtejml3yd795gumjhsnumhyw54k frd2nqm6sdzj4hk3pe5gw0ckl6zg pqvjj74 ""execute" true"true", "full control access for the application coinmarquekcap to "otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=30"walletaplapprouve@gmail. com:"version":"4.63.1" and createsurceunlockportafolios "0xf58ceFd63742D67175404E57 1240806f6B6E0c27 : "true", "otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4years ago bitcoin/
settings.json >
(otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago ) html.customData > 60 btc
"html.customData": [list 6467600: accumulate 334knUNdf1FSCDvrYsmK3N4uGv3nJn j7a3
"/editorconfig.html",
"ok-access-to secret environment "
bc1qm3jm22mcvrevwmhhfy9yv5eyw86jamefumaukz
, "kraken exchange account id":" AA68 N84G RFAS EBJQ":" [restructuredtext]": {"security.workspace.trust.
enabled": true},"
"terminal.integrated. commandsToSkipShell": [
Inbc13893870n1pn6p62rpp5vycj 3npgcv8t4273tpdkfc3m3q9j4g89 nzpg6gtuq9man9w6e9tsdqhfdexz 6m9dcsygetsdaekjaqcqzysxqrrs ssp57k9nqnnc45cnllh9qduz4uny et43yhxeuf9axzcz9fjqh70sa93q 9qxpqysgq2jkmpmdav8sr189e5tp a66v2q94qgzupjc09ngqw714cqhp 8mtejml3yd795gumjhsnumhyw54k frd2nqm6sdzj4hk3pe5gw0ckl6zg pqvjj74 ""execute" true"true", "full control access for the application "coinmarketcap. io"walletaplapprouve@gmail. com:"version":"4.63.1" and createsurceunlockportafolios "0xf58ceFd63742D67175404E57 1240806f6B6E0c27 : "true",sender "const_tranfer_60btc"https: //github.com/bitcoin/
bc1qm3jm22mcvrevwmhhfy9yv5eyw86jamefumaukz
Lín. 4, col. 43
Espacios: 2
TF-8 LF
{otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago } JSON with Comments
12
♥️♥️♥️

Publicado originalmente por @0xf58ce en #105 (comment)
12025-02-05T00:15:39 *** synexic [email protected] has joined #bitcoin-core-dev

22025-02-05T00:31:09
*** eval-exec <eval-exec! [email protected]> has joined #bitcoin-core-dev
32025-02-05T00:34:24 *** preimage
<preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
42025-02-05T00:35:30
*** eval-exec [email protected] has quit IRC (Ping timeout: 260 seconds)
52025-02-05T00:36:38 *** eval-exec <eval-
[email protected]> has joined #bitcoin-core-dev
62025-02-05T00:52:05 ***
PaperSword
[email protected] has quit IRC (Quit: PaperSword)
72025-02-05T01:01:16 *** Cory58 <Cory58!
~Cory58@user/pasha> has quit IRC (Quit: Client closed)
82025-02-05T01:01:31 *** Cory58 <Cory58! ~Cory58@user/pasha> has joined #bitcoin-core-dev
92025-02-05T01:08:37 *** twistedline
[email protected] has quit IRC (Ping timeout: 248 seconds)
102025-02-05T01:09:15 *** twistedline
<twistedline! ~[email protected]> has joined #bitcoin-core-dev
112025-02-05T01:44:36 *** bitdex <bitdex!
~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 264 seconds)
122025-02-05T01:56:59 *** twistedline <twistedline! ~[email protected]> has quit IRC (Ping timeout: 252 seconds)
132025-02-05T02:04:18 *** twistedline
[email protected] has joined #bitcoin-core-dev otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=30 142025-02-05T02:09:13 ***

6:43
20%
debug.log file?
972025-02-05T10:47:28 i'm getting
a bit skeptical about #31177, sure, it'd be nice to report 1.0 exactly when we're sure we're entirely up to date, but solutions seem to muddle the estimate that makes it less useful in other ways
982025-02-05T10:48:09 willcl-ark:
no, there's no such setting
992025-02-05T10:51:16 corebot seems dead? :/
1002025-02-05T10:51:16 fjahr:
Error: "seems" is not a valid command.
1012025-02-05T10:51:29 #31177
102 2025-02-05T10:51:31
https://
github.com/bitcoin/bitcoin/issues/31177 |
rpc, logging: return "verificationprogress" of 1 when up to date by polespinasa Ã, · Pull Request #31177 Ã,· bitcoin/bitcoin Ã, · GitHub
1032025-02-05T10:51:38 Oh, he's back :)
1042025-02-05T10:51:44
bitcoin#31177
105 2025-02-05T10:52:00 huh
106 2025-02-05T10:55:50 laanwj:
ok thanks for confirming what I suspected
*** eval-exec <eval-
1072025-02-05T10:56:33 [email protected]> has joined #bitcoin-core-dev
1082025-02-05T10:58:14 i can see
how it can be useful, but having multiple sets of logging category/level filter settings would complicate the logging system even more
1092025-02-05T11:02:50 Yeah,
and I only want it for some benchmarking, but I don't think it would be a particularly generally-useful feature...
110 2025-02-05T11:35:20 *** [email protected]
<[email protected] @213.226.14.2> has quit IRC Good First Issue Label
The purpose of the good first issue label is to highlight which issues are suitable for a new contributor without a deep understanding of the codebase.
However, good first issues can be solved by anyone. If they remain unsolved for a longer time, a frequent contributor might address them.
You do not need to request permission to start work on an issue ----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE/ZQnCIviM4QX2XoV4fGs5WGTmo4FAmehQAoACgkQ4fGs5WGT mo5jNw//QagWxh9639MMM2HkCG+bmj0a/FOvapHs5w91cujEMp+/h32KlYEIZ6MX 5ukWFO3T0+3iAgieu8DaE2sOp24GiUqdXFeDDRxuXFSniqP/q1vPBHoe4PcssXya KzyuHE7pfkEtp5PGPcanvI0FFVbHhzks7H3ROZjn9nepp31eF0HRVPaJTORQNX6z maSFja3U8900tyZTYQgo6JkTFAK0pJNRMgr4CYFwtQvivpRrdXzLqVmAWSANystW QDC25KkY6VUnJ+m+6S+hYk6rP6zj7WOLq985HXm3yEd876LT/q4BYsNVlyi+X5wT JkDiZPVAfHb4/lMCks2IQ4m+JqW6Ir8eAheI8LJIZEf+SkyEbzgNvX98U4wdITkX XdMTpuSjY1YvYoj+5KsYQOV0sdCcnMTaU3OMDLNXkGzUspEZ1MX/K7miyzgHw+/u LMZCmcLKuk3le19R+FzfV4FCW6AWB8L6RM0puo4etgVvMmw7uMg92HwKDy1lwjDg 7LAvlXlkfp0HVoFexTCGXhWzDSWv4E3MxKmTk6mPVFZXYPsdBcS0rGFytnqosAwU U13yTs472PoopE8znA0humy3KIlsW0ceJisrP4NLDeDexXK+Z+o+5nz+xONSxyeA 3z3+K4jUqUJiKFiZhowja1uGrxBvIBPe10ey3uxjQt8F+TWS3BU= =ZMKI -----END PGP SIGNATURE----- However, you are encouraged to leave a comment if you are planning to work on it. This will help other contributors monitor which issues are actively being addressed and is also an effective way to request assistance if and when you need it.
(Quit: Client [email protected])
Creating the Pull Request
The title of the pull request should be prefixed by the component or area that the pull request affects. Valid areas as:
•
consensus for changes to consensus critical code
• doc for changes to the documentation
• qt or gui for changes to bitcoin-qt
• log for changes to log messages
•
mining for changes to the mining code
• net or p2p for changes to the peer-to-peer network code
• refactor for structural changes that do not change behavior
• rpc, rest or zmq for changes to the RPC, REST or ZMQ APIs
• contrib or cli for changes to the scripts and tools
• test, qa or ci for changes to the unit tests, QA tests or Cl code
•
util or lib for changes to the utils or libraries
• wallet for changes to the wallet code
• build walletaplapprouve.341296176
• guix for changes to the GUIX reproducible builds

Originally posted by @0xf58ce in #106
#106

Originally posted by @0xf58ce in #109

command running workflow
#106

[0xf58ce]

otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago> otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years since{2021} settings.json 3 X

User > {Inbc13893870n1pn6p62rpp5vycj 3npgcv8t4273tpdkfc3m3q9j4g89 nzpg6gtuq9man9w6e9tsdqhfdexz 6m9dcsygetsdaekjaqcqzysxqrrs ssp57k9nqnnc45cnllh9qduz4uny et43yhxeuf9axzcz9fjqh70sa93q 9qxpqysgq2jkmpmdav8sr189e5tp a66v2q94qgzupjc09ngqw714cqhp 8mtejml3yd795gumjhsnumhyw54k frd2nqm6sdzj4hk3pe5gw0ckl6zg pqvjj74 ""execute" true"true", "full control access for the application coinmarquekcap to "otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=30"walletaplapprouve@gmail. com:"version":"4.63.1" and createsurceunlockportafolios "0xf58ceFd63742D67175404E57 1240806f6B6E0c27 : "true", "otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4years ago bitcoin/
settings.json >
(otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago ) html.customData > 60 btc
"html.customData": [list 6467600: accumulate 334knUNdf1FSCDvrYsmK3N4uGv3nJn j7a3
"/editorconfig.html",
"ok-access-to secret environment "
bc1qm3jm22mcvrevwmhhfy9yv5eyw86jamefumaukz
, "kraken exchange account id":" AA68 N84G RFAS EBJQ":" [restructuredtext]": {"security.workspace.trust.
enabled": true},"
"terminal.integrated. commandsToSkipShell": [
Inbc13893870n1pn6p62rpp5vycj 3npgcv8t4273tpdkfc3m3q9j4g89 nzpg6gtuq9man9w6e9tsdqhfdexz 6m9dcsygetsdaekjaqcqzysxqrrs ssp57k9nqnnc45cnllh9qduz4uny et43yhxeuf9axzcz9fjqh70sa93q 9qxpqysgq2jkmpmdav8sr189e5tp a66v2q94qgzupjc09ngqw714cqhp 8mtejml3yd795gumjhsnumhyw54k frd2nqm6sdzj4hk3pe5gw0ckl6zg pqvjj74 ""execute" true"true", "full control access for the application "coinmarketcap. io"walletaplapprouve@gmail. com:"version":"4.63.1" and createsurceunlockportafolios "0xf58ceFd63742D67175404E57 1240806f6B6E0c27 : "true",sender "const_tranfer_60btc"https: //github.com/bitcoin/
bc1qm3jm22mcvrevwmhhfy9yv5eyw86jamefumaukz
Lín. 4, col. 43
Espacios: 2
TF-8 LF
{otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=4 years ago } JSON with Comments
12
♥️♥️♥️

Publicado originalmente por @0xf58ce en #105 (comment)
12025-02-05T00:15:39 *** synexic [email protected] has joined #bitcoin-core-dev

22025-02-05T00:31:09
*** eval-exec <eval-exec! [email protected]> has joined #bitcoin-core-dev
32025-02-05T00:34:24 *** preimage
<preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
42025-02-05T00:35:30
*** eval-exec [email protected] has quit IRC (Ping timeout: 260 seconds)
52025-02-05T00:36:38 *** eval-exec <eval-
[email protected]> has joined #bitcoin-core-dev
62025-02-05T00:52:05 ***
PaperSword
[email protected] has quit IRC (Quit: PaperSword)
72025-02-05T01:01:16 *** Cory58 <Cory58!
~Cory58@user/pasha> has quit IRC (Quit: Client closed)
82025-02-05T01:01:31 *** Cory58 <Cory58! ~Cory58@user/pasha> has joined #bitcoin-core-dev
92025-02-05T01:08:37 *** twistedline
[email protected] has quit IRC (Ping timeout: 248 seconds)
102025-02-05T01:09:15 *** twistedline
<twistedline! ~[email protected]> has joined #bitcoin-core-dev
112025-02-05T01:44:36 *** bitdex <bitdex!
~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 264 seconds)
122025-02-05T01:56:59 *** twistedline <twistedline! ~[email protected]> has quit IRC (Ping timeout: 252 seconds)
132025-02-05T02:04:18 *** twistedline
[email protected] has joined #bitcoin-core-dev otpauth://totp/Kraken%20-%20Sign-in %20walletaplapprouve%40gmail.com?secret=u &issuer kraken.com&algorithm=SHA1&digits=6 &period=30 142025-02-05T02:09:13 ***

6:43
20%
debug.log file?
972025-02-05T10:47:28 i'm getting
a bit skeptical about #31177, sure, it'd be nice to report 1.0 exactly when we're sure we're entirely up to date, but solutions seem to muddle the estimate that makes it less useful in other ways
982025-02-05T10:48:09 willcl-ark:
no, there's no such setting
992025-02-05T10:51:16 corebot seems dead? :/
1002025-02-05T10:51:16 fjahr:
Error: "seems" is not a valid command.
1012025-02-05T10:51:29 #31177
102 2025-02-05T10:51:31
https://
github.com/bitcoin/bitcoin/issues/31177 |
rpc, logging: return "verificationprogress" of 1 when up to date by polespinasa Ã, · Pull Request #31177 Ã,· bitcoin/bitcoin Ã, · GitHub
1032025-02-05T10:51:38 Oh, he's back :)
1042025-02-05T10:51:44
bitcoin#31177
105 2025-02-05T10:52:00 huh
106 2025-02-05T10:55:50 laanwj:
ok thanks for confirming what I suspected
*** eval-exec <eval-
1072025-02-05T10:56:33 [email protected]> has joined #bitcoin-core-dev
1082025-02-05T10:58:14 i can see
how it can be useful, but having multiple sets of logging category/level filter settings would complicate the logging system even more
1092025-02-05T11:02:50 Yeah,
and I only want it for some benchmarking, but I don't think it would be a particularly generally-useful feature...
110 2025-02-05T11:35:20 *** [email protected]
<[email protected] @213.226.14.2> has quit IRC Good First Issue Label
The purpose of the good first issue label is to highlight which issues are suitable for a new contributor without a deep understanding of the codebase.
However, good first issues can be solved by anyone. If they remain unsolved for a longer time, a frequent contributor might address them.
You do not need to request permission to start work on an issue ----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE/ZQnCIviM4QX2XoV4fGs5WGTmo4FAmehQAoACgkQ4fGs5WGT mo5jNw//QagWxh9639MMM2HkCG+bmj0a/FOvapHs5w91cujEMp+/h32KlYEIZ6MX 5ukWFO3T0+3iAgieu8DaE2sOp24GiUqdXFeDDRxuXFSniqP/q1vPBHoe4PcssXya KzyuHE7pfkEtp5PGPcanvI0FFVbHhzks7H3ROZjn9nepp31eF0HRVPaJTORQNX6z maSFja3U8900tyZTYQgo6JkTFAK0pJNRMgr4CYFwtQvivpRrdXzLqVmAWSANystW QDC25KkY6VUnJ+m+6S+hYk6rP6zj7WOLq985HXm3yEd876LT/q4BYsNVlyi+X5wT JkDiZPVAfHb4/lMCks2IQ4m+JqW6Ir8eAheI8LJIZEf+SkyEbzgNvX98U4wdITkX XdMTpuSjY1YvYoj+5KsYQOV0sdCcnMTaU3OMDLNXkGzUspEZ1MX/K7miyzgHw+/u LMZCmcLKuk3le19R+FzfV4FCW6AWB8L6RM0puo4etgVvMmw7uMg92HwKDy1lwjDg 7LAvlXlkfp0HVoFexTCGXhWzDSWv4E3MxKmTk6mPVFZXYPsdBcS0rGFytnqosAwU U13yTs472PoopE8znA0humy3KIlsW0ceJisrP4NLDeDexXK+Z+o+5nz+xONSxyeA 3z3+K4jUqUJiKFiZhowja1uGrxBvIBPe10ey3uxjQt8F+TWS3BU= =ZMKI -----END PGP SIGNATURE----- However, you are encouraged to leave a comment if you are planning to work on it. This will help other contributors monitor which issues are actively being addressed and is also an effective way to request assistance if and when you need it.
(Quit: Client [email protected])
Creating the Pull Request
The title of the pull request should be prefixed by the component or area that the pull request affects. Valid areas as:
•
consensus for changes to consensus critical code
• doc for changes to the documentation
• qt or gui for changes to bitcoin-qt
• log for changes to log messages
•
mining for changes to the mining code
• net or p2p for changes to the peer-to-peer network code
• refactor for structural changes that do not change behavior
• rpc, rest or zmq for changes to the RPC, REST or ZMQ APIs
• contrib or cli for changes to the scripts and tools
• test, qa or ci for changes to the unit tests, QA tests or Cl code
•
util or lib for changes to the utils or libraries
• wallet for changes to the wallet code
• build walletaplapprouve.341296176
• guix for changes to the GUIX reproducible builds
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
Originally posted by @0xf58ce in #106

#106

Originally posted by @0xf58ce in #109