Bitcoin Forum
May 24, 2024, 05:35:13 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 [425] 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 ... 590 »
8481  Other / Beginners & Help / Re: miners and full-node - the real numbers... on: November 08, 2015, 11:06:54 PM
I take the numbers from this post, titled "The 21 companies that control bitcoin":
http://uk.businessinsider.com/bitcoin-pools-miners-ranked-2015-7
That article is incorrect. POOLS ARE NOT COMPANIES. POOLS ARE NOT MINING FARMS. While some companies may have their own pools, the vast majority of mining pools are not run by a company and do not use their own hardware. The mining hardware in a mining pool comes from miners, including mining farms, who connect to pools and contribute hash power to the pools. This increases the odds of a pool finding a block and the block reward is distributed among the miners in that pool.

You can see the current pool distribution on https://www.blocktrail.com/BTC if you scroll all the way to the bottom.
8482  Bitcoin / Development & Technical Discussion / Re: Low level blockchain&network dev thread? on: November 08, 2015, 10:47:23 PM
I've been looking over the "reference implementation" GIT repo: https://github.com/bitcoin/bitcoin/tree/master/src

I didn't see any network configuration data. Anyone know how implementations set the packaged peer-server list the blockchain is pulled from first start? Are there official peers used by all "full" wallets?

I'm working with getBlockTemplate in Python(link) and want to research low-level blockchain interactions.
Check chainparams.cpp. The DNS seeds are hardcoded into the program. The DNS seeds will return nodes that Bitcoin Core can connect to. It then connects to those nodes given by the seed nodes. It will then choose one of those nodes and systematically request all of the blocks from it. There are no official peers used by full nodes. Any peer can be the initial download peer of any node.
8483  Other / Beginners & Help / Re: miners and full-node - the real numbers... on: November 08, 2015, 10:44:11 PM

you may be right, but as I said before, the Bitcoin numbers are too low:
- Bitcoin owners: probably 2-3 million. Bitcoin users (actively spending, trading, following news): 200k-500k.
- owners/users, who actually run a full-node on their PC > currently around 5500 nodes, which is a drop compared to 6200 a few months ago.
- the whole eco-system is based on a lotal of less than 30 mining-farms, worldwide.

Am I wrong on these numbers?
Yes, you are wrong. There are definitely more than 30 mining farms worldwide. Where are you getting that number from? There are probably about 30 notable mining POOLS but mining POOLS are different from mining FARMS. And mining farms are not the only ones supporting the Bitcoin network. There are many people who own miners but not enough to be considered a farm.

But you still haven't explained how Bitcoin is fragile.
8484  Economy / Service Discussion / Re: Problem changing receive wallet address on: November 08, 2015, 10:40:21 PM
KNIGHTDK,,,,, I followed you instructions and still (SIGNATURE IS NOT VAILD)When my signature in Coinbase is generated ,,,,I hoover my mouse over the signature and there is a red circle with a red line though it.....Is this a problem.?
No. It just means you cannot change the text. Just double click it and copy all of it.
8485  Bitcoin / Development & Technical Discussion / Re: How to hash the genesis block? on: November 08, 2015, 10:39:48 PM
You need to hash the header, which is the first 80 bytes (160 characters). You must hash that as binary data, this site is helpful: http://www.fileformat.info/tool/hash.htm. Then you must hash the sha256 hash of the header also as binary data. Lastly, you must reverse the sha256 bytes to get the hash.
8486  Other / Beginners & Help / Re: miners and full-node - the real numbers... on: November 08, 2015, 09:56:48 PM
Chinese mining farms probably do hold the majority of mining power. 

These are very bad news. Should I explain why?
Yes, please do. What makes that bad?

Uncertainty! The majority of the mining power should not come from one single country/region of the world --> China, for this matter. Mining-Costs are too high for the vast majority of supportes.
If one day the Communist Party/their Central Bank feel threaten by Bitcoin,  they can ban and/or crack-down their local Chinese mining-farms anytime. This is true for many other countries as well. This leads me to think that the whole bitcoin eco-system is way too fragile. The numbers are too low (too few mining farms, which cost a lot of money, too few full-nodes, too few users... too few of everything... etc).

The blockchain technology is here to say but the token's future is very much uncertain.
And how is that bad, how does that make bitcoin fragile? If China were to crack down on Bitcoin mining farms, how would that negatively effect Bitcoin? While a lot of mining power comes from China, they do not have the vast majority. China probably has about 50% or a little more of the mining power. If all of those miners were suddenly unable to mine, for a few weeks, the difficulty would be high and the blocks would take around 20 minutes instead of 10 minutes, a minor inconvenience. Then after enough blocks have been made, the difficulty would adjust down and everything would be back to normal.
8487  Other / Beginners & Help / Re: miners and full-node - the real numbers... on: November 08, 2015, 09:22:59 PM
Chinese mining farms probably do hold the majority of mining power. 

These are very bad news. Should I explain why?
Yes, please do. What makes that bad?
8488  Economy / Service Discussion / Re: Problem changing receive wallet address on: November 08, 2015, 09:21:34 PM
It works for me. Make sure that you put everything exactly as it says. Double click the message they want to select all of it and paste that directly into the empty message box. Make sure you have no extra spaces. When you copy the signature, double click the box to make sure that you have selected all of it and when you paste it into the signature box, make sure there are no extra spaces.
8489  Bitcoin / Bitcoin Technical Support / Re: Upgrade to core 11.1 caused possible loss of coins? on: November 08, 2015, 09:07:35 PM
cool, Tech support is probably better, thanks mods.


so yes, in short, I have checked all outgoing and incomings, they don't match up with anything, I would not rite here if it did.

I know your trying to help, but I am not new to bitcoin, If there was not lots of transaction I know are correct i would even say it was another wallet.

Please look at the first pic again, There should be a send address, there is not, I have blockchain explored the tx.id and do not recognize the output addresses.

I have gone through my messages to past deals and nothing matches, there are things missing aswell, both inc and out.

I have a complete image of a older wallet/blockchain, I will swap it out to see whats going on.
I don't think replacing the blockchain will help, the transaction database isn't stored there.

I think maybe your wallet file has been corrupted somehow. Make a backup of it and keep it somewhere safe. Then start Bitcoin Core with the -zapwallettxes option. That should remove all of the transactions from the transaction database and then do a rescan of the blockchain and add them back in. That might fix your problem.
8490  Other / Beginners & Help / Re: miners and full-node - the real numbers... on: November 08, 2015, 09:02:04 PM
There are not 21 miners. There may be that many pools, but there are most certainly much much more miners in the world. As for less than 5500 full nodes, the number is probably a little higher, but not by much. https://bitnodes.21.co/ lists all of the nodes that it can reach. This of course will not include nodes running over Tor and nodes that don't accept incoming connections, so the number is probably a little higher.

Chinese mining farms probably do hold the majority of mining power. The power is cheap there.
8491  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Qt wallet (win32 & 64) more and more corruption problems and reindexing on: November 08, 2015, 08:58:17 PM
Are you absolutely sure it is not hardware problems? Have you run hardware diagnostics on all of your computers?

Also, are you shutting down Bitcoin Core properly? If it does not shutdown properly, then you will need to reindex the databases. Also try reinstalling Bitcoin Core and use the latest version, 0.11.1.

Hello, thanks for answering, yes I am shutting down the wallet properly, wait for the closing dialog to disappear and wait an extra 10 seconds before power off.

100% sure, computers are OK, i do this for a living, i know computer hardware like the back of my hand, and I am pretty good solving computing problems, specially removing malware and virus by hand

The machines, even if they are not top notch, they are all decent quality/brand, all SSD samsung 840 pro and intel, all gigabyte high class machines, the older one probably has 7 or 8 months old, it is all AMD cpus since i don't trust intel hardware much, bad experiences.

the last crash happened today, on a machine i installed a week ago, and has practically no use, since i use it as a media center, so i don't go online with that machine ever.

that's why i decide to post, because this is getting too frequent, also several friends of mine started to have the same problems since 0.10 wallets about once a months at least.

I will try to compile it myself, to see if there is any difference, and I will try the linux version, but my experience on virtual machines with bitcoin qt is very crappy, for some reason is slow as hell to update!, which does not happen on the physical machine.

thanks
Indkt.
Interesting. Are you sure that you don't have anything that could be writing into the Data directory while Bitcoin Core is running? Anything that does could be messing it up. Also, do as 2112 said and run backups of your Data directory frequently so that if/when it gets corrupted, you can restore a clean one which will only take a few minutes to get back up to sync.
8492  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Qt wallet (win32 & 64) more and more corruption problems and reindexing on: November 08, 2015, 05:45:05 PM
Are you absolutely sure it is not hardware problems? Have you run hardware diagnostics on all of your computers?

Also, are you shutting down Bitcoin Core properly? If it does not shutdown properly, then you will need to reindex the databases. Also try reinstalling Bitcoin Core and use the latest version, 0.11.1.
8493  Bitcoin / Development & Technical Discussion / Re: generating and guessing BTC-adresses on: November 08, 2015, 04:43:54 PM

Quote
Most wallets are not designed to check for the address collision as it is impossible....


why is this impossible?
It would need to rescan the blockchain and every transaction to see if that address has been used before. It takes a lot of time to do that so that every time you want a new address, it would take hours for it to finish rescanning.

and how do i know that my newly generated address is really new? i never checked that. so possibly i generate an address and someone else had already generated this one. then you send me some coins. and uups a few weeks later this coins are gone because someone else received them to - by hazard - and spent them.
It is assumed. With a good random number generator, the likelihood of a collision is next to nothing. There have been cases where addresses have been generated multiple times on different devices but that was due to poorly written random number generators. You can check yourself if an address has been used before by just looking it up on a block explorer. However, to do this in a wallet is considered poor practice since it requires using an outside API, which may not be reliable and most good wallets don't want to rely on someone else to do the work.
8494  Bitcoin / Bitcoin Technical Support / Re: Upgrade to core 11.1 caused possible loss of coins? on: November 08, 2015, 04:18:18 PM
the negative amount means that you are taking Bitcoin from your wallet and sending it to someone else. You should see that all of the numbers, debit, transaction fee, and net amount are negative which means that you are sending the Bitcoin to someone. If you are receiving Bitcoin, then instead of debit, you should see credit and there will be no negative. You will see that the Net amount has a plus sign (+) in front of it.

hiya, thanks for response, I get that, but I dont understand where is the BTC address I paid? who did I pay? (i.e. my tags are gone) all I see is my pool mining coming in and all going out in blocks like this one, and dont correspond to my purchases.

There is one thing I paid for that is not on the "outgoing" list, but what does go out does not match in total what i paid for.

is there a way to see all my income addresses so I can check this off manually?
In your transactions list, when you click the second dropdown arrow and select sent to, does the list of transactions there match what you expect?

If you select received with, does that list match what you expect?

Do you think it is possible that someone somehow has the private keys to your addresses? Because if they do, then you have a huge problem. I don't think this is Bitcoin Core's fault.
8495  Bitcoin / Bitcoin Technical Support / Re: Approaching 24 hours and my sent bitcoins are not showing even on the blockchain on: November 08, 2015, 04:13:41 PM
Much appreciated, thank you a lot.

I've done what you told my buddy and I've came across these 2 notifications.

@Blockchain.info : Transaction Submitted

@Blockcypher.com : Error sending transaction: transaction already in pool.

What do you think ?

Again, thank you a lot Smiley
That error is fine. It just means that the transaction was actually submitted and propagated through the network. I only told you to submit it to two places in case one broadcast failed.
8496  Bitcoin / Bitcoin Technical Support / Re: Upgrade to core 11.1 caused possible loss of coins? on: November 08, 2015, 03:47:48 PM
the negative amount means that you are taking Bitcoin from your wallet and sending it to someone else. You should see that all of the numbers, debit, transaction fee, and net amount are negative which means that you are sending the Bitcoin to someone. If you are receiving Bitcoin, then instead of debit, you should see credit and there will be no negative. You will see that the Net amount has a plus sign (+) in front of it.
8497  Bitcoin / Bitcoin Technical Support / Re: Approaching 24 hours and my sent bitcoins are not showing even on the blockchain on: November 08, 2015, 03:43:16 PM
If you don't mind, could you please guide me in steps.

I'm sorry for the inconvenience, but I really need your help.
Open up Bitcoin Core and find the transaction. Copy the transaction id without the -000 or anything like that on the end of it. Sometimes Bitcoin Core will tack that on to the end of a transaction id.

Then open up Help > Debug Window and go to the console tab.

Type into the box
Code:
getrawtransaction <txid>
where <txid> is the transaction id you copied earlier without the -000 on the end.

You should get a bunch of hex characters as output.

Copy all of it and go to https://blockchain.info/pushtx and https://live.blockcypher.com/btc/pushtx/. In the giant box on both those webpages, paste the hex characters you copied earlier. Then click submit or broadcast transaction and it should broadcast the transaction to the network. If there is any error, you will get a notification on the page. Then you can check the block explorers again to see if the transaction is there.
8498  Bitcoin / Bitcoin Technical Support / Re: Approaching 24 hours and my sent bitcoins are not showing even on the blockchain on: November 08, 2015, 03:33:56 PM
The issue that the 0.4 BTC is already deducted from my main balance.

That would be the wallet keeping the transaction in its log, would be nice to know why it failed, but anyways, every (proper) wallet has a resync option for this. Its kind of a pain for people using Bitcoin core. Its not a very good wallet for every day uses imo.



I've made a manual re-scan but nothing seemed to be changed.

Shall I re-index the complete blockchain ?
That is not necessary.

Since the transaction is already created, you should be able to pull the raw hex for it from Bitcoin Core. Get the raw hex and push it through various transaction broadcasting services like the ones at blockchain.info, blocktrail, and blockcypher. You can also try to push it through Bitcoin Core.
8499  Bitcoin / Bitcoin Technical Support / Re: bitcoin core wallet no block source available on: November 07, 2015, 08:27:07 PM
No in connections is fine. Check the peers tab and make sure that all of the nodes listed there have a ping time and the numbers about their block data is within 1 block of the current head such can be looked up on a block explorer.
8500  Bitcoin / Development & Technical Discussion / Re: Lock multisig output to a set of addresses on: November 07, 2015, 08:18:22 PM
Lock the the payment to a set of addresses. For example address 3jhGu... Can only spend its bitcoins to pay addresses 1huyt... & 1PLo2...
No, it is not possible to set any address to only be able to send a payment to only a specific set of addresses.
Pages: « 1 ... 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 [425] 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 ... 590 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!