Bitcoin Forum
January 17, 2019, 02:00:40 PM *
News: Latest Bitcoin Core release: 0.17.1 [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 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 ... 550 »
521  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.15.1 Released on: February 17, 2018, 08:54:28 PM
- breach the on chain system, the fees and all ways to estimates income from miners.

- I fear that segwit txs will take over the blocks and or that txs can be blocked from segwit. I know those 2 comments are uninformed but I think that the more segwit scale, the more it will have a larger imbedded fee, which will raise the fee for the on chain users. Is it wrong? Then I fear that segwit may be able to ban certain txs. is it true?
These are completely untrue. You are conflating segwit with the lightning network. They are two completely and absolutely different things. Segwit does not do anything to how fees are calculated nor does it have a "larger imbedded fee" nor does it do anything to raise fees for on chain users. Segwit cannot ban anything. It is a technology, not a system. i suggest that you actually read up on how segwit works (as in read the BIPs) and not just people's blog posts.

3. btcash I like the idea of on chain scaling. I think it is the cleanest way forward. However it doesn't change the hardware mining cartel. best fabs, best layout, best everything is very capital intensive. Hardware isn't really open sourceable, yet. Then more practically looking at the wallet options, it is way less clear than with core. At least with core I know one main wallet that works, is continually improved and safe. Here I have no idea which one to download, not even a torrent...
One of the biggest issues with on chain scaling is that it becomes more difficult for people who want to run nodes to actually be able to run nodes. The cost required to run a node (which includes more than just bandwidth and disk space) increases dramatically by increasing block sizes, so much so that the idea of decentralized nodes just completely goes out the window.
522  Bitcoin / Bitcoin Technical Support / Re: Restore Bitcoin-qt from wallet.dat after crash on: February 17, 2018, 05:36:16 PM
So you're saying I will only need to swap out the wallet.dat file and then restart the client without rescan?
Yes, it will actually perform the rescan itself if it needs to. You don't actually need to force a rescan.

I tried to switch out the wallet.dat file before downloading the blockchain, but since this is a fresh installation there was no new wallet.dat.
You can stop it now and swap out the wallet.dat file. It may actually be better to do that to avoid a longer rescan later. The sync will pick up where it left off.

Once the chain is synced, I simply swap the wallet.dat files, restart Bitcoin-qt normally, and my coins should be restored with no need for dumping the key or rescan?
A rescan is still required, but it will be started automatically by the software.

Will it have to rescan the entire chain (a week) all over again or will it take around 30 minutes or so?
Rescanning is not the same as downloading the blockchain or reindexing the blockchain. It will be much, much, much faster. On the order of tens of minutes rather than days.
523  Bitcoin / Development & Technical Discussion / Re: Why was ECDSA encryption chosen? on: February 17, 2018, 05:16:38 PM
First of all, ECDSA is not an encryption algorithm. Nothing is being encrypted with ECDSA. ECDSA is a signature algorithm (it's in the name!).

ECDSA was likely chosen because it is secure with shorter key lengths. An ECDSA private key of 256 bits has the roughly the same security of a RSA key with 3072 bits. This is a massive space saving measure.
524  Other / Meta / Re: Where are the merit sources? on: February 17, 2018, 05:57:02 AM
Honestly, I think that high members ranks are more eligible for the merit source than lower ranks, they have more merit points to award. The right question is:" Why merit sources are mostly given merit points to high ranks members, instead, to give more merit points to low ranks members who deserve that?"
This may happen because those high ranking members have made/make high quality posts so users will merit them. I personally have a policy of not giving out merit to anyone that is Legendary or eligible for Legendary (although that has been violated a few times by accident and during the first few days of the merit system).

The main issue is likely an issue with bubbles. For example, I only really frequent the Dev & Tech and Technical Support boards because those are ones that I moderate and find interesting. Thus the people I will merit are going to be people who post in those boards. This means that there are going to be lots of people who I don't give merit to because I don't every see their posts. So some merit sources may simply not be giving merits to high quality posts because they don't even see them.

Furthermore, there are some threads which may contain high quality posts but the thread itself is garbage and just shitposting threads. I tend to ignore these threads, and even if I were to see a high quality post in such a thread, I won't merit it because it is in what is effectively a shitposting thread (this has happened a few times as there are some shitposting threads in Dev & Tech). Merit sources may behave in a similar way.
525  Bitcoin / Development & Technical Discussion / Re: Not sure if this is specifically an RPC problem or code change... on: February 17, 2018, 04:31:26 AM
I looked at my client again, getinfo still produces data but with the deprecated warning as part of the array now. So why the code I'm using thats not working but was about a yr ago is now not working. I don't know but would like to find out.

The node I run is of no real signifigance, so if I end up having to keep an older client for the use of getinfo is fine with me.
The data type of getinfo is a JSON object, but your script expects a JSON array. It must have changed data types since your script was written.
526  Bitcoin / Bitcoin Technical Support / Re: Restore Bitcoin-qt from wallet.dat after crash on: February 17, 2018, 03:40:11 AM
Can anyone tell me what "txtfile_keysfile_path.txt" means?
The dumpwallet command takes a path to a file. It writes the wallet's key data to that file. So "txtfile_keysfile_path.txt" is a string which is the path to the file where you want the key data to go. So you might do something like
bitcoin-cli dumpwallet C:\Users\user\Documents\wallet_data.txt

Another method I've seen involves a similar swap out of the wallet.dat file but the instructions are to then:

After swapping out wallet.dat
Go to the Windows command prompt and enter

C:\Program Files\Bitcoin>bitcoin-qt.exe -rescan

From what I gathered this would rescan the wallet.dat and my coin would then be restored.
Can anyone elaborate on these methods and tell me if I have the right idea or not? Right now I'm about half done syncing the blockchain.
Really appreciate your help.
The only actual restoring is the second thing with starting Bitcoin Core with -rescan. But you don't actually have to use -rescan if you are syncing from scratch. If you are syncing from scratch, you can just put your wallet.dat file in the data directory and start Bitcoin Core. It will automatically scan the blockchain for your transactions as it syncs.

The first option with dumpwallet is only if you want to import your private keys into another wallet.
527  Bitcoin / Development & Technical Discussion / Re: Not sure if this is specifically an RPC problem or code change... on: February 17, 2018, 03:35:38 AM
The getinfo RPC command which your script relies on has been removed from Bitcoin Core. You should be able to replace it with the getblockchaininfo command.
528  Bitcoin / Development & Technical Discussion / Re: By what formula is the genesis-hash calculated? on: February 16, 2018, 09:07:51 PM
It's the hash of the genesis block. The genesis blocks parameters can be found in chainparams.cpp. It is then serialized and hashed.
529  Bitcoin / Development & Technical Discussion / Re: How to place tx in own mempool without broadcasting? on: February 16, 2018, 06:18:41 PM
Oh gee that's a good idea.  And that just applies to the RPC call, right?  So it wouldn't interfere with broadcasting the transaction if/when the block is mined..??
Yes, it should only applies to the RPC call. Of course you should test that for yourself before actually using it.

Assuming that's the case, that's exactly what I'm looking for, thanks!  One quick question, is that code you highlighted also responsible for using sendrawtransaction via the bitcoin-cli program, or do I need to find and commend out code somewhere else for doing it via the cli?  Either way, it's no trouble to use the RPC interface, so you've definitely given me a working solution.  Thanks!
You can use bitcoin-cli. bitcoin-cli is just a tool to interact with the RPC interface.
530  Bitcoin / Development & Technical Discussion / Re: Bitcoin Core & Milestones on: February 16, 2018, 05:59:49 PM
There is a time window for that? A bug could be there but just not found by users, so for how long developers wait before they consider RC4 as a stable version?
If no new bugs are found within a week of an RC's release, it will become the final version.
531  Bitcoin / Bitcoin Technical Support / Re: Bitcoin core multi wallet on: February 16, 2018, 03:47:48 AM
Good to know it's planned for 0.17. How come, even though it was useful to have also years ago, multi-wallet was never on the radar but started now getting more attention?
The way that the wallet implementation was before made it very difficult to implement multi wallet. In order to properly implement multiwallet, a lot of stuff had to first be done to decouple the wallet stuff from the rest of the software, and that requires a lot of changes and a lot of review. Only then were we able to get proper multiwallet support.
532  Bitcoin / Bitcoin Technical Support / Re: Bitcoin core multi wallet on: February 16, 2018, 01:55:20 AM
Can anyone suggest an effective way to interact with multiple wallets?
Use the bitcoin-cli utility and use the JSON-RPC interface.

The GUI only allows interacting with the first wallet, and as far as I know there's no way to switch the primary wallet without restarting.
GUI support for multiwallet will hopefully be in 0.17.0.
533  Bitcoin / Development & Technical Discussion / Re: How to place tx in own mempool without broadcasting? on: February 16, 2018, 01:10:09 AM
You can modify Bitcoin Core from source to disable transaction relay for things that come from the sendrawtransaction RPC command. Just remove or comment out these lines:
534  Alternate cryptocurrencies / Altcoin Discussion / Re: Are there no tutorial cloning bitcoin source? on: February 16, 2018, 12:26:05 AM
There are a number of old forum threads that explain how to create an altcoin from Bitcoin using older versions of Bitcoin Core. Many of the things that are mentioned there are the same things, just not in the same places. You can use grep to find where those variables are located now and change them as you want.
535  Bitcoin / Bitcoin Technical Support / Re: move wallet.dat from windows to linux on: February 16, 2018, 12:21:55 AM
If you created your wallet in an old version (< 0.13, i think) and upgraded it, yes.
No, there is currently no way to upgrade a non-HD wallet to a HD wallet. Upgrading requires generating a completely new wallet and moving your coins there or importing all of your private keys.

So, first, when my keypool empty - I cannot generate new bitcoin addresses =  Payment system  not working
Second - I have to enter password for wallet. On online computer. It's bad.
That is correct, you cannot generate new addresses to refill the keypool without unlocking your wallet. This is for security reasons. The private key needs to be stored somewhere once it has been generated. It cannot be stored unencrypted as that would be a security violation. The only way to store it encrypted is to provide the password so that the private key can be encrypted.
536  Bitcoin / Bitcoin Technical Support / Re: About double-spend ??? on: February 15, 2018, 04:31:02 AM
Bitcoin Cash is basically identical to Bitcoin except in three aspects: the signature hashing algorithm (which is actually partially the same as Bitcoin's as it is used for segwit), the difficulty adjustment algorithm, and the maximum block size. Because of this, they are vulnerable to largely the same attacks, including double spends of unconfirmed transactions.
537  Other / Meta / Re: A friend of mine can't register on: February 15, 2018, 04:29:10 AM
His account is proxybanned which means that he is accessing the forum from an IP address that is considered evil (that IP address was used to do evil things before like DoS attacks, spamming, having banned accounts, etc.). Such IPs are usually Tor exit nodes or proxies.

The only way around it is to pay the fee.
538  Bitcoin / Development & Technical Discussion / Re: How to make transaction speed faster? on: February 15, 2018, 04:27:06 AM
So bitcoin block generation speed is 10 minutes, is this minimum transaction speed?
No, that is the average block time that we want.

Then how can faster it?

I find at 'chainparams.cpp', consensus.nPowTargetSpacing = 10 * 60;

So this is 10 minutes, so if I change it to 0.1 * 60, then transaction speed also become 6 seconds?
If by transaction speed you mean confirmation time, then changing that will effect confirmation time because it effects the block time. Note that changing that does not guarantee that blocks will be found every 6 seconds, it only says that the average time in between blocks is 6 seconds.

What else parameters should I change to speed up?
You will need to change the maximum proof of work target (which thus decreases the minimum difficulty). The proof of work target is what actually regulates block times.
539  Alternate cryptocurrencies / Altcoin Discussion / Re: Genesis block compile error on: February 15, 2018, 03:22:02 AM
Your genesis block is invalid; it probably does not have a valid proof of work. You will actually need to mine your genesis block which you can easily do by adding a while loop to the genesis block creation code (and a few other lines to check the PoW).
540  Bitcoin / Bitcoin Technical Support / Re: Btc question on: February 14, 2018, 07:43:42 PM
I have a payment due into my Blockchain wallet, however, I have been advised that I need to make a payment to the sender in order to release my funds.  I gave the sender my normal blockchain wallet so I don't understand why I need to make a payment to release the incoming payment.  I have looked on the blockchain & can see the incoming btc.   The trader has access to my blockchain btw. Oh and also the tranactions say watch only Any help/advice would be appreciated, thank you.
If the sender is asking you to send him money so that he can send you money, then you are being scammed.

If you has access to your wallet, then he can take all of your coins.

I think you are being scammed.
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 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 ... 550 » is not available or authorized for sale. Do not believe any fake listings.
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!