< kinlo>
asu: that question is for #bitcoin, not for here
< asu>
buy i found if my customer send 0.01bitcoin to another, the fee is 0.00027 bitcoin
< asu>
i want to build a bitcoin p2p trade web
< bitcoin-git>
[bitcoin] laanwj closed pull request #11654: tests: Initialize recently introduced non-static class member lastCycles to zero in constructor (master...uninitialized-members) https://github.com/bitcoin/bitcoin/pull/11654
< bitcoin-git>
bitcoin/master 084f52f Wladimir J. van der Laan: Merge #11654: tests: Initialize recently introduced non-static class member lastCycles to zero in constructor...
< bitcoin-git>
bitcoin/master 069215e practicalswift: Initialize recently introduced non-static class member lastCycles to zero in constructor...
< gmaxwell>
But there is just an utterly stupendous amount of work required, ... the software is highly optimized (and sure, there are also still many things that could be done to make it faster). .. but e.g. compared to ethereum the amount of blockchain bitcoin core processes per second is something like two orders of magnitude greater. ( https://anduck.net/bitcoincore_vs_geth_full_node_stats.png )
< wumpus>
LMDB seemed promising but I never got spectacular results, maybe I was just using it wrong, and maybe the approach of not caching at the bitcoin level would work better with it
< eck>
alright, at a high level i want to know why bitcoin has a caching layer at all: there is already some caching in the kernel page cache, leveldb has some caching og it its own, and then bitcoin itself will cache data for up to 24h
< bitcoin-git>
[bitcoin] laanwj closed pull request #11651: refactor: Make all #includes relative to project root (laanwj, MeshCollider, ryanofsky) (master...201711_absolute_includes) https://github.com/bitcoin/bitcoin/pull/11651
< bitcoin-git>
bitcoin/master 5b56ec9 Wladimir J. van der Laan: qt: refactor: Use absolute include paths in .ui files
< bitcoin-git>
bitcoin/master 0c71521 Wladimir J. van der Laan: build: Remove -I for everything but project root...
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #11690: [trivial] Fix the StartupWMClass for bitoin-qt, so gnome-shell can recognize it (master...desktop-file) https://github.com/bitcoin/bitcoin/pull/11690
< bitcoin-git>
bitcoin/master f0c1f8a MarcoFalke: Merge #11690: [trivial] Fix the StartupWMClass for bitoin-qt, so gnome-shell can recognize it...
< bitcoin-git>
bitcoin/master b077fe9 Evan Klitzke: fix the StartupWMClass for bitoin-qt, so gnome-shell can recognize it
< gustav>
oopsie, using bitcoin-core latest version on linux (rpc, with php)
< gustav>
i have one app where users are given 1 bitcoin address A, they deposit btc on A and later on they withdraw on their address B. I'd like to use segwit addresses to cut down expenses on network fees (if im getting this right). now i use getnewaddress, sendmany and rawtransactions functions. would it be possible to use $addr = getnewaddress(); $segwit
< bitcoin-git>
bitcoin/master aca77a4 Wladimir J. van der Laan: Merge #11655: net: Assert state.m_chain_sync.m_work_header in ConsiderEviction...
< bitcoin-git>
bitcoin/master 63c2d83 practicalswift: Explicitly state assumption that state.m_chain_sync.m_work_header != nullptr in ConsiderEviction...
< kgc>
well, it's slightly weird because if I create corresponding deposit address and import it inside bitcoin core wallet, I can send to and spend funds without anyproblems
< bitcoin-git>
[bitcoin] eklitzke opened pull request #11690: [trivial] Fix the StartupWMClass for bitoin-qt, so gnome-shell can recognize it (master...desktop-file) https://github.com/bitcoin/bitcoin/pull/11690
< eck>
if any of you use fedora, I just set up a bitcoin rpm repo based mostly on the existing spec file in the contrib/ directory, feel free to help me test it or give me feedback: https://copr.fedorainfracloud.org/coprs/eklitzke/bitcoin/
< Tatty>
no, they are conecting to the seconf one, managed by bitcoin-qt
< Tatty>
I run 2 different ptor proxies as allowed by Bitcoin Core 0.15.0.1
< Tatty>
I think I found an outdated version User Agent on Bitcoin Core 64 bit for Windows v0.15.0.1. I enabled 2 tor proxies, both making bidirectional connections. It happened one of the proxies contacted the other, and that's when I saw a wrong version: User Agent /Satoshi:0.14.0/
< gmaxwell>
There is some layout tension on that; abstracting consensus rules can make them more opaque and harder to review; and bitcoin core is not an altcoin construction set. :) OTOH, sometimes moving things around makes things more clear, enables better testing harnesses, etc.
< karelb>
hm, doing refactoring like that seems like an easy way to get some cheap commits in bitcoin core code :D
< karelb>
Question about bitcoin-core - why is validation.h/.cpp so "overloaded"? It seems to me half of the things in there don't have to do much with validation
< bitcoin-git>
[bitcoin] practicalswift opened pull request #11689: Fix missing locking in CTxMemPool::check(const CCoinsViewCache *pcoins) (master...CTxMemPool-check) https://github.com/bitcoin/bitcoin/pull/11689
< Nobody_>
Everything ECDSA Public Key (Bitcoin Compatible): 1N2EWy7LroJVFYXtmYZryh7W9eV3k6qajd exists since Mon Oct 02 2017 23:48:19 GMT-0700 (Pacific Daylight Time)
< LumberCartel>
Nobody_: You should raise your concerns in the #bitcoin channel rather than in this channel.
< Nobody_>
also a Faucet in the core is needed for Nobody to send Bitcoin to the requested wallet of your choice, for reasons if it is not avaliable from anyone else the system will continue to function appropriately.
< Nobody_>
If anybody could get a message to the Bitcoin Core Developers to add the Mining back into the Core that would be perfect, ASIC is not needed to mine and is outdated plus not as power efficient
< Nobody_>
i just wanted to state that i am requesting as a System that nobody owns and if you abuse the system you abuse yourself some upgrades that need to happen for the Bitcoin Core
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #11686: Make ISSUE_TEMPLATE a bit shorter, mention hardware tests (master...2017-11-shorter-default-issue) https://github.com/bitcoin/bitcoin/pull/11686
< eck>
just thinking out loud here, but you could train a simple convolutional filter (for example) to learn the best parameters to estimate a fee rate given the fee histogram from the last N time periods; but you'd have to update the convolution parameters for each bitcoin release, and it would be trivial to find pathological values after the fact to trick the trained algorithm
< bitcoin-git>
bitcoin/master cbb54e7 Wladimir J. van der Laan: Merge #11533: Docs: Update WSL installation notes for Fall Creators update...
< bitcoin-git>
bitcoin/master 73a7e6d Thoragh: Update WSL installation for Fall Creators update
< bitcoin-git>
[bitcoin] Thoragh reopened pull request #11533: Docs: Update WSL installation notes for Fall Creators update (master...Update-WSL-installation-for-Fall-Creators-update) https://github.com/bitcoin/bitcoin/pull/11533
< bitcoin-git>
[bitcoin] Thoragh closed pull request #11533: Docs: Update WSL installation notes for Fall Creators update (master...Update-WSL-installation-for-Fall-Creators-update) https://github.com/bitcoin/bitcoin/pull/11533
< sipa>
tloriato: let's move to #bitcoin-wizards
< bitcoin-git>
[bitcoin] achow101 opened pull request #11678: [wip][wallet] Don't shut down after encrypting the wallet (master...encrypt-no-restart) https://github.com/bitcoin/bitcoin/pull/11678
< achow101>
could someone help me debug some locks on https://github.com/achow101/bitcoin/tree/encrypt-no-restart? That branch is for encrypting wallets without restarting, and something in the GUI part is holding cs_KeyStore causing the GUI to freeze
< Victorsueca>
trying to build bitcoin core on WSL, when building the depends it tells me automake is not installed, however it is and both the automake and autoconf commands work when writing them on the terminal
< bitcoin-git>
[bitcoin] laanwj closed pull request #11438: Updated Windows build doc for WSL/Xenial workaround (master...wslbuilddoc) https://github.com/bitcoin/bitcoin/pull/11438
< bitcoin-git>
bitcoin/master 7fbf3c6 Wladimir J. van der Laan: Merge #11438: Updated Windows build doc for WSL/Xenial workaround...
< bitcoin-git>
bitcoin/master 7383d77 Aaron Clauson: Updated instructions for Windows 10 Fall Creators Update.
< bitcoin-git>
bitcoin/master e0fc4a7 Aaron Clauson: Updated Windows build doc for WSL/Xenial workarounds.
< fanquake>
roconnor The signatures used to create the final release are available from https://github.com/bitcoin-core/gitian.sigs . There is no way to get the various build.logs from each of the individual builders.
< ZSky>
How popular is the idea of moving from hashcash to another one (not requiring ASICs) in Bitcoin core (not a fork but the real one)?
2017-11-12
< oerauakk>
I'll switch to #bitcoin
< luke-jr>
oerauakk: I answered that already in #Bitcoin fyi
< sturles>
Can I make bitcoin use segwit addresses for change now, on master, or is that still a subject for discussion on how to do it properly?
< sipa>
also, this discussion probably belongs on #bitcoin
< oerauakk>
"But in reality that's bullshit, full nodes are useless in the Bitcoin beyond providing connection points, what matter is the ring of inter connected mining nodes that guarantee your new transactions to reach 99% of hash power within 3 seconds."
< eck>
I was told that there's a proposal from someone (I forget who!) to do multi-process bitcoin core, where some of the processes could be sandboxed (similar to firefox/chrome); does anyone know where I could learn more about this?
< blockchain>
So actually I have saved one wallet.dat with all my bitcoins stored some years ago. Then when I want to use some bitcoin I just load one privat key into my new wallet.dat. I am somehow concerned loading my whole wallet with all my bitcoins stored evertime I want to move some bitcoins
< sipa>
it's not what bitcoin core was designed for
< sipa>
blockchain: bitcoin core now supports multiple wallets
< bitcoin-git>
[bitcoin] mikedennis closed pull request #11670: [Docs] Update with instructions for WSL for Win 10 fall 2017 creator update (master...master) https://github.com/bitcoin/bitcoin/pull/11670
< luke-jr>
might be best to take this to #bitcoin ..
< BGL>
why can't bitcoin core start where it left off on re-indexing blocks, i seriously just had to restart twice in the last day and i'm back to zero again
< LumberCartel>
tyrick: This is where core developers are collaborating. I suggest not trying to "bug" anyone here. You might try asking about your issue in the #bitcoin channel first.
2017-11-11
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #10749: Use compile-time constants instead of unnamed enumerations (remove "enum hack") (master...enum-hack) https://github.com/bitcoin/bitcoin/pull/10749
< bitcoin-git>
bitcoin/master 2adbddb MarcoFalke: Merge #10749: Use compile-time constants instead of unnamed enumerations (remove "enum hack")...
< bitcoin-git>
bitcoin/master 1e65f0f practicalswift: Use compile-time constants instead of unnamed enumerations (remove "enum hack")
< bitcoin-git>
[bitcoin] benma closed pull request #9897: AppInitMain: split initialization of Connman into a new function (master...connman) https://github.com/bitcoin/bitcoin/pull/9897
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #11055: [wallet] [rpc] getreceivedbyaddress should return error if called with address not owned by the wallet (master...getreceivedbyaddress_error) https://github.com/bitcoin/bitcoin/pull/11055
< bitcoin-git>
bitcoin/master 95e14dc MarcoFalke: Merge #11055: [wallet] [rpc] getreceivedbyaddress should return error if called with address not owned by the wallet...
< bitcoin-git>
bitcoin/master 5e0ba8f John Newbery: [wallet] getreceivedbyaddress should return error if address is not mine
< bitcoin-git>
bitcoin/master ea0cd24 John Newbery: [tests] Tidy up receivedby.py...
< bitcoin-git>
[bitcoin] luke-jr opened pull request #11658: During IBD, when doing pruning, prune 10% extra to avoid pruning again soon after (master...ibd_prune_extra) https://github.com/bitcoin/bitcoin/pull/11658
< bitcoin-git>
[bitcoin] practicalswift opened pull request #11655: Explicitly state assumption that state.m_chain_sync.m_work_header != nullptr in ConsiderEviction(…) (master...m_chain_sync.m_work_header) https://github.com/bitcoin/bitcoin/pull/11655
< bitcoin-git>
[bitcoin] practicalswift opened pull request #11654: Initialize recently introduced non-static class member lastCycles to zero in constructor (master...uninitialized-members) https://github.com/bitcoin/bitcoin/pull/11654
< bitcoin-git>
[bitcoin] practicalswift opened pull request #11652: Add missing locks to init.cpp (in AppInitMain + ThreadImport) and validation.cpp (master...init-and-validation-locks) https://github.com/bitcoin/bitcoin/pull/11652
< bitcoin-git>
bitcoin/master fe503e1 Wladimir J. van der Laan: Merge #11646: Require a steady clock for bench with at least micro precision...
< bitcoin-git>
[bitcoin] laanwj closed pull request #11646: Require a steady clock for bench with at least micro precision (master...2017-11-11562-cleanups) https://github.com/bitcoin/bitcoin/pull/11646
< bitcoin-git>
bitcoin/master 620bae3 Matt Corallo: Require a steady clock for bench with at least micro precision
< LumberCartel>
exit70: There's a bot here named bitcoin-git that announces pull requests and the status updates. So lurking here can be educational too. (Welcome, by the way.)
< LumberCartel>
exit70: This is probably where you want to start looking into the source code for Bitcoin: https://www.github.com/bitcoin/
< bitcoin-git>
[bitcoin] fanquake closed pull request #11053: refactor: Make all #includes relative to project root (master...2017_08_includes_absolute) https://github.com/bitcoin/bitcoin/pull/11053
< bitcoin-git>
[bitcoin] MeshCollider opened pull request #11651: refactor: Make all #includes relative to project root (rebased) (master...201711_absolute_includes) https://github.com/bitcoin/bitcoin/pull/11651
< bitcoin-git>
bitcoin/master 3155fd2 Jonas Schnelli: CKeystore: move relevant implementation out of the header
< BlueMatt>
jonasschnelli: heh, I'm not too worried, if they google any of us they'll find bitcoin faster than if they look at what companies we are connected to :p
< jonasschnelli>
BlueMatt: The ownership can have some sideeffects... I personally don't want to be in a register with my Name tied to a company that have "Bitcoin" in it's name. For travel purposes...
< achow101>
BlueMatt: people who want to look at the paperwork and then go "X controls bitcoin blarg" conspiracy
< gmaxwell>
"Orginization which does not control Bitcoin. LLC"
< jonasschnelli>
DCI would be fine for me as well, though I prefer "Bitcoin Core Code Signing Assocation" over "DCI" (which is a private owned company) in the signing details
< gmaxwell>
I would rather not use DCI simply because we really have suffered from people using that stupid message as proof BCF controls bitcoin. I'd rather the name be more benign. (the "foo code signing" sort).
< wumpus>
but it's outside the scope of the bitcoin core project
< morcos>
Guys, if you are signing code, you are responsible for that code. If we are signing it in the name of Bitcoin Core we are all taking responsibility. Please let's limit this discussion to the code we all work on together