Bitcoin Forum
November 17, 2018, 07:56:50 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 [12] 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 ... 547 »
221  Bitcoin / Electrum / Re: bitcoin is hackable on electrum-2.9.3-portable news may 2018 on: May 21, 2018, 03:41:01 PM
Electrum versions between 2.6 and 3.0.4 are known to be vulnerable and you should upgrade immediately.

Unfortunately there is nothing that can be done to recover your Bitcoin.
222  Bitcoin / Development & Technical Discussion / Re: Atomic Swap - is it a best way to exchange cryptocurrencies? on: May 21, 2018, 03:38:24 PM
Not all coins can have HTLCs (they don't all have OP_CLTV) so this method does not work for some coins.
223  Bitcoin / Development & Technical Discussion / Re: Question about LN routing at 1 Million TPS on: May 21, 2018, 02:49:14 AM
Well if we had an open channel and I transfer all my available funds in the channel to you, I wouldn't be able to transfer more funds to you so that path would be blocked, wouldn't it?

Consequently, when a sender would use our channel as part of his route, it could have been blocked before the sender knows about it.

Is there a solution to that or do I have an error on my part here?
This is certainly possible, but I doubt it would be likely or really that big of an issue.

In the event that this happens, the node which has the problem will send an error back to the origin node and then the HTLCs will fail and be removed from the commitment transactions. Then the node will choose a different route and try the payment again. It's trivial to solve and not really a problem, especially with a large, well connected network.
224  Bitcoin / Development & Technical Discussion / Re: Question about LN routing at 1 Million TPS on: May 20, 2018, 08:39:51 PM
Why would it? Having 1 million tps does not necessarily effect the open channels. Furthermore, calculating a path does not take all that long.
225  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: May 17, 2018, 11:23:46 PM
This is a great news, but am a kind of person that ask a lot of questions. I want to know the principle of working of Bitcoin Core version 0.16.0. Does it entails POW
Of course, Bitcoin uses PoW. Bitcoin Core is the reference implementation for Bitcoin, it is not an altcoin.
226  Bitcoin / Development & Technical Discussion / Re: A thought experiment: PROVE you own a bitcoin on: May 16, 2018, 03:33:51 AM
C does not require trust, does it?

A person verifies a public address, then he sees that one bitcoin has moved to a new address, that was previously specified by you.

There is no way he could know whether you were the sole owner of the old address.

Now, how could a proof be devised that you owned the new address?
Just send back to the same address. No need for a new address and it proves that you have the private key for that address and can move coins associated with it.
227  Bitcoin / Development & Technical Discussion / Re: A thought experiment: PROVE you own a bitcoin on: May 16, 2018, 12:21:37 AM
If you want proof of "I can spend coins associated with this address", you can sign a message with the address (or specifically with the private key whose public key hashes to the hash encoded by an address).
228  Bitcoin / Development & Technical Discussion / Re: 64: too-long-mempool-chain on: May 15, 2018, 05:09:18 AM
No need to do that. This has nothing to do with the databases.
Does this  means that there is no need for adding reindex options ?
  2. Restart bitcoind (← without adding -reindex options)
Correct. Just restart without -reindex
229  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: May 15, 2018, 04:21:12 AM
Is this version available for mobile?
No, Bitcoin Core is not a mobile application.
230  Bitcoin / Development & Technical Discussion / Re: 64: too-long-mempool-chain on: May 15, 2018, 04:20:08 AM
Can I override the default limit of 25 unconfirmed transactions by adding to cofiguration file as below.

  1.  Additionally write to configuration file.
  bitcoin.conf-----------------------
  limitancestorcount=1000 ← e.g. 1000
  limitdescedantcount=1000 ← e.g. 1000
  ----------------------------------
Sure, you can do that, but that does not mean that your transactions will actually be relayed across the network. Just because you have this in your config does not mean that your peers will so they likely won't accept any transactions once you reach the default limit. Your local config only applies to your node. Changing this just means the transactions will sit in your node's mempool (and not be relayed across the network). They won't even be rebroadcast by your node because nodes don't do that.

Instead of trying to get long unconfirmed transaction chains to be relayed, you should be rethinking why you are generating long unconfirmed transaction chains and thinking of ways that you can avoid making long unconfirmed transaction chains instead.

 2. Restart bitcoind with -reindex options.
No need to do that. This has nothing to do with the databases.
231  Bitcoin / Bitcoin Technical Support / Re: Node Privacy on: May 15, 2018, 04:17:19 AM
Privacy in what regard? Do you want people to not know your node's IP address? Or do you want people to not know whether you are behind your transactions? Or something else?
232  Bitcoin / Bitcoin Technical Support / Re: Berkeley db address format on: May 14, 2018, 06:08:04 PM
A follow up question...I understand that if an address has a transaction, then the public key can then be known. Thatís why bitcoin generally uses new addresses every time. How can I find the public key in the event that the address has a transaction?  The address Iím looking for does not, but Iím just asking to learn in this case.
You would have to find the transaction, parse it as a standard Bitcoin transaction, and look at the inputs to see if any of the public keys hash to the hash encoded by your address. Bitcoin Core does not store transactions by association to the address, and addresses nor their data are contained in the inputs of a transaction.

Note that transactions can also be associated by the outputs. In that case, the public key is not known, however the hash provided in the output will be the same hash encoded by the address.
233  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: May 14, 2018, 05:24:52 AM
What happen if send BTC from legacy address to SegWit address?
The typical thing happens, your Bitcoin are transferred from a legacy address to a Segwit address. The address types really don't matter; the network doesn't care and such transactions are possible due to the soft forking nature of Segwit. You can even do it the other way around, segwit address to legacy address. It doesn't matter.
234  Bitcoin / Bitcoin Technical Support / Re: Berkeley db address format on: May 14, 2018, 05:22:15 AM
Bitcoin Core does not store the address itself nor does it store the hash160 which is encoded by the address. Bitcoin Core stores the public key and its private key, but the address encodes the hash of the public key. You cannot compute the public key from the address, all you can really do is find public keys and compute their addresses to see if they match your address.

Luckily Bitcoin Core stores public keys in a fairly obvious form. They are prefixed with the letters "key" or "ckey" depending on whether your wallet is encrypted. Not that you cannot just search for these strings as there are other data in the wallet file that have the string "key" in them. Following the string will be a length prefix specifying 33 or 65 bytes and then the public key itself.
235  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: May 13, 2018, 04:21:24 PM
On one on our computers, on which we use Bitcoin Core, we are behind a NAT. Before 0.16, we had 8 incoming connections at most, but lately, we're seeing 16 incoming connections. Certainly speed things up. Thank you, I guess? Is this a documented new feature?
There was no such change that does that. Seeing your incoming connection count increase is normal behavior.
236  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: May 13, 2018, 02:14:56 AM
i got a question, can i add 2 datapaths to the config so i could store 2 copies of the blockchain in 2 difference locations from 1 node thats running?
No, you cannot do that.
237  Bitcoin / Bitcoin Technical Support / Re: WARNING: request rejected because http work queue depth exceeded on: May 12, 2018, 11:53:01 PM
the node accepts HTTP and RPC requests during regular operation, from other nodes in the network?
No, it does not.

Connections from other nodes use the peer-to-peer network protocol which uses different ports and is not HTTP.
238  Bitcoin / Bitcoin Technical Support / Re: WARNING: request rejected because http work queue depth exceeded on: May 12, 2018, 05:39:27 PM
1. What could be triggering this error?
RPC commands are being issued faster than they can be handled.

2. What can I do to avoid it? Settings recommended here fix it or just delay the problem?
You can set -rpcworkqueue to a number higher than 16.

3. Is there a log or a command that allows me to query and monitor the number and origin of RPC quests over time?
Start bitcoind with -debug=rpc and -debug=http. You will see information about the RPC commands and HTTP server stuff logged to the debug.log file.
239  Bitcoin / Development & Technical Discussion / Re: Unable to make a payment for using Segwit and not using a desktop wallet, wtf? on: May 10, 2018, 06:47:06 AM
This issue is unrelated to hardware wallets or segwit entirely. It is solely related to the software that you are using (and yes, if you are using a hardware wallet, there is still a wallet software that you are using. Hardware wallets cannot operate completely standalone). Furthermore, the payment protocol is completely unrelated to segwit entirely; they only specify non-segwit in the guide because that is what they show for setting up Electrum.

Unfortunately there is no known easy workaround for this problem. Bitpay has removed other methods of getting addresses from their website. The only method that I know of is to extract the address from the payment protocol data itself which requires other specialized software such as http://github.com/achow101/payment-proto-interface.
240  Bitcoin / Bitcoin Technical Support / Re: Unstable Bitcoin Connection on: May 08, 2018, 09:13:00 PM
addnode does not guarantee that a connection to the specified node will be attempted. If you want to guarantee that a connection will be attempted, then you need to use the -connect option.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 [12] 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 ... 547 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!