< mryandao>
hi, i just ran `ldd` on bitcoin-cli and noticed that it requires libboost, is it really necessary?
< bitcoin-git>
[bitcoin] OmeGak opened pull request #11419: Utils: Fix launchctl not being able to stop bitcoind (master...fix-macos-init) https://github.com/bitcoin/bitcoin/pull/11419
< bitcoin-git>
[bitcoin] maaku opened pull request #11418: Add error string for CLEANSTACK script violation (master...cleanstack-error-code) https://github.com/bitcoin/bitcoin/pull/11418
< bitcoin-git>
[bitcoin] laanwj closed pull request #11414: [docs] Remove partial gitian build instructions from descriptors dir. (master...gitian-cleanups) https://github.com/bitcoin/bitcoin/pull/11414
< bitcoin-git>
bitcoin/master bbc901d Wladimir J. van der Laan: Merge #11414: [docs] Remove partial gitian build instructions from descriptors dir....
< bitcoin-git>
bitcoin/master bb174e1 fanquake: [docs] Remove partial gitian instructions from descriptors dir
< jnewbery>
suggested topic: next Bitcoin Core meetup
< gmaxwell>
ISTM the caller will need a consierable amount of complexity to avoid losing data, vs sending a poll every coupld seconds. Polling faster than seconds hardly makes sense in the context of bitcoin in any case, since txn take seconds to propagate through the network.
< gribble>
https://github.com/bitcoin/bitcoin/issues/8498 | Near-Bugfix: Optimization: Minimize the number of times it is checked that no money... by jtimon · Pull Request #8498 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] laanwj closed pull request #10858: [RPC] Add "errors" field to getblockchaininfo and unify "errors" field in get*info RPCs (master...getblockchaininfo-errors) https://github.com/bitcoin/bitcoin/pull/10858
< bitcoin-git>
bitcoin/master 395cef7 Andrew Chow: Change getmininginfo errors field to warnings...
< bitcoin-git>
bitcoin/master f77f0e4 Andrew Chow: Add warnings field to getblockchaininfo
< bitcoin-git>
bitcoin/master 8502b20 Andrew Chow: Unify help text for GetWarnings output in get*info RPCs
< bitcoin-git>
[bitcoin] jimpo opened pull request #11411: script: Change SignatureHash input index check to an assert. (master...sighash-bounds-check) https://github.com/bitcoin/bitcoin/pull/11411
< bitcoin-git>
[bitcoin] mess110 opened pull request #11410: [rpc] [tests] Add minrelaytxfee to getmempoolinfo (master...add_minrelaytxfee_to_getmempoolinfo) https://github.com/bitcoin/bitcoin/pull/11410
< instagibbs>
wraithm, https://github.com/bitcoin/bitcoin/pull/9728 does hd watchonly, but as sipa said, how it interacts with stuff is non-trivial. I think a lot of the corner-cases go away post-overhaul
< kebman>
Any technical documentation on how Bitcoin signs messages?
< kebman>
Can anyone guide me to good resources on how to programmatically sign messages with a Bitcoin address?
< jnewbery>
boltzar: please ask at #bitcoin or https://bitcoin.stackexchange.com/ . This is a channel for discussing Bitcoin Core development
< boltzar>
is: on my bitcoind server after i make 25 unconfirmed transactions they stop showing on blockchain.info for example untill they confirm ( the payments are made because i can see the tx hashes ) . Now i use another bitcoin api from block.io . Using their api i can make the same a lot of unconfirmed transactions , but their transactions are showing on blockchain.info even if there are
< boltzar>
hello guys. i have a small issue. i own an exchange website and i usually use bitcoind to send the bitcoin to my clients. With these problems in the bitcoin network sometimes i have activated these options walletrejectlongchains=false , limitancestorcount=1000 , limitdescendantcount=1000 . If i didn't activate these my api would stop working on 25 unconfirmed transactions . The issue
< bitcoin-git>
[bitcoin] instagibbs opened pull request #11407: add functional test for mempoolreplacement command line arg (master...testmempoolreplacearg) https://github.com/bitcoin/bitcoin/pull/11407
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #11406: Add state message print to AcceptBlock failure message. (master...2017-09-checkblock-fail-print) https://github.com/bitcoin/bitcoin/pull/11406
< gmaxwell>
jtimon: Making everything use the same rpc port means you cannot run testnet and bitcoin at the same time anymore except through manually configuring them.
< jtimon>
esotericnonsense: for bitcoin-cli, specifying -testnet does the same as -rpcport=18332, if you specify rpcport, specifying -testnet is completely meaningless
< sipa>
with the bias, that can pretty much only happen for P2P default port, which is very unlikely to have any interesting services running, other than bitcoin :)
< sipa>
jtimon: otherwise you can spam the network with addr messages for services you don't like, and get the whole bitcoin network to try connecting to them
< analiser>
look like #10783 041dad9 RCP Various rpc argument fixes(instagiibbs) in the 0.15 channelog is what cause some errors in python bicoinlib module i just solve the issue removing from module bitcoin SelectParams() attribute and from bitcoin.rpc remove Proxy() attribute hope that work for any here
< bitcoin-git>
[bitcoin] sipa opened pull request #11389: Support having SegWit always active in regtest (master...201709_itsalwayssegwitinregtestia) https://github.com/bitcoin/bitcoin/pull/11389
< bitcoin-git>
[bitcoin] sipa closed pull request #11362: Remove nBlockMaxSize from miner opt struct as it is no longer used. (master...2017_09_rm_nBlockMaxSize) https://github.com/bitcoin/bitcoin/pull/11362
< bitcoin-git>
bitcoin/master c6223b3 Pieter Wuille: Merge #11362: Remove nBlockMaxSize from miner opt struct as it is no longer used....
< bitcoin-git>
bitcoin/master 22fd04b Gregory Maxwell: Remove nBlockMaxSize from miner opt struct as it is no longer used.
< ossifrage>
gmaxwell, it doesn't seem to be IO or CPU bound, but I am using spinning rust, it seemed wasteful to eat up a large % of my ssd on bitcoin
< ossifrage>
gmaxwell, I had a 4G dbcache which was part of the reason the oom killer picked on bitcoin
< ossifrage>
That is really annoying chrome decided to eat up all the memory, but the oom killer took out bitcoin (while doing a reindex) and somehow the progress went from 99ish% to 85%, that is quite a bit of rollback
< gribble>
https://github.com/bitcoin/bitcoin/issues/7533 | RPC: sendrawtransaction: Allow the user to ignore/override specific rejections by luke-jr · Pull Request #7533 · bitcoin/bitcoin · GitHub
< wumpus>
importing keys in bitcoin core is considered advanced functionality anyhow
< kallewoof>
Someone wrote a post about that on reddit. One of the devs said two weeks I think. (LN is actually not bitcoin core, but a separate client entirely.)
< achow101>
I wonder if gavin made bitcoin xt or bitcoin classic releases signed with that key...
< kallewoof>
Would it be worth it to add a replay protection mechanism in Bitcoin where a NOP is replaced with <height> <blockhash> OP_CHECKBLOCKVERIFY which would fail if the hash of the block at the given height did not match <blockhash>? (It would probably require that <height> was less than <current height> - 100 to avoid nasty double spends at reorgs...)
< bitcoin-git>
[bitcoin] tomasvdw opened pull request #11376: Ensure backupwallet fails when attempting to backup to source file (master...core) https://github.com/bitcoin/bitcoin/pull/11376
< ThomasV>
well, p2pk is a bit different, because you do not create a bitcoin address for it
< bitcoin-git>
[bitcoin] laanwj closed pull request #11132: Document assumptions that are being made to avoid NULL pointer dereferences (master...document-non-nullptr-assumptions) https://github.com/bitcoin/bitcoin/pull/11132
< bitcoin-git>
bitcoin/master 551d7bf Wladimir J. van der Laan: Merge #11132: Document assumptions that are being made to avoid NULL pointer dereferences...
< bitcoin-git>
bitcoin/master fdc3293 practicalswift: Document assumptions that are being made to avoid NULL pointer dereferences
< BlueMatt>
https://github.com/bitcoin/bitcoin/issues/11373 should just be closed with "Your filesystem permissions have been set to prevent bitcoind from accessing its datadir, which prevents it from starting" (unless someone wants to change it to a "we need a better error message for this bug" issue)