< August 2022 >
Su Mo Tu We Th Fr Sa 123456789 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31
2016-11-07
< GitHub68>
[bitcoin] MarcoFalke opened pull request #9093: [doc] release-process: Mention GitHub release and archived release notes (master...Mf1611-docRel) https://github.com/bitcoin/bitcoin/pull/9093
< MarcoFalke>
I feel like we should change the releases to only contain a link to the release notes and not the full release notes copied: https://github.com/bitcoin/bitcoin/releases
< GitHub104>
[bitcoin] rebroad opened pull request #9091: Optimize sending of getheaders when pindexLast is an ancestor of pindexBestHeader (master...OptimizeMoreGetheaders) https://github.com/bitcoin/bitcoin/pull/9091
< GitHub137>
[bitcoin] rebroad opened pull request #9088: Reduce ambiguity of warning message (master...LessAmbiguousWalletWarning) https://github.com/bitcoin/bitcoin/pull/9088
< GitHub182>
[bitcoin] jtimon opened pull request #9087: RPC: WALLET: why not give more details when "generate" fails? (master...0.13-errors-rpc-mining) https://github.com/bitcoin/bitcoin/pull/9087
< jtimon>
whphhg: now that you mention god instead of the creator of the system, it comes to mind that we should probably have #bitcoin-religion to redirect people who make such comments, or commments like this one
< jtimon>
or 29 new users upgrading from a bitcoin bank to a full node :p
< rebroad>
Victorsueca, I hope you are right... although I do get the impression that zcash has some quite clever technology in it... but why ddn't they help put this into bitcoin instead of an alt-coin... well.. I think I already know the answer to this... greed
< Victorsueca>
actually nobody cares about classic or zcash, there's no competition at all because reasonable people just ignores them, they will eventually die like all other attempts to compete with bitcoin did so nothing to worry about and nothing we can do about
< rebroad>
I just want to see bitcoin do well. I certainly don't want to see anyone burn out.. i'd rather see more collaboration rather than empire building
< rebroad>
wumpus, gmaxwell, just want to say thank you for all the hard work you do on bitcoin-core and apologies that I sometimes facilitate a perception of distraction from the more important duties... certainly not my intention. and apologies for the paranoia I sometimes exhibit.. I just find it so hard to understand some of your decisions but I realise you feel you have too little time to explain them fully, so it's ok
< GitHub47>
[bitcoin] rebroad opened pull request #9082: Fix peer selection so that non-Witness peers are still connected to (master...FixPeerSelection) https://github.com/bitcoin/bitcoin/pull/9082
< gribble>
https://github.com/bitcoin/bitcoin/issues/8969 | Decouple peer-processing-logic from block-connection-logic (#2) by TheBlueMatt · Pull Request #8969 · bitcoin/bitcoin · GitHub
< GitHub2>
[bitcoin] instagibbs opened pull request #9073: Trivial: Add common failure cases for rpc server connection failure (master...rpcnoconnectstring) https://github.com/bitcoin/bitcoin/pull/9073
< GitHub52>
bitcoin/master fcf61b8 Wladimir J. van der Laan: Merge #9050: net: make a few values immutable, and use deterministic randomness for the localnonce...
< GitHub54>
[bitcoin] laanwj closed pull request #9050: net: make a few values immutable, and use deterministic randomness for the localnonce (master...connman-const) https://github.com/bitcoin/bitcoin/pull/9050
< GitHub52>
bitcoin/master aff6584 Cory Fields: net: constify a few CNode vars to indicate that they're threadsafe
< GitHub52>
bitcoin/master 59ac5c5 Cory Fields: net: Use deterministic randomness for CNode's nonce, and make it const
< GitHub156>
[bitcoin] laanwj closed pull request #9061: Ignore getheaders prior to passing all checkpoints. (master...FixGetheadersResponseWhenSyncing) https://github.com/bitcoin/bitcoin/pull/9061
< GitHub127>
[bitcoin] sipa closed pull request #9053: IBD using chainwork instead of height and not using header timestamps (master...no_checkpoint_for_ibd) https://github.com/bitcoin/bitcoin/pull/9053
< GitHub151>
[bitcoin] jnewbery opened pull request #9069: Clean up bctest.py and bitcoin-util-test.py (master...btutiltestcleanup) https://github.com/bitcoin/bitcoin/pull/9069
< GitHub86>
bitcoin/master bae81b8 Wladimir J. van der Laan: Merge #8674: tools for analyzing, updating and adding copyright headers in source files...
< GitHub54>
[bitcoin] laanwj closed pull request #8674: tools for analyzing, updating and adding copyright headers in source files (master...copyright-scripts) https://github.com/bitcoin/bitcoin/pull/8674
< GitHub86>
bitcoin/master 159597a isle2983: [devtools] script support for managing source file copyright headers...
< BlueMatt>
yes, wouldve been hilarious if that ended up in bitcoin
< GitHub77>
[bitcoin] laanwj closed pull request #9063: Do not shadow variable, use deprecated MAP_ANON if MAP_ANONYMOUS is not defined (master...20161102_fix_lockedpool) https://github.com/bitcoin/bitcoin/pull/9063
< GitHub68>
bitcoin/master f2a6e82 Wladimir J. van der Laan: Merge #9063: Do not shadow variable, use deprecated MAP_ANON if MAP_ANONYMOUS is not defined...
< GitHub68>
bitcoin/master 4a9f3c5 Pavel Janík: Do not shadow variable, use deprecated MAP_ANON if MAP_ANONYMOUS is not defined.
< GitHub123>
[bitcoin] paveljanik opened pull request #9063: Do not shadow variable, use deprecated MAP_ANON if MAP_ANONYMOUS is not defined (master...20161102_fix_lockedpool) https://github.com/bitcoin/bitcoin/pull/9063
< gmaxwell>
achow101: using software bitcoin's creator wrote which has never been publically distributed.
< gmaxwell>
achow101: sounds fine to me more or less.. Perhaps "Warning: This is outdated and network-inconsistent software. Also, the alert system has been deprecated. Upgrade is strongly recommended. See https://bitcoin.org/alert-retirement"
< achow101>
so, how about "Warning: Network rules in this version are out of date. Additionally the Alert System has been deprecated. Upgrade is strongly recommended. See https://bitcoin.org/alert-retirement"
< achow101>
gmaxwell: so just make the message "Warning: This version is obsolete. The Alert System has been deprecated. Upgrade is strongly recommended. See: https://bitcoin.org/alert-retirement"
< BlueMatt>
bitcoin 0.10.4 released
< morcos>
theuni/bitcoin/copy-move
< GitHub45>
[bitcoin] ryanofsky opened pull request #9058: Fixes for p2p-compactblocks.py test timeouts on travis (#8842) (master...fix-8842-sync-timeouts) https://github.com/bitcoin/bitcoin/pull/9058
< gmaxwell>
https://github.com/bitcoin/bitcoin/pull/9053 < can someone trigger a rerun here? I'm pretty sure this change couldn't make test_bitcoin fail (and it passes locally.)
< gribble>
https://github.com/bitcoin/bitcoin/issues/9053 | IBD using chainwork instead of height and not using header timestamps by gmaxwell · Pull Request #9053 · bitcoin/bitcoin · GitHub
< GitHub58>
[bitcoin] gmaxwell opened pull request #9053: IBD using chainwork instead of height and not using header timestamps (master...no_checkpoint_for_ibd) https://github.com/bitcoin/bitcoin/pull/9053
< GitHub141>
[bitcoin] gmaxwell opened pull request #9052: Use RelevantServices instead of node_network in AttemptToEvict. (master...prefer_relevant2) https://github.com/bitcoin/bitcoin/pull/9052
2016-10-31
< BlueMatt>
I mean its easy...4 digit number starting with a # and link to github.com/bitcoin/bitcoin/issue/#
< GitHub106>
[bitcoin] theuni opened pull request #9050: net: make a few values immutible, and use deterministic randomness for the localnonce (master...connman-const) https://github.com/bitcoin/bitcoin/pull/9050
< GitHub112>
[bitcoin] TheBlueMatt opened pull request #9049: Remove duplicatble duplicate-input check from CheckTransaction (master...2016-10-bench-checkblock) https://github.com/bitcoin/bitcoin/pull/9049
< GitHub178>
[bitcoin] TheBlueMatt opened pull request #9045: Hash P2P messages as they are received instead of at process-time (master...2016-10-p2p-hash) https://github.com/bitcoin/bitcoin/pull/9045
< GitHub139>
[bitcoin] paveljanik closed pull request #8468: Do not shadow member variables in serialization (master...20160805_Wshadow_serialization) https://github.com/bitcoin/bitcoin/pull/8468
< GitHub107>
[bitcoin] MarcoFalke opened pull request #9043: [qt] Return useful error message on ATMP failure (master...Mf1611-qtATMPerror) https://github.com/bitcoin/bitcoin/pull/9043
< GitHub141>
[bitcoin] MarcoFalke opened pull request #9042: [rpc] ParseHash: Fail when length is not 64 (master...Mf1611-rpcParseHash64) https://github.com/bitcoin/bitcoin/pull/9042
< Victorsueca>
does bitcoin core support 64-bit POSIX time?
< GitHub115>
[bitcoin] sipa opened pull request #9039: Various serialization simplifcations and optimizations (master...simpleserial) https://github.com/bitcoin/bitcoin/pull/9039
2016-10-28
< GitHub166>
[bitcoin] EthanHeilman opened pull request #9037: net: Add test-before-evict discipline to addrman (master...test-before-evict) https://github.com/bitcoin/bitcoin/pull/9037
< ArtGravity>
Just the logo covering the "Bit" in Bitcoin Core
< ArtGravity>
in the 8043 screenshot, where it says Bitcoin Core - Wallet at the top left of the screen is where it should have the usual menus
< ArtGravity>
my icon appears where the B in Bitcoin Core is in the image on 8043
< BlueMatt>
I'd like to nominate https://github.com/bitcoin/bitcoin/pull/9026 (well, a variant of it, because that is gonna end up adapting to some reorgs that are in-progress) for 0.13.2
< petertodd>
morcos: again, this is a scenario where bitcoin as you know it is horribly insecure - anyone with >10 machines could attack your min-diff chain. I had a high enough credit limit as a student to buy more machines than that. :)
< petertodd>
Chris_Stewart_5: yes, removiing is a hard fork, but remember we're talking about a situation where bitcoin as you know it is useless, so tha'ts irrelevant IMO
< petertodd>
jeremyrubin: yes, and at that point your idea of what bitcoin is is so insecure as to be useless
< petertodd>
wumpus: right, I mean, w/o the minimum diff thing, the effect would be no different than ensuring bitcoin core shipped with blockchain data
< petertodd>
note that from the point of view of consensus this is technically speaking no different than making bitcoin core come with a set of blockchain data
< BlueMatt>
Frederic94500: we're in the middle of a meeting, please go to #bitcoin
< Frederic94500>
#bitcoin If segwit doesn't activate, he will be activate to the next 2016 blocks?
< jtimon>
I'm still trying to test the blocksigning stuff, but the "custom chain" code that preceeds it is pretty much ready I think (feel free to test it and give suggestions), see https://github.com/bitcoin/bitcoin/pull/8994
<@wumpus>
or magnet:?xt=urn:btih:dbe48c446b1113890644bbef03e361269f69c49a&dn=bitcoin-core-0.13.1&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&ws=https%3A%2F%2Fbitcoin.org%2Fbin%2F
< btcdrak>
achow101_: looks like everything has been done barring release notes and upload to bitcoin.org
< andytoshi>
kanzure: no, i have a rust json parsing library for bitcoin purposes, a low-priority TODO is for me to aggressively compare its behaviour to that of univalue