edit: unless they just live in the same house in southern california
Topic: [XCT] C-Bit - Elegantly Solving Bitcoin's Blocksize Problem [SHA256][POW] - page 16. (Read 66819 times)
March 22, 2016, 09:06:18 PM
btw, anderson705 and gembitz are the same person. just an fyi everyone.
edit: unless they just live in the same house in southern california
edit: unless they just live in the same house in southern california
March 22, 2016, 08:59:00 PM
look noob ===vvv all the 1.O diff blocks go to the attacker ! ~ pfft you guys need another hint? 
54983 2016-03-22 23:48:57 3 1885.83161148 1.0 27492000 68.8401 30.0157%
54982 2016-03-22 23:28:46 2 15500.0100089 1.0 27491500 68.8261 30.041%
54981 2016-03-22 23:08:36 3 2479.20837787 1.0 27491000 68.8121 30.0321%
54983 2016-03-22 23:48:57 3 1885.83161148 1.0 27492000 68.8401 30.0157%
54982 2016-03-22 23:28:46 2 15500.0100089 1.0 27491500 68.8261 30.041%
54981 2016-03-22 23:08:36 3 2479.20837787 1.0 27491000 68.8121 30.0321%
they arent going to an "attacker" you baffoon lol they are going to the c-bit pool that has the most hashpower
edit: and they are 1 diff because they are 20 minutes apart and there needs to be 6 per hour haha what an idiot
edit edit: they went to the "Foxtrot" pool http://foxtrot.btc-bit.com/stats
lmao you are acting like there is a conspiracy here and its hilarious.
ok wiseguy show us wheres the outgoing transactions from this gimmick "pool" ===> http://cryptobe.com/address/1Qk3HDZgr9fh5NR6wasdX2FTexLKnzF2j
are you blind?
Transactions in: 9488
Received: 4649120.39247834 XCT
Transactions out: 9448
Sent: 4629520.38077819 XCT
learn how to read a blockchain, then come back.
March 22, 2016, 08:56:57 PM
look noob ===vvv all the 1.O diff blocks go to the attacker ! ~ pfft you guys need another hint?
54983 2016-03-22 23:48:57 3 1885.83161148 1.0 27492000 68.8401 30.0157%
54982 2016-03-22 23:28:46 2 15500.0100089 1.0 27491500 68.8261 30.041%
54981 2016-03-22 23:08:36 3 2479.20837787 1.0 27491000 68.8121 30.0321%
54983 2016-03-22 23:48:57 3 1885.83161148 1.0 27492000 68.8401 30.0157%
54982 2016-03-22 23:28:46 2 15500.0100089 1.0 27491500 68.8261 30.041%
54981 2016-03-22 23:08:36 3 2479.20837787 1.0 27491000 68.8121 30.0321%
they arent going to an "attacker" you baffoon lol they are going to the c-bit pool that has the most hashpower
edit: and they are 1 diff because they are 20 minutes apart and there needs to be 6 per hour haha what an idiot
edit edit: they went to the "Foxtrot" pool http://foxtrot.btc-bit.com/stats
lmao you are acting like there is a conspiracy here and its hilarious.
ok wiseguy show us wheres the outgoing transactions from this gimmick "pool" ===> http://cryptobe.com/address/1Qk3HDZgr9fh5NR6wasdX2FTexLKnzF2j
March 22, 2016, 08:43:19 PM
look noob ===vvv all the 1.O diff blocks go to the attacker ! ~ pfft you guys need another hint?
54983 2016-03-22 23:48:57 3 1885.83161148 1.0 27492000 68.8401 30.0157%
54982 2016-03-22 23:28:46 2 15500.0100089 1.0 27491500 68.8261 30.041%
54981 2016-03-22 23:08:36 3 2479.20837787 1.0 27491000 68.8121 30.0321%
54983 2016-03-22 23:48:57 3 1885.83161148 1.0 27492000 68.8401 30.0157%
54982 2016-03-22 23:28:46 2 15500.0100089 1.0 27491500 68.8261 30.041%
54981 2016-03-22 23:08:36 3 2479.20837787 1.0 27491000 68.8121 30.0321%
they arent going to an "attacker" you baffoon lol they are going to the c-bit pool that has the most hashpower
edit: and they are 1 diff because they are 20 minutes apart and there needs to be 6 per hour haha what an idiot
edit edit: they went to the "Foxtrot" pool http://foxtrot.btc-bit.com/stats
lmao you are acting like there is a conspiracy here and its hilarious.
March 22, 2016, 08:15:05 PM
what are you guys trying to figure out? it's all pretty clear. there is no mystery here.
someone went on the network with a few ph/s (they've already admitted that here in the thread, also that is alot larger than a 51% attack, its more like a 500% attack)
luckily, they were noobs and mined on low difficulty ports on the c-bit official pools, and it crashed the unomp stratum due to being overwhelmed with shares.
this caused the difficulty to drop since there was alot less hashpower after.
there's about 40th/s on the network right now. the difficulty is climbing back up/adjusting, and its over 9 million. there are 6 blocks being made per hour. a block releases at a difficulty of 1 when it takes too long and gets close to being only 5 blocks in an hour. this is standard in both bitcoin and c-bit, as well as many other coins with a bitcoin codebase.
i don't know why anyone is confused about this.
if you increased the network hashrate by 500% on the bitcoin network, the same thing would happen, but instead of it costing a few thousand dollars, it would cost hundreds of millions. (estimated, i dont feel like doing the math)
the only solution to prevent this from happening again, would be to put more steady hashpower on the network, and/or change the retarget from 2016 blocks (2 weeks) like bitcoin, to something much lower, like a few hours.
as far as what you guys should do with the millions stuck in the pool, that is up to you. personally i would burn it, by sending it to an address that doesnt exist, like 1cbitBURN212h12kjl312jk3jk or something. i certainly wouldnt reward the idiot that did this. i'd assume it was malicious. i can dig up his info and post it here in the thread if thats what the community/devs want.
if anyone needs help, feel free to contact me.
someone went on the network with a few ph/s (they've already admitted that here in the thread, also that is alot larger than a 51% attack, its more like a 500% attack)
luckily, they were noobs and mined on low difficulty ports on the c-bit official pools, and it crashed the unomp stratum due to being overwhelmed with shares.
this caused the difficulty to drop since there was alot less hashpower after.
there's about 40th/s on the network right now. the difficulty is climbing back up/adjusting, and its over 9 million. there are 6 blocks being made per hour. a block releases at a difficulty of 1 when it takes too long and gets close to being only 5 blocks in an hour. this is standard in both bitcoin and c-bit, as well as many other coins with a bitcoin codebase.
i don't know why anyone is confused about this.
if you increased the network hashrate by 500% on the bitcoin network, the same thing would happen, but instead of it costing a few thousand dollars, it would cost hundreds of millions. (estimated, i dont feel like doing the math)
the only solution to prevent this from happening again, would be to put more steady hashpower on the network, and/or change the retarget from 2016 blocks (2 weeks) like bitcoin, to something much lower, like a few hours.
as far as what you guys should do with the millions stuck in the pool, that is up to you. personally i would burn it, by sending it to an address that doesnt exist, like 1cbitBURN212h12kjl312jk3jk or something. i certainly wouldnt reward the idiot that did this. i'd assume it was malicious. i can dig up his info and post it here in the thread if thats what the community/devs want.
if anyone needs help, feel free to contact me.
look noob ===vvv all the 1.O diff blocks go to the attacker ! ~ pfft you guys need another hint?
54983 2016-03-22 23:48:57 3 1885.83161148 1.0 27492000 68.8401 30.0157%
54982 2016-03-22 23:28:46 2 15500.0100089 1.0 27491500 68.8261 30.041%
54981 2016-03-22 23:08:36 3 2479.20837787 1.0 27491000 68.8121 30.0321%
March 22, 2016, 07:04:39 PM
what are you guys trying to figure out? it's all pretty clear. there is no mystery here.
someone went on the network with a few ph/s (they've already admitted that here in the thread, also that is alot larger than a 51% attack, its more like a 500% attack)
luckily, they were noobs and mined on low difficulty ports on the c-bit official pools, and it crashed the unomp stratum due to being overwhelmed with shares.
this caused the difficulty to drop since there was alot less hashpower after.
there's about 40th/s on the network right now. the difficulty is climbing back up/adjusting, and its over 9 million. there are 6 blocks being made per hour. a block releases at a difficulty of 1 when it takes too long and gets close to being only 5 blocks in an hour. this is standard in both bitcoin and c-bit, as well as many other coins with a bitcoin codebase.
i don't know why anyone is confused about this.
if you increased the network hashrate by 500% on the bitcoin network, the same thing would happen, but instead of it costing a few thousand dollars, it would cost hundreds of millions. (estimated, i dont feel like doing the math)
the only solution to prevent this from happening again, would be to put more steady hashpower on the network, and/or change the retarget from 2016 blocks (2 weeks) like bitcoin, to something much lower, like a few hours.
as far as what you guys should do with the millions stuck in the pool, that is up to you. personally i would burn it, by sending it to an address that doesnt exist, like 1cbitBURN212h12kjl312jk3jk or something. i certainly wouldnt reward the idiot that did this. i'd assume it was malicious. i can dig up his info and post it here in the thread if thats what the community/devs want.
if anyone needs help, feel free to contact me.
someone went on the network with a few ph/s (they've already admitted that here in the thread, also that is alot larger than a 51% attack, its more like a 500% attack)
luckily, they were noobs and mined on low difficulty ports on the c-bit official pools, and it crashed the unomp stratum due to being overwhelmed with shares.
this caused the difficulty to drop since there was alot less hashpower after.
there's about 40th/s on the network right now. the difficulty is climbing back up/adjusting, and its over 9 million. there are 6 blocks being made per hour. a block releases at a difficulty of 1 when it takes too long and gets close to being only 5 blocks in an hour. this is standard in both bitcoin and c-bit, as well as many other coins with a bitcoin codebase.
i don't know why anyone is confused about this.
if you increased the network hashrate by 500% on the bitcoin network, the same thing would happen, but instead of it costing a few thousand dollars, it would cost hundreds of millions. (estimated, i dont feel like doing the math)
the only solution to prevent this from happening again, would be to put more steady hashpower on the network, and/or change the retarget from 2016 blocks (2 weeks) like bitcoin, to something much lower, like a few hours.
as far as what you guys should do with the millions stuck in the pool, that is up to you. personally i would burn it, by sending it to an address that doesnt exist, like 1cbitBURN212h12kjl312jk3jk or something. i certainly wouldnt reward the idiot that did this. i'd assume it was malicious. i can dig up his info and post it here in the thread if thats what the community/devs want.
if anyone needs help, feel free to contact me.
I think the idea of setting the complexity to adjust every few hours until our hashing power is built up and the complexity is consistantly staying up is a good idea. I am ot sure it would stop a 51% attack, but might make it less sucesfull for the attackers. I am not sure there is anyway fro prevent a 51% attack as long as we are small and new.
Mtnminer
March 22, 2016, 06:58:02 PM
what are you guys trying to figure out? it's all pretty clear. there is no mystery here.
someone went on the network with a few ph/s (they've already admitted that here in the thread, also that is alot larger than a 51% attack, its more like a 500% attack)
luckily, they were noobs and mined on low difficulty ports on the c-bit official pools, and it crashed the unomp stratum due to being overwhelmed with shares.
this caused the difficulty to drop since there was alot less hashpower after.
there's about 40th/s on the network right now. the difficulty is climbing back up/adjusting, and its over 9 million. there are 6 blocks being made per hour. a block releases at a difficulty of 1 when it takes too long and gets close to being only 5 blocks in an hour. this is standard in both bitcoin and c-bit, as well as many other coins with a bitcoin codebase.
i don't know why anyone is confused about this.
if you increased the network hashrate by 2000% on the bitcoin network, the same thing would happen, but instead of it costing a few thousand dollars, it would cost hundreds of millions. (estimated, i dont feel like doing the math)
the only solution to prevent this from happening again, would be to put more steady hashpower on the network, and/or change the retarget from 2016 blocks (2 weeks) like bitcoin, to something much lower, like a few hours.
as far as what you guys should do with the millions stuck in the pool, that is up to you. personally i would burn it, by sending it to an address that doesnt exist, like 1cbitBURN212h12kjl312jk3jk or something. i certainly wouldnt reward the idiot that did this. i'd assume it was malicious. i can dig up his info and post it here in the thread if thats what the community/devs want.
if anyone needs help, feel free to contact me.
someone went on the network with a few ph/s (they've already admitted that here in the thread, also that is alot larger than a 51% attack, its more like a 500% attack)
luckily, they were noobs and mined on low difficulty ports on the c-bit official pools, and it crashed the unomp stratum due to being overwhelmed with shares.
this caused the difficulty to drop since there was alot less hashpower after.
there's about 40th/s on the network right now. the difficulty is climbing back up/adjusting, and its over 9 million. there are 6 blocks being made per hour. a block releases at a difficulty of 1 when it takes too long and gets close to being only 5 blocks in an hour. this is standard in both bitcoin and c-bit, as well as many other coins with a bitcoin codebase.
i don't know why anyone is confused about this.
if you increased the network hashrate by 2000% on the bitcoin network, the same thing would happen, but instead of it costing a few thousand dollars, it would cost hundreds of millions. (estimated, i dont feel like doing the math)
the only solution to prevent this from happening again, would be to put more steady hashpower on the network, and/or change the retarget from 2016 blocks (2 weeks) like bitcoin, to something much lower, like a few hours.
as far as what you guys should do with the millions stuck in the pool, that is up to you. personally i would burn it, by sending it to an address that doesnt exist, like 1cbitBURN212h12kjl312jk3jk or something. i certainly wouldnt reward the idiot that did this. i'd assume it was malicious. i can dig up his info and post it here in the thread if thats what the community/devs want.
if anyone needs help, feel free to contact me.
Let me be the first to say this..
Sunerok just --
The shit out of you idiots.
Burn the damn coins because clearly no one in this thread (besides maybe a couple of us) are deserving of them - Let's move on from this incident.
Cheers-
March 22, 2016, 06:44:38 PM
what are you guys trying to figure out? it's all pretty clear. there is no mystery here.
someone went on the network with a few ph/s (they've already admitted that here in the thread, also that is alot larger than a 51% attack, its more like a 500% attack)
luckily, they were noobs and mined on low difficulty ports on the c-bit official pools, and it crashed the unomp stratum due to being overwhelmed with shares.
this caused the difficulty to drop since there was alot less hashpower after.
there's about 40th/s on the network right now. the difficulty is climbing back up/adjusting, and its over 9 million. there are 6 blocks being made per hour. a block releases at a difficulty of 1 when it takes too long and gets close to being only 5 blocks in an hour. this is standard in both bitcoin and c-bit, as well as many other coins with a bitcoin codebase.
i don't know why anyone is confused about this.
if you increased the network hashrate by 500% on the bitcoin network, the same thing would happen, but instead of it costing a few thousand dollars, it would cost hundreds of millions. (estimated, i dont feel like doing the math)
the only solution to prevent this from happening again, would be to put more steady hashpower on the network, and/or change the retarget from 2016 blocks (2 weeks) like bitcoin, to something much lower, like a few hours.
as far as what you guys should do with the millions stuck in the pool, that is up to you. personally i would burn it, by sending it to an address that doesnt exist, like 1cbitBURN212h12kjl312jk3jk or something. i certainly wouldnt reward the idiot that did this. i'd assume it was malicious. i can dig up his info and post it here in the thread if thats what the community/devs want.
if anyone needs help, feel free to contact me.
someone went on the network with a few ph/s (they've already admitted that here in the thread, also that is alot larger than a 51% attack, its more like a 500% attack)
luckily, they were noobs and mined on low difficulty ports on the c-bit official pools, and it crashed the unomp stratum due to being overwhelmed with shares.
this caused the difficulty to drop since there was alot less hashpower after.
there's about 40th/s on the network right now. the difficulty is climbing back up/adjusting, and its over 9 million. there are 6 blocks being made per hour. a block releases at a difficulty of 1 when it takes too long and gets close to being only 5 blocks in an hour. this is standard in both bitcoin and c-bit, as well as many other coins with a bitcoin codebase.
i don't know why anyone is confused about this.
if you increased the network hashrate by 500% on the bitcoin network, the same thing would happen, but instead of it costing a few thousand dollars, it would cost hundreds of millions. (estimated, i dont feel like doing the math)
the only solution to prevent this from happening again, would be to put more steady hashpower on the network, and/or change the retarget from 2016 blocks (2 weeks) like bitcoin, to something much lower, like a few hours.
as far as what you guys should do with the millions stuck in the pool, that is up to you. personally i would burn it, by sending it to an address that doesnt exist, like 1cbitBURN212h12kjl312jk3jk or something. i certainly wouldnt reward the idiot that did this. i'd assume it was malicious. i can dig up his info and post it here in the thread if thats what the community/devs want.
if anyone needs help, feel free to contact me.
March 22, 2016, 06:14:11 PM
Smell of a new chain 
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
just pay everyone out from the pools! lol ~ simple
dump i will buy all of them
i can tell you who i think is minting many coins right now...
hodl XCT who is who
looks like we got it figured out...i'll have more clues soon
~hashing away zzz 
March 22, 2016, 05:03:42 PM
Smell of a new chain
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
just pay everyone out from the pools! lol ~ simple
dump i will buy all of them
i can tell you who i think is minting many coins right now...
hodl XCT who is who
March 22, 2016, 04:59:11 PM
Smell of a new chain
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
just pay everyone out from the pools! lol ~ simple
dump i will buy all of them
i can tell you who i think is minting many coins right now...
hodl XCT March 22, 2016, 04:54:13 PM
Smell of a new chain
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
just pay everyone out from the pools! lol ~ simple
dump i will buy all of them
March 22, 2016, 04:52:36 PM
Smell of a new chain
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
just pay everyone out from the pools! lol ~ simple
dump i will buy all of them
March 22, 2016, 04:51:55 PM
Smell of a new chain
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
just pay everyone out from the pools! lol ~ simple
March 22, 2016, 04:49:53 PM
Smell of a new chain
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
just pay everyone out from the pools! lol ~ simple
March 22, 2016, 04:48:51 PM
Smell of a new chain
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
March 22, 2016, 04:44:27 PM
Smell of a new chain
nope just a more well distributed coin!
~ we are all good !
POWER IN NUMBERS!!!!
March 22, 2016, 04:36:14 PM
Smell of a new chain
March 22, 2016, 04:20:54 PM
@gembitz So if the attack was a time stamp one and not 51% we can say that toronto held coins must be released because it was no attacker there.
Another thing is,watching the block explorer we can say that the attack is not over yet as there are always 1diff blocks generated again and again and if it not will stop,diff will return to 1 one more time
Another thing is,watching the block explorer we can say that the attack is not over yet as there are always 1diff blocks generated again and again and if it not will stop,diff will return to 1 one more time
the said [ 51% / timewarp ] is obvious ~ just look @ those 1.0 diff blocks ...stay tuned
actually that quote gembitz posted is from 2011 lmao
the difficulty went down and then someone mined with a 1+ ph/s rig. there was no timewarp, just a 500% attack.. i looked at the source code, its identical to the newest bitcoin source code. what happened here could happen to bitcoin, if enough hashpower hit it. from what i read, farms do shut off before difficulty retarget and then turn back on when it switches if its lower. 1 difficulty blocks are to make sure that at least 6 blocks get released per hour. if there are only 5 and an hour approaches, a block with a difficulty of 1 is released. :yawn:
fool look at these blocks (diff = 1.0 )===>
54950 2016-03-22 17:01:46 2 990 1.0 27475500 68.5573 30.4018%
54949 2016-03-22 16:41:34 2 990 1.0 27475000 68.5433 30.4289%
54948 2016-03-22 16:21:23 2 990.01024709 1.0 27474500 68.5293 30.4561%
per : http://cryptobe.com/chain/CBit
====================
what else do you call this?>>> could it be a classic timewarp type attack ...hmmm ?
you must not have read what i typed/you quoted. the network makes 6 blocks per hour. if it has not done that, and it gets past ten minutes, it makes a block with a difficulty of 1. rofl, definitely not a time warp.
see, after block 54948, 20 minutes had gone by, so it released a block with a difficulty of 1. then, at that block, another 20 minutes had gone by, so another block with a difficulty of 1 was released. this is to ensure that 6 blocks are released per hour. its standard per bitcoins 6 blocks per hour rule.
March 22, 2016, 04:06:55 PM
Jump to: