Hello Bitcoin gurus. I always come here to find answers to my problems after some unsuccessful search in google.

Now that the mempool is being crushed. I have problem with several transactions.

Case #1:
I needed to send 0.625927 BTC to wallet 3FcJ5qSBExencX5eowGJwrPBnfKX41FrXK (a ledger wallet generated address)
First I sent the BTC from my GreenAddress wallet thinking being a segwit address would be quicker and cheaper, it wasnt faster enough. That txid is 4821084d640e48ee247160620aedbe9b5605621486270bd570032c94368d6966
It was stuck so I believed it will be abadoned in time.

Then I sent the other 0.625927 BTC from Copay, my former trust wallet. I used a higher fee. The txid is f11436dd3a7de43d09e362bf3fbb3ea56b14c14c81007831e96d9588bb9a84c1
This TX was successful and the BTC were transfered on 01/01/18

My surprise is that when the mempool gets down the first tx is executed too. I asked the owner of the wallet 3FcJ5qSBExencX5eowGJwrPBnfKX41FrXK if he received another payment and he told me checked on his ledger wallet GUI and he received it but it was tagged as double spending and then the print screen he sent me only show one TX.

I checked a block explorer and you can see the two txs. What is happening how can he confirm the other tx ? he is currently choosing in the ledger the Segwit chain.

Case #2:
Im trying to send some BTC from BitcoinCore segwit address to another segwit address in GreenAddress.
I tried several times and because of mempool full I had to abandon transaction.
Turns out abandon a tx is not cancel it, from all of the abandoned the one with higher fee is the one that got confirmed. NOT the first one in being into a block. Can someone explain me that?
Could I receive BTC from a wallet and check +6 confirmations and then lose those BTC because the same BTC were sent to another wallet with a high fee but "abandoned"
The issue is that I checked the receiver wallet and the TX in a block explorer and I can see they are there but in GreenAddress the TX is tagged as double spend and not added to my total wallet funds. What can I do ?


I'll go to translate bitcoin core 0.16.x while I get some replies, thanks in advance...

Hello guys, I have an Antminer S5 that is not mining even when the local work is increasing and the chip are all "ooooo" , the pools are alive but wont detect the miner (worker cuz im with kano.is)

Everything seems to be ok,

Here you can see the kernel log ,
https://pastebin.com/XLpfQfRm

 it has a few error but I can see they are "normal" . This is a suposely Antminer S5 mining and the kernel log has the same errors https://support.myrig.com/hc/en-us/articles/205463055-Good-Kernel-Log-Example

Maybe has something to do with the FPGA error? I dont know what does that means exactly.

and the image from the Miner Status

https://imgur.com/a/0Tw22

Feel free to ask me any question about it,

as always thank you community I can always count with you all.

Hi there, I did my first SegWit transaction and due to a mistake and a not so clear GUI in Bitcoin Core I have a transaction stucked for a month.

I wonder if someone can explain how can this happen. In the past I've had low fees transaction stucked for about 3 days to one week, nothing uncommon I dont complain but this is outrageous.

https://blockchain.info/tx/2d73dfb6b98f4dcd066134081a670cda09304b268f0a5d7ca451ed8ed6e7d940


Peace

In times like these of network congestion and theres still blocks mined with no transaction i.e. 498218

How could this be possible?

Thanks

[I tried to install a Bitcore node to create my own wallet service but that wasnt possible. If anyone had done this please write me to help me.]

Hi all, here I am again with my problems about nodes 

This time is about another node I am setting on a pine64.

I tried to install a Bitcore node to create my own wallet service but that wasnt possible. If anyone had done this please write me to help me.

..following with the pine64 setting: I installed Bitcoin Core 0.15.0.1 and after executing bitcoind -daemon I can send RPC calls and the node answer every command.

Then I edited crontab so if the node gets rebooted bitcoind should start again.

This is when my problem occur, if I reboot the node bitcoind is executed but when I send RPC call I got this message:

Code:

pine@pine64:~$ bitcoin-cli getconnectioncount
error: couldn't connect to server: unknown (code -1)
(make sure server is running and you are connecting to the correct RPC port)

Here is my crontab config

Code:

pine@pine64:~$ crontab -e

# m h  dom mon dow   command

@reboot /usr/local/bin/bitcoind &

My bitcoin.conf file

Code:

pine@pine64:~$ cat .bitcoin/bitcoin.conf
##
## bitcoin.conf configuration file. Lines beginning with # are comments.
##

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=0

# Run a regression test network
#regtest=0

# Connect via a SOCKS5 proxy
#proxy=127.0.0.1:9050

# Bind to given address and always listen on it. Use [host]:port notation for IPv6
#bind=<addr>

# Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
#whitebind=<addr>

##############################################################
##            Quick Primer on addnode vs connect            ##
##  Let's say for instance you use addnode=4.2.2.4          ##
##  addnode will connect you to and tell you about the      ##
##    nodes connected to 4.2.2.4.  In addition it will tell ##
##    the other nodes connected to it that you exist so     ##
##    they can connect to you.                              ##
##  connect will not do the above when you 'connect' to it. ##
##    It will *only* connect you to 4.2.2.4 and no one else.##
##                                                          ##
##  So if you're behind a firewall, or have other problems  ##
##  finding nodes, add some using 'addnode'.                ##
##                                                          ##
##  If you want to stay private, use 'connect' to only      ##
##  connect to "trusted" nodes.                             ##
##                                                          ##
##  If you run multiple nodes on a LAN, there's no need for ##
##  all of them to open lots of connections.  Instead       ##
##  'connect' them all to one node that is port forwarded   ##
##  and has lots of connections.                            ##
##       Thanks goes to [Noodle] on Freenode.               ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# Alternatively use as many connect= settings as you like to connect ONLY to specific peers
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Listening mode, enabled by default except when 'connect' is being used
#listen=1

# Maximum number of inbound+outbound connections.
#maxconnections=

#
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
#

# server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands
#server=0

# Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6.
# This option can be specified multiple times (default: bind to all interfaces)
#rpcbind=<addr>

# If no rpcpassword is set, rpc cookie auth is sought. The default `-rpccookiefile` name
# is .cookie and found in the `-datadir` being used for bitcoind. This option is typically used
# when the server and client are run as the same user.
#
# If not, you must set rpcuser and rpcpassword to secure the JSON-RPC api. The first
# method(DEPRECATED) is to set this pair for the server and client:
#rpcuser=Ulysseys
#rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED_385593
#
# The second method `rpcauth` can be added to server startup argument. It is set at initialization time
# using the output from the script in share/rpcuser/rpcuser.py after providing a username:
#
# ./share/rpcuser/rpcuser.py alice
# String to be appended to bitcoin.conf:
# rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae
# Your password:
# DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
#
# On client-side, you add the normal user/password pair to send commands:
#rpcuser=alice
#rpcpassword=DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
#
# You can even add multiple entries of these to the server conf file, and client can use any of them:
# rpcauth=bob:b2dd077cb54591a2f3139e69a897ac$4e71f08d48b4347cf8eff3815c0e25ae2e9a4340474079f55705f40574f4ec99

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpcclienttimeout=30

# By default, only RPC connections from localhost are allowed.
# Specify as many rpcallowip= settings as you like to allow connections from other hosts,
# either as a single IPv4/IPv6 or with a subnet specification.

# NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED,
# because the rpcpassword is transmitted over the network unencrypted.

# server=1 tells Bitcoin-Qt to accept JSON-RPC commands.
# it is also read by bitcoind to determine if RPC should be enabled
#rpcallowip=10.1.1.34/255.255.255.0
#rpcallowip=1.2.3.4/24
#rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96

# Listen for RPC connections on this TCP port:
#rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
#rpcconnect=127.0.0.1

# Create transactions that have enough fees so they are likely to begin confirmation within n blocks (default: 6).
# This setting is over-ridden by the -paytxfee option.
#txconfirmtarget=n

# Miscellaneous options

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100

# Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
#paytxfee=0.00

# Enable pruning to reduce storage requirements by deleting old blocks.
# This mode is incompatible with -txindex and -rescan.
# 0 = default (no pruning).
# 1 = allows manual pruning via RPC.
# >=550 = target to stay under in MiB.
prune=1000

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

ps results when bitcoin -daemon is executed from cli

Code:

pine@pine64:~$ ps aux | grep bitcoind
pine      2214  9.9 22.6 1862152 461952 ?      Ssl  Oct31  95:02 bitcoind -daemon
pine     26429  0.0  0.0 121620   908 pts/0    S+   11:53   0:00 grep --color=auto bitcoind

ps results when bitcoin is executed after reboot in crontab

Code:

pine@pine64:~$ ps aux | grep bitcoind
pine       636 65.8 11.3 841216 230304 ?       DLl  11:56   0:11 /usr/local/bin/bitcoind
pine      1073  0.0  0.0 121620   904 pts/0    S+   11:57   0:00 grep --color=auto bitcoind
What am I missing in crontab?

I hope someone can tell me what is happening, I wont like to define a RPC user and password. For me it is ok to leave that blank and generate a new cookie everytime I start bitcoind.

Thanks guys

Hi all, I had bit expectation about Copay and its planned SegWit support.
Turns out they have BCH as a priority over SegWit support.

https://github.com/bitpay/copay/issues/4020#issuecomment-335866158

We support Bitcoin, and most of the work we do (by FAR) is related to Bitcoin.

We are now in the process of developing a new UI (Copay V4) and that is our main priority. We think segwit support is not as critical as to interrupt our current developments. On the other hand, hundreds of thousands of users had BCH in Copay and enabling them to access to them, easily, (given the financial implications) was critical.

We are now testing a new version of Insight-api that will have better support for segwit and we expect to release it soon (it is a complete rewrite of insight-api), so some progress is been made in that front.

I understand your frustration, but we have tons of things to work and we try to prioritize them the way we think are more relevant to our users.

  maybe it is time to move on to another wallet. Samourai maybe?

Time will tell

I wonder if someone here has started using the Samourai Wallet.

You can download it here
https://samouraiwallet.com/

Right about now it is only available for Android devices. They say soon it will be out a version for iOS.

It is a wallet with segwit enabled transaction, I wonder if the fees are really reduced as people say.

Some reall nice features:

RBF (Replace By Fee)
Allows senders to rebroadcast a stuck transaction to the network

CPFP (Child Pays for Parent)
Allows users with stuck transactions to top up fee for quick confirmation.

Trusted Node - PushTX
Users can add their own trusted node details. Samourai will use this node to push all transactions.

 Sound like this is how a wallet should be.


peace

So... anyone has noticed that graphs for Kraken in the pair BTC/EUR has gone bananas?
bitcoinwisdom.com/markets/kraken/btceur

Take a look by yourselves, I wonder how longer will they take to figure out what is going on.

It is the first time I see something like that lets hope it doesnt turn into something usual.

I have found a series of question on reddit about the Lightning Network and I found out they were the same doubts I have about it.

The source link to the question is here:
https://www.reddit.com/r/lightningnetwork/comments/6uo5ck/lightning_network_noob_questions/

I wonder if someone has an answer to all (or some) of them:

I want to start a LN node, what are the requirements?
- Will my coins be tied up while a channel is open?
- How many coins will I need to have? the more the better?
- How will users find my node?
- How will they decide to use my node or not?
- If I'm the only node in my area, are my chances of being used higher?
- How will fees actually be calculated?
- If nodes set their own fees, will it be a race to the bottom (fee-wise) for competing nodes?

Thanks in advance guys.

As many of you might now, yesterday the Lightning Labs blog published this new entry:

http://blog.lightning.engineering/announcement/2017/10/12/test-blitz.html

it is about The Lightning Network Desktop app being published to start testing. I have download it but it seems I lack the knowledge to start using it.

Can somebody give me a hand?

I have read in Bitcoin.org site that some wallet and developers supports 2X. Ok, that is fine if they want to but what calls my attention is that Bitpay supports 2X and Bitpay is related to the wallet Copay.

So my question is: Would my BTC stored in Copay be compromised after the hardfork?

I know Copay points to a Bitpaywallet but what if they go rogue and change all the BTC to BTG or whatever after the hardfork?

Does anyone how could I get my own bitcoin node wallet service URL to change it in the app?

Hello, I don't think a lot of people, other than the real developers and hardcore fans :p , are subscribed to the bitcoin-dev mailing list.
About a week ago I read something interesting. It is about Address expiration time added to BIP-173.

Sometimes we have problems when an old address is used by someone who pays us frequently and we could just not want to use that address anymore. If a expiration time is set (and checked by Bob before sending BTC to Alice) we could avoid this uncomfortable situations and, of course, the losing of bitcoins in such transactions.

If you want to read about BIP-173 this is the link to it:
https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki

What do you think about Address expiration settings?

Hi community, I have a pruned Raspnode on 0.15.0.1 and I have been monitoring it using bitnode21.co

Thing is that today I got a email about my node being STALLED the message from bitnodes21.co is the following:

Bitcoin node at [XXXXXXXXXXXXXXX]:8333 has stalled and does not appear to be downloading newer blocks from its peers.
If you are running this node, try restarting the Bitcoin client. If the issue persists, please report it to the software maintainer of the Bitcoin client.

I ssh to the Raspnode and I can see on the debug the following:

Code:

2017-10-01 19:58:04 connect() to 70.67.108.238:8333 failed after select(): Connection refused (111)
2017-10-01 19:59:49 connect() to 58.8.174.136:8333 failed after select(): Connection refused (111)

Still when I do a

Code:

getblockchaininfo

the headers and blocks keep updated to the last one. So it seems it was downloading newer blocks.

I would like to know what can I do to evade this stall status so my raspnode can run smoothly.

Thanks for your comments

I would like to ask your opinion about TOR enabled nodes.
Do you think it is worthy to enabled TOR in every one of our nodes?

I can see in bitnodes21.co the amount of TOR nodes in the network and it is not even then half. I'm considering my self to enable TOR network in mine.
Also, because I think it is better to enabled it to accept incoming connections rather than open the 8333 port on my router.

What are my odds of my privacy and security being compromised if I enable TOR network? I have read is not 100% fail safe.

If my ISP start sharing public my public IP with another clients I wont be able to open the 8333 port.

If anyone can send me links or publish here the pros and cons of enabling TOR network in my nodes you are welcome.

Thanks,

Hi, I've been setting up a store in Openbazaar and I have a server running version 1.0 while 2.0 come out of beta.
I can see in the log the following message:
 [CRITICAL] Libbitcoin server offline

Can someone explain what is the relation between Libbitcoin server and Openbazaar ?

Does openbazaar only work with its own libbitcoin server?

I have seen its most of the time down. This is a downside to this wonderfull and with great potential project.
one should be able to set its own libbitcoin server and point it to Openbazaar.

This smells like centralization.

Hope someone could clarify my doubts. thanks

I had to create a new post because moderator erase my replies in post older than 120 days.

With this sad introduction I am here to ask the following:


I would like to start running a pruned node with 1000 MB of pruning and set in a Raspberry Pi 2 B. I wonder if someone has set it with this level of pruning at the present size of the blockchain.

I'm updating the node pruned in my laptop and I'm planning to move everything to an microsd of 16 GB and class 10.
Do you think the raspberry pi will handle the load?

Hi fellas, I wonder if someone has set and keep an openbazaar service into a rPi II.

I found this URL https://github.com/OpenBazaar/OpenBazaar-Server/wiki/Raspberry-Pi-Install-Raspbian
with a step by step procedure that I will do later this week but I want to know if its worth the hassle.

Please share if you have some story about this services (happy or not so happy), it is already in use? It is worth using a rPi to maintain the shop online?



I would like to start a little shop online to earn some BTC so I'm all eyes  .

[Address does not refer to a key (code -3)]

Hello, I want to export my private keys for a SegWit wallet I created in Bitcoin Core 0.14

Currently I'm using Bitcoin Core 0.15
I did the usual procedure:
- walletpassphrase "passphrase" 600
- dumpprivkey "MySegWit-address-starting-in-3"

Then I got this error message:
Address does not refer to a key (code -3)


I check out the error code and is the following:
RPC_TYPE_ERROR                  = -3,  //! Unexpected type was passed as parameter

Is this a bug? Can some one confirm if its possible to export the private keys for a SegWit address in Bitcoin Core?

Hi experts, I wonder if you could recommend me the best PSU you would install for a Bitmain's S9.
Of course my installation is a 220v one

I have seen some Asian proposals in EBay, some unbranded "platinum" 1600W PSU.

I think 1600W is enough for the S9 but what about brands?

I'm all eyes to your comments and thanks in advance

Hi, good news, Bitcoin Core 0.15 is now released for Ubuntu.

It has not been published for other OS neither in the official download page.

I notice there's a new initial step:

I quote from [mod edit: link removed]

"The first time you run version 0.15.0, your chainstate database will be converted to a new format, which will take anywhere from a few minutes to half an hour, depending on the speed of your machine."

have fun and UPDATE!