aurel57
Legendary
Offline
Activity: 1246
Merit: 1000
|
|
April 01, 2015, 10:16:51 PM |
|
Can anybody get logged in on a IPhone or IPad? if so please tell me how. Thanks
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
|
|
April 01, 2015, 11:11:48 PM |
|
Someone please explain to me how and what it means for a block to get orphaned.
Thanks,
Tom
An oprhaned block is a block that wasn't actually accepted into the blockchain. True. It usually is caused by the longer chain accepting the block because more work and effort was put forth compared to your block.
Not true. There wasn't more work and effort put into the solution of that other block. It's a majority consensus. You and I both solve block number 12345. I submit my block to the network. You also submit yours. If more nodes accept your version of the chain, then my block becomes orphaned. I say to a node, "Hi, here's block 12345". That node says, "I've already got 12345, you need to update yourself with my copy." Eventually every node has your copy of the chain and my poor block 12345 no longer has a parent on the chain (the block it claimed as its parent has already been linked to your block) and is orphaned.
|
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
TTravis
|
|
April 01, 2015, 11:29:38 PM |
|
Thanks, This stuff is slow to soak in.
Tom
|
|
|
|
|
MyRig
Donator
Hero Member
Offline
Activity: 792
Merit: 510
support@myrig.com
|
|
April 02, 2015, 12:11:55 AM |
|
P2pool is a tough one to make it work for the engineers.
Hashrate drop... Spring Maintenance and Migration of miners to Bitmain Own facility from Umisoo.com facility. Missing hash power will be back in a few days!!
Some customers received email from Umisoo.com regarding the spring cleaning and migration
|
Antminer & DragonMint Repair E-mail: support@myrig.com T: @MyRig_com Return Address: MyRig 3700 Quebec Street, Unit 100-239, Denver, Colorado 80207, USA
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
April 02, 2015, 01:20:14 AM |
|
Someone please explain to me how and what it means for a block to get orphaned.
Thanks,
Tom
An oprhaned block is a block that wasn't actually accepted into the blockchain. True. It usually is caused by the longer chain accepting the block because more work and effort was put forth compared to your block.
Not true. There wasn't more work and effort put into the solution of that other block. It's a majority consensus. You and I both solve block number 12345. I submit my block to the network. You also submit yours. If more nodes accept your version of the chain, then my block becomes orphaned. I say to a node, "Hi, here's block 12345". That node says, "I've already got 12345, you need to update yourself with my copy." Eventually every node has your copy of the chain and my poor block 12345 no longer has a parent on the chain (the block it claimed as its parent has already been linked to your block) and is orphaned. Actually, it's even simpler than that. It's who makes the NEXT block that decides which one wins (and which is orphaned) The block they built off becomes the winner. Of course the statistics of it says that it is most likely to be the block being built on by the most miners, but that is just probability. Also of course, the orphan process can continue for more than one block, if yet again the next block has 2 candidates built off the 2 original 12345 blocks - but that is very rare - but still works the same way. What happens at a pool (or on a solo miner) is that it will submit a block to it's peers and then work on the next one. It will base the new work on the block it submitted to the network. If the pool (or solo miner) also happens to find the next block before anyone else, then even if they were the only ones mining off their block, it will still make them the winner. It really boils down to who gets the next (or the next, or the next ...) block out first that decides it all. Edit: this also, though may not be obvious, explains how a 51% works
|
|
|
|
TTravis
|
|
April 02, 2015, 02:14:11 AM |
|
It seems to mess up the percentage of luck calculation some because the time it took to get from the last good block to the orphaned block is no longer counted in the time it takes to get to the next good block. Any recommendations on a book I could buy and read to get more up to speed on this stuff? I red a couple introductory books that did not get into these details. I think the overall concept of blockchain, something I only heard of a few weeks ago, is going to open up a whole new world. And thanks "Mikestang" for your helpful suggestion on Google. I'll have to try that out sometime.
|
|
|
|
aurel57
Legendary
Offline
Activity: 1246
Merit: 1000
|
|
April 02, 2015, 12:45:11 PM |
|
Can anybody get logged in on a IPhone or IPad? if so please tell me how. Thanks
It works now.
|
|
|
|
notlist3d
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
April 02, 2015, 01:06:16 PM |
|
P2pool is a tough one to make it work for the engineers.
Hashrate drop... Spring Maintenance and Migration of miners to Bitmain Own facility from Umisoo.com facility. Missing hash power will be back in a few days!!
Some customers received email from Umisoo.com regarding the spring cleaning and migration
Thank you for being transparent on what it was . I appreciate you telling us and not keeping us in dark. Looks like it's back up now on hashrate.
|
|
|
|
ezeminer
Legendary
Offline
Activity: 2212
Merit: 1118
Lie down. Have a cookie
|
|
April 02, 2015, 01:11:34 PM |
|
Someone please explain to me how and what it means for a block to get orphaned.
Thanks,
Tom
An oprhaned block is a block that wasn't actually accepted into the blockchain. True. It usually is caused by the longer chain accepting the block because more work and effort was put forth compared to your block.
Not true. There wasn't more work and effort put into the solution of that other block. It's a majority consensus. You and I both solve block number 12345. I submit my block to the network. You also submit yours. If more nodes accept your version of the chain, then my block becomes orphaned. I say to a node, "Hi, here's block 12345". That node says, "I've already got 12345, you need to update yourself with my copy." Eventually every node has your copy of the chain and my poor block 12345 no longer has a parent on the chain (the block it claimed as its parent has already been linked to your block) and is orphaned. Actually, it's even simpler than that. It's who makes the NEXT block that decides which one wins (and which is orphaned) The block they built off becomes the winner. Of course the statistics of it says that it is most likely to be the block being built on by the most miners, but that is just probability. Also of course, the orphan process can continue for more than one block, if yet again the next block has 2 candidates built off the 2 original 12345 blocks - but that is very rare - but still works the same way. What happens at a pool (or on a solo miner) is that it will submit a block to it's peers and then work on the next one. It will base the new work on the block it submitted to the network. If the pool (or solo miner) also happens to find the next block before anyone else, then even if they were the only ones mining off their block, it will still make them the winner. It really boils down to who gets the next (or the next, or the next ...) block out first that decides it all. Edit: this also, though may not be obvious, explains how a 51% works Thanks kano! You know this stuff better than I ever will
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
|
|
April 02, 2015, 01:17:05 PM |
|
Someone please explain to me how and what it means for a block to get orphaned.
Thanks,
Tom
An oprhaned block is a block that wasn't actually accepted into the blockchain. True. It usually is caused by the longer chain accepting the block because more work and effort was put forth compared to your block.
Not true. There wasn't more work and effort put into the solution of that other block. It's a majority consensus. You and I both solve block number 12345. I submit my block to the network. You also submit yours. If more nodes accept your version of the chain, then my block becomes orphaned. I say to a node, "Hi, here's block 12345". That node says, "I've already got 12345, you need to update yourself with my copy." Eventually every node has your copy of the chain and my poor block 12345 no longer has a parent on the chain (the block it claimed as its parent has already been linked to your block) and is orphaned. Actually, it's even simpler than that. It's who makes the NEXT block that decides which one wins (and which is orphaned) The block they built off becomes the winner. Of course the statistics of it says that it is most likely to be the block being built on by the most miners, but that is just probability. Also of course, the orphan process can continue for more than one block, if yet again the next block has 2 candidates built off the 2 original 12345 blocks - but that is very rare - but still works the same way. What happens at a pool (or on a solo miner) is that it will submit a block to it's peers and then work on the next one. It will base the new work on the block it submitted to the network. If the pool (or solo miner) also happens to find the next block before anyone else, then even if they were the only ones mining off their block, it will still make them the winner. It really boils down to who gets the next (or the next, or the next ...) block out first that decides it all. Edit: this also, though may not be obvious, explains how a 51% works Thanks for explaining it in even better terms than I did!
|
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
MyRig
Donator
Hero Member
Offline
Activity: 792
Merit: 510
support@myrig.com
|
|
April 02, 2015, 06:32:08 PM |
|
@Kano,
Thank you SIR!! Nice Explanation, easy to understand!
|
Antminer & DragonMint Repair E-mail: support@myrig.com T: @MyRig_com Return Address: MyRig 3700 Quebec Street, Unit 100-239, Denver, Colorado 80207, USA
|
|
|
Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
|
April 02, 2015, 07:39:54 PM |
|
And thanks "Mikestang" for your helpful suggestion on Google. I'll have to try that out sometime. You're welcome, always happy to help an eager mind.
|
|
|
|
marvykkio
|
|
April 03, 2015, 05:59:02 AM |
|
be careful to purchase material from bitmain, I bought 4x antminer s5, 2 paid by bank transfer, and 2 with bicoin, I have made three separate expedition, I wanted to pay 3 times the expedition, three times the customs, 380 euro of taxes, my miner are blocked by Italian customs because they noticed three different expeditions always the same person, that if bitmain had sent all 4 miner in only shipment would have paid much less, I sent an email asking for a refund of the money more than I paid, and they said he's sorry but they could not do anything, not even a coupon, then notify all the people who shop on bitmain to be careful. sorry for my english (google translador).
|
|
|
|
notlist3d
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
April 03, 2015, 07:45:09 AM |
|
be careful to purchase material from bitmain, I bought 4x antminer s5, 2 paid by bank transfer, and 2 with bicoin, I have made three separate expedition, I wanted to pay 3 times the expedition, three times the customs, 380 euro of taxes, my miner are blocked by Italian customs because they noticed three different expeditions always the same person, that if bitmain had sent all 4 miner in only shipment would have paid much less, I sent an email asking for a refund of the money more than I paid, and they said he's sorry but they could not do anything, not even a coupon, then notify all the people who shop on bitmain to be careful. sorry for my english (google translador). This is wrong thread to vent but: I'm sorry to hear about your problems. Personally I have always had good luck with Bitmain. For customer service on order's email: info@bitmaintech.comOn custom's you can not blame Bitmain for that. That would be something they have zero control over. Also it sounds like different orders since one paid with bank transfer other bitcoin. So it showing at customs as multiple orders I would guess is right. I suggest looking into hosting centers if your country has a big vat. Bitmain really cannot pay your vat, buyers should know about it before buying. I think it is up to customer to know your countries import laws. On thread: As far as pool it's working great! Thanks Bitmain for putting so much work into it.
|
|
|
|
aurel57
Legendary
Offline
Activity: 1246
Merit: 1000
|
|
April 04, 2015, 09:03:42 PM Last edit: April 04, 2015, 09:45:06 PM by aurel57 |
|
WOW Block 350738 took 1 sec .10%
also 4 out of the last 5 blocks.
EDIT: Something looks screwy as its says 190PH/s??? how did the hash go up x4 in 1 sec?? That can't be right...cut everyone pay by 4??
|
|
|
|
coinits
Legendary
Offline
Activity: 1582
Merit: 1019
011110000110110101110010
|
|
April 04, 2015, 09:20:15 PM |
|
WOW Block 350738 took 1 sec .10%
also 4 out of the last 5 blocks.
EDIT: Something looks screwy as its says 190PH/s??? how did the hash go up x4 in 1 sec?? That can't be right...cut everyone pay by 4??
True dat!
|
Jump you fuckers! | The thing about smart motherfuckers is they sound like crazy motherfuckers to dumb motherfuckers. | My sig space for rent for 0.01 btc per week.
|
|
|
Ecnad
|
|
April 04, 2015, 09:27:51 PM |
|
Some kind of error as I got the same payout for the block as the one before it.
|
|
|
|
DebitMe
Legendary
Offline
Activity: 2800
Merit: 1012
Get Paid Crypto To Walk or Drive
|
|
April 04, 2015, 09:33:06 PM |
|
Some kind of error as I got the same payout for the block as the one before it.
its not an error, read about how payouts are determined before posting.
|
|
|
|
Ecnad
|
|
April 04, 2015, 09:38:01 PM |
|
Some kind of error as I got the same payout for the block as the one before it.
its not an error, read about how payouts are determined before posting. I meant an error on the stats page showing the unusual hash rate, since the payout itself is right. But thanks for the suggestion on furthering my education in payouts.
|
|
|
|
|