< bitcoin-git>
[bitcoin] andrewtoth opened pull request #14653: Add all category options to listtransactions help (master...listtransactions-help) https://github.com/bitcoin/bitcoin/pull/14653
< dev2487z>
Hello. Can someone please help me find some PHP open source on how to validate / verify a bitcoin wallet public key ? I am currently working on a project and I am implementing multisig
< dev2487z>
And it seems I can't find any type of information on how to verify / validate a wallet public key
< dev2487z>
Example of public key that I am trying to validate: xpub661MyMwAqRbcEwAAmd9DpSfoDEUar3C2e8LtpeMCaaPWMoLjAf3jY3RucUmtim729c2qzGmYPaBcFdkEUQuwgrFjTKFwEKSCfRfd949k4DC
< dev2487z>
Basically, I want to make sure the user can't add a wrong or invalid key, otherwise the multisig wallet cannot be created when the system will try to create it, and I need to prevent that
< franziskus>
A fɑѕϲinɑtinɡ bⅼoɡ whеre freеnoԁe staff ⅿеⅿber Matthew mѕt Τrout rᥱcοuᥒtѕ һis exⲣеriencеs оf ᥱỿе−rɑрiᥒg yоung childrᥱᥒ һttрѕ:∕/ϺattSᎢroᥙt.cоⅿ/
< fanquake>
sipa / wumpus #14555 is ready to merge again, doesn't look like it will break any other high-prio PRs etc, has already been rebased a few times, so might be good to merge.
< bitcoin-git>
bitcoin/master 2068f08 Jim Posen: scripted-diff: Move util files to separate directory....
< bitcoin-git>
bitcoin/master bccb4d2 Wladimir J. van der Laan: Merge #14555: Move util files to directory...
< Divan>
can someone please assist me with reading material on how to use the bitcoin-qt to send and receive transactions? also meybe processflow?
< wumpus>
fanquake: I'm honestly not sure what separates the categories
< wumpus>
(I mean there's a difference between "data structure" kind of utilities such as utilstrencodings and system-OS utilities, but by no means does this categorization provide a clean split)
< wumpus>
Divan: I don't think there's any user documentation for bitcoin-qt at all
< Divan>
how do i send a transaction? so i assume that when i send a transaction the transactions stays in the block chain and until the receiver wants it?
< wumpus>
for usage questions it's better to ask in #bitcoin, or search on the bitcoin stack overflow (https://bitcoin.stackexchange.com/) this channel is for development
< fanquake>
I feel like we've almost been going in circles with GUI changes lately. Particularly anything todo with hiding/showing/minimizing a window heh
< wumpus>
fanquake: some things have been 'fixed' so many times
< wumpus>
I feel we don't really have any guidance with regard to UI
< wumpus>
but that's not quite unique among open source projects at least :)
< fanquake>
wumpus yea. I also feel that some of these "fixes" are likely to be incredibly low impact/probably noticed by very few people.
< fanquake>
I'd love to have a better insight into actual gui/os/version usage, so we could try and target "fixes" a little better, if anything.
< wumpus>
the biggest interaction issue with the UI, is that too much work happens in the UI loop and the thing hangs quite a lot
< wumpus>
in retrosepct I *sigh* should have gone with a more asynchronous design buut at the time, it was already so much work to port over the Wx UI at all
< wumpus>
also it's more or less usable and that seems to be a stable state
< fanquake>
It's also annoying that we have to continue to maintain obj-c code for macos, for things I'd have thought would be handled by qt.
< fanquake>
i.e 14597, we've got to keep some of it around because qt doesn't quite handle clicking on the dock icon?
< wumpus>
apart from occasional bouts of users complaining about a specific thing, then suddesnly forgetting about it again the next day, then it sits unchanged for years again :)
< wumpus>
also... so much of our UI code is working around limitations and bugs of Qt, you can't rely on things like 'click on dock', 'minimize', 'bring to foreground' to simply work with a single API call
< wumpus>
yes, as you say fanquake
< wumpus>
Qt is certainly not as nice as I thought at the time, I thought it would take care of most platform level issues and allow focusing on UI aspects
< wumpus>
but sometimes it feels liek piling hacks on hacks on hacks just to stay in the same place!
< fanquake>
Surprised we don't have a showUnNormalIfNotMinimized yet
< wumpus>
ideally that would be a built-in UI metaphor, it looks like we're fighting Qt there not working with it
< fanquake>
That is being refactored at the moment, and I can't imagine we'll be able to do it without breaking at least 1 behaviour somewhere
< fanquake>
I just can't test (and sometimes can't be bothered) to test trivial behaviours on "every" potential platform
< fanquake>
i.e I don't feel like spinning up Windows 7 vm (which I think we still support?)
< Divan>
hi all, is there a sandbox environment i can test transactions on?
< meshcollider>
Divan: yes, either testnet or regtest networks, but this isn't the place to discuss, please go to #bitcoin :)
< promag>
wumpus: looks like we need an issue compressor :P
< meshcollider>
promag: what exactly is one of those :P
< Divan>
okay , thank you. sorry.
< fanquake>
here's the DrahtBot mergocalypse
< promag>
fanquake: because of util/ change?
< fanquake>
promag yea, got about ~25 emails heh. Although quite a few older PRs in there.
< wumpus>
fanquake: that's one of the things that makes cross-platform native UI development pretty much an impossiblity nowadays, I suppose, there's a reason even large companies aren't bothering with it anymore
< wumpus>
fanquake: let alone open source projects
< wumpus>
there's such a maddening combination of operating systems, UI shells, hardware (esp GPU/monitor wise and input like keyboard/touchscreen), and everything has to work in all locales of course
< wumpus>
things that actually do work and work across a wide range of envirnoments need to get more appreciation
< wumpus>
but it's not possible to aim for everything perfectly
< wumpus>
am I... going to merge a PR that adds *one space*?
< promag>
lol
< fanquake>
wumpus well you just removed about 10, so better even it back out hah
< promag>
if you mean contrib/init/README.md I suggest to improve the markdown
< promag>
at least it could be a table
< provoostenator>
I'm getting "Invalid descriptor" when using an xpub, even using an example from descriptors.md: scantxoutset start '[{"desc": "pk(xpub661MyMwAqRbcFtXgS5sYJABqqG9YLmC4Q1Rdap9gSE8NqtwybGhePY2gZ29ESFjqJoCu1Rupje8YtGqsefD265TMg7usUDFdp6W1EGMcet8)"}]'
< provoostenator>
Also the next documented example uses hardened derivation after an xpub: pkh(xpub68...Dnw/1'/2)
< ezzzy>
btw this estimation is based on the speed at which bitcoind writes to stdout, so it might be a little off
< ezzzy>
I'm getting ~2 blocks per second where some days ago I was getting ~15-20
< wumpus>
so you're not comparing full sync times at different times, or with different versions, yes then it's difficult to say, if it's literally the sync slowing down for you on the fly, the validation probably has entered blocks with more transactions in them
< wumpus>
you're later in the chain, the later in the chain the (on average) bigger the blocks
< wumpus>
more transactions, more to validate, so less lbocks per second that's completely expected
< wumpus>
all that information is in the debug log, too
< wumpus>
so I'm sorry for nagging about this again, but please review #14532
< gribble>
https://github.com/bitcoin/bitcoin/issues/14532 | Never bind INADDR_ANY by default, and warn when doing so explicitly by luke-jr · Pull Request #14532 · bitcoin/bitcoin · GitHub
< ezzzy>
makes sense, blocks are definitely way bigger
< wumpus>
at some point this was the heat of discussion and now it's not even getting reviews in two weeks
< bitcoin-git>
bitcoin/master a4edb16 mruddy: ZMQ: add options to configure outbound message high water mark, aka SNDHWM
< bitcoin-git>
bitcoin/master dac2caa Wladimir J. van der Laan: Merge #14060: ZMQ: add options to configure outbound message high water mark, aka SNDHWM...
< promag>
thanks wumpus
< bitcoin-git>
[bitcoin] laanwj closed pull request #14060: ZMQ: add options to configure outbound message high water mark, aka SNDHWM (master...zmqhwm) https://github.com/bitcoin/bitcoin/pull/14060
< Sentineo>
hm interesting bug :)
< Sentineo>
load bitcoin-qt , use loadwalelt to load non default wallet, loadwalelt wallet.dat (why not try to load the default again) - and crash bitcoin-qt
< Sentineo>
does anyone have 0.16.3 here? I recall i could not reproduce it there, but nuked mine already
< Sentineo>
0.17.0 and 0.17.0.1 crash
< wumpus>
yes that's kind of annoying
< Sentineo>
I will open an issue shortly, tried only on ubuntu 18.04
< bitcoin-git>
bitcoin/master dfef0df practicalswift: tests: Dry run bench_bitcoin (-evals=1 -scaling=0: <1 second running time) as part "make check" to allow for quick identification of assertion/sanitizer failures in benchmarking code
< bitcoin-git>
bitcoin/master 73a8408 MarcoFalke: Merge #14092: tests: Dry run bench_bitcoin as part "make check" to allow for quick identification of assertion/sanitizer failures in benchmarking code...
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #14092: tests: Dry run bench_bitcoin as part "make check" to allow for quick identification of assertion/sanitizer failures in benchmarking code (master...dry-run-of-bench_bitcoin-as-part-of-check-local) https://github.com/bitcoin/bitcoin/pull/14092
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #14658: qa: Add test to ensure node can generate all help texts at runtime (master...Mf1811-qaRpcHelpMan) https://github.com/bitcoin/bitcoin/pull/14658
< bitcoin-git>
[bitcoin] instagibbs opened pull request #14664: example_test.py: fixup coinbase height argument, derive number clearly (master...example_cleanup) https://github.com/bitcoin/bitcoin/pull/14664
< luke-jr>
wtf, everything needs rebase⁇
< luke-jr>
what's the point of rebasing when by the time I'm done it needs another rebase?
< luke-jr>
(can we just switch to a rebase-just-prior-to-merge -or-when-major-rebasing-changes-needed model?)
< provoostenator>
I find regularly rebasing more effective than waiting a very long time. People can always review before you rebase, but it's non-trivial to check if a rebased update still matches the previous thing.
< provoostenator>
Ryanofsky has some incantations which show what's changed since the last rebase. Would be nice to get those into contrib/scripts.
< jnewbery>
luke-jr: after doing too many rebases, I've decided that it's easier just to have a smaller number of PRs open at any one time. It also helps focus reviewer time on the PRs that you've prioritized.
< luke-jr>
jnewbery: total time wasted on needless rebasing is the same that way though :/
< luke-jr>
provoostenator: checking the rebase once is less work than checking it every time something changes
< bitcoin-git>
bitcoin/master 9f49db7 practicalswift: Enable functional tests in UBSAN job. Enable -fsanitize=integer (part of UBSAN). Merge UBSAN Travis job with no depends.
< bitcoin-git>
bitcoin/master 1ba5583 MarcoFalke: Merge #14252: build: Run functional tests and benchmarks under the undefined behaviour sanitizer (UBSan)...
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #14252: build: Run functional tests and benchmarks under the undefined behaviour sanitizer (UBSan) (master...ubsan) https://github.com/bitcoin/bitcoin/pull/14252
< warren>
MarcoFalke: Hey, have you upgraded to Fedora 29? Have you tried bitcoin-qt since?
< phantomcircuit>
wumpus, believe i've addressed all the concerns for #14336
< warren>
Hmm, bitcoin-qt no longer works at all ever since I upgraded to Fedora 29. It doesn't appear to do anything to ~/.bitcoin either. Nothing is being written to debug.log. Will dig more.
< MarcoFalke>
warren: There is an issue with the Bitcoin Core gui and qt-5.11 on the 0.17 branch