but still would like to know how it all began,
Mining is the process specified by Satoshi Nakamoto in the Bitcoin whitepaper which generates a proof of work for each block in the blockchain. Mining was always around and could previously be done on CPUs and GPUs. The first release of the Bitcoin client contained a built-in miner. I think mining was the fastest way to get bitcoins when it first came out.
Part of mining is the generation of new Bitcoin. Because Bitcoin is not premined, the only way to get Bitcoin when Bitcoin first came out was to mine them.
|
|
|
I'm reading BIP143 about new transaction digest algorithm. In Specification item 5 is scriptCode of the input and for P2WPKH it says 'For P2WPKH witness program, the scriptCode is 0x1976a914{20-byte-pubkey-hash}88ac'. For a script to be P2WPKH it has to have output '0 {20-byte-hash}'. Am I to understand that this new digest algorithm takes this 20-byte-hash and wraps it into script code before hashing?
No. The 20-byte-hash in the output script is the same as the 20-byte-hash in the scriptCode. It is the ripemd160(sha256(pubkey)).
|
|
|
Forgot to say that I extended the deadlines. The auction will end at 0:00 December 21st UTC. The ads will show for a week, from December 22nd to December 29th.
|
|
|
I mean, seriously? What kind of idiot do you think would chose any of the above passwords to protect his life's savings? Clearly multiple people chose those passwords to protect some amount of Bitcoin. The point is that people think those passwords are strong passwords because online password checkers say that those passwords are strong. If you are recommending people to use brainwallets, they are likely to use those types of passwords thinking that they are strong passwords when in actuality they are not.
|
|
|
Please don't use words like "horribly" or "probably" trying to discuss technical issues.
Why? I understand not using probably (I thought this was in beginners and help so it was primarily as a warning to noobs) but what is wrong with "horribly insecure"? Please refer me to the multiple research papers (and programs) you've mentioned.
Cracking programs: Research: I am able to discuss technical aspects (numbers, codes, algorithms) and science behind them. I am not however willing to argue with your emotions or believes.
This is not just something that I believe or my emotions. Many other people in the Bitcoin technical area have discussed how brainwallets are insecure and not recommended for general use. Off the top of my head, I know that greg and theymos has discussed this before. I use brain wallets myself, have been for years. For me they are more secure, reliable and convenient than wallets which require to be stored and backed up.
It is possible to securely use brainwallets, but it should not be something that is recommended to newbies and those who do not understand technical aspects of Bitcoin IMO.
|
|
|
My code rejects the message since it is too short (message decode fails)
Yes, mine too. But maybe it shouldn't? I think it should be failing. sendcmpct is supposed to be 9 bytes (1 byte boolean 8 byte uint64). My guess is that someone wrote their own node software, set the user agent to be /Satoshi:0.13.1/ for some reason, and then did not realize that the version integer is uint64 instead of uint32.
|
|
|
OP, please mention the bid increments. Bid increments are 0.001 BTC
|
|
|
Let me list a few... - Bitcoin Knots
- Bitcoin Unlimited
- Bitcoin Classic
- Bitcoin XT
All full nodes. None of them are Core. None of them require that Core be installed. There's also btcd, bitcore (note: not Bitcoin Core but bitpay's thing), bitcoinj. There a list of all full node implementations floating around here somewhere.
|
|
|
It is highly NOT RECOMMENDED to use brainwallets. Humans are a horrendously low source of entropy. There are multiple research papers and programs that show that brainwallets are horribly insecure and easily cracked as what you think is a strong password probably is not a strong password.
BIP 38 paper wallets will not be particularly helpful here. It only protects against someone stealing your paper wallet and trying to get the keys. BIP 38 does not protect against someone just guessing the password you used to create your brainwallet.
|
|
|
But on an HDD I can completely destroy the data with DBAN, is this a valid option on SSDs?
There are certainly software that can securely erase the data on an SSD. They use different ways to do this so DBAN won't work, but the software to securely erase SSDs exist. Just use Google and you will find them.
|
|
|
You cannot post images until you are a Jr. Member or above.
|
|
|
Veracrypt is considered safe. It has been audited and it is based on TrueCrypt. If you encrypt your hard drive with at least AES, you should be good to go.
BTW, this belongs in off topic, I have moved it.
Even if it's an SSD? I know it's based on TrueCrypt but I keep running into posts claiming SSD encryption isn't safe enough since deleted data is never actually deleted Having an SSD shouldn't make a difference. Regardless of whether you use and SSD or an HDD, deleted data is never actually deleted. That is something caused by the filesystem, not the hardware itself.
|
|
|
I am looking for people who would like to advertise on my website, https://www.bctalkaccountpricer.info/What is the website?For those of you who don't know what this website is, it is a place to look up various stats about an account, including a price estimation. This site is frequently used by account sellers as well as those who want to find out the potential activity of an account, posting statistics of the account, and all of the addresses previously posted by the account. For more details, see https://bitcointalk.org/index.php?topic=1142314.0. StatsThe website receives 100-300 impressions per day. Ad SlotsThere are two ad slots currently available, a banner ad on top and a sidebar ad on the right. The banner ad must be 728x90 and the sidebar 120x600. The ads will be shown from Tuesday December 20th at midnight until Monday December 26th at 11:59 PM UTC. The following screenshot shows the ad locations: Ad restrictionsThe ads must either be images with links or an iframe. Any ads related to anything NSFW will not be allowed. I reserve the right to reject bids and ads. BiddingWhen bidding, please indicate which ad slot (banner or sidebar) you would are bidding for. Bids for each slot start at 0.005 BTCBidding ends on December 19th at Midnight UTC. The winner of the auction will be notified once the auction is over. You must either send first or use a reputable escrow.
|
|
|
Today I stopped my computer (after exiting Bitcoin Core properly), and I just started it. I examined ...AppData/Roaming/Bitcoin, the database dir was not present and debug.log contained logs from yesterday. I started Bitcoin Core, it started syncing where it left before the shutdown; I then examined ...AppData/Roaming/Bitcoin, database dir was created and debug.log contains only logs from today (yesterday's logs are no longer there).
It seems that when I start Bitcoin Core the debug.log only keeps today's logs (or something similar), is this possible? Any conf option that would be responsible for that?
The database folder should disappear after you shut down Bitcoin Core. That is expected behavior. What is not expected is clearing the debug.log. I don't know of anything that would cause the debug.log to be cleared on startup. Concerning the syncing from scratch, it doesn't seem like the restart was the problem, but rather that it happened when Bitcoin Core was running, which means, it (BC) didn't exit properly.
It should only be reindexing and warning you that it is reindexing. That it does reindex when you don't exit Bitcoin Core improperly is not surprising, although this behavior should have already been fixed. Moreover, the last time the resyncing happened, blk files were already present ...
Next time that happens, watch your network traffic. If you look at the task manager, there should be something there to watch your network traffic. You can also go to the debug window and there is a tab for Network Traffic. If you actually are resynching, you should see that that you are suddenly receiving a ton of data and that there is a lot of network traffic. If you are not, then you are reindexing instead of resynching.
|
|
|
also those nodes you see on blockchain.info does not belong to the site, they are bitcoin nodes that they connect to. and you can check them yourself if you want, i don't see any of them lagging behind. and if one of them is offline they disconnect, you can't stay on the network and be offline.
Blockchain.info has to run their own full node(s) as well (which is connected to the nodes listed). Their node(s) seems to have issues every so often.
|
|
|
Veracrypt is considered safe. It has been audited and it is based on TrueCrypt. If you encrypt your hard drive with at least AES, you should be good to go.
BTW, this belongs in off topic, I have moved it.
|
|
|
That is a service issue. Users on this forum cannot help you with this. Please contact the support of bitpanda to resolve your issue.
|
|
|
My computer restarted yesterday, the debug.log file has logs from only today.
Why would that be the case? The log files are persistent and stored on disk, they should not be deleted between starts of the computer, or of the software. That your log files are deleted between starts and that you constantly have to redownload seems to indicate that something is deleting your datadir and Bitcoin Core has to recreate it every time it starts up. Is there something particular to look for?
Any errors. Pay attention to anything regarding the data directory and blocks folder. You should also look at the lines that are logged when you start up Bitcoin Core and see what it says about the initial state and whether that matches your settings.
|
|
|
There is no difference between the confirmations times of transactions made by web wallets and desktop wallets. There is no distinction in those transactions that would cause one to confirm faster. What does matter is the transaction fee and that can be set by any wallet, regardless of desktop or web.
Using a web wallet is highly NOT recommended. Most do not give you access to the private keys, so you don't actually control your Bitcoin. Furthermore, your Bitcoin is at the whim of the web wallet. If the web wallet shuts down, your Bitcoin will no longer be accesible (usually). If you don't take the proper precautions to backup your private keys if you have access to them, you will lose all your Bitcoin.
|
|
|
|