pool.mn is on true block now?
Yes.
|
|
|
Pool.mn was initially what you call the official fork - the first block the pool has found was block 66, however most of the hashrate was on another fork, so I've deleted the blockchain and downloaded the new one with 4 nodes that dev gave. This new blockchain turned out to be the one where dedicatedpool is. Try deleting your blockchain and downloading the fresh one
|
|
|
make[1]: *** No rule to make target `libleveldb.a'. Stop.
|
|
|
I've officially earned more in the last 10 minutes with hyper.dgbpool.com than I did for over 4 hours with hyper.pool.mn.......makes no sense to me but glad I switched!
The pool's crons were didn't work for 8 hours, that is why you haven't seen any coins in your account. This has been resolved, please check your account balance.
|
|
|
http://hyper.pool.mnThe pool is up and running!0% fees Powerful dedicated server DDOS Protection Friendly support via email, jabber or support forums Skilled admin Please, join us
|
|
|
The pool is up and running!0% fees Powerful dedicated server DDOS Protection Friendly support via email, jabber or support forums Skilled admin Please, join us
|
|
|
There are some problems with scrypt algo - difficulty is too low but it is not possible to find blocks. Moreover, blocks are literally raining, more than 1 block/sec are being generated.
|
|
|
So.. what will happening with this lucky block? Who will get him? This lucky block is being shared by everyone who was mining on our pool for that particular block. Btw, it seems that there are some problems with the wallet and lucky blocks . The first lucky block that http://super.pool.mn has found had the same height 332 and same blockhash as the regular block (i.e. lucky block is actually just another block with 3*512 = 1536 coins and the same height and blockhash) and this creates problems at the front end. We will add 1536 coins to the next block the pool finds as these coins were not properly accounted in block with height 332. Moreover, the block with height 368 had only 1536 coins and there was no regular block of 512 coins with the same height and blockhash. It would be good if dev could comment on this. This is how the superblock works. You use the hash of that block to determine if the block is a superblock or not, but there is a paradox there: in order to determine the hash, you need the payout value, but the payout value depends on whether the block is a superblock or not. This true randomness solved this problem nicely. And this is how it works: - each block will have a normal payout (in this case 512). - the hash is computed and then we determine is the hash is a superblock hash or not - if it is not, then nothing happens - if it is a superblock, then we create a new payout with (n-1)*512, n=4 in your case, you get 3*512 = 1536 coins, and this is created as the supplement of the last block (in next block), and it is sent to the same address that receives the last block. So the person who found the superblock, will get 512+1536 = 2048 coins in total. Therefore, the supercoin worked perfectly! BTW, the true random is not invented in SuperCoin, I saw it in some other coins such as JackpotCoin, but I believe the dev of Graincoin first invented it. Thanks for explaining!
|
|
|
So.. what will happening with this lucky block? Who will get him? This lucky block is being shared by everyone who was mining on our pool for that particular block. Btw, it seems that there are some problems with the wallet and lucky blocks . The first lucky block that http://super.pool.mn has found had the same height 332 and same blockhash as the regular block (i.e. lucky block is actually just another block with 3*512 = 1536 coins and the same height and blockhash) and this creates problems at the front end. We will add 1536 coins to the next block the pool finds as these coins were not properly accounted in block with height 332. Moreover, the block with height 368 had only 1536 coins and there was no regular block of 512 coins with the same height and blockhash. It would be good if dev could comment on this.
|
|
|
Guys, this is not the dev premining. The source was on GitHub hours before launch, for anyone to find. Some pool(s) obviously installed it and launched. Take note of the pools in the official list in the OP - these are the problem here.
I've posted the source code once I've found it on github, block chain was on block 433 when I've compiled the wallet and I've decided to launch the pool. I wrote about this in the thread. I'm not saying it was you specifically. There's a lot of pools in the main list - it could be a few of them. I gave the source code to everyone. No one has bothered to comment. EDIT: http://acc.hashhot.com/index.php?page=statistics&action=round&height=10&prev=1Definitely Hashhot. They really need to be blacklisted as a pool. I don't think they were the only one. Someone else was mining blocks from 250 until 433 (bigger reward blocks)
|
|
|
Guys, this is not the dev premining. The source was on GitHub hours before launch, for anyone to find. Some pool(s) obviously installed it and launched. Take note of the pools in the official list in the OP - these are the problem here.
I've posted the source code once I've found it on github, block chain was on block 433 when I've compiled the wallet and I've decided to launch the pool. I wrote about this in the thread. I'm not saying it was you specifically. There's a lot of pools in the main list - it could be a few of them. I gave the source code to everyone. No one has bothered to comment.
|
|
|
Guys, this is not the dev premining. The source was on GitHub hours before launch, for anyone to find. Some pool(s) obviously installed it and launched. Take note of the pools in the official list in the OP - these are the problem here.
I've posted the source code once I've found it on github, block chain was on block 433 when I've compiled the wallet and I've decided to launch the pool. I wrote about this in the thread.
|
|
|
At least this coin as lots of legit pools I think pool.mn prevented an even bigger instamine by launching at block 433. If every pool was to wait until the launch time instamine would be even bigger. The launch was not perfect, but having a pool running from block 433 is better than having a pool running from block 700 Yes ,you are the one who had mined a lot before the launch time. In which way? I wrote about the pool on this forum (the pool had 30+ miners when it was launched) and I gave the link to the source code. Would it be better to let the mining go unnoticed?
|
|
|
At least this coin as lots of legit pools I think pool.mn prevented an even bigger instamine by launching at block 433. If every pool was to wait until the launch time instamine would be even bigger. The launch was not perfect, but having a pool running from block 433 is better than having a pool running from block 700. Moreover, I've posted the guthub link when I've compiled the wallet and saw that the block chain was active but no one bothered to say anything.
|
|
|
it still 20 minutes left ,but why pool's up already?
The coin was launched some time ago. Someone started to mine the coin even before the pool was launched. The pool started at block 433.
|
|
|
We've found this source code on github https://github.com/AccCoin/AntarcticcoinWhen I've compiled the wallet 432 blocks were already mined, so we've decided to give mining a go and currently mining is working at http://acc.pool.mn However, please bear in mind that we are not 100% sure it is the correct source code.
|
|
|
Is the launch at 17:00 GMT or 17:00 London? London is now GMT+1
|
|
|
first pool isn't finding blocks or something, no accepted share from them
The pool is finding blocks, but difficulty is very high, now on average we are finding blocks every 30-45min. Do you still have problems with accepted shares? I don't see any problems on our side. maybe your pool have low hash? didn't notice it From the available pools http://vio.pool.mn has the highest hashrate, however network hashrate is much bigger. Either multipool or some big solo miners are mining this coin.
|
|
|
first pool isn't finding blocks or something, no accepted share from them
The pool is finding blocks, but difficulty is very high, now on average we are finding blocks every 30-45min. Do you still have problems with accepted shares? I don't see any problems on our side.
|
|
|
|