Search content
Sort by
Showing 20 of 78 results by xrobau
Re: [ANN][MID]MidasCoin|New Scrypt PoM|Backed Value|ATM card|Referral|NO IPO|UNIQUE
Unfortunately we cannot offer a bounty for this, since we have no premine, but we really appreciate your dedication at making #midascoin thread appear on top.
Wait. So now you're saying you CAN'T pay the bounty that you offered? Isn't that LYING? You wouldn't be admitting that you lied, are you?
Re: [ANN][MID]MidasCoin|New Scrypt PoM|Backed Value|ATM card|Referral|NO IPO|UNIQUE
Even faking the first post, you can't do better?
You know, I had a run-in with another scamcoin developer. Your lack of comprehension, and inability to actually answer questions, makes me think that you're one and the same.
I can not mine coins without mining through that pool. There is only one central pool. It is centralized. There is only one central place to mine coins. Can I phrase this in any other way?
They're dead, Dave. Dave, they're dead. Dead they are, Dave.
OK, here's the simple way to figure out who's right:
How do I mine coins WITHOUT going through the 'main pool'?
Re: [ANN][MID]MidasCoin|New Scrypt PoM|Backed Value|ATM card|Referral|NO IPO|UNIQUE
In #midascoin any node can hash blocks/confirm tx, prove that is not possible to setup a node and confirm/hash blocks, like that "uber informed" person declare, and i will issue you a 10 BTC bounty, right now!
Your first post says this:
Quote
Minable only through the PoM official pool Midaspool.com.
I'd like to claim that 10BTC bounty. Please send it to 1xrobauEmhLwVnTmLbs6M92n1xGFAFbgq
Wow, that was easy.
There's a REASONABLY good chance that filtering them through LeaseRig's LR3 proxy will sanitize and fix this issue, too.
https://bitcointalk.org/index.php?topic=544732.0
https://bitcointalk.org/index.php?topic=544732.0
Re: Proof of dishonesty and lies from Gawminers.com Hashlet Ponzi Scheme Scam
Quote
Have you ever wondered why GAW don't allow us to choose our own worker ID?
How come different pools generate exactly the same return curves?
How come different pools generate exactly the same return curves?
That's kind of a smoking gun right there. You mean to say that they host miners, but don't let you mine where you want to mine?
(I don't have any link to GAW at all. I was just keeping abreast of the latest in scam when I came across this thread)
Hrm. I just had a PM from 'GAW Miners_CEO'. It said: "The reason we dont allow folks to put in their own pool is to follow our uptime commitment. The number one issue that we deal with on our hosting platform, that does allow for their own pools, is folks putting in the wrong pool info. This then creates down time, that the customer (often) blames us for"
Screenshot, with mouseover the User ID
This makes me even MORE suspicious. Because, according to the OP, their hosting platform does NOT allow people to enter their own pools, or change the account. Either way, I can't see why, even if they DID have a whitelist of known good pools, they wouldn't allow people to mine to their own accounts on the known good pools.
Which is it OP?
Re: Proof of dishonesty and lies from Gawminers.com Hashlet Ponzi Scheme Scam
There is no proof of anything you've said, multiple, multiple times.
Uh, actually, I think the important thing is here:
Quote
Have you ever wondered why GAW don't allow us to choose our own worker ID?
How come different pools generate exactly the same return curves?
How come different pools generate exactly the same return curves?
That's kind of a smoking gun right there. You mean to say that they host miners, but don't let you mine where you want to mine?
(I don't have any link to GAW at all. I was just keeping abreast of the latest in scam when I came across this thread)
Agreed, Asicminer's BE200 is a pretty good chip. We've incorporated their boards into 2U casing, we'll release them next week.
Before you start selling stuff, you may wish to check your trust -- lots and LOTS of people have left bad feedback about you. https://bitcointalk.org/index.php?action=trust;u=152891 and click on 'show ratings'.
Re: [SSD] SonicScrewdriver [PoW/PoS] Sha256.[Tor Included]BITTREX CCEX and Bleutrade
If my coins are still on Bittrex (haven't moved them yet) will it show up as it's own address or be lumped in with exchange addresses...because I don't see my amount number on there...
If they're at bittrex, they are not on your own account. Also, as another downside for keeping them in an exchange, is the exchange will be earning PoS blocks, and not you.
Buy, move to local wallet, repeat.
Also, if your local wallet isn't running, you will not earn PoS shares, either.
Re: [SSD] SonicScrewdriver [PoW/PoS] Sha256.[Tor Included]CCEX and Bleutrade
I have my own block explorer almost ready to go just cant get the source to compile.
Or just jump on IRC and ask for help there.
Re: [SSD] SonicScrewdriver [PoW/PoS] Sha256.[Tor Included]CCEX and Bleutrade
A current richlist, before the next block halving in about 6 hours.
(Code is on my github if anyone else wants to run it)
Code:
(snipped)
(Code is on my github if anyone else wants to run it)
Im in 23rd place!! Nice!
I pointed argakiig at the parser, so hopefully he may stick that up on the block explorer page, too.
Re: [SSD] SonicScrewdriver [PoW/PoS] Sha256.[Tor Included]CCEX and Bleutrade
A current richlist, before the next block halving in about 6 hours.
(Code is on my github if anyone else wants to run it)
Code:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Balance Hash160 Base58 nbIn lastTimeIn nbOut lastTimeOut
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
1871417.35323700 52dace488926640c882667f44ac4e63489c1c340 sRoVcCQV1yEmjR3dhUpMgZup1sWjfZDNLw 526 Sat Aug 9 14:35:41 2014 20 Mon Aug 11 02:18:49 2014
1654867.98588800 1edf549eefe91b17eaa436dc9aa989c3bf6aa199 sM4dtcCxoYRLTyVc3SLmyc1UAozBKxamQ8 848 Mon Aug 11 04:09:34 2014 0 Thu Jan 1 00:00:00 1970
1368003.65000000 b09f2730e94eab097fa8d2ec037a3e0b556f7647 saMHfVCPNs9VgZ2mvRAgH2LcfrHAxM4M7K 316 Mon Aug 11 07:12:51 2014 0 Thu Jan 1 00:00:00 1970
1302836.00000000 b69bac55aad93bd4a29613b2e863487f2b84862a satwYrEet6PEXCUQndtaeDtwEpBEMABfid 2 Mon Aug 11 17:38:22 2014 0 Thu Jan 1 00:00:00 1970
1300016.70735800 fc54f3046a3f4189698f80fbcbe20221d81b53cd shFc8J5vzcDst2dkwZMV976v19BrfWqudj 1603 Mon Aug 11 20:25:10 2014 1085 Mon Aug 11 20:24:28 2014
1089617.54694300 ff271828369f485ecf1cbcca5492503b0a888a18 shWXDpDw5C48k8PR3mwRoXKDDLcVvt9hhT 905 Sun Aug 10 06:08:31 2014 0 Thu Jan 1 00:00:00 1970
961137.86000000 50ffe43754922176d6562cd5a215cc1e32cb0f6d sRdgga7KmcztLX2PpBdGDwfkFxEysnsKJA 1 Mon Aug 11 12:53:28 2014 0 Thu Jan 1 00:00:00 1970
752124.28873900 8a9d0542ff92971b62d7801c63a1c255b35749d2 sWtKS2UHbreEtFNMjxPUuk5vWzvMeaQVk1 784 Sun Aug 10 07:00:18 2014 0 Thu Jan 1 00:00:00 1970
605558.46115200 7242c7222c8f8ceec1a6c0a7a598e4bcb263cef8 sUfZ7FUMmT9tVL4wuzbQT1sBDWMXyw6mTU 987 Sun Aug 10 23:02:30 2014 332 Mon Aug 11 20:15:24 2014
599460.02336300 399f657e418599c7d40c4ab45c5d2d0fe1926ef3 sPW5YZw6rde9nPG3CC7gVQ8ocnwGbYJC7j 1 Mon Aug 11 02:20:39 2014 0 Thu Jan 1 00:00:00 1970
489606.08812800 a7a1201d58083065b20ec77bf7fb8cc97f89f2b3 sZXjwoVByia3tGnBsgZy8Q1hqC14bDfUfa 1228 Mon Aug 11 20:22:54 2014 0 Thu Jan 1 00:00:00 1970
463935.46080200 589b3a2dc0c44d5ba453763c3523b3cd8420c917 sSKuVqMR24G3BjvfXpNaAeFKBGM9xjPYxa 771 Sun Aug 10 15:17:34 2014 0 Thu Jan 1 00:00:00 1970
403164.71098000 3bd81a0d684d78505c1a97c25fa522b99fd6299b sPhppuWsQo9grizoYaRL1oz7gQt1P8PYA7 1 Mon Aug 11 14:42:59 2014 0 Thu Jan 1 00:00:00 1970
397619.69848200 0a1358c4da91716bc700ac4c952c9990c5f194ad sKAg1jD9bNuggFJAs81cwyzqopkERfTGvN 59 Mon Aug 11 19:06:02 2014 0 Thu Jan 1 00:00:00 1970
389650.26693500 d31b6d2c7d7ba27d00e1bfe15cab5d972fa19940 sdVdWg4fdbQUHTwA6y4YZiJWkn6WT4Gfe5 70 Mon Aug 11 19:39:41 2014 0 Thu Jan 1 00:00:00 1970
388828.00000000 56d3788da6e29a5c89ef5aed0123b6c5a9a1c167 sSAVXKzF5q4KJHnJWmcrJu31jHvaNzXjmi 1 Mon Aug 11 10:45:00 2014 0 Thu Jan 1 00:00:00 1970
352410.78353700 ce588297bfff598de03c665ad3e681e8d80283c8 sd4TJtA4KwTBgKa64EsxnonQTCXJh1rcrJ 2 Mon Aug 11 20:00:48 2014 0 Thu Jan 1 00:00:00 1970
275909.07060900 e0e38aef6efb6286b9e1afaecbdb647a95f5da0c sekW2VLN4PZPzMx9dYEbdeJFM4zS1fHsuh 4 Mon Aug 11 20:04:18 2014 0 Thu Jan 1 00:00:00 1970
240000.00000000 9edbcaac325ced69c49c56974e54a3fe3f41c12c sYjN9H4maH85G1NSCUGxQ4WcRiTaEqwDek 4 Mon Aug 11 20:15:24 2014 0 Thu Jan 1 00:00:00 1970
239516.10718100 6c7b63056f1f2ea2644dc1e60fb5f439beb02b03 sU8zsMftrfbvBdxzyroFbzYdYvS42Lqvce 1 Mon Aug 11 08:09:24 2014 0 Thu Jan 1 00:00:00 1970
214498.76725800 47f3cba7fee965259fb6427189e5812f9a0b3014 sQor7QRp1jxFr2qtfrD7UPBJrTiAu92VbD 1193 Mon Aug 11 12:59:30 2014 0 Thu Jan 1 00:00:00 1970
211376.70913700 dcf3f655d8c8a78f60952cc41d312cfc48f1de1d sePgza5HQh5QP1EZGeozf6tutWpPXiBMfE 538 Mon Aug 11 16:58:36 2014 0 Thu Jan 1 00:00:00 1970
209499.85699900 98afb8c34c16a74148c586050b7d8a4f2b7b609b sYAjJ6Jo9YNiJ2tkpFZkdD79csM4oY43Ti 209 Mon Aug 11 20:22:54 2014 0 Thu Jan 1 00:00:00 1970
186887.31075400 5107f4e8dee0ff166bdee892c510d9d354e62d1a sRdrLxBVRb9tUgXavmmXuL8ftSpiwWiRud 5 Mon Aug 11 19:39:41 2014 0 Thu Jan 1 00:00:00 1970
177362.56668200 ad836a42d78833c7f6b52f3b39967e11a2bb5c51 sa4rQe8GqF6zKKdLMh81QJXjknLigpGqFL 121 Mon Aug 11 17:40:27 2014 0 Thu Jan 1 00:00:00 1970
169948.88529300 a6830424a60b1bcd36922964a4749cf5ea18f95f sZRqCaieeTVkUzocSBZ9t7PiH5pfqxNJLQ 637 Mon Aug 11 20:22:54 2014 0 Thu Jan 1 00:00:00 1970
149071.92714900 31f51ecc6e89acaf8cbddf38a5102ddf0d626180 sNoYqENoYPLeLYftSSJvuVbMvbkc7dzdbW 1168 Mon Aug 11 20:22:54 2014 0 Thu Jan 1 00:00:00 1970
136003.00000000 eb08847e9c5505644fcecd5e70189b276d8da0a8 sfg95TuFNAantpBRemd7Jsa9b9Mraqjv2z 1 Mon Aug 11 08:59:51 2014 0 Thu Jan 1 00:00:00 1970
135000.00000000 baf8932cb1f6137009b89b6aee938de490b7b2a2 sbJ1YYNAuTCCPSZ4R8j4ysqfHdUqEmR4fP 9 Mon Aug 11 17:08:41 2014 0 Thu Jan 1 00:00:00 1970
133315.42020500 459b255b6befe7ece87bc5e3affcb8cfdb080712 sQbSZYBhZn35K97Hx8fzi3QmpWCPP9jPS9 696 Sun Aug 10 01:09:47 2014 4 Mon Aug 11 20:15:24 2014
125000.00000000 400e2e6818a842cec7da9951aa51bba0eaa21582 sQ66KBcGXPzvtqtJYDNB2THSFP9vUTpga5 6 Mon Aug 11 15:11:42 2014 1 Mon Aug 11 16:47:09 2014
123138.04902800 1e564ff3bb3c19e38505db4574dac18e63acb105 sM1okQxEPgSkpmx4hp3763s2fu3N7yHNoL 438 Sun Aug 10 19:50:19 2014 0 Thu Jan 1 00:00:00 1970
108000.00000000 93139311890b6b6465f7b04410d7e55617e943c4 sXf4rqEgSzpbDgzz6jFMztTVeyimnUfNtZ 7 Sun Aug 10 17:57:43 2014 0 Thu Jan 1 00:00:00 1970
106000.24050000 999a4ebc810f9f9e6d1336310d24115717b5b9f5 sYFaKQFtjz5VtgTpajpqbVLR6CoZidCnPG 1810 Mon Aug 11 20:20:46 2014 5 Sat Aug 9 07:21:43 2014
101000.00000000 35d10dd5b04a5bd95b5edf9627471587275d5b97 sP9xL54CZ4SgbyyMTKe3y6DndxWkExrBXo 5 Sun Aug 10 17:57:43 2014 0 Thu Jan 1 00:00:00 1970
100000.00000000 3d706d6c2f68027d79e6fb9b5c1f06b132b722b1 sPrFysThuEaRs2vC1t2MCXxPSmhyMvujrr 1 Sat Aug 9 07:21:43 2014 0 Thu Jan 1 00:00:00 1970
100000.00000000 76f41ca317592862c3231042122c2f33f276fed5 sV6NFQ9QBDnAeMFwBepHXcTn9WDBuoFU4n 2 Mon Aug 11 13:32:43 2014 1 Mon Aug 11 16:47:09 2014
99675.68823700 891f3218596e2cc96af0185222726337bac16402 sWkS2NN34dRNhdZFF172WBUUdYAz1iJqNV 554 Mon Aug 11 14:40:09 2014 8 Mon Aug 11 00:32:03 2014
Balance Hash160 Base58 nbIn lastTimeIn nbOut lastTimeOut
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
1871417.35323700 52dace488926640c882667f44ac4e63489c1c340 sRoVcCQV1yEmjR3dhUpMgZup1sWjfZDNLw 526 Sat Aug 9 14:35:41 2014 20 Mon Aug 11 02:18:49 2014
1654867.98588800 1edf549eefe91b17eaa436dc9aa989c3bf6aa199 sM4dtcCxoYRLTyVc3SLmyc1UAozBKxamQ8 848 Mon Aug 11 04:09:34 2014 0 Thu Jan 1 00:00:00 1970
1368003.65000000 b09f2730e94eab097fa8d2ec037a3e0b556f7647 saMHfVCPNs9VgZ2mvRAgH2LcfrHAxM4M7K 316 Mon Aug 11 07:12:51 2014 0 Thu Jan 1 00:00:00 1970
1302836.00000000 b69bac55aad93bd4a29613b2e863487f2b84862a satwYrEet6PEXCUQndtaeDtwEpBEMABfid 2 Mon Aug 11 17:38:22 2014 0 Thu Jan 1 00:00:00 1970
1300016.70735800 fc54f3046a3f4189698f80fbcbe20221d81b53cd shFc8J5vzcDst2dkwZMV976v19BrfWqudj 1603 Mon Aug 11 20:25:10 2014 1085 Mon Aug 11 20:24:28 2014
1089617.54694300 ff271828369f485ecf1cbcca5492503b0a888a18 shWXDpDw5C48k8PR3mwRoXKDDLcVvt9hhT 905 Sun Aug 10 06:08:31 2014 0 Thu Jan 1 00:00:00 1970
961137.86000000 50ffe43754922176d6562cd5a215cc1e32cb0f6d sRdgga7KmcztLX2PpBdGDwfkFxEysnsKJA 1 Mon Aug 11 12:53:28 2014 0 Thu Jan 1 00:00:00 1970
752124.28873900 8a9d0542ff92971b62d7801c63a1c255b35749d2 sWtKS2UHbreEtFNMjxPUuk5vWzvMeaQVk1 784 Sun Aug 10 07:00:18 2014 0 Thu Jan 1 00:00:00 1970
605558.46115200 7242c7222c8f8ceec1a6c0a7a598e4bcb263cef8 sUfZ7FUMmT9tVL4wuzbQT1sBDWMXyw6mTU 987 Sun Aug 10 23:02:30 2014 332 Mon Aug 11 20:15:24 2014
599460.02336300 399f657e418599c7d40c4ab45c5d2d0fe1926ef3 sPW5YZw6rde9nPG3CC7gVQ8ocnwGbYJC7j 1 Mon Aug 11 02:20:39 2014 0 Thu Jan 1 00:00:00 1970
489606.08812800 a7a1201d58083065b20ec77bf7fb8cc97f89f2b3 sZXjwoVByia3tGnBsgZy8Q1hqC14bDfUfa 1228 Mon Aug 11 20:22:54 2014 0 Thu Jan 1 00:00:00 1970
463935.46080200 589b3a2dc0c44d5ba453763c3523b3cd8420c917 sSKuVqMR24G3BjvfXpNaAeFKBGM9xjPYxa 771 Sun Aug 10 15:17:34 2014 0 Thu Jan 1 00:00:00 1970
403164.71098000 3bd81a0d684d78505c1a97c25fa522b99fd6299b sPhppuWsQo9grizoYaRL1oz7gQt1P8PYA7 1 Mon Aug 11 14:42:59 2014 0 Thu Jan 1 00:00:00 1970
397619.69848200 0a1358c4da91716bc700ac4c952c9990c5f194ad sKAg1jD9bNuggFJAs81cwyzqopkERfTGvN 59 Mon Aug 11 19:06:02 2014 0 Thu Jan 1 00:00:00 1970
389650.26693500 d31b6d2c7d7ba27d00e1bfe15cab5d972fa19940 sdVdWg4fdbQUHTwA6y4YZiJWkn6WT4Gfe5 70 Mon Aug 11 19:39:41 2014 0 Thu Jan 1 00:00:00 1970
388828.00000000 56d3788da6e29a5c89ef5aed0123b6c5a9a1c167 sSAVXKzF5q4KJHnJWmcrJu31jHvaNzXjmi 1 Mon Aug 11 10:45:00 2014 0 Thu Jan 1 00:00:00 1970
352410.78353700 ce588297bfff598de03c665ad3e681e8d80283c8 sd4TJtA4KwTBgKa64EsxnonQTCXJh1rcrJ 2 Mon Aug 11 20:00:48 2014 0 Thu Jan 1 00:00:00 1970
275909.07060900 e0e38aef6efb6286b9e1afaecbdb647a95f5da0c sekW2VLN4PZPzMx9dYEbdeJFM4zS1fHsuh 4 Mon Aug 11 20:04:18 2014 0 Thu Jan 1 00:00:00 1970
240000.00000000 9edbcaac325ced69c49c56974e54a3fe3f41c12c sYjN9H4maH85G1NSCUGxQ4WcRiTaEqwDek 4 Mon Aug 11 20:15:24 2014 0 Thu Jan 1 00:00:00 1970
239516.10718100 6c7b63056f1f2ea2644dc1e60fb5f439beb02b03 sU8zsMftrfbvBdxzyroFbzYdYvS42Lqvce 1 Mon Aug 11 08:09:24 2014 0 Thu Jan 1 00:00:00 1970
214498.76725800 47f3cba7fee965259fb6427189e5812f9a0b3014 sQor7QRp1jxFr2qtfrD7UPBJrTiAu92VbD 1193 Mon Aug 11 12:59:30 2014 0 Thu Jan 1 00:00:00 1970
211376.70913700 dcf3f655d8c8a78f60952cc41d312cfc48f1de1d sePgza5HQh5QP1EZGeozf6tutWpPXiBMfE 538 Mon Aug 11 16:58:36 2014 0 Thu Jan 1 00:00:00 1970
209499.85699900 98afb8c34c16a74148c586050b7d8a4f2b7b609b sYAjJ6Jo9YNiJ2tkpFZkdD79csM4oY43Ti 209 Mon Aug 11 20:22:54 2014 0 Thu Jan 1 00:00:00 1970
186887.31075400 5107f4e8dee0ff166bdee892c510d9d354e62d1a sRdrLxBVRb9tUgXavmmXuL8ftSpiwWiRud 5 Mon Aug 11 19:39:41 2014 0 Thu Jan 1 00:00:00 1970
177362.56668200 ad836a42d78833c7f6b52f3b39967e11a2bb5c51 sa4rQe8GqF6zKKdLMh81QJXjknLigpGqFL 121 Mon Aug 11 17:40:27 2014 0 Thu Jan 1 00:00:00 1970
169948.88529300 a6830424a60b1bcd36922964a4749cf5ea18f95f sZRqCaieeTVkUzocSBZ9t7PiH5pfqxNJLQ 637 Mon Aug 11 20:22:54 2014 0 Thu Jan 1 00:00:00 1970
149071.92714900 31f51ecc6e89acaf8cbddf38a5102ddf0d626180 sNoYqENoYPLeLYftSSJvuVbMvbkc7dzdbW 1168 Mon Aug 11 20:22:54 2014 0 Thu Jan 1 00:00:00 1970
136003.00000000 eb08847e9c5505644fcecd5e70189b276d8da0a8 sfg95TuFNAantpBRemd7Jsa9b9Mraqjv2z 1 Mon Aug 11 08:59:51 2014 0 Thu Jan 1 00:00:00 1970
135000.00000000 baf8932cb1f6137009b89b6aee938de490b7b2a2 sbJ1YYNAuTCCPSZ4R8j4ysqfHdUqEmR4fP 9 Mon Aug 11 17:08:41 2014 0 Thu Jan 1 00:00:00 1970
133315.42020500 459b255b6befe7ece87bc5e3affcb8cfdb080712 sQbSZYBhZn35K97Hx8fzi3QmpWCPP9jPS9 696 Sun Aug 10 01:09:47 2014 4 Mon Aug 11 20:15:24 2014
125000.00000000 400e2e6818a842cec7da9951aa51bba0eaa21582 sQ66KBcGXPzvtqtJYDNB2THSFP9vUTpga5 6 Mon Aug 11 15:11:42 2014 1 Mon Aug 11 16:47:09 2014
123138.04902800 1e564ff3bb3c19e38505db4574dac18e63acb105 sM1okQxEPgSkpmx4hp3763s2fu3N7yHNoL 438 Sun Aug 10 19:50:19 2014 0 Thu Jan 1 00:00:00 1970
108000.00000000 93139311890b6b6465f7b04410d7e55617e943c4 sXf4rqEgSzpbDgzz6jFMztTVeyimnUfNtZ 7 Sun Aug 10 17:57:43 2014 0 Thu Jan 1 00:00:00 1970
106000.24050000 999a4ebc810f9f9e6d1336310d24115717b5b9f5 sYFaKQFtjz5VtgTpajpqbVLR6CoZidCnPG 1810 Mon Aug 11 20:20:46 2014 5 Sat Aug 9 07:21:43 2014
101000.00000000 35d10dd5b04a5bd95b5edf9627471587275d5b97 sP9xL54CZ4SgbyyMTKe3y6DndxWkExrBXo 5 Sun Aug 10 17:57:43 2014 0 Thu Jan 1 00:00:00 1970
100000.00000000 3d706d6c2f68027d79e6fb9b5c1f06b132b722b1 sPrFysThuEaRs2vC1t2MCXxPSmhyMvujrr 1 Sat Aug 9 07:21:43 2014 0 Thu Jan 1 00:00:00 1970
100000.00000000 76f41ca317592862c3231042122c2f33f276fed5 sV6NFQ9QBDnAeMFwBepHXcTn9WDBuoFU4n 2 Mon Aug 11 13:32:43 2014 1 Mon Aug 11 16:47:09 2014
99675.68823700 891f3218596e2cc96af0185222726337bac16402 sWkS2NN34dRNhdZFF172WBUUdYAz1iJqNV 554 Mon Aug 11 14:40:09 2014 8 Mon Aug 11 00:32:03 2014
(Code is on my github if anyone else wants to run it)
And, just as a reminder, the coin has been proven to be broken and insecure.
https://docs.google.com/document/d/1d8dwuGznri35uNHDxhUcRDXD0I8afKN9R3G3oPNhBbo
https://docs.google.com/document/d/1d8dwuGznri35uNHDxhUcRDXD0I8afKN9R3G3oPNhBbo
Re: [SSD] SonicScrewdriver [15 day PoW 20% POS annually] Sha256. Ninja Launch
I notice that we've just clicked over block 1400, and the reward is still 8000 SSD?
Edit: Looking at the code, the original post is in error. The post currently says 'Rewards halving every 1400 blocks', when it's actually every 1440.
(etc).
Edit: Looking at the code, the original post is in error. The post currently says 'Rewards halving every 1400 blocks', when it's actually every 1440.
Code:
if (nHeight == 0)
nSubsidy = 16 * COIN; // genesis block coinbase is unspendable
else if (nHeight <= 1440)
nSubsidy = 8000 * COIN;
else if (nHeight <= 2880)
nSubsidy = 16 * COIN; // genesis block coinbase is unspendable
else if (nHeight <= 1440)
nSubsidy = 8000 * COIN;
else if (nHeight <= 2880)
(etc).
The number of confirmations you have to wait for is not relevant. As I pointed out above, by having a block time that is so short, it's amazingly easy to do a 51% attack, without actually having 51% of the coin's hashrate.
I did explain this to the dev, but he said that he knew better, and he was right, and I was wrong.
Here's how it works.
There is the public 'good' chain. It is mining along at.. let's say (for ease of counting) 12TH. It's split up amongst 3 pools, and each of them have 4TH each (That means that the coin will be asking for difficulty 30000-ish blocks, btw)
We live in a universe where there is a finite speed of light. There is an amount of time it takes for Pool A (that mined the coin) to send it to the other pools, and other coinds. This is the network latency time. In bitcoind it takes, on average, 4 seconds (and that's an average, not a mean. Mean is much higher) for a block to propogate to 90% of the nodes. (These numbers are from memory. They're roughly accurate, but not exact. They won't be an order of magnitude out). Whatever the time in una is, it's an amount.. I'm going to keep on at 4 seconds, because the exact number doesn't actually matter.
If we work on 4 seconds, then roughly -half- of the blocks that are mined, will be mined within the same window. There will be two valid blocks, and only one of them will be accepted by the blockchain.
So that brings the -effective- hashing rate of the coin down to 6TH. Everyone's hashes who mined the rejected coins were wasted.
Along comes Mr 'I actually HAVE a clue' who understands this. He goes and rents 4TH of SHA mining, and sets up his own coind. He's going to solomine, to his own pool. His own pool isn't GOING to have any orphans, because he's always going to mine to his chain. He'll never accept a block mined by someone else.
He is, however, going to spam his blocks out, so that everyone else must discard what they're doing (on the non-evil chain), and start working on the new (evil) block.
Now, we have 4TH of 100% guaranteed never-gunna-orphan, and 6TH of 25% chance of orphaning (we still have network latency, but now it's only half as likely).
So there's your first 51% attack. It's pretty visible though, as people watching the blockchain will notice.
The second one is much sneakier, and kinda awesome. Basically, the second one runs his own parallel blockchain. Same deal, it'll never orphan (so you only need 25%-ish), BUT, he doesn't send his blockchain out until AFTER his double spend is completed.
This one is much easier to manage, as you can control the hashrate exactly to encourage more blocks to be mined than the public chain.
I am, admittedly, glossing over the hard-er bits. I encourage anyone who's actually interested in this to watch the upcoming Dogecoin double spend attack, which is going to be using option 1 I believe, from what I've read.
I did explain this to the dev, but he said that he knew better, and he was right, and I was wrong.
Here's how it works.
There is the public 'good' chain. It is mining along at.. let's say (for ease of counting) 12TH. It's split up amongst 3 pools, and each of them have 4TH each (That means that the coin will be asking for difficulty 30000-ish blocks, btw)
We live in a universe where there is a finite speed of light. There is an amount of time it takes for Pool A (that mined the coin) to send it to the other pools, and other coinds. This is the network latency time. In bitcoind it takes, on average, 4 seconds (and that's an average, not a mean. Mean is much higher) for a block to propogate to 90% of the nodes. (These numbers are from memory. They're roughly accurate, but not exact. They won't be an order of magnitude out). Whatever the time in una is, it's an amount.. I'm going to keep on at 4 seconds, because the exact number doesn't actually matter.
If we work on 4 seconds, then roughly -half- of the blocks that are mined, will be mined within the same window. There will be two valid blocks, and only one of them will be accepted by the blockchain.
So that brings the -effective- hashing rate of the coin down to 6TH. Everyone's hashes who mined the rejected coins were wasted.
Along comes Mr 'I actually HAVE a clue' who understands this. He goes and rents 4TH of SHA mining, and sets up his own coind. He's going to solomine, to his own pool. His own pool isn't GOING to have any orphans, because he's always going to mine to his chain. He'll never accept a block mined by someone else.
He is, however, going to spam his blocks out, so that everyone else must discard what they're doing (on the non-evil chain), and start working on the new (evil) block.
Now, we have 4TH of 100% guaranteed never-gunna-orphan, and 6TH of 25% chance of orphaning (we still have network latency, but now it's only half as likely).
So there's your first 51% attack. It's pretty visible though, as people watching the blockchain will notice.
The second one is much sneakier, and kinda awesome. Basically, the second one runs his own parallel blockchain. Same deal, it'll never orphan (so you only need 25%-ish), BUT, he doesn't send his blockchain out until AFTER his double spend is completed.
This one is much easier to manage, as you can control the hashrate exactly to encourage more blocks to be mined than the public chain.
I am, admittedly, glossing over the hard-er bits. I encourage anyone who's actually interested in this to watch the upcoming Dogecoin double spend attack, which is going to be using option 1 I believe, from what I've read.
U better pay me back my btc scammer... (bitspender) Angry Instead of posting here on bctalk, w8tch out people.. this guy is bad news...
You know, I'm kind of unsurprised that he's being accused of being a scammer. Their behaviour in IRC is .. odd, to put it mildly.
Quote
<Unattainium> If you had any idea who you were talking to, you would know I definitely know what I'm doing
And yet, he/she is not saying who he/she is?
Quote
There is a bug. I see and understand the bug. You don't, or claim not to understand the bug. That's.. pretty much it. You're the one with access to the code, so, i fyou want to leave it broken, there's not much I can do about it, apart from warn other people.
<Unattainium> Ok, give me the bug
<Unattainium> "I don't like fast block times"
I have. Several times.
No, that's not the bug
<Unattainium> Not a bug
<Unattainium> Ok
<Unattainium> I'm like
← You were kicked by Unattainium (175c3d62@gateway/web/freenode/ip.23.92.61.98): wibble
→ X-Rob joined (X-Rob@gateway/web/irccloud.com/x-boeazzlbzlokrgfu)
Channel mode is +cnt
Heh
So
here's the bug
'8 second block times are insecure'
<Unattainium> Meant to ignore not kick
<Unattainium> That was my bad
now, you can either claim it's not a bug, which is factually false
or, you can say that you're aware of the issue, and it's fixed because of xyz.
or, you can say something else.
<Unattainium> For the record, I can't see what you're typing anymore. I'll just wait until you crawl to the forums to try and get someone as equally ill informed to agree with you
I have an 8 year old son who does that. Puts his hands over his ears and goes 'LALALALA I CAN'T HEAR YOU' when you're saying something he doesn't want to hear.<Unattainium> Ok, give me the bug
<Unattainium> "I don't like fast block times"
I have. Several times.
No, that's not the bug
<Unattainium> Not a bug
<Unattainium> Ok
<Unattainium> I'm like
← You were kicked by Unattainium (175c3d62@gateway/web/freenode/ip.23.92.61.98): wibble
→ X-Rob joined (X-Rob@gateway/web/irccloud.com/x-boeazzlbzlokrgfu)
Channel mode is +cnt
Heh
So
here's the bug
'8 second block times are insecure'
<Unattainium> Meant to ignore not kick
<Unattainium> That was my bad
now, you can either claim it's not a bug, which is factually false
or, you can say that you're aware of the issue, and it's fixed because of xyz.
or, you can say something else.
<Unattainium> For the record, I can't see what you're typing anymore. I'll just wait until you crawl to the forums to try and get someone as equally ill informed to agree with you
Quote
And.. he -still- hasn't adressed the latency issue.
This is amazingly hilarious.
Yes, it was made not to work. The whole idea make it so no one wanted to go though the trouble to "obtain" it.
There's a difference between 'making it hard to obtain' and 'making it amazingly easy to perform a 51% attack and all the bad that that entails'.
Edit: Attack occurred, and the coin is, indeed, vulnerable. I wrote a small paper on it, that's available here:
https://docs.google.com/document/d/1d8dwuGznri35uNHDxhUcRDXD0I8afKN9R3G3oPNhBbo
It's only three pages, and contains far too much maths and hypotheticals. However, instructions for taking over the coin yourself are in the last section.
For those that are unaware, Unattanium is a newish limited-number-of-coins SHA coin.
They've recently had to fork the chain, because the difficulty calculations were broken, and it went far too high. Sadly, they've now broken it in the other direction, and the dev seems intent on ignoring this, and abusing or hand-waving the problems away.
It's now running at an 8 second block time.
Now, for everyone who is NOT facepalming right now, this is faster than blockchain propagation. Basically, it will be amazingly difficulty for the coin to agree on a valid chain, because there will be any number of chains that are almost the same length.
So, After being asked to help out to fix the stuck difficulty, I jumped on their IRC channel and had a discussion with someone called 'Unattanium' who was opped in the channel mentioned on their website.
I phrase that carefully, because I'd hate to slander someone who actually knows what he or she is doing. Because this person didn't.
Anyway, rather than addressing the issue, he (I'm assuming this person is a male. I apologise if you're not) said things like...
Which is obviously wrong. All I, as a bad guy, need to do is to have more hash rate than you, the innocent miner. At 8 seconds, it's highly unlikely that your block will even have reached me before I mine my next one, leaving me to perform a 51% attack with much less than 51% - it would be (coin hashrate * 0.51)/(average block latency time / coin block time)
Average block latency from bitcoind is around 4 seconds. Or, basically, I can now perform a 51% attack with only 25% of the coin.
So there you go, people. Fixing a design flaw in the change, that was to FIX a design flaw, is not worth his or her time.
Of course the next design flaw, which will be implemented to fix this design flaw, will be be something awesomely terrible, and I can't wait to see what it is.
Edit: The next design flaw, which was implemented ... for no real reason that I could see, was to randomise the reward, leaving the block times the same, but not giving anyone any notice. So yes. It was awesomely terrible.
Have fun now.
https://docs.google.com/document/d/1d8dwuGznri35uNHDxhUcRDXD0I8afKN9R3G3oPNhBbo
It's only three pages, and contains far too much maths and hypotheticals. However, instructions for taking over the coin yourself are in the last section.
For those that are unaware, Unattanium is a newish limited-number-of-coins SHA coin.
They've recently had to fork the chain, because the difficulty calculations were broken, and it went far too high. Sadly, they've now broken it in the other direction, and the dev seems intent on ignoring this, and abusing or hand-waving the problems away.
It's now running at an 8 second block time.
Now, for everyone who is NOT facepalming right now, this is faster than blockchain propagation. Basically, it will be amazingly difficulty for the coin to agree on a valid chain, because there will be any number of chains that are almost the same length.
So, After being asked to help out to fix the stuck difficulty, I jumped on their IRC channel and had a discussion with someone called 'Unattanium' who was opped in the channel mentioned on their website.
I phrase that carefully, because I'd hate to slander someone who actually knows what he or she is doing. Because this person didn't.
Anyway, rather than addressing the issue, he (I'm assuming this person is a male. I apologise if you're not) said things like...
Quote
<Unattainium> and who cares about orphans
<Unattainium> it doesnt break a chain or anything
<Unattainium> i dont care if it fucks up miner ui or stats
Well. Everyone who's mining cares about orphan shares.
uh orphan blocks
<Unattainium> Everyone will be on the same playing field
Well no
<Unattainium> I'll get the same amount of orphans are you
<Unattainium> as you*
<Unattainium> it doesnt break a chain or anything
<Unattainium> i dont care if it fucks up miner ui or stats
Well. Everyone who's mining cares about orphan shares.
uh orphan blocks
<Unattainium> Everyone will be on the same playing field
Well no
<Unattainium> I'll get the same amount of orphans are you
<Unattainium> as you*
Which is obviously wrong. All I, as a bad guy, need to do is to have more hash rate than you, the innocent miner. At 8 seconds, it's highly unlikely that your block will even have reached me before I mine my next one, leaving me to perform a 51% attack with much less than 51% - it would be (coin hashrate * 0.51)/(average block latency time / coin block time)
Average block latency from bitcoind is around 4 seconds. Or, basically, I can now perform a 51% attack with only 25% of the coin.
Quote
if your'e going to claim I'm wrong, you'll need to actually back that up.
<Unattainium> You're spewing nonsense\
Yet, here I am, saying I'm not.
<Unattainium> I'm just gonna stop responding
And you're yet to provide proof that I am
<Unattainium> Beacuse I think you are either a) ignorant as fuck, or b) trolling hard
I'm neither
<Unattainium> there is no option c
I'm trying to fix a problem that you seem to be deliberately ignoring
problem is: 8 seconds is far too short.
<Unattainium> I'm done
<Unattainium> Not worth my time
<Unattainium> You're spewing nonsense\
Yet, here I am, saying I'm not.
<Unattainium> I'm just gonna stop responding
And you're yet to provide proof that I am
<Unattainium> Beacuse I think you are either a) ignorant as fuck, or b) trolling hard
I'm neither
<Unattainium> there is no option c
I'm trying to fix a problem that you seem to be deliberately ignoring
problem is: 8 seconds is far too short.
<Unattainium> I'm done
<Unattainium> Not worth my time
So there you go, people. Fixing a design flaw in the change, that was to FIX a design flaw, is not worth his or her time.
Of course the next design flaw, which will be implemented to fix this design flaw, will be be something awesomely terrible, and I can't wait to see what it is.
Edit: The next design flaw, which was implemented ... for no real reason that I could see, was to randomise the reward, leaving the block times the same, but not giving anyone any notice. So yes. It was awesomely terrible.
Have fun now.
Re: Announcement: A1 28NM 2TH/S Asic miner 1.15$/G delivery time in 2 days
Hi everyone!
IS ANYBODY from REAL Members of this FORUM bought this miners?
Is it scam or this company are real? Is it can be trusted?
IS ANYBODY from REAL Members of this FORUM bought this miners?
Is it scam or this company are real? Is it can be trusted?
I have bought a 2TH miner from this guys. I was massively unimpressed with the hardware, which was damaged in transit, underspecced, and used much more power than originally stated.
So yes, they exist. They do actually send hardware out. Check my profile history for photos of what arrived.