Re: [bitcoin-dev] Few questions regarding ListTransaction
OK. Thank you guys for clarification. On Wed, Apr 11, 2018 at 1:00 PM, Karl-Johan Alm via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Thanks for clarifying! > > On Wed, Apr 11, 2018 at 6:48 PM, ZmnSCPxj wrote: > > Good morning Karl-Johan Alm, > > > > To clarify: > > > > Nothing prevents a miner from completely ignoring nSequence when putting > transactions in blocks. > > > > Unconfirmed transactions are, by definition, not recorded in blocks. So > if there is a transaction 0xFFF nSequence and fee 1000 satoshi, and > another conflicting transaction 0xFFF nSequence and fee 1 > satoshi, miners can include the latter one even if the first one came to > their knowledge first, regardless nSequence. > > > > Thus, in the end "full replace-by-fee", where nSequence is IGNORED for > purposes of replace-by-fee, is expected to become the norm, and we should > really be designing our wallets and so on so that we only trust > transactions that have confirmations. > > > > The "nSequence=0x means opt-OUT of RBF" convention is only > followed by fullnodes running standard bitcoind. Nothing prevents miners > from running patched bitcoind that ignores this rule, and connecting with > similar peers who also ignore this rule. > > > > Regards, > > ZmnSCPxj > > > > > > Sent with ProtonMail Secure Email. > > > > ‐‐‐ Original Message ‐‐‐ > > > > On April 11, 2018 5:37 PM, Peter Todd via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> wrote: > > > >> On Wed, Apr 11, 2018 at 05:10:43PM +0900, Karl-Johan Alm wrote: > >> > >> > On Wed, Apr 11, 2018 at 4:52 PM, Peter Todd p...@petertodd.org wrote: > >> > > >> > > Or via full replace-by-fee, which appears to be used by a > significant minority > >> > > > >> > > of miners: > >> > > >> > I was of the impression that final transactions (sequence=0x) > >> > > >> > cannot be RBF'd. > >> > >> My full-replace-by-fee tree ignores that. It also does preferential > peering to > >> > >> ensure it's well connected with likewise peers, and thus the whole > network. > >> > >> > >> > > --- > >> > >> https://petertodd.org 'peter'[:-1]@petertodd.org > >> > >> bitcoin-dev mailing list > >> > >> bitcoin-dev@lists.linuxfoundation.org > >> > >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > > > > ___ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[bitcoin-dev] Few questions regarding ListTransaction
Hi, I have few questions regarding ListTransaction RPC call and I hope you can help me. Documentation for the RPC call is here: https://bitcoin.org/en/developer-reference#listtransactions 1. What does it mean for a transaction ( with 0 confirmations ) to be *trusted* or not? There is such field in the response of ListTransaction As far as I know bitcoin - nothing is trusted unless there are some numbers of confirmations. How does this value is set to true or false? 2. When does *confirmations* can be -1 ( conflicted )? What does it mean to have conflicted transaction? Is it about Transaction Malleability? Double Spend? or both? 3. *walletconflicts*. What if I add watch-only address to my bitcoind process. This address will not be a part of my wallet. Now, someone will pay me to this address and someone else will make Transaction Malleability ( for the sake of example, lets assume this second one will be confirmed, not the original one ). Will I get a first transaction in *walletconflicts* array when ListTransaction will return me second transaction in the response? Thank you in advance! ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[bitcoin-dev] Setting up bitcoin dev environment ( bitcoind, bitcoin-cli )
Hi guys, I am trying to set up the bitcoin development environment on my Mac. I installed the Bitcoin Core client ( bitcoin-qt ) and also downloaded the binaries. I face the following issues and hope you can help me to resolve these: 1) Can't open the configuration file from bitcoin-qt. I have a configuration file $HOME/Library/Application Support/Bitcoin/bitcoin.conf but it's empty. When I try to open it via bitcoin-qt ( Preferences -> Show configuration file ) it shows me a popup with an error "Configuration file could not be opened". I tried to change the permissions: "chmod 600"...no luck... 2) I can launch bitcoind in -regtest regime. But when I launch *bitcoin-cli -regtest setgenerate true 101* I get an error: > error code: -32601 > error message: > Method not found 3) If I try *bitcoin-cli getinfo* I get an error: > error: Could not locate RPC credentials. No authentication cookie could be > found, and no rpcpassword is set in the configuration file > (/Users//Library/Application Support/Bitcoin/bitcoin.conf) Hope you can help me! Thanks Best, ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
