< bitcoin-git>
[bitcoin] 251Labs opened pull request #12074: [qt] Optimizes boolean expression model && model->haveWatchOnly() (master...patch/TransactionView-optimize-boolean-expression) https://github.com/bitcoin/bitcoin/pull/12074
< bitcoin-git>
[bitcoin] fanquake opened pull request #12075: [scripts] Add missing univalue file to copyright_header.py (master...copyright-add-missing) https://github.com/bitcoin/bitcoin/pull/12075
< cloudrunner_>
join #litecoin
< cloudrunner_>
sorry, a typepo
< xiedeacc>
hi, output of block 0 can't be spent as this would allow Satoshi to fork the network. how could this happen ? because at first bitcoin released by Satoshi, the coinbase of block 0 cannot spendable, so if some client allow that address spend, then Satoshi can fork a new blockchain from block 0, and mine his own blockchain more longer than legal blockchain in a private way, then satoshi publish his blockchain, made legal blcokchain cancelled?
< provoostenator>
Or maybe the "simple IPC mechanism" wouldn't need the RPC, but it's not clear to me how this would work (other than the fallback to BIP21, but that's not enough).
< space_424>
▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!ejcphbsep: Mattie161^ Kozuch lio17 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!nmdjhx: t0adst00l Mattie161^ echonaut ▄▄▄▄▄▄▄▄▄▄▄
< space_424>
â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!rktuneumtw: mcochrane adiabat owowo â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â
< space_424>
▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!cuekxoofx: echonaut luke-jr BashCo_ ▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!pfvxh: whphhg mbcav emzy ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!pdlzlnnlnm: booyah LeMiner vicenteH ▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!wtofobs: whphhg booyah Randolf ▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!cwvhfxhw: Guyver2 ghost43 niska ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!abbhbve: goatpig Dyaheon lnostdal ▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!buqapqhaoh: mrfrasha mbcav unholymachine ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!vzhcjud: n1bor lio17 BashCo_ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!otnqqx: mcochrane Dyaheon dcousens â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!cmgzs: Dyaheon echonaut n1bor ▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!hfsnvlcn: meshcollider contrapumpkin Kozuch ▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!bwmnwbb: Guyver2 echonaut luke-jr ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!gcetqww: echonaut promag Guest70592 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!nkmqurhiv: lio17 mrfrasha fanquake â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–
< space_424>
▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!rsjrxqc: BashCo_ t0adst00l whphhg ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!swbns: d9b4bef9 mcochrane laurentmt ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!rwhrwup: unholymachine meshcollider Mattie161^ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!miquhuvcfw: dcousens nullptr| meshcollider ▄▄▄▄▄▄▄▄▄▄▄▄
< fanquake>
beh sipa/wumpus ^
< space_424>
▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!npcaa: LeMiner dcousens luke-jr ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!fxpbiv: davec owowo indistylo ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!flxcumttaf: BashCo_ Guest70592 Guyver2 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!uwzflf: Cheeseo mrfrasha meshcollider ▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!hquper: emzy goatpig Mattie161^ ▄▄▄▄▄▄▄▄▄▄▄▄
< space_424>
▄▄▄▄▄▄▄▄▄▄▄▄ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!jqycncivh: fanquake jouke__ Emilia21Graham ▄▄▄▄▄▄▄▄▄▄▄
< space_424>
â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„ ANOTHER EXPLOIT HAS BEEN FOUND IN WEECHAT ONE THAT SENDS YOUR LOGS TO THE DEVS IP ADDRESS!!rxcfqvc: ghost43 emzy meshcollider â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–
<@sipa>
no way to make chanserv enforce +c and +n on this channel?
< mryandao>
you could, #bitcoin has those modes enabled.
< NielsvG>
sipa: /msg ChanServ SET <channel> MLOCK <mode>
<@sipa>
NielsvG: thank you!
< kinlo>
sipa: I believe -n was done for bitcoin-git
< aj>
there's an option for colours there too, which might need to be unset?
< sipa>
hmm
< sipa>
i guess i'll leave it off for now
< plp_>
Gents, quick question. What's the best channel for people outside the dev community to submit ideas? Thanks
< meshcollider>
plp_: probably ask in #bitcoin to see if the ideas been suggested before, and then use the mailing list
< plp_>
thanks!
< provoostenator>
The function tests keep saying "WARNING! There is already a bitcoind process running on this system." which is a lie! :-) How does it check this?
< aj>
provoostenator: it runs "pidof bitcoind" and checks for output
< provoostenator>
I installed pidof via homebrew (it's not part of MacOS) for some other project, so maybe that works slightly different than the linux variant.
< provoostenator>
Other question: what's supposed to be the difference between qt/bitcoin.cpp and qt/bitcoin-gui.cpp? And why are they both importing qt/bitcoin-gui.h (theres no qt/bitcoin.h)?
< provoostenator>
aj: pidof bitcoind returns nothing when these tests aren't running and returns the ids for all the regtest instances when it does run.
< bitcoin-git>
[bitcoin] akx20000a closed pull request #12062: Increment MIT Licence copyright header year on files modified in 2017 (master...2018) https://github.com/bitcoin/bitcoin/pull/12062
< bitcoin-git>
[bitcoin] akx20000a reopened pull request #12062: Increment MIT Licence copyright header year on files modified in 2017 (master...2018) https://github.com/bitcoin/bitcoin/pull/12062
< exs>
hi, found that chan now. can someone be so kind and explain me why you should not increase the blocksize in bitcoin?
< belcher>
wrong channel, ask in #bitcoin
< bitcoin-git>
[bitcoin] 251Labs opened pull request #12077: Fixes issue #12067 `sendmany` curl example is wrong. (master...patch/12067/fixes-sendmany-curl-example) https://github.com/bitcoin/bitcoin/pull/12077
< spudowiar>
Is 3b7cd5d89a226426df9c723d1f9ddfe08b7d1def a commit from Satoshi Nakamoto? The Git author is s_nakamoto <s_nakamoto@1a98c847-1fd6-4fd8-948a-caf3550aa51b> but I wanted to check whether these are accurate to the original authors
< spudowiar>
Or whether that could have been sirius-m, etc.
< larafale>
at the Address gap limit it says : "We scan just the external chains, because internal chains receive only coins that come from the associated external chains"
< larafale>
I'm trying to reconstitute a balance deriving addresses of an xpubkey, but in order to get the account balance, i need to also look up for utxos in in the internal chain (change address)
< larafale>
so my question is : can you confirm that in order to get the balance of an utxo set, you must also scan for internal address ?
< larafale>
just to be sure i'm not missing anything :) thx
< phantomcircuit>
larafale, "internal chains" are used only for change, so if you hit a single one that is unused, that *might* mean that there are no more
< phantomcircuit>
however that's not really a strong guarantee
< larafale>
yes ok i get that, but if i'm launching an account discovery on an xpub key that already have a lot of received and change adresses used, in order to get the total balance associated to that xpub i do have to look for change address
< larafale>
it's just that the BIP 44 says that we don't need to scan for internal addresses
< larafale>
but if i don't do that I'm unable to get total balance
< larafale>
can you confirm ? :)
< digger>
Join
< larafale>
I'm already succefully achieving what i want to do (which is get total balance of an xpub key), but bip 44 confused me, and I just want to make sure that scanning for both received & change address is the good way to achieve account discovery
< phantomcircuit>
larafale, it depends on how expensive it is to check for previous usage
< phantomcircuit>
if you have a complete set of all the script pubkeys ever used
< phantomcircuit>
then it's cheap
< phantomcircuit>
but building/maintaining that is not cheap
< phantomcircuit>
so
< phantomcircuit>
:shrug:
< larafale>
@phantomcircuit Electrum let you query utxos by address, so i'm proxying to my electrum client to scan.
< larafale>
phantomcircuit: ok thx for the feedback
< * luke-jr>
wonders what HD wallets do for refund addresses (BIP70)
< larafale>
luke-jr: thx will check
< sipa>
luke-jr: they're treated as new addresses
< phantomcircuit>
larafale, ye but for current utxo's or for old ones?
< phantomcircuit>
cause you need to know about transaction outputs generallt not just unspent ones for that