Bitcoin Forum
February 19, 2018, 01:07:38 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
  Home Help Search Donate Login Register  
  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 ... 534 »
1  Other / Meta / Re: BTT MESSAGING ERROR on: Today at 06:44:10 AM
Go to your Profile. On the left side, click the link for Personal Message Options. Check the box labeled Allow newbies to send you PMs.
2  Bitcoin / Bitcoin Technical Support / Re: Lost bitcoins on: Today at 05:17:05 AM
Given that I have recovered an unsent raw transaction and posted a redacted version of the output above, is there anything obviously wrong with it?
I don't see anything obviously wrong with it. There's a transaction fee and, assuming that the input you are spending is actually 50 BTC, there's no need for a change address.

if there is any advantage to trying to make a raw transaction from scratch, in the way that you describe?
The advantage that you are more likely to create the transaction correctly. However yours looks correct, so there shouldn't be any problems.
3  Bitcoin / Bitcoin Technical Support / Re: Lost bitcoins on: Today at 03:26:20 AM
I've redacted all the long numbers just in case there's anything sensitive there. The big 'gotcha' it seems is that if you're not careful and don't either spend the lot in one transaction or create a second output going back to yourself, then any change will go to the miners. The intuitively sensible thing to do is to send one bitcoin just to test and see whether it works, with the intention of sending the rest later. This would be a very bad idea as you would be donating a mining fee of 49 bitcoins!

So there ends the limits of my understanding of raw transactions. I'd be very grateful if anybody knowledgeable could look over the redacted transaction and tell me whether there's anything else I might have gotten wrong?
You don't know what you are doing with raw transactions; you should not be attempting to create a raw transaction manually.

The following assumes that you don't want to have your private key exposed to a machine that is on the internet, if it is, let me know and I will give you modified instructions.

On a machine connected to the internet, install Bitcoin Core, start it up and then use the importaddress command to import your address. This will import just the address, not the private key, so your coins are still safe. Do this as soon as possible so that you don't have to wait for it to rescan the blockchain later.

Once the address is imported, let Bitcoin Core sync. If you don't have the disk space for the blockchain (~180 GB), then you can use pruning. There should be an option for pruning in the settings somewhere.

Once Bitcoin Core has synced, make sure that it has the balance that you expect.

Now using createrawtransaction, create a raw transaction with no inputs and the output you want. So your command will look something like this:
createrawtransaction '[]' '{"<address>":50}'
Note that using the full value of your coins (~50) there is okay, the fee will be handled later. Additionally any change outputs will be handled later.

Take the output of that and pass it into the fundrawtransaction command with the options I will specify in the example:
fundrawtransaction <hex> '{"includeWatching":"true", "subtractFeeFromOutputs":[0]}'
What this command does it lets Bitcoin Core fill in the inputs and the transaction fee necessary. The includeWatching parameter lets it choose the inputs from your watching-only address and subtractFeeFromOutputs will subtract the fee from your outputs so you can send the maximum amount possible.

Take the result of the above command and pass it into signrawtransaction. Then broadcast that result with sendrawtransaction.
4  Bitcoin / Development & Technical Discussion / Re: Some testnet questions on: Today at 03:15:36 AM
Thanks for the answers! That was helpful. I'd imagine that testnet coins would still have a value of a few cents, right?
No, because testnet coins are freely given away and in large quantities. They are not traded anywhere. Some scammers may claim that testnet coins have value and try to sell testnet coins, but they are easily obtainable for free.

If testnet coins were to have a value, then the testnet would be reset and started from scratch. This has happened twice already; the original testnet was discarded and replaced with testnet2. When testnet2 was being traded for money, it was discarded and replaced with testnet3. Testnet3 is the current iteration of testnet, and it can be discarded and replaced with a new testnet.

I've always been curious - who creates testnet coins?
Miners do. People mine on testnet.

If they have no value, I'm sure there would be no incentive to mine them - so where exactly do they come from?
The incentive is a safe testing environment where people can do crazy things without risking any money. Some of those things may involve mining, so people will mine on testnet. Others may decide to mine testnet coins to use for themselves, so they mine on testnet. And others may use testnet frequency and just need it to not be dead so they can test things on it, so they mine it. The difficulty of testnet is so low that it can usually be CPU mined. At other times, it can be gamed into CPU mining difficulty levels since testnet has a difficulty reset mechanism.

Who holds them, and why?
Developers and people who want to test things without risking money.

What is the testnet supply cap?
Sam as Bitcoin's, ~21 million

I'm sure that if thousands of shitcoins have value, then a BTC testnet coin would also eventually have value, so why doesn't the testnet coin immediately gain some form of value (since it is scarce and acts exactly like BTC)?
Because if it were to have value, then testnet loses its value as a testing ground (place to test with coins that can be gotten for free). Additionally, the testnet can be reset and has been reset in the past.

When i run a bitcoin core node in testnet, how do i mine bitcoin in testnet? What is the settings in bitcoin.conf ? 

The setgenerate is not working, see below:
./bitcoin-cli -testnet setgenerate true
How do you know that it isn't working? setgenerate doesn't give any visible output. And testnet still has a difficulty, so it takes time to mine blocks.
5  Bitcoin / Bitcoin Technical Support / Re: Restore Bitcoin-qt from wallet.dat after crash on: February 18, 2018, 08:18:22 PM
Just curious, when would a forced rescan ( -rescan ) be useful or necessary?
A forced rescan is only necessary if you don't see your expected balance once the wallet has finished syncing.
6  Bitcoin / Development & Technical Discussion / Re: How do exchange transactions work? on: February 18, 2018, 06:31:00 PM
Exchanges do not make transactions on chain, that would be inefficient and costly. Rather they have a central database with their customer's balances. So when you make a trade, they just update balances in their database. The same happens when you deposit or withdraw, a value in their database is updated.

When you deposit coins into your exchange wallet, they just change values in their database. The coins are no longer yours nor are they identifiable to you once they enter an exchange. Don't think of those coins as "your coins" but rather "the exchange's coins". What they do with deposits is much like a traditional bank does - they update a balance in their database which is effectively a promise to you that they will give you that amount in the future when you ask for it (aka withdraw). The coins themselves will be put in some wallet and then later used for someone else's withdrawals. The transactions that happen within the exchange itself happen on a database and they can keep logs of everything, so they do actually know how much you had, when, and how much you traded.
7  Bitcoin / Development & Technical Discussion / Re: Anon hosting for seed-node? on: February 18, 2018, 05:27:00 PM
2. Depending on what source you are using, these likely can just be IP Addresses.
They can't be IP addresses. The DNS seeders are not servers that you send queries to. Rather you do a DNS lookup for the domain name, and because the DNS seeder is configured to be the nameserver for that domain, it will provide DNS records that are for the domain. However those records don't point to any IP addresses for a server at that domain; rather they point to nodes that you can connect to.
8  Bitcoin / Development & Technical Discussion / Re: Bitcoin's earliest developers on: February 18, 2018, 05:22:12 PM
It's pretty funny, but the earliest developers of Bitcoin used the source code of the application as a forum board. They commented some lines of code, for example: "Why Base58 is used instead of standard Base64?" Then they gave an answer commenting code again. Smiley
No, that's not meant as a forum board but rather providing a question that people are going to ask and then answering it. The source code as not used to ask questions like that. If you look carefully, you'll see that both the question and answer were written by the same person (satoshi) in the same commit.
9  Bitcoin / Bitcoin Technical Support / Re: Importing wallet.dat on: February 18, 2018, 04:35:32 AM
If it was, it was compiled with --with-incompatible-bdb, because BDB 4.8 uses Btree version 9, not version 10, hence the error. (I don't know if any altcoins are still using BDB 4.8; if not, it might be an altcoin wallet.)
Ah, I didn't know what the version BDB 4.8 was. If version 10 is for a more recent version of BDB, then he's probably using an altcoin, not Bitcoin. I doubt he would have compiled Bitcoin Core himself.
10  Bitcoin / Bitcoin Technical Support / Re: Importing wallet.dat on: February 18, 2018, 03:41:09 AM
I tried to run it with -salvagewallet option, but client window just closes after launch and in db.log there is a message "path/to/wallet/wallet.dat: unsupported btree version: 10".
How old is this wallet.dat file? What's the creation date?

A long time ago, the wallet.dat format was changed so very old wallets are not compatible with modern versions of Bitcoin Core. I suspect that is what you are running into here.
11  Bitcoin / Bitcoin Technical Support / Re: Importing wallet.dat on: February 18, 2018, 02:21:58 AM
wallet.dat is the wallet file for wallets based on Bitcoin Core. Typically it refers to a Bitcoin Core wallet, but other coins that have clients based on Bitcoin Core will also create wallet.dat files. There's a good chance that it is for Bitcoin Core.

If the wallet cannot be opened in Bitcoin Core, it may be corrupted as is indicated by Bitcoin Core. You can try starting Bitcoin Core with the -salvagewallet option in order to attempt a wallet recovery. You should of course make a backup of the file before actually doing that.
12  Bitcoin / Development & Technical Discussion / Re: Bitcoin source 'make install' take over 2 giga capacity? on: February 18, 2018, 02:18:38 AM
Now suddenly bitcoin folder's size become over 2 giga, almost take all the empty capacity (total 20giga hdd inside virtualbox), system become unstable, even all apps does not appear, can't run terminal itself.
By "bitcoin folder" do you mean the folder containing the source code or do you mean the datadir?
13  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.15.1 Released on: February 17, 2018, 09:35:40 PM
1.I disagree as soon as the blockspace is increased it changes the pricing structure. it's a simple mathematical statement. I don't understand how you can deny it logically. What ever the modification to the max txs per block will have an impact on the fee. So if txs more to segwit it means less for blockspace or what ever the system off chain (and true I didn't read the bip). I mean it isn't on chain, on the block chain as intented by satoshi and us when we joined. I mean it was clearly all txs in a block every 10 min, the block 1mb, no one can change that blah blah... then saturation.
I never said that it wouldn't effect fees. I said it does not effect fee calculation.

Segwit transactions are still on chain and fees are still basically calculated in the same way (some constants change). It does not suddenly become impossible to estimate fees are to estimate income for miners. All segwit transactions are in blocks; all data in segwit transactions are in block. Nothing about that has changed.

I do highly suggest that you read up on how segwit actually works before jumping to conclusions and trying to have a discussion about it.

2. Wrong a 500GB SSD cost 150$ !!! It is such a lie about difficulty for people. What the fuck all interconnected system are super complex to setup and the DIY about banking is quite risky and can WAY more expansive than decades of banking fees...  At one point the market will bash all narratives that you try to construct here. even more brutal will be your fall if you believe them. Safety cost don't increase with the size of the blockchain.
I said there's more to it than just disk space. Can you read?

You also need a computer, one with a CPU and RAM that can handle the load of processing the blocks that are being received. You also need to have enough network bandwidth in order to be able to receive and relay blocks and transactions. Furthermore, blocks could be constructed to be malicious and cause DoS attacks, and larger blocks make those worse. So there's way more to larger blocks than just disk space, or even network bandwidth requirements.

your all argument is so flawed, it's brutal... never written a line of code in your life I guess? mostly pr and cr?
Yes, I totally have never written a single line of code in my life. That's why I have a Github account with several repositories (many of which are my own) where I have made several commits. It's also why I have 52 commits in Bitcoin Core and several Pull Requests. It's also why my name is in the release notes at the beginning of this thread.

I think I'm being trolled. I'll probably ignore you now.
14  Bitcoin / Bitcoin Technical Support / Re: Restore Bitcoin-qt from wallet.dat after crash on: February 17, 2018, 08:55:39 PM
That was a quick response. Smiley Thanks for everything. So it doesn't make much of a difference if I wait for the chain to finish loading before switching the wallet.dat, since it won't take long to sync after I switch them?
Yes. Rescanning is not the same as syncing.
15  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.
16  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.
17  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.
18  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.
19  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.
20  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.
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 ... 534 »
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!