Topic: [OLD][CSC]CasinoCoin ♠ A Digital Currency For The Regulated Online Gaming Sector - page 19. (Read 343087 times)
July 16, 2017, 04:30:49 AM
I might be able to contribute a steady 100MH mining power. If we get more mining power this could certainly help protection.
July 15, 2017, 09:58:58 PM
Why not roll the coin over to a platform like Waves or another blockchain that offers child/side chains so you draw from the strength and security of the network? That's what other scrypt coins are doing that don't have enough hash to protect against a 51% attack.
New blockchain tech has come out in the 4 years since CSC was created so why not utilize it? Make CSC an ERC20 token with an ICO and allow existing holders the ability to swap coins. Create some kind of mobile app that allows people to use CSC in personal settings like card games or "other enterprises".
I hold 16k CSC and at this time and I find it hard to believe that CSC would be able to beat out other casino focused coins given all the ICO hype right now; especially given this 51% attack now. Chances are you haven't heard from more affected users as they've either forgot about the coins they held or the current price isn't worth the hassle.
I feel like someone screaming I will never get rid of my tube black and white tv (CSC), meanwhile flat screen tvs exist with color picture with better tech. Imagine a CSC smart contract where people can create their own betting pool that auto-payouts depending on a given end result. For instance a pool of who was going to win the US election; Trump or Hilary. People use their mobile app to pay the smart contract and get paid out once results are in. Also ensures the person can't run away with everyone's coins. That's just one idea....So much potential in CSC; just needs to be tapped.
New blockchain tech has come out in the 4 years since CSC was created so why not utilize it? Make CSC an ERC20 token with an ICO and allow existing holders the ability to swap coins. Create some kind of mobile app that allows people to use CSC in personal settings like card games or "other enterprises".
I hold 16k CSC and at this time and I find it hard to believe that CSC would be able to beat out other casino focused coins given all the ICO hype right now; especially given this 51% attack now. Chances are you haven't heard from more affected users as they've either forgot about the coins they held or the current price isn't worth the hassle.
I feel like someone screaming I will never get rid of my tube black and white tv (CSC), meanwhile flat screen tvs exist with color picture with better tech. Imagine a CSC smart contract where people can create their own betting pool that auto-payouts depending on a given end result. For instance a pool of who was going to win the US election; Trump or Hilary. People use their mobile app to pay the smart contract and get paid out once results are in. Also ensures the person can't run away with everyone's coins. That's just one idea....So much potential in CSC; just needs to be tapped.
I like your ideas smokingman. Casinocoin has really great potentials. We need to learn from this experience and make improvements on the coin.
July 15, 2017, 09:36:38 AM
Why not roll the coin over to a platform like Waves or another blockchain that offers child/side chains so you draw from the strength and security of the network? That's what other scrypt coins are doing that don't have enough hash to protect against a 51% attack.
New blockchain tech has come out in the 4 years since CSC was created so why not utilize it? Make CSC an ERC20 token with an ICO and allow existing holders the ability to swap coins. Create some kind of mobile app that allows people to use CSC in personal settings like card games or "other enterprises".
I hold 16k CSC and at this time and I find it hard to believe that CSC would be able to beat out other casino focused coins given all the ICO hype right now; especially given this 51% attack now. Chances are you haven't heard from more affected users as they've either forgot about the coins they held or the current price isn't worth the hassle.
I feel like someone screaming I will never get rid of my tube black and white tv (CSC), meanwhile flat screen tvs exist with color picture with better tech. Imagine a CSC smart contract where people can create their own betting pool that auto-payouts depending on a given end result. For instance a pool of who was going to win the US election; Trump or Hilary. People use their mobile app to pay the smart contract and get paid out once results are in. Also ensures the person can't run away with everyone's coins. That's just one idea....So much potential in CSC; just needs to be tapped.
New blockchain tech has come out in the 4 years since CSC was created so why not utilize it? Make CSC an ERC20 token with an ICO and allow existing holders the ability to swap coins. Create some kind of mobile app that allows people to use CSC in personal settings like card games or "other enterprises".
I hold 16k CSC and at this time and I find it hard to believe that CSC would be able to beat out other casino focused coins given all the ICO hype right now; especially given this 51% attack now. Chances are you haven't heard from more affected users as they've either forgot about the coins they held or the current price isn't worth the hassle.
I feel like someone screaming I will never get rid of my tube black and white tv (CSC), meanwhile flat screen tvs exist with color picture with better tech. Imagine a CSC smart contract where people can create their own betting pool that auto-payouts depending on a given end result. For instance a pool of who was going to win the US election; Trump or Hilary. People use their mobile app to pay the smart contract and get paid out once results are in. Also ensures the person can't run away with everyone's coins. That's just one idea....So much potential in CSC; just needs to be tapped.
July 14, 2017, 05:04:54 AM
What I do not understand is: Even if the 51% attack had been fully successful, how did the attackers think they will be able to liquidate 9.7m CSC? Surely, their objective must have been to illicitly gain the CSC and then sell them for BTC and walk away with the BTC. Given the historic market depth, that seems nigh on impossible without crashing the price to zero.
So, something is fishy here. Why would an attacker go to such lengths only to end up, even in the best case scenario, with 9.7m CSC that are practically unsalable?
Unless of course the attackers were insiders and had other motives, such as taking over a large part of the coin supply.
Don't speak without knowledge of the subject, ... if there is any insider it would be Cryptopia themselves as they required the CSC dev team to deposit 9,7 mln coins or they would delist CSC. We offered to look into replacing the involved users BTC instead of CSC as we do not have any reserve CSC available as CSC does not have a premine. Cryptopia refused that so they are at fault here and i do not react very well to threats! Until now only 1,8 mln coins have been reported missing by users so i wonder where the other 8 mln is??
All malicious transactions are rolled back on the blockchain within acceptable timeframes and could take place because Cryptopia had only 6 confirms on deposits and works only on their own internal DB instead of verifying against the blockchain. The attacker got users BTC and run off. To stop all speculation you can find all transactions below with their rollbacks from a primary CSC seed, ... you can check that in your own debug.log if you run your own full-time online CSC node:
Code:
CSC 400000.00000000 0bb3f971f28abe5ba49939e0c6ce8be88e832d9b740cf190d79bd6d43fb0417e 2017-06-20 21:10:17.0000000
CSC 400000.00000000 586abaa47ad566c53f62906605f7a7b426db1adcba7d6f9674117072b6153592 2017-06-20 20:07:13.0000000
CSC 400000.00000000 b502469d3014ec5ea4f71f53fd21b1a2b51382057401bae7a204380ffbdcc389 2017-06-20 19:29:04.0000000
CSC 400000.00000000 d753e7e1aa4806f289613e667637f7258e293c484d35ae4bd2577a94d66dc0c5 2017-06-19 21:54:56.0000000
CSC 400000.00000000 cf37242d44d6180c7898b04eb8251c1b66ab834cf594c428867c2f8962af4b27 2017-06-18 21:17:20.0000000
CSC 400000.00000000 bd61179254d51ab1b8940d36c82498510c996df202b8450a47f02af937288b55 2017-06-18 20:45:35.0000000
CSC 400000.00000000 b3ab695db31388ce96f0bba4f151b0f25d6787aea097145950901f069a03dc71 2017-06-18 20:08:37.0000000
CSC 400000.00000000 074cfdac8066841a91a0dd335d4b4f5f4c4b437b3f78e7b6172c8546ff51cdf9 2017-06-18 19:49:40.0000000
CSC 400000.00000000 2b4f8a511437fcb1582c3dc89434cd5624bf4e2c8a0a629e261853ea0d7a2d1e 2017-06-17 13:22:09.0000000
CSC 400000.00000000 b065895f157fc6d237ae4bd8b8b5ad3dca934510b9f70e7bb7450dff31f37cc0 2017-06-17 12:40:31.0000000
CSC 400000.00000000 0fb78c9ac533c064943cd90ed807a759c88ffcca18783f920185b57986bab1c5 2017-06-17 12:01:38.0000000
CSC 400000.00000000 8ce954b43bdb369cd2d1e5849941a279691c7647a3af23ef191555ac6d79a05b 2017-06-17 11:19:30.0000000
CSC 400000.00000000 54f496ada83fa08f765e5d08c518c52319f8f546b3d6a08656be14011b87a578 2017-06-17 10:12:34.0000000
CSC 400000.00000000 2a56334a520da44473a94bc061f08b8ece28be781dceac92bd2c503a94d58378 2017-06-17 09:38:46.0000000
CSC 400000.00000000 b2e4390d91701bfbf4498bd612ba7ef6bdafd69d5df4cf2b4e8a51a5f79147b1 2017-06-17 09:09:07.0000000
CSC 400000.00000000 b3f5139a27e888056d7d61ac2478788ca57e699405748e162e673a9def5105a8 2017-06-16 23:14:47.0000000
CSC 400000.00000000 e87014dc9fc3fedcb25a07c0cfdab1da1ee180e62bac5c94dac5303732aafefa 2017-06-16 22:36:02.0000000
CSC 400000.00000000 55361dee7277e0341968a4eefcf40f668fc5e0edcfbab09113eb983d7c8bcadb 2017-06-16 21:48:54.0000000
CSC 400000.00000000 381faf0ebcf7e16ca2c18b82c51e8851e3d08b8c9ffab94dc62b7364e3e5d1f2 2017-06-16 21:07:49.0000000
CSC 400000.00000000 807723365f7a410b7ca67c1d7cf9abca4c1af248a0b71bdb725b20a2558dcd93 2017-06-16 20:05:58.0000000
CSC 200000.00000000 6860fc113e0c01b6fafc1535bd97520647fa2cb885d55565d703d5a4caf67519 2017-06-16 19:26:11.0000000
CSC 200000.00000000 10dfe009eeaf619d59e3c4e18c48d4f06bbba5a47b0802ceb0d85928f61d4f6e 2017-06-16 18:48:18.0000000
CSC 114000.00000000 86950fb41cde845ad39a7d4d093ff1b3b4bc3063303897b7ea5f3a901c2c44ff 2017-06-16 17:50:17.0000000
CSC 114000.00000000 f45405d4ca53252eb653b175177f1b8eaac5a01011a86a748c07b2f5d3706bcd 2017-06-16 13:29:49.0000000
CSC 114000.00000000 d3e89ea4b0a4286689a26929ea27a725495353bfd9bb5fcc9a53c597399999ef 2017-06-16 12:43:06.0000000
CSC 114000.00000000 c7b1c1b37597154af07d8189ca513cada4f51363ecc0d792f6e5780ac800caed 2017-06-16 11:46:02.0000000
CSC 114000.00000000 d8913bb321fe50e84b18e8c2a41ff8a2edd9f6f7b2fe6f88ca2738cb0d999d74 2017-06-16 09:21:35.0000000
CSC 114000.00000000 541a44b2b1e526157f13089159afa6aa97ce558211f83a9c5558c97fa792cd48 2017-06-16 08:49:37.0000000
CSC 57000.00000000 25a7e7f0c2f72869626bea52e10826176383a50ccdcdb8d12a14321de664465d 2017-06-15 22:38:51.0000000
CSC 57000.00000000 47c6a397bcab18e77ff99c8ad2bb7dda2013d0f7612401a2984728165e808b3e 2017-06-15 22:13:04.0000000
CSC 74500.00000000 6e64724ee5daedbbcd98da3af36cfd09332864b17350028919f21ea5f00bfcd6 2017-06-13 19:34:01.0000000
CSC 75000.00000000 41da631b9579141ee8fe2137b247a9b2aad3acbd10b47b63ece628f97a7a06c1 2017-06-13 17:50:10.0000000
CSC 75000.00000000 3e25e78f64ff80840b37d2a4154a2a3d3b4c26c00895e0fcd652daea8abdebcd 2017-06-13 16:56:41.0000000
CSC 75000.00000000 1c6edddab9b4a0d442c36f50adb1f9b3c459b8fd2b49944db7f39f69a048b67a 2017-06-13 16:20:30.0000000
CSC 75000.00000000 e438a555dcc6a788c4d51814ac02c21bcd9b3d6e130726222d9fca3f9dcc6359 2017-06-13 15:27:23.0000000
CSC 76000.00000000 0c406c2016e7418f2e96884898671bacad20590bd30e5617d17bee4903a4968c 2017-06-13 14:55:02.0000000
CSC 38300.00000000 2634f0879c67e6618dddbefbffbd72db8566ae26b593e4aa3d68393529f3f740 2017-06-13 14:16:18.0000000
CSC 38300.00000000 dae189c8827078fcf75881ba105d1b398560329e5a7d4ef19b7046ba2380f41f 2017-06-12 21:10:11.0000000
CSC 38300.00000000 8c11ea0658c486b994586032d1bc7af543a6da973f98d867f1ff0b40beed9864 2017-06-12 13:51:31.0000000
CSC 38300.00000000 2da41a8cf1b483a2095f99c2bea75ca144129d8aff070a8306a85daad42def99 2017-06-12 13:28:29.0000000
CSC 19200.00000000 36f86626caa3acdf6b04d9590e881288121d2ab46a3643374cd897f872256739 2017-06-12 09:42:14.0000000
CSC 400000.00000000 807723365f7a410b7ca67c1d7cf9abca4c1af248a0b71bdb725b20a2558dcd93 2017-06-16 20:05:58.0000000 -> Block c0fd5937e445d2dbf94150f2fc4f3601ab0a69e894aaaaccecc49d007e1e300e
height -> 2031736
2017-06-16 20:09:19 received block c0fd5937e445d2dbf94150f2fc4f3601ab0a69e894aaaaccecc49d007e1e300e
2017-06-16 21:03:18 REORGANIZE: Disconnect 65 blocks; edd1c7cac77a5cee78294446938f6d3714207d92dc0df4c03406f2ec1eb015cf..
2017-06-16 21:03:18 REORGANIZE: Connect 17 blocks; ..b1bae61557ba1d9adb9e0a3837e938a03d2a8cbf859da77568deaacaad4fab55
CSC 400000.00000000 381faf0ebcf7e16ca2c18b82c51e8851e3d08b8c9ffab94dc62b7364e3e5d1f2 2017-06-16 21:07:49.0000000 -> Block 407fbc1b09f52df2a01d400fa0ba0dfa312368c8e9b3db4f6bed24758973f8c5
height -> 2031788
2017-06-16 21:08:53 received block 407fbc1b09f52df2a01d400fa0ba0dfa312368c8e9b3db4f6bed24758973f8c5
2017-06-16 21:46:52 REORGANIZE: Disconnect 34 blocks; e3d4829859dd6601bd3773d92ef95c2d0760fa09acb649f0119729f4dd494b5a..
2017-06-16 21:46:52 REORGANIZE: Connect 16 blocks; ..d9402d7e4c456aff7f8c104d80db054c5f799fcb8dbd3cfc7f365211247fc6bd
CSC 400000.00000000 55361dee7277e0341968a4eefcf40f668fc5e0edcfbab09113eb983d7c8bcadb 2017-06-16 21:48:54.0000000 -> Block ca2429d56c40b85fd8679340e10e84c2e38335b43a5ce55e3ff4c051129df729
height -> 2031827
2017-06-16 21:52:39 received block ca2429d56c40b85fd8679340e10e84c2e38335b43a5ce55e3ff4c051129df729
2017-06-16 22:32:16 REORGANIZE: Disconnect 29 blocks; 928ee46d1506cf7fd6e1f09ee57bed6d633e61ee6670f9a40ee2e4672181590d..
2017-06-16 22:32:16 REORGANIZE: Connect 21 blocks; ..70971b3ea24465c4160bd40bfe34ed2256978b9f49fe2dab68d11cc26827a22d
CSC 400000.00000000 e87014dc9fc3fedcb25a07c0cfdab1da1ee180e62bac5c94dac5303732aafefa 2017-06-16 22:36:02.0000000 -> Block bbb52f7d47b422fdb0529c1cfa217d100071721b421d15c9b4d2da8814d987b1
height -> 2031891
2017-06-16 22:41:34 received block bbb52f7d47b422fdb0529c1cfa217d100071721b421d15c9b4d2da8814d987b1
2017-06-16 23:12:39 REORGANIZE: Disconnect 40 blocks; ad9b80025dbd2ca27262769a8272588cec092155da433bba06f810dda0d89d7c..
2017-06-16 23:12:39 REORGANIZE: Connect 33 blocks; ..8ed38ca4bf218073da7e43755171e2d8babcd5bdd68b648381c3f1f5d333e332
CSC 400000.00000000 b3f5139a27e888056d7d61ac2478788ca57e699405748e162e673a9def5105a8 2017-06-16 23:14:47.0000000 -> Block feaf6739256550922ed490dc9760c2d5020b0239a4aedde4a178ae9314350366
height -> 2031939
2017-06-16 23:17:30 received block feaf6739256550922ed490dc9760c2d5020b0239a4aedde4a178ae9314350366
2017-06-16 23:51:37 REORGANIZE: Disconnect 55 blocks; 5d0d63667a40172f94327c4ff7d505f19e21c5d0d4e61ebaf379245fca3ab368..
2017-06-16 23:51:37 REORGANIZE: Connect 17 blocks; ..6a3e799c28c3930aadf4286003d55bab0498c1de53ad37baa7b368b03bcf7cd5
CSC 400000.00000000 b2e4390d91701bfbf4498bd612ba7ef6bdafd69d5df4cf2b4e8a51a5f79147b1 2017-06-17 09:09:07.0000000 -> Block 61dcf1a6ee3bcd262fc828d2faf2efd501a7fa1698742348f7a0e32e824056b6
height -> 2032834
2017-06-17 09:09:29 received block 61dcf1a6ee3bcd262fc828d2faf2efd501a7fa1698742348f7a0e32e824056b6
2017-06-17 09:37:38 REORGANIZE: Disconnect 57 blocks; 1b3486ea5edfbab640b4a0e81ee852db8424bbe34c15bb0bcf11ec465d9a7d10..
2017-06-17 09:37:38 REORGANIZE: Connect 22 blocks; ..96ab5bd0178beb78c8ceb312cc4fa0656480a3c64a8e04ddbcc9ccee48b93183
CSC 400000.00000000 2a56334a520da44473a94bc061f08b8ece28be781dceac92bd2c503a94d58378 2017-06-17 09:38:46.0000000 -> Block 657ff4b684c6dbd5c19ec953b3778aa76921b1d23cb7c6ec8cf3d1ee16c8171b
height -> 2032866
2017-06-17 09:40:37 received block 657ff4b684c6dbd5c19ec953b3778aa76921b1d23cb7c6ec8cf3d1ee16c8171b
2017-06-17 10:08:38 REORGANIZE: Disconnect 41 blocks; 2f4128e0c9d6823aaba5508500bdb67804762630953d87bbac3904bec7e8c6f4..
2017-06-17 10:08:38 REORGANIZE: Connect 19 blocks; ..6f5e190d6d2225c27b6beef2b0150bf5bfd7dc5f85ee00bc8cf57f2d83e38d17
CSC 400000.00000000 54f496ada83fa08f765e5d08c518c52319f8f546b3d6a08656be14011b87a578 2017-06-17 10:12:34.0000000 -> Block f3a29257327f6441308ac85603e6669909222f065971a571edf07e35432c8730
height -> 2032900
2017-06-17 10:15:20 received block f3a29257327f6441308ac85603e6669909222f065971a571edf07e35432c8730
2017-06-17 11:17:17 REORGANIZE: Disconnect 98 blocks; 7235a637c3913a39035814818cf8670b9c4c1a57bffdd54180b9eee54a66d933..
2017-06-17 11:17:17 REORGANIZE: Connect 36 blocks; ..d0ed7def0d6686d5edbe2924813f8cb4fdf04ac739ac9c1b77d880b61b10b45f
CSC 400000.00000000 8ce954b43bdb369cd2d1e5849941a279691c7647a3af23ef191555ac6d79a05b 2017-06-17 11:19:30.0000000 -> Block b435b80f7c27a743576b172f80bbf55bd8d81c78e5d43c8d34ff83add9a6f504
height -> 2032993
2017-06-17 11:20:37 received block b435b80f7c27a743576b172f80bbf55bd8d81c78e5d43c8d34ff83add9a6f504
2017-06-17 12:00:48 REORGANIZE: Disconnect 40 blocks; 50f60d706b62c7224d2a86583e14728bc31b56ff123e3a03fc5a8eb0d23a165e..
2017-06-17 12:00:48 REORGANIZE: Connect 17 blocks; ..41e3735a612eb22499292e2717c80f3dab9603ed66fd69d03fbca989f20f8dd6
CSC 400000.00000000 0fb78c9ac533c064943cd90ed807a759c88ffcca18783f920185b57986bab1c5 2017-06-17 12:01:38.0000000 -> Block 08b2cb6e452ce926a16c16e7ae4812a1fcf3dae7c819d1eb4caea2ffe1de7d15
height -> 2033036
2017-06-17 12:02:07 received block 08b2cb6e452ce926a16c16e7ae4812a1fcf3dae7c819d1eb4caea2ffe1de7d15
2017-06-17 12:37:21 REORGANIZE: Disconnect 40 blocks; 1e8a19dfa29f183d4133ced8858ec26cd6792bada4d59339a3e56fbad5395650..
2017-06-17 12:37:21 REORGANIZE: Connect 16 blocks; ..063ca3ec55ea56a9ddf41cdc02ecffbae7c504ac1298d7255bf833d01a6639a8
CSC 400000.00000000 b065895f157fc6d237ae4bd8b8b5ad3dca934510b9f70e7bb7450dff31f37cc0 2017-06-17 12:40:31.0000000 -> Block 9aa33fae6382027cf26eb5abeba3cc96cab693817ce481bdd527944c7c51dd6b
height -> 2033085
2017-06-17 12:43:44 received block 9aa33fae6382027cf26eb5abeba3cc96cab693817ce481bdd527944c7c51dd6b
2017-06-17 13:20:59 REORGANIZE: Disconnect 56 blocks; 11b14f94f0e9cc0f2108e68cde3729113e2046988a9170be3db52558fa32a54b..
2017-06-17 13:20:59 REORGANIZE: Connect 14 blocks; ..b227ffb3fc8e3d32c6a7d15845b4c8e49bbd4c84d1508edce584aeebc5c176ff
CSC 400000.00000000 2b4f8a511437fcb1582c3dc89434cd5624bf4e2c8a0a629e261853ea0d7a2d1e 2017-06-17 13:22:09.0000000 -> Block e7e4db2d4af06c78b9108c38b0c383fc8ede61e89395f78085affe39eade4e70
height -> 2033120
2017-06-17 13:23:25 received block e7e4db2d4af06c78b9108c38b0c383fc8ede61e89395f78085affe39eade4e70
2017-06-17 14:24:17 REORGANIZE: Disconnect 43 blocks; e93b3bbcb874a53308f8151b10ce814551242727726e599ea40d6c92cf40f809..
2017-06-17 14:24:17 REORGANIZE: Connect 14 blocks; ..bb3ab00d217fe73b7cd0aa856c69ff9d7f0a2326916daf176d3fb0b096322090
CSC 400000.00000000 074cfdac8066841a91a0dd335d4b4f5f4c4b437b3f78e7b6172c8546ff51cdf9 2017-06-18 19:49:40.0000000 -> Block 1efe8b7160396e01d20b64bf3ceb8e2465ea3e2d49fe60f22d6a4605eb95e341
height -> 2035735
2017-06-18 19:50:27 received block 1efe8b7160396e01d20b64bf3ceb8e2465ea3e2d49fe60f22d6a4605eb95e341
2017-06-18 20:07:13 REORGANIZE: Disconnect 28 blocks; 5e2bf3c531084cd931c00c6947b749b5ce35724a178c6248c1c2867b3542bb08..
2017-06-18 20:07:13 REORGANIZE: Connect 26 blocks; ..ecd3575e09827bed1442daf747525a548947c9277bfe61a25150932ea548130d
CSC 400000.00000000 b3ab695db31388ce96f0bba4f151b0f25d6787aea097145950901f069a03dc71 2017-06-18 20:08:37.0000000 -> Block 72204fa23d40ff407783aee8ecb9282b751dd3b91c557d2e40c81dd82755020f
height -> 2035772
2017-06-18 20:09:43 received block 72204fa23d40ff407783aee8ecb9282b751dd3b91c557d2e40c81dd82755020f
2017-06-18 20:43:39 REORGANIZE: Disconnect 36 blocks; 43c67d5996fc753d53d317149b64f56ef2ae9def1c68d1654da5521917e80abf..
2017-06-18 20:43:39 REORGANIZE: Connect 19 blocks; ..64c06cfc8adbd14c60cd8a5e3df8bc39503e503fd363218791ca4308ed39e8c1
CSC 400000.00000000 bd61179254d51ab1b8940d36c82498510c996df202b8450a47f02af937288b55 2017-06-18 20:45:35.0000000 -> Block 12ffc169597782b6aebb6c174e1cad7b83c4db82e1efd985c9280e6fdeedab1f
height -> 2035820
2017-06-18 20:46:45 received block 12ffc169597782b6aebb6c174e1cad7b83c4db82e1efd985c9280e6fdeedab1f
2017-06-18 21:15:33 REORGANIZE: Disconnect 51 blocks; b80aaefea8bd90f4df80b3f590b86b4174aa4a9ac66775c304fed79c00ec90f9..
2017-06-18 21:15:33 REORGANIZE: Connect 14 blocks; ..e54539386d071d7b5bf8b9a31dac05b340822fc7edfb76bdf19de3aaa332d9c4
CSC 400000.00000000 cf37242d44d6180c7898b04eb8251c1b66ab834cf594c428867c2f8962af4b27 2017-06-18 21:17:20.0000000 -> Block 9d355a08059b0ec23194a36ad620d7b52ad5f361dc4e999b6005745734f00380
height -> 2035857
2017-06-18 21:19:16 received block 9d355a08059b0ec23194a36ad620d7b52ad5f361dc4e999b6005745734f00380
2017-06-18 21:48:32 REORGANIZE: Disconnect 48 blocks; 3119b3e1ad5c37379d99894ed4be1d3ec488ad6ef279531ea2f81d0bdf46d732..
2017-06-18 21:48:32 REORGANIZE: Connect 27 blocks; ..9d35e447fc5c9a32a4315407f89af4c71e71a04654b0b69066c633a538f96f34
CSC 400000.00000000 d753e7e1aa4806f289613e667637f7258e293c484d35ae4bd2577a94d66dc0c5 2017-06-19 21:54:56.0000000 -> Block 3f5928ba7b2691c60b2b234f1ce8898822e9cec8880917687e5d0ab72ab9a2be
height -> 2037979
2017-06-19 21:55:43 received block 3f5928ba7b2691c60b2b234f1ce8898822e9cec8880917687e5d0ab72ab9a2be
2017-06-19 22:24:19 REORGANIZE: Disconnect 42 blocks; cacd3425fd309cf339229ac96415ccf0b03426d4bc5a523cf19867c04b0d4a7f..
2017-06-19 22:24:19 REORGANIZE: Connect 19 blocks; ..22d7b2fe6d44dc108cf79d47fec64d3e0ba631d3c7e2bd8e741a82222db588cc
CSC 400000.00000000 b502469d3014ec5ea4f71f53fd21b1a2b51382057401bae7a204380ffbdcc389 2017-06-20 19:29:04.0000000 -> Block 4912d5e77b9cb337dcd078b7129e3d2dfd04b371971c9cc1a7b33095aaad70a3
height -> 2039957
2017-06-20 19:32:27 received block 4912d5e77b9cb337dcd078b7129e3d2dfd04b371971c9cc1a7b33095aaad70a3
2017-06-20 20:04:51 REORGANIZE: Disconnect 48 blocks; 00a160af0aa6945a35441a6c1d32d9b9c81a0327b6679e77655de5879b32070e..
2017-06-20 20:04:51 REORGANIZE: Connect 22 blocks; ..8260d2b210663ec0d010210b34ff117032164900e6e074199baf5d8e5a05a4f0
CSC 400000.00000000 586abaa47ad566c53f62906605f7a7b426db1adcba7d6f9674117072b6153592 2017-06-20 20:07:13.0000000 -> Block 5ba858753b123365736e04673222499c0dfe5117d1a9102ec9c303fc1b304963
height -> 2040011
2017-06-20 20:08:58 received block 5ba858753b123365736e04673222499c0dfe5117d1a9102ec9c303fc1b304963
2017-06-20 21:07:59 REORGANIZE: Disconnect 56 blocks; 75717553a04f5e08cd7c630897bd6d1c515a4f94b302f74c8d3b4749819da909..
2017-06-20 21:07:59 REORGANIZE: Connect 15 blocks; ..3920bbeb86a9b358f1d9222d32ce58b6579bb42297c4ae640d2d6b0790f31b30
CSC 400000.00000000 0bb3f971f28abe5ba49939e0c6ce8be88e832d9b740cf190d79bd6d43fb0417e 2017-06-20 21:10:17.0000000 -> Block 88e317066c938eb3510493b4c198d473d843a2300c26b90214d0ad47aee059c2
height -> 2040042
2017-06-20 21:12:24 received block 88e317066c938eb3510493b4c198d473d843a2300c26b90214d0ad47aee059c2
2017-06-20 21:56:00 REORGANIZE: Disconnect 45 blocks; 93788937f6bec41daf203405b72830e87920276ea2d7b575dc2acbc4faa3ddc4..
2017-06-20 21:56:00 REORGANIZE: Connect 8 blocks; ..0ab3ea1b09c1093a4ffa3ca629d5d4ed7b376b1861677669bddbc67e6989f51a
CSC 400000.00000000 586abaa47ad566c53f62906605f7a7b426db1adcba7d6f9674117072b6153592 2017-06-20 20:07:13.0000000
CSC 400000.00000000 b502469d3014ec5ea4f71f53fd21b1a2b51382057401bae7a204380ffbdcc389 2017-06-20 19:29:04.0000000
CSC 400000.00000000 d753e7e1aa4806f289613e667637f7258e293c484d35ae4bd2577a94d66dc0c5 2017-06-19 21:54:56.0000000
CSC 400000.00000000 cf37242d44d6180c7898b04eb8251c1b66ab834cf594c428867c2f8962af4b27 2017-06-18 21:17:20.0000000
CSC 400000.00000000 bd61179254d51ab1b8940d36c82498510c996df202b8450a47f02af937288b55 2017-06-18 20:45:35.0000000
CSC 400000.00000000 b3ab695db31388ce96f0bba4f151b0f25d6787aea097145950901f069a03dc71 2017-06-18 20:08:37.0000000
CSC 400000.00000000 074cfdac8066841a91a0dd335d4b4f5f4c4b437b3f78e7b6172c8546ff51cdf9 2017-06-18 19:49:40.0000000
CSC 400000.00000000 2b4f8a511437fcb1582c3dc89434cd5624bf4e2c8a0a629e261853ea0d7a2d1e 2017-06-17 13:22:09.0000000
CSC 400000.00000000 b065895f157fc6d237ae4bd8b8b5ad3dca934510b9f70e7bb7450dff31f37cc0 2017-06-17 12:40:31.0000000
CSC 400000.00000000 0fb78c9ac533c064943cd90ed807a759c88ffcca18783f920185b57986bab1c5 2017-06-17 12:01:38.0000000
CSC 400000.00000000 8ce954b43bdb369cd2d1e5849941a279691c7647a3af23ef191555ac6d79a05b 2017-06-17 11:19:30.0000000
CSC 400000.00000000 54f496ada83fa08f765e5d08c518c52319f8f546b3d6a08656be14011b87a578 2017-06-17 10:12:34.0000000
CSC 400000.00000000 2a56334a520da44473a94bc061f08b8ece28be781dceac92bd2c503a94d58378 2017-06-17 09:38:46.0000000
CSC 400000.00000000 b2e4390d91701bfbf4498bd612ba7ef6bdafd69d5df4cf2b4e8a51a5f79147b1 2017-06-17 09:09:07.0000000
CSC 400000.00000000 b3f5139a27e888056d7d61ac2478788ca57e699405748e162e673a9def5105a8 2017-06-16 23:14:47.0000000
CSC 400000.00000000 e87014dc9fc3fedcb25a07c0cfdab1da1ee180e62bac5c94dac5303732aafefa 2017-06-16 22:36:02.0000000
CSC 400000.00000000 55361dee7277e0341968a4eefcf40f668fc5e0edcfbab09113eb983d7c8bcadb 2017-06-16 21:48:54.0000000
CSC 400000.00000000 381faf0ebcf7e16ca2c18b82c51e8851e3d08b8c9ffab94dc62b7364e3e5d1f2 2017-06-16 21:07:49.0000000
CSC 400000.00000000 807723365f7a410b7ca67c1d7cf9abca4c1af248a0b71bdb725b20a2558dcd93 2017-06-16 20:05:58.0000000
CSC 200000.00000000 6860fc113e0c01b6fafc1535bd97520647fa2cb885d55565d703d5a4caf67519 2017-06-16 19:26:11.0000000
CSC 200000.00000000 10dfe009eeaf619d59e3c4e18c48d4f06bbba5a47b0802ceb0d85928f61d4f6e 2017-06-16 18:48:18.0000000
CSC 114000.00000000 86950fb41cde845ad39a7d4d093ff1b3b4bc3063303897b7ea5f3a901c2c44ff 2017-06-16 17:50:17.0000000
CSC 114000.00000000 f45405d4ca53252eb653b175177f1b8eaac5a01011a86a748c07b2f5d3706bcd 2017-06-16 13:29:49.0000000
CSC 114000.00000000 d3e89ea4b0a4286689a26929ea27a725495353bfd9bb5fcc9a53c597399999ef 2017-06-16 12:43:06.0000000
CSC 114000.00000000 c7b1c1b37597154af07d8189ca513cada4f51363ecc0d792f6e5780ac800caed 2017-06-16 11:46:02.0000000
CSC 114000.00000000 d8913bb321fe50e84b18e8c2a41ff8a2edd9f6f7b2fe6f88ca2738cb0d999d74 2017-06-16 09:21:35.0000000
CSC 114000.00000000 541a44b2b1e526157f13089159afa6aa97ce558211f83a9c5558c97fa792cd48 2017-06-16 08:49:37.0000000
CSC 57000.00000000 25a7e7f0c2f72869626bea52e10826176383a50ccdcdb8d12a14321de664465d 2017-06-15 22:38:51.0000000
CSC 57000.00000000 47c6a397bcab18e77ff99c8ad2bb7dda2013d0f7612401a2984728165e808b3e 2017-06-15 22:13:04.0000000
CSC 74500.00000000 6e64724ee5daedbbcd98da3af36cfd09332864b17350028919f21ea5f00bfcd6 2017-06-13 19:34:01.0000000
CSC 75000.00000000 41da631b9579141ee8fe2137b247a9b2aad3acbd10b47b63ece628f97a7a06c1 2017-06-13 17:50:10.0000000
CSC 75000.00000000 3e25e78f64ff80840b37d2a4154a2a3d3b4c26c00895e0fcd652daea8abdebcd 2017-06-13 16:56:41.0000000
CSC 75000.00000000 1c6edddab9b4a0d442c36f50adb1f9b3c459b8fd2b49944db7f39f69a048b67a 2017-06-13 16:20:30.0000000
CSC 75000.00000000 e438a555dcc6a788c4d51814ac02c21bcd9b3d6e130726222d9fca3f9dcc6359 2017-06-13 15:27:23.0000000
CSC 76000.00000000 0c406c2016e7418f2e96884898671bacad20590bd30e5617d17bee4903a4968c 2017-06-13 14:55:02.0000000
CSC 38300.00000000 2634f0879c67e6618dddbefbffbd72db8566ae26b593e4aa3d68393529f3f740 2017-06-13 14:16:18.0000000
CSC 38300.00000000 dae189c8827078fcf75881ba105d1b398560329e5a7d4ef19b7046ba2380f41f 2017-06-12 21:10:11.0000000
CSC 38300.00000000 8c11ea0658c486b994586032d1bc7af543a6da973f98d867f1ff0b40beed9864 2017-06-12 13:51:31.0000000
CSC 38300.00000000 2da41a8cf1b483a2095f99c2bea75ca144129d8aff070a8306a85daad42def99 2017-06-12 13:28:29.0000000
CSC 19200.00000000 36f86626caa3acdf6b04d9590e881288121d2ab46a3643374cd897f872256739 2017-06-12 09:42:14.0000000
CSC 400000.00000000 807723365f7a410b7ca67c1d7cf9abca4c1af248a0b71bdb725b20a2558dcd93 2017-06-16 20:05:58.0000000 -> Block c0fd5937e445d2dbf94150f2fc4f3601ab0a69e894aaaaccecc49d007e1e300e
height -> 2031736
2017-06-16 20:09:19 received block c0fd5937e445d2dbf94150f2fc4f3601ab0a69e894aaaaccecc49d007e1e300e
2017-06-16 21:03:18 REORGANIZE: Disconnect 65 blocks; edd1c7cac77a5cee78294446938f6d3714207d92dc0df4c03406f2ec1eb015cf..
2017-06-16 21:03:18 REORGANIZE: Connect 17 blocks; ..b1bae61557ba1d9adb9e0a3837e938a03d2a8cbf859da77568deaacaad4fab55
CSC 400000.00000000 381faf0ebcf7e16ca2c18b82c51e8851e3d08b8c9ffab94dc62b7364e3e5d1f2 2017-06-16 21:07:49.0000000 -> Block 407fbc1b09f52df2a01d400fa0ba0dfa312368c8e9b3db4f6bed24758973f8c5
height -> 2031788
2017-06-16 21:08:53 received block 407fbc1b09f52df2a01d400fa0ba0dfa312368c8e9b3db4f6bed24758973f8c5
2017-06-16 21:46:52 REORGANIZE: Disconnect 34 blocks; e3d4829859dd6601bd3773d92ef95c2d0760fa09acb649f0119729f4dd494b5a..
2017-06-16 21:46:52 REORGANIZE: Connect 16 blocks; ..d9402d7e4c456aff7f8c104d80db054c5f799fcb8dbd3cfc7f365211247fc6bd
CSC 400000.00000000 55361dee7277e0341968a4eefcf40f668fc5e0edcfbab09113eb983d7c8bcadb 2017-06-16 21:48:54.0000000 -> Block ca2429d56c40b85fd8679340e10e84c2e38335b43a5ce55e3ff4c051129df729
height -> 2031827
2017-06-16 21:52:39 received block ca2429d56c40b85fd8679340e10e84c2e38335b43a5ce55e3ff4c051129df729
2017-06-16 22:32:16 REORGANIZE: Disconnect 29 blocks; 928ee46d1506cf7fd6e1f09ee57bed6d633e61ee6670f9a40ee2e4672181590d..
2017-06-16 22:32:16 REORGANIZE: Connect 21 blocks; ..70971b3ea24465c4160bd40bfe34ed2256978b9f49fe2dab68d11cc26827a22d
CSC 400000.00000000 e87014dc9fc3fedcb25a07c0cfdab1da1ee180e62bac5c94dac5303732aafefa 2017-06-16 22:36:02.0000000 -> Block bbb52f7d47b422fdb0529c1cfa217d100071721b421d15c9b4d2da8814d987b1
height -> 2031891
2017-06-16 22:41:34 received block bbb52f7d47b422fdb0529c1cfa217d100071721b421d15c9b4d2da8814d987b1
2017-06-16 23:12:39 REORGANIZE: Disconnect 40 blocks; ad9b80025dbd2ca27262769a8272588cec092155da433bba06f810dda0d89d7c..
2017-06-16 23:12:39 REORGANIZE: Connect 33 blocks; ..8ed38ca4bf218073da7e43755171e2d8babcd5bdd68b648381c3f1f5d333e332
CSC 400000.00000000 b3f5139a27e888056d7d61ac2478788ca57e699405748e162e673a9def5105a8 2017-06-16 23:14:47.0000000 -> Block feaf6739256550922ed490dc9760c2d5020b0239a4aedde4a178ae9314350366
height -> 2031939
2017-06-16 23:17:30 received block feaf6739256550922ed490dc9760c2d5020b0239a4aedde4a178ae9314350366
2017-06-16 23:51:37 REORGANIZE: Disconnect 55 blocks; 5d0d63667a40172f94327c4ff7d505f19e21c5d0d4e61ebaf379245fca3ab368..
2017-06-16 23:51:37 REORGANIZE: Connect 17 blocks; ..6a3e799c28c3930aadf4286003d55bab0498c1de53ad37baa7b368b03bcf7cd5
CSC 400000.00000000 b2e4390d91701bfbf4498bd612ba7ef6bdafd69d5df4cf2b4e8a51a5f79147b1 2017-06-17 09:09:07.0000000 -> Block 61dcf1a6ee3bcd262fc828d2faf2efd501a7fa1698742348f7a0e32e824056b6
height -> 2032834
2017-06-17 09:09:29 received block 61dcf1a6ee3bcd262fc828d2faf2efd501a7fa1698742348f7a0e32e824056b6
2017-06-17 09:37:38 REORGANIZE: Disconnect 57 blocks; 1b3486ea5edfbab640b4a0e81ee852db8424bbe34c15bb0bcf11ec465d9a7d10..
2017-06-17 09:37:38 REORGANIZE: Connect 22 blocks; ..96ab5bd0178beb78c8ceb312cc4fa0656480a3c64a8e04ddbcc9ccee48b93183
CSC 400000.00000000 2a56334a520da44473a94bc061f08b8ece28be781dceac92bd2c503a94d58378 2017-06-17 09:38:46.0000000 -> Block 657ff4b684c6dbd5c19ec953b3778aa76921b1d23cb7c6ec8cf3d1ee16c8171b
height -> 2032866
2017-06-17 09:40:37 received block 657ff4b684c6dbd5c19ec953b3778aa76921b1d23cb7c6ec8cf3d1ee16c8171b
2017-06-17 10:08:38 REORGANIZE: Disconnect 41 blocks; 2f4128e0c9d6823aaba5508500bdb67804762630953d87bbac3904bec7e8c6f4..
2017-06-17 10:08:38 REORGANIZE: Connect 19 blocks; ..6f5e190d6d2225c27b6beef2b0150bf5bfd7dc5f85ee00bc8cf57f2d83e38d17
CSC 400000.00000000 54f496ada83fa08f765e5d08c518c52319f8f546b3d6a08656be14011b87a578 2017-06-17 10:12:34.0000000 -> Block f3a29257327f6441308ac85603e6669909222f065971a571edf07e35432c8730
height -> 2032900
2017-06-17 10:15:20 received block f3a29257327f6441308ac85603e6669909222f065971a571edf07e35432c8730
2017-06-17 11:17:17 REORGANIZE: Disconnect 98 blocks; 7235a637c3913a39035814818cf8670b9c4c1a57bffdd54180b9eee54a66d933..
2017-06-17 11:17:17 REORGANIZE: Connect 36 blocks; ..d0ed7def0d6686d5edbe2924813f8cb4fdf04ac739ac9c1b77d880b61b10b45f
CSC 400000.00000000 8ce954b43bdb369cd2d1e5849941a279691c7647a3af23ef191555ac6d79a05b 2017-06-17 11:19:30.0000000 -> Block b435b80f7c27a743576b172f80bbf55bd8d81c78e5d43c8d34ff83add9a6f504
height -> 2032993
2017-06-17 11:20:37 received block b435b80f7c27a743576b172f80bbf55bd8d81c78e5d43c8d34ff83add9a6f504
2017-06-17 12:00:48 REORGANIZE: Disconnect 40 blocks; 50f60d706b62c7224d2a86583e14728bc31b56ff123e3a03fc5a8eb0d23a165e..
2017-06-17 12:00:48 REORGANIZE: Connect 17 blocks; ..41e3735a612eb22499292e2717c80f3dab9603ed66fd69d03fbca989f20f8dd6
CSC 400000.00000000 0fb78c9ac533c064943cd90ed807a759c88ffcca18783f920185b57986bab1c5 2017-06-17 12:01:38.0000000 -> Block 08b2cb6e452ce926a16c16e7ae4812a1fcf3dae7c819d1eb4caea2ffe1de7d15
height -> 2033036
2017-06-17 12:02:07 received block 08b2cb6e452ce926a16c16e7ae4812a1fcf3dae7c819d1eb4caea2ffe1de7d15
2017-06-17 12:37:21 REORGANIZE: Disconnect 40 blocks; 1e8a19dfa29f183d4133ced8858ec26cd6792bada4d59339a3e56fbad5395650..
2017-06-17 12:37:21 REORGANIZE: Connect 16 blocks; ..063ca3ec55ea56a9ddf41cdc02ecffbae7c504ac1298d7255bf833d01a6639a8
CSC 400000.00000000 b065895f157fc6d237ae4bd8b8b5ad3dca934510b9f70e7bb7450dff31f37cc0 2017-06-17 12:40:31.0000000 -> Block 9aa33fae6382027cf26eb5abeba3cc96cab693817ce481bdd527944c7c51dd6b
height -> 2033085
2017-06-17 12:43:44 received block 9aa33fae6382027cf26eb5abeba3cc96cab693817ce481bdd527944c7c51dd6b
2017-06-17 13:20:59 REORGANIZE: Disconnect 56 blocks; 11b14f94f0e9cc0f2108e68cde3729113e2046988a9170be3db52558fa32a54b..
2017-06-17 13:20:59 REORGANIZE: Connect 14 blocks; ..b227ffb3fc8e3d32c6a7d15845b4c8e49bbd4c84d1508edce584aeebc5c176ff
CSC 400000.00000000 2b4f8a511437fcb1582c3dc89434cd5624bf4e2c8a0a629e261853ea0d7a2d1e 2017-06-17 13:22:09.0000000 -> Block e7e4db2d4af06c78b9108c38b0c383fc8ede61e89395f78085affe39eade4e70
height -> 2033120
2017-06-17 13:23:25 received block e7e4db2d4af06c78b9108c38b0c383fc8ede61e89395f78085affe39eade4e70
2017-06-17 14:24:17 REORGANIZE: Disconnect 43 blocks; e93b3bbcb874a53308f8151b10ce814551242727726e599ea40d6c92cf40f809..
2017-06-17 14:24:17 REORGANIZE: Connect 14 blocks; ..bb3ab00d217fe73b7cd0aa856c69ff9d7f0a2326916daf176d3fb0b096322090
CSC 400000.00000000 074cfdac8066841a91a0dd335d4b4f5f4c4b437b3f78e7b6172c8546ff51cdf9 2017-06-18 19:49:40.0000000 -> Block 1efe8b7160396e01d20b64bf3ceb8e2465ea3e2d49fe60f22d6a4605eb95e341
height -> 2035735
2017-06-18 19:50:27 received block 1efe8b7160396e01d20b64bf3ceb8e2465ea3e2d49fe60f22d6a4605eb95e341
2017-06-18 20:07:13 REORGANIZE: Disconnect 28 blocks; 5e2bf3c531084cd931c00c6947b749b5ce35724a178c6248c1c2867b3542bb08..
2017-06-18 20:07:13 REORGANIZE: Connect 26 blocks; ..ecd3575e09827bed1442daf747525a548947c9277bfe61a25150932ea548130d
CSC 400000.00000000 b3ab695db31388ce96f0bba4f151b0f25d6787aea097145950901f069a03dc71 2017-06-18 20:08:37.0000000 -> Block 72204fa23d40ff407783aee8ecb9282b751dd3b91c557d2e40c81dd82755020f
height -> 2035772
2017-06-18 20:09:43 received block 72204fa23d40ff407783aee8ecb9282b751dd3b91c557d2e40c81dd82755020f
2017-06-18 20:43:39 REORGANIZE: Disconnect 36 blocks; 43c67d5996fc753d53d317149b64f56ef2ae9def1c68d1654da5521917e80abf..
2017-06-18 20:43:39 REORGANIZE: Connect 19 blocks; ..64c06cfc8adbd14c60cd8a5e3df8bc39503e503fd363218791ca4308ed39e8c1
CSC 400000.00000000 bd61179254d51ab1b8940d36c82498510c996df202b8450a47f02af937288b55 2017-06-18 20:45:35.0000000 -> Block 12ffc169597782b6aebb6c174e1cad7b83c4db82e1efd985c9280e6fdeedab1f
height -> 2035820
2017-06-18 20:46:45 received block 12ffc169597782b6aebb6c174e1cad7b83c4db82e1efd985c9280e6fdeedab1f
2017-06-18 21:15:33 REORGANIZE: Disconnect 51 blocks; b80aaefea8bd90f4df80b3f590b86b4174aa4a9ac66775c304fed79c00ec90f9..
2017-06-18 21:15:33 REORGANIZE: Connect 14 blocks; ..e54539386d071d7b5bf8b9a31dac05b340822fc7edfb76bdf19de3aaa332d9c4
CSC 400000.00000000 cf37242d44d6180c7898b04eb8251c1b66ab834cf594c428867c2f8962af4b27 2017-06-18 21:17:20.0000000 -> Block 9d355a08059b0ec23194a36ad620d7b52ad5f361dc4e999b6005745734f00380
height -> 2035857
2017-06-18 21:19:16 received block 9d355a08059b0ec23194a36ad620d7b52ad5f361dc4e999b6005745734f00380
2017-06-18 21:48:32 REORGANIZE: Disconnect 48 blocks; 3119b3e1ad5c37379d99894ed4be1d3ec488ad6ef279531ea2f81d0bdf46d732..
2017-06-18 21:48:32 REORGANIZE: Connect 27 blocks; ..9d35e447fc5c9a32a4315407f89af4c71e71a04654b0b69066c633a538f96f34
CSC 400000.00000000 d753e7e1aa4806f289613e667637f7258e293c484d35ae4bd2577a94d66dc0c5 2017-06-19 21:54:56.0000000 -> Block 3f5928ba7b2691c60b2b234f1ce8898822e9cec8880917687e5d0ab72ab9a2be
height -> 2037979
2017-06-19 21:55:43 received block 3f5928ba7b2691c60b2b234f1ce8898822e9cec8880917687e5d0ab72ab9a2be
2017-06-19 22:24:19 REORGANIZE: Disconnect 42 blocks; cacd3425fd309cf339229ac96415ccf0b03426d4bc5a523cf19867c04b0d4a7f..
2017-06-19 22:24:19 REORGANIZE: Connect 19 blocks; ..22d7b2fe6d44dc108cf79d47fec64d3e0ba631d3c7e2bd8e741a82222db588cc
CSC 400000.00000000 b502469d3014ec5ea4f71f53fd21b1a2b51382057401bae7a204380ffbdcc389 2017-06-20 19:29:04.0000000 -> Block 4912d5e77b9cb337dcd078b7129e3d2dfd04b371971c9cc1a7b33095aaad70a3
height -> 2039957
2017-06-20 19:32:27 received block 4912d5e77b9cb337dcd078b7129e3d2dfd04b371971c9cc1a7b33095aaad70a3
2017-06-20 20:04:51 REORGANIZE: Disconnect 48 blocks; 00a160af0aa6945a35441a6c1d32d9b9c81a0327b6679e77655de5879b32070e..
2017-06-20 20:04:51 REORGANIZE: Connect 22 blocks; ..8260d2b210663ec0d010210b34ff117032164900e6e074199baf5d8e5a05a4f0
CSC 400000.00000000 586abaa47ad566c53f62906605f7a7b426db1adcba7d6f9674117072b6153592 2017-06-20 20:07:13.0000000 -> Block 5ba858753b123365736e04673222499c0dfe5117d1a9102ec9c303fc1b304963
height -> 2040011
2017-06-20 20:08:58 received block 5ba858753b123365736e04673222499c0dfe5117d1a9102ec9c303fc1b304963
2017-06-20 21:07:59 REORGANIZE: Disconnect 56 blocks; 75717553a04f5e08cd7c630897bd6d1c515a4f94b302f74c8d3b4749819da909..
2017-06-20 21:07:59 REORGANIZE: Connect 15 blocks; ..3920bbeb86a9b358f1d9222d32ce58b6579bb42297c4ae640d2d6b0790f31b30
CSC 400000.00000000 0bb3f971f28abe5ba49939e0c6ce8be88e832d9b740cf190d79bd6d43fb0417e 2017-06-20 21:10:17.0000000 -> Block 88e317066c938eb3510493b4c198d473d843a2300c26b90214d0ad47aee059c2
height -> 2040042
2017-06-20 21:12:24 received block 88e317066c938eb3510493b4c198d473d843a2300c26b90214d0ad47aee059c2
2017-06-20 21:56:00 REORGANIZE: Disconnect 45 blocks; 93788937f6bec41daf203405b72830e87920276ea2d7b575dc2acbc4faa3ddc4..
2017-06-20 21:56:00 REORGANIZE: Connect 8 blocks; ..0ab3ea1b09c1093a4ffa3ca629d5d4ed7b376b1861677669bddbc67e6989f51a
July 14, 2017, 01:23:08 AM
What I do not understand is: Even if the 51% attack had been fully successful, how did the attackers think they will be able to liquidate 9.7m CSC? Surely, their objective must have been to illicitly gain the CSC and then sell them for BTC and walk away with the BTC. Given the historic market depth, that seems nigh on impossible without crashing the price to zero.
So, something is fishy here. Why would an attacker go to such lengths only to end up, even in the best case scenario, with 9.7m CSC that are practically unsalable?
Unless of course the attackers were insiders and had other motives, such as taking over a large part of the coin supply.
July 13, 2017, 08:37:09 AM
We are also coming up on our 4 year anniversary.
"CasinoCoin was officially launched on Thursday, July 18th at 9:00PM EST with absolutely no premine."
I'd like to throw out a big thanks to Transcoder for creating CSC and to all of the developers and community members who have contributed their own time and skills over the past years to Casinocoin.
Keep you're eye out for future developments and if you can contribute to CSC get in touch with us and check out our github https://github.com/casinocoin
"CasinoCoin was officially launched on Thursday, July 18th at 9:00PM EST with absolutely no premine."
I'd like to throw out a big thanks to Transcoder for creating CSC and to all of the developers and community members who have contributed their own time and skills over the past years to Casinocoin.
Keep you're eye out for future developments and if you can contribute to CSC get in touch with us and check out our github https://github.com/casinocoin
Glad to hear these exciting news for Casinocoin! It is almost 4 years since its inception, and it has managed to survive with a community behind supporting it in every way possible.
It is one of those coins with huge potential, although it may take quite some time before it sparkles and becomes very popular. Prices are still cheap, and way below the $1 USD mark, but I'm confident that we will get there soon when real usability comes in for CSC within mainstream casinos from around the world.
When it becomes the top cryptocurrency for casinos, the value per CSC will skyrocket, making many of those who have invested earlier into it as millionaires.
Nevertheless, despite the profits, and value of each CSC coin, the most important thing for any cryptocurrency is long term stability, and development to ensure its survival for many years to come. I'm hoping to see more exciting stuff to come by before the end of the year for Casinocoin.
July 11, 2017, 09:04:20 AM
We are also coming up on our 4 year anniversary.
"CasinoCoin was officially launched on Thursday, July 18th at 9:00PM EST with absolutely no premine."
I'd like to throw out a big thanks to Transcoder for creating CSC and to all of the developers and community members who have contributed their own time and skills over the past years to Casinocoin.
Keep your eye out for future developments and if you can contribute to CSC get in touch with us and check out our github https://github.com/casinocoin
"CasinoCoin was officially launched on Thursday, July 18th at 9:00PM EST with absolutely no premine."
I'd like to throw out a big thanks to Transcoder for creating CSC and to all of the developers and community members who have contributed their own time and skills over the past years to Casinocoin.
Keep your eye out for future developments and if you can contribute to CSC get in touch with us and check out our github https://github.com/casinocoin
July 11, 2017, 09:00:00 AM
Wow that's crazy to hear, hope everyone that lost their money on there is able to recover.
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
The coins didn't exist and the exchange is blaming Litecoin code. Unless i missed something huge in the commits, its Litecoin core that they are blaming
If you trade or run a CSC service please consider:
- Never leave coins in exchange wallets
- Always trade/deposit/withdraw in small amounts
- Always use a minimum for CSC block confirmations of 50, preferably 100 or more!
- If you run an exchange, ... ALWAYS run checks on transactions against the blockchain!
Until now only about 2,5 mln of the missing 9,7 mln Cryptopia coins have been reported. Can everybody who lost coins please inform us?
Also, there is still 0.64143185 BTC on the buy side on Cryptopia, .... i would move that to AlcurEX or NovaExchange as soon as possible!!!
Thanks!
I had about 15000 there I was trading.
Cryptopia seems like a pretty crap exchange, they screwed up Diamond coin there as well.
They didn't have the ability to upgrade the exchange wallet after the last fork, so delisted it.
I would say stay the hell away from them, its only a matter of time before they are hacked big time.
https://casinocoin.org/join-slack
July 11, 2017, 08:22:19 AM
Wow that's crazy to hear, hope everyone that lost their money on there is able to recover.
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
The coins didn't exist and the exchange is blaming Litecoin code. Unless i missed something huge in the commits, its Litecoin core that they are blaming
If you trade or run a CSC service please consider:
- Never leave coins in exchange wallets
- Always trade/deposit/withdraw in small amounts
- Always use a minimum for CSC block confirmations of 50, preferably 100 or more!
- If you run an exchange, ... ALWAYS run checks on transactions against the blockchain!
Until now only about 2,5 mln of the missing 9,7 mln Cryptopia coins have been reported. Can everybody who lost coins please inform us?
Also, there is still 0.64143185 BTC on the buy side on Cryptopia, .... i would move that to AlcurEX or NovaExchange as soon as possible!!!
Thanks!
I had about 15000 there I was trading.
Cryptopia seems like a pretty crap exchange, they screwed up Diamond coin there as well.
They didn't have the ability to upgrade the exchange wallet after the last fork, so delisted it.
I would say stay the hell away from them, its only a matter of time before they are hacked big time.
July 11, 2017, 05:27:31 AM
Wow that's crazy to hear, hope everyone that lost their money on there is able to recover.
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
The coins didn't exist and the exchange is blaming Litecoin code. Unless i missed something huge in the commits, its Litecoin core that they are blaming
If you trade or run a CSC service please consider:
- Never leave coins in exchange wallets
- Always trade/deposit/withdraw in small amounts
- Always use a minimum for CSC block confirmations of 50, preferably 100 or more!
- If you run an exchange, ... ALWAYS run checks on transactions against the blockchain!
Until now only about 2,5 mln of the missing 9,7 mln Cryptopia coins have been reported. Can everybody who lost coins please inform us?
Also, there is still 0.64143185 BTC on the buy side on Cryptopia, .... i would move that to AlcurEX or NovaExchange as soon as possible!!!
Thanks!
July 10, 2017, 01:32:34 AM
Wow that's crazy to hear, hope everyone that lost their money on there is able to recover.
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
The coins didn't exist and the exchange is blaming Litecoin code. Unless i missed something huge in the commits, its Litecoin core that they are blaming
July 09, 2017, 02:31:14 PM
Wow that's crazy to hear, hope everyone that lost their money on there is able to recover.
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
So the attacker was able to steal 9.7 million coins from Cryptopia? Or are all those coins invalid?
I know you said there was rollbacks, but just want to be sure that person didn't get to keep any of the stolen coins
July 09, 2017, 02:15:22 PM
Information regarding the Cryptopia issues.
On 12-06-2017 a 51% attack on Cryptopia started. The attackers targeted various coins, including CSC. By now, after thorough analysis, we can conclude that the attackers were able to deposit some 9.7 million CSC to Cryptopia without actually having those coins in their possession. While Cryptopia tells its users that the coin developers are responsible for the loss, analysis shows a different story.
- more than 200 double spent deposits took place
- 41 of those deposits succeeded
- all double spent transactions have been rolled back by the CSC blockchain and there is NO fork
- most transactions rolled back within 1-2 blocks, the double spends that succeeded had rollbacks between 10-60 blocks
- the attack continued for 8 days
- Cryptopia claims block rollbacks of 300 blocks took place, this is not true
- Cryptopia claims there was 1.2Thash involved, this is not true, there was a max of about 800 MHash during the attack
- Cryptopia had set block confirmations to only 6 blocks for deposits
- Cryptopia had no checks of their wallet against the blockchain at any time
- Cryptopia only depends on its own DB instead of the coins blockchain after the 6 confirmations
- Cryptopia allowed for 25% of total market capital to be deposited by a single user
- Only when a large withdraw was no longer possible they detected something was wrong
- We tried to work out a solution with Cryptopia but they demanded we deposited the missing 9.7 million coins or altered the blockchain. It seems obvious that both are not viable options for the casinocoin team.
- As an alternative we asked for a detailed list of BTC that would be required to rollback the malicious transactions and return the original BTC to the users but Cryptopia refused to supply that.
- Cryptopia decided to walk away, delist CSC and leave users with their losses.
Anybody that wants the detailed information of the log analysis can get it on request. We know there has been discussion of the network hashrate in the past but we want to remind everybody that network hashing power can be acquired at about 0.003 BTC per hour for 1 GHash at this moment. That makes almost all Scrypt based coins vulnerable for a 51% attack at this moment. Problems for exchanges however can be prevented by running decent block confirmation amounts and running regularly checks on wallets and transactions, .... either one would have raised red flags at Cryptopia a lot sooner. We have advised AlcurEX and NovaExchange about the attack and they both verified that they have block confirmations at 100 or more. Although we are sad for the users that have losses because of Cryptopia we would not know how to supply a solution as Cryptopia refuses to further collaborate and walks away.
We would like all Cryptopia users to gather as much information as possible on all their BTC and CSC deposits and withdraws (addresses and transaction id's) and sent them to Casinocoin, GoldSeal or myself. Also information about balances and filled orders should be saved e.g. by making screenshots of everything. The CSC team might find a way in the near future to reimburse some of the losses of Cryptopia users and in that case you would need to show some proof. As Cryptopia now shows they do not care about their users and they were running an insecure exchange we suggest everybody to get their balances of Cryptopia as soon as possible and advise other users to do the same!!
On 12-06-2017 a 51% attack on Cryptopia started. The attackers targeted various coins, including CSC. By now, after thorough analysis, we can conclude that the attackers were able to deposit some 9.7 million CSC to Cryptopia without actually having those coins in their possession. While Cryptopia tells its users that the coin developers are responsible for the loss, analysis shows a different story.
- more than 200 double spent deposits took place
- 41 of those deposits succeeded
- all double spent transactions have been rolled back by the CSC blockchain and there is NO fork
- most transactions rolled back within 1-2 blocks, the double spends that succeeded had rollbacks between 10-60 blocks
- the attack continued for 8 days
- Cryptopia claims block rollbacks of 300 blocks took place, this is not true
- Cryptopia claims there was 1.2Thash involved, this is not true, there was a max of about 800 MHash during the attack
- Cryptopia had set block confirmations to only 6 blocks for deposits
- Cryptopia had no checks of their wallet against the blockchain at any time
- Cryptopia only depends on its own DB instead of the coins blockchain after the 6 confirmations
- Cryptopia allowed for 25% of total market capital to be deposited by a single user
- Only when a large withdraw was no longer possible they detected something was wrong
- We tried to work out a solution with Cryptopia but they demanded we deposited the missing 9.7 million coins or altered the blockchain. It seems obvious that both are not viable options for the casinocoin team.
- As an alternative we asked for a detailed list of BTC that would be required to rollback the malicious transactions and return the original BTC to the users but Cryptopia refused to supply that.
- Cryptopia decided to walk away, delist CSC and leave users with their losses.
Anybody that wants the detailed information of the log analysis can get it on request. We know there has been discussion of the network hashrate in the past but we want to remind everybody that network hashing power can be acquired at about 0.003 BTC per hour for 1 GHash at this moment. That makes almost all Scrypt based coins vulnerable for a 51% attack at this moment. Problems for exchanges however can be prevented by running decent block confirmation amounts and running regularly checks on wallets and transactions, .... either one would have raised red flags at Cryptopia a lot sooner. We have advised AlcurEX and NovaExchange about the attack and they both verified that they have block confirmations at 100 or more. Although we are sad for the users that have losses because of Cryptopia we would not know how to supply a solution as Cryptopia refuses to further collaborate and walks away.
We would like all Cryptopia users to gather as much information as possible on all their BTC and CSC deposits and withdraws (addresses and transaction id's) and sent them to Casinocoin, GoldSeal or myself. Also information about balances and filled orders should be saved e.g. by making screenshots of everything. The CSC team might find a way in the near future to reimburse some of the losses of Cryptopia users and in that case you would need to show some proof. As Cryptopia now shows they do not care about their users and they were running an insecure exchange we suggest everybody to get their balances of Cryptopia as soon as possible and advise other users to do the same!!
July 08, 2017, 05:22:41 PM
THis is a clusterfuck hahahahahahaha. Lets hope it will be sorted out soon. these things do happen though its nature
July 08, 2017, 05:14:18 PM
Sender: DaRoll7/7/2017 11:12:59 PM
Hi arvin777,
We are currently in discussion with the CSC team to see if we can get this issue resolved. As soon as we hear back from them, we will know what is happening with CSC going forward.
Unfortunately until then, I can't give you any definite answer but as soon as we know what is happening going forward, you will see the status change on our coin info page here -
https://www.cryptopia.co.nz/CoinInfo/?coin=CSC
Thanks, Cryptopia Support.
Hi arvin777,
We are currently in discussion with the CSC team to see if we can get this issue resolved. As soon as we hear back from them, we will know what is happening with CSC going forward.
Unfortunately until then, I can't give you any definite answer but as soon as we know what is happening going forward, you will see the status change on our coin info page here -
https://www.cryptopia.co.nz/CoinInfo/?coin=CSC
Thanks, Cryptopia Support.
Thanks for putting here the news coming from cryptopia ... In summary, I think we can expect more losses ... this coin is more and more "special"...
July 08, 2017, 05:55:05 AM
Sender: DaRoll7/7/2017 11:12:59 PM
Hi arvin777,
We are currently in discussion with the CSC team to see if we can get this issue resolved. As soon as we hear back from them, we will know what is happening with CSC going forward.
Unfortunately until then, I can't give you any definite answer but as soon as we know what is happening going forward, you will see the status change on our coin info page here -
https://www.cryptopia.co.nz/CoinInfo/?coin=CSC
Thanks, Cryptopia Support.
Hi arvin777,
We are currently in discussion with the CSC team to see if we can get this issue resolved. As soon as we hear back from them, we will know what is happening with CSC going forward.
Unfortunately until then, I can't give you any definite answer but as soon as we know what is happening going forward, you will see the status change on our coin info page here -
https://www.cryptopia.co.nz/CoinInfo/?coin=CSC
Thanks, Cryptopia Support.
June 30, 2017, 09:59:51 PM
As I said, CSC is a joke, and now the clowns from Prypto, who achieved exactly zero, zilch, nada, nix, rien, nothing, in 2 years, are in control of the coin and probably the network also.
You're probably right. Personally i don't see the problem.
I most certainly haven't paid them to do anything and thats probably why i don't see the issue you seem to think is and should be all of our reality. Ahh the beauty of free thinking.
June 30, 2017, 07:33:38 PM
nethash at 800mhs 
June 30, 2017, 03:39:11 AM
As I said, CSC is a joke, and now the clowns from Prypto, who achieved exactly zero, zilch, nada, nix, rien, nothing, in 2 years, are in control of the coin and probably the network also.
Man grow up! You have no idea whats going on, ... you do not have any idea about who is in control, .... you lost interest in the coin, ..... you sold off all your coins to somebody else, .... move on and go away please! 
June 30, 2017, 03:27:56 AM
any news from cryptopia??
We've supplied them with additional information regarding the attack. They are still in contact with Andre. We will pass updates when they become available.
Jump to: