Look at dedicatedpool's block statistics, every single block was mined on their pool for the first 98 blocks(!!!), including blocks 1 and 2. For any pool operator this should ring alarm bell that something is fishy about their blockchain. However, dedicatepool insisted that they are on the correct blockchain and used their reputation to force everyone to jump on their incorrect blockchain, thereby stealing the premine (I am not saying they did it because of the premine, probably they did it to get as much hashrate as possible, but this is reckless behavior).
Transaction that I gave above are from the alternative chain that is now not accepted by community and that shows what dev's premine address is, as block 1 and 2 went to this address. In order to see these transactions you would have to download that blockchain by using OP nodes and don't sync with dedicatedpool.
Blocks 1-60 were part of the premine. They went to the DEV PREMINE ADDRESS (look at the picture of the wallet in the OP).
After the premine was done, sure dedicated probably made a pretty decent headstart on the mining, but they didn't do anything as you are suggesting.
This was supposed to be, however dedicatedpool jumped start on the blockchain before nodes were up and running and they mined every single block for the first 98 blocks!!! Take a look at block statistics for dedicatedpool
http://pure.v2.dedicatedpool.com/index.php?page=statistics&action=blocks&height=13&next=1As you can see block 2 of 250k was also mined on dedicatedpool and EVERY SINGLE BLOCK FROM BLOCK 1 UNTIL BLOCK 98.
Every honest pool operator would notice that something is wrong with his blockchain when you are the only one on it but binaryclock insisted that dedicatedpool was on the correct blockchain and used his reputation to force everyone to use their forked blockchain.
No this is wrong. Merx (Trademybit) and I had exchanged nodes before the coin start. Trademybit dumped 30gh/s on it, and dedicated had 15gh/s on it. We had 10 connections then suddenly merx (trademybit) and I both forked at the start.Once we came back up, i told all my users I'd grant them the forked coins and take the hit. I noticed that my wallet was -255,000 coins and was like WTF? I checked the mysql blocks and found one block was worth 250k, block number 3. I deleted it from the mysql database and set all the orphaned blocks to confirmed so my users wouldn't be screwed out of the forked blocks.If you deleted block #3 from your database then why is it showing as found block in dedicatepool's block statistics. Apparently, you have that block in your database but you are again trying to use your reputation to blame others.
Okay just checked.
I deleted the transaction not the block from the mysql. The blocks aren't even real up to 138. I kept the blocks there and confirmed them all automatically.
So yes, the block #2 shows as 250k but that was on the fork.
Here is the mysqldump from the orphaned forks:
select * from blocks order by height limit 5;
+----+--------+------------------------------------------------------------------+---------------+--------+------------+------------+-----------+------------+-------------+--------+----------+
| id | height | blockhash | confirmations | amount | difficulty | time | accounted | account_id | worker_name | shares | share_id |
+----+--------+------------------------------------------------------------------+---------------+--------+------------+------------+-----------+------------+-------------+--------+----------+
| 40 | 1 | 00000050c8cfdcf3172c1a94e2377c57863022952474c5de29e79157eeed8181 | 120 | 1 | 0.00024414 | 1401393857 | 1 | -- | --- | 1 | 1 |
| 78 | 2 |
0000009e3d5a320d788bba0e08ef2f1bad2b185652c882b72ce2aed921536be1 | 120 | 250000 | 0.00024414 | 1401393859 | 1 | -- | --- | 2 | 3 |
| 65 | 3 | 00000044db58ce33ca0d172e209ba9f3fd575ac9ca4a2663c0755d2896d66cc2 | 120 | 1 | 0.00026858 | 1401393859 | 1 | -- | --- | 1 | 5 |
| 33 | 4 | 0000001b12ad7fe6d2bfe23cbf5ef3a3a3061013930268e7db2f3114a94c88a3 | 120 | 1 | 0.00029685 | 1401393860 | 1 | --| --- | 1 | 6 |
| 66 | 5 | 0000004e036759e7f53a59c3a53e75c4c846d334c7c0d5b649d4d3bf31559523 | 120 | 1 | 0.00032733 | 1401393863 | 1 | -- | --- | 1 | 7 |
+----+--------+------------------------------------------------------------------+---------------+--------+------------+------------+-----------+------------+-------------+--------+----------+
Please do a blockhash check on the forked chain and the real chain.
I'll do some for you..
PureCoind getblockhash 1
000008558c3b917ba58709506d6064b689ea4681a9fe583efb0dc37c17996766
PureCoind getblockhash 2
0000089c0df55f9b360b3a8aded563ace1042148b93839176eff84b7d957f088You can see, the blockhashes are different!!!
Comon guys, enough with this FUD.
Work with me here... can someone who has a brain speak up instead of people who have no idea how crypto works?
http://dedicatedpool.comRyan, dedicatedpool.com support/admin
[email protected] / IRC on freenode ##dedicatedpool