< meshcollider> cfields: yeah about time, whats that, nearly 14.5 hours since wumpus tagged the release ;)
< meshcollider> PRed my sigs too
< achow101> Updated my sigs PR with the codesigned ones
< bitcoin-git> [bitcoin] MeshCollider opened pull request #11610: Update release notes for 0.15.1 (0.15...201711_releasenotes0151) https://github.com/bitcoin/bitcoin/pull/11610
< meshcollider> ryanofsky: you should add the script from https://github.com/bitcoin/bitcoin/pull/11592#pullrequestreview-73922693 to contrib/devtools/ IMO
< bitcoin-git> [bitcoin] fanquake opened pull request #11611: [build] Don't fail when passed --disable-lcov and lcov isn't available (master...dontfaillcov) https://github.com/bitcoin/bitcoin/pull/11611
< fanquake> Yea I think we had a few new contributors.
< wumpus> wampy and sjors :)
< wumpus> I think we've seen wampy before
< fanquake> Yes I think so
< wumpus> whoa meshcollider achow101 fanquake michagogo cfields and anyone I forgot thanks for gitian building so quickly
< wumpus> gmaxwell: I'd even expect little benefit from lto across library boundaries in code that uses secp256k1, pretty much all secp256k1 operations take significant time and probably little would be won in e.g. inlining/specializing them into the caller
< wumpus> heh someone sent me a peers.dat that crashes 0.15.0, turns out the problem is already solved in 0.15.1, that's awesome
< instagibbs> wumpus, I feel like this issue must have started recently, ran into it during core dev SF, and multiple incidents from others since then
< instagibbs> oh i guess 0.15 eh
< meshcollider> wumpus: cool yeah, is that because of #11252 backport
< meshcollider> #11252
< gribble> https://github.com/bitcoin/bitcoin/issues/11252 | [P2P] When clearing addrman clear mapInfo and mapAddr. by instagibbs · Pull Request #11252 · bitcoin/bitcoin · GitHub
< netyul> oi
< wumpus> instagibbs: I guess it still doesn't explain why the file gets corrupted, but not crashing is good, thanks for the fix :)
< instagibbs> right, mine was specifically running out of battery, but others seems not the case
< wumpus> oh indeed it might be something like truncating while writing due to unclean exit
< wumpus> more robustly it would write to peers.dat.tmp and then do an atomic rename when finished
< wumpus> we did a similar thing with the auth cookie
< wumpus> (though for a different reason)
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/2ce9e586d5b11e1f61af4db27b7326687d5e5124
< bitcoin-git> bitcoin/0.15 2ce9e58 Wladimir J. van der Laan: doc: Fill in 0.15.1 changelog and authors in release notes...
< wxss> the Windows binaries are still signed by The Bitcoin Foundation, Inc. -- that is kinda gross
< wumpus> yeah... working on that
< wumpus> it's a lot of paperwork though
< wumpus> OS code signing is always a problem for open source projects as they're not released by a company
< MarcoFalke> I recall the key will expire soon, no?
< Sentineo> wumpus: in that case do some dev guys have to do that work as a person(not company)? Or the open source project figures as an entity?
< wumpus> Sentineo: the problem is that they don't recognize an open source project as entity (because it isn't really one) - I'm sure I could get a signing key for my company, or have one of the well-known companies in the space provide a signing key, it's not like we lack options, but whoever signs it is going to raise questions.
< Sentineo> right
< Sentineo> human nature, nothing is enough ;)
< Sentineo> ty
< LumberCartel> wxss: What's the problem with The Bitcoin Foundation, Inc.?
< wumpus> Sentineo: yeah it's a political issue, not a technical one, so much harder. If only OSes supported decentralized signing e.g. gitian builds.
< wumpus> LumberCartel wxss please take the fight about TBF outside :)
< LumberCartel> wumpus: Sorry, I was asking a genuine question -- I wasn't aware that there's a problem there.
< Sentineo> wumpus: that would be nice, but gitian build looks pretty complicated. in my todolist to try it out though. It is the best way of ensuring the code one runs.
< wumpus> LumberCartel: let's say the bitcoin foundation has a checkered reputation, there's been so much drama about it. But it's off topic here, #bitcoin would be a better place to discuss.
< sipa> also, none of the people currently involved with bitcoin core development are working for the foundation anymore
< achow101> wumpus: have blockstream sign it :p
< sipa> ignoring any political drama, that on itself should be sufficient reason i think
< wumpus> sipa: that's true, though maybe it's not necessary for anyone to work for them to act as a neutral trusted signee, except that they're not that :)
< LumberCartel> wumpus: Okay, thanks. If there is a need to start a company, or a non-profit society, I can certainly help with getting that started from here in Canada as I'm quite familiar with the process here. I'm willing to help with that even if it's an enttity whose sole purpose is to satisfy OS code
< wumpus> achow101: I was waiting for that one
< sipa> wumpus: fair
< LumberCartel> I'll just leave it at that.
< LumberCartel> signing requirements.
< wumpus> LumberCartel: thanks!
< wumpus> LumberCartel: yes, some kind of very formal setup would be best - an organization whose sole purpose is to sign the executables when a certain gitian builder threhold is reached
< LumberCartel> wumpus: You're welcome. Those kinds of conditions can be specified in the mandate before the organization is started.
< LumberCartel> wumpus: There would be a need for an AGM with an election for who are the directors. I can even help with setting this up without having to be a director myself -- the elected directors would have the control.
< LumberCartel> wumpus: The fees aren't very high, and I could find out what's all required if people here are in agreement with going ahead with this.
< LumberCartel> wumpus: Just in case you want to know how to contact me (e.g., while I'm not on IRC), my real name is Randolf and my details are on my web site, here: https://www.randolfrichardson.com/contact/
< wxss> wumpus: maybe nChain/CSW could sign the executables with the private key of the genesis block, that should solve a lot of problems at once
< wumpus> LumberCartel: okay!
< wumpus> wxss: lol, yes but it would be only verifyiable on laptops that he provides :p
< jl2012> wumpus: "factory sealed laptop!"
< Blackcode> Hi friends, watch this video on youtube, I just tried it and it's really perfect. https://youtu.be/UEm0f1PihWo Send me a message in private, and I send you the password and activation key for free.
< Danini_> Hi friends, watch this video on youtube, I just tried it and it's really perfect. https://youtu.be/UEm0f1PihWo Send me a message in private, and I send you the password and activation key for free.
< promag> omg ^
< analiser> if bitcoin-cli move and accounts are deprecated how should i identify users ? only by address?
< wumpus> analiser: you can still use labels, there are just no balances anymore
< wumpus> but a label can still mark a group of addresses, say, the receiving addresses of a user
< analiser> cool i will read about it
< analiser> tk is hard find the right way to off-block-chain transaction
< dongcarl> w/re #9195, would it make sense to write out a BNF/EBNF representation of the RPC-console language for documentation? (starting with single RPC commands first then describing things that are in #7783 (nested commands and simple value queries))?
< gribble> https://github.com/bitcoin/bitcoin/issues/9195 | Debug console needs a little documentation on usage · Issue #9195 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/7783 | [Qt] RPC-Console: support nested commands and simple value queries by jonasschnelli · Pull Request #7783 · bitcoin/bitcoin · GitHub
< wumpus> dongcarl: yes, something like that could probably be helpful
< analiser> wumpus, bitcoin-cli getnewaddress "test" this you mean by labels?
< dongcarl> wumpus: would it make more sense to write a YACC file or a BNF/EBNF representation? I think perhaps more value would be added if the representation could be used in parsing/validating/etc.
< wumpus> dongcarl: really any kind of documentation in the debug console would be nice, but I'm not sure that would be understandable for many users
< wumpus> dongcarl: what I mean in the issue is just a small manual page or so, that explains how to use the nested commands, it doesn't need to be a formal, fully detailed description of the entire system
< wumpus> analiser: yes
< analiser> should we still use (bitcoin-cli move "label1" "label2" amount) to move off-chain funds between labels?
< analiser> just ask because seems deprecated
< wumpus> no, labels don't contain funds
< wumpus> they are just a tag to group one or more addresses
< analiser> work great on v13
< analiser> i dont disturb you guys anymore tk for your time i will try find more documentation
< wumpus> it works on 0.13 because 0.13 (and 0.15) still have the account system. But that's going away, there is no concept of 'off chain funds' or balances anymore.
< analiser> where i can find documentation because im working on site and this is critical
< analiser> about sysmbolic moving funds between labels
< wumpus> labels *have no funds*
< wumpus> for the last time, they are just a convenient tag for addresses, they are not accounts and do not have balances
< analiser> i know but address inside labels yes
< jijojohn> hello
< jijojohn> how can i create a bitcoin wallet app...
< jijojohn> do you guys have any resources on bitcoin wallet development ?
< wxss> jijojohn: try #bitcoin or #bitcoin-dev, this channel is for dev of Bitcoin Core
< bitcoin-git> [bitcoin] jonasschnelli pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/2f959a58744d...0cc98763919a
< bitcoin-git> bitcoin/master 41b15cf Sjors Provoost: Add sjors gitian key
< bitcoin-git> bitcoin/master 0cc9876 Jonas Schnelli: Merge #11607: Add Gitian PGP key: Sjors...
< bitcoin-git> [bitcoin] astanway opened pull request #11614: ZMQ: Add decodedtx topic for JSON tx publishing (master...master) https://github.com/bitcoin/bitcoin/pull/11614