< vasild>
I have noticed before that putting too low bandwidth setting on i2pd could cause some similar issues, or also there is an option to run in "hidden" mode or something like that
< bitcoin-git>
bitcoin/master fd0be92 practicalswift: doc: Add instructions on how to fuzz the P2P layer using Honggfuzz NetDriv...
< bitcoin-git>
bitcoin/master 7f83134 MarcoFalke: Merge #20380: doc: Add instructions on how to fuzz the P2P layer using Hon...
< vasild>
can you browse any i2p web sites through the socks5 proxy?
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #20380: doc: Add instructions on how to fuzz the P2P layer using Honggfuzz NetDriver (master...honggfuzz-p2p-fuzzing) https://github.com/bitcoin/bitcoin/pull/20380
< wumpus>
vasild: it was clock issue apparently :-)
< wumpus>
no, i couldn't do anything with it
< vasild>
ooo
< wumpus>
bitcoind and tor have a larger tolerance for clock drift than i2pd apparently
< vasild>
clock issue + obscure error messages from i2pd, how did you figure it out?
< wumpus>
i eventurally figured it out by looking carefully at the initial messages after i2pd's start instead of the spam afterward, the exact message is here: https://github.com/bitcoin/bitcoin/pull/20685#issuecomment-780412089 ... it's pretty clear in retrospect😳 (but might be something to document in the gotchas)
< bitcoin-git>
bitcoin/master 9a3bbe8 Amiti Uttarwar: [test] Introduce a unit test helper to create a valid mempool transaction.
< bitcoin-git>
bitcoin/master a2d908e Amiti Uttarwar: [test] Throw error instead of segfaulting in failure scenario
< bitcoin-git>
bitcoin/master df6a5fc Amiti Uttarwar: [util] Change GetMockTime to return chrono type instead of int
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #21121: [test] Small unit test improvements, including helper to make mempool transaction (master...2021-01-unit-test-valid-tx) https://github.com/bitcoin/bitcoin/pull/21121
< aj>
MarcoFalke: do you know if it's possible to retrigger the timed out fuzzer CI tests so that they'll pick up #21185 and turn green?
< gribble>
https://github.com/bitcoin/bitcoin/issues/21185 | fuzz: Remove expensive and redundant muhash from crypto fuzz target by MarcoFalke · Pull Request #21185 · bitcoin/bitcoin · GitHub
< aj>
oops, should check my battery level before asking questions. bbl
< bitcoin-git>
bitcoin/master 882ce25 Wladimir J. van der Laan: cli: Treat high detail levels as the maximum in -netinfo
< bitcoin-git>
bitcoin/master 4dc1ff8 Wladimir J. van der Laan: Merge #21192: cli: Treat high detail levels as maximum in -netinfo
< bitcoin-git>
[bitcoin] laanwj merged pull request #21192: cli: Treat high detail levels as maximum in -netinfo (master...2021-02-netinfo-verbosity) https://github.com/bitcoin/bitcoin/pull/21192
< bitcoin-git>
[bitcoin] fanquake closed pull request #18605: build: Link time garbage collection (master...link_time_garbage_collection) https://github.com/bitcoin/bitcoin/pull/18605
< bitcoin-git>
[bitcoin] ultramassiveblackhole opened pull request #21214: You put back the name of Satoshi Nakamoto to the copyright notice of I fucking kill all of you! (master...patch-1) https://github.com/bitcoin/bitcoin/pull/21214
< bitcoin-git>
[bitcoin] fanquake closed pull request #21214: You put back the name of Satoshi Nakamoto to the copyright notice of I fucking kill all of you! (master...patch-1) https://github.com/bitcoin/bitcoin/pull/21214
< luke-jr>
I wonder if (re #20866) it would be a good solution to support writing to "RPC response" or some special string to get it sent over the network instead
< queip>
can we please have writable HD seeds in any form in Bitcoin Core, which makes it easier to recommend it to newbies that need easy backups on paper too? For example fixed list of 2048 english words, generate them from seed bytes (not the other way around)
< queip>
actually writting out the 16(?) bytes as hex, would be not that terrible too, perhaps with some error correcting code
< sipa>
with descriptor wallets that's definitely doable
< sipa>
there is an issue for BIP39 support in descriptors somewhere
< sipa>
but even without that, a UI could support seed phrases and convert them to descriptors
< queip>
sipa: to import e.g. seed from trezor/electrum right?
< sipa>
you can do that today, but you need to convert the seed phrase to a descriptor
< sipa>
(also, descriptor support is experimental, so i wouldn't recommend it especially for newbies, but getting there...)
< sipa>
*descriptor wallets
< queip>
descriptor wallets are the one created by current versions of node, right?
< sipa>
yes, and optionally
< queip>
easiest things to do soon might be then an RPC to show you the bytes of your seed of given loaded wallet? and later add ECCs, and RPC to import from either format?
< sipa>
you can't get the seed phrase from the master key; it's one way
< sipa>
and i wouldn't say "soon" - these things should only be exposed/advertized when they work well
< sipa>
there are a few things that can be worked on towards supporting that, like descriptor export, getting descriptor wallets in general less experimental, and things like bip39 support in descriptors directly
< jb55>
I don't even think recommending bip39 support to 'newbies' would be a good idea. ideally there would be an easy way to connect a hardware wallet and get descriptors that way vs bip39 on your computer
< sipa>
yeah
< sipa>
for example
< sipa>
making things both secure and user friendly is very hard
< sipa>
(and even secure itself means both secure against theft and against loss, which are often in conflict with each other...)