[bitcoin] fanquake merged pull request #28542: wallet: Check for uninitialized last processed and conflicting heights in MarkConflicted (master...migrate-with-conflicted-txs) https://github.com/bitcoin/bitcoin/pull/28542
bitcoin/master 50f250a fanquake: Merge bitcoin/bitcoin#28542: wallet: Check for uninitialized last processe...
bitcoin/master 782701c Andrew Chow: test: Test loading wallets with conflicts without a chain
bitcoin/master 4660fc8 Andrew Chow: wallet: Check last block and conflict height are valid in MarkConflicted
achow101: sounds good, but I do think its important to limit voting to people who are actively contributing/reviewing in the project. this isnt a vote of "what would you like to see in bitcoin core" and more signaling "i will prioritise working on and reviewing x"
Testing PR #27596 (AssumeUTXO) and the pruning (prune=3000) doesn't work, still getting a 'blocks' folder size of 37 GB even after the progress has reached 1 (progress=1.000000), am I missing something perhaps in the bitcoin.conf file?
Sadly because this room is registered-only this requires actually signing in with @libera_irc_NickServ:bitcoin.ninja and then storing a password through a bridge I operate. I do promise I'm too lazy to look up your password, but no promises, of course.
I added this channel to my matrix bridge for those who want to access via matrix after the all-of-libera bridge was shutdown - #libera_bitcoin-core-dev:bitcoin.ninja.
I created pull https://github.com/bitcoin/bitcoin/pull/28447, becuase I thought it was what was causing the linter errors. It was not. I closed it. None the less it might be good to consider to remove linter warnings for those 2 words.
some probably read the previous conversation here, pinheadmz made a new github bot that currently lives in #bitcoin-core-github and now emulates the behavior of the matrix bridge/gh-bot. If people like it could be pointed on this channel as well. But I guess it’s also fine to have a separate channel, at least that also works for me. Just wanted to put it out there as an option.
What are you interested in working on in Bitcoin?
Bz0: try bitcoin.stackexchange.com
const bitcoin = new BitcoinCore(config);"
host: '127.0.0.1', // Your Bitcoin Core node's IP address
Can anyone help me out connecting my NodeJS script to my bitcoin core node? No matter what i try it constantly tells me "ThreadRPCServer incorrect password attempt". ive tried with rpcuser+rpcpassword first, then tried the rpcauth method and finally tried the __cookie__ method, nothing works... Using windows 10. i have this at the top of my JS file
This channel is particularly for development of bitcoin core, an alternative implementation of the protocol is out of scope. I would recommend you post your question on bitcoin stack exchange. And fwiw, you should also check if you can achieve your goal by just using bitcoin core's zmq interface, then you won't need to think about version messages etc.
i am trying to make a program that connects to the bitcoin network to collect new transactions in the mempool and new blocks in real time, but I am having trouble getting it going. My version message doesn't get a response... I suspect it's something to do with the formatting or something, but i have tried a few things and nothing has worked so far, if anybody could help me get this running it would be quite appreciated
and yes, we could prune some more unspendable outputs, but that's an implementation detail inside bitcoin core, which imho shouldn't really interact with questions about relay policy
provoostenator: "why would they not mine them" -- because they have a long term investment in bitcoin, and they believe mining those txs is bad for that investment, same as the reason why people would want to remove the spam in the first place
provoostenator: it's malicious to setup private relay networks to mine attacks on Bitcoin that the community is actively trying to mitigate