Honestly I don't see why the pools are jumping on this. Pushing shitcoins with 5000 block premines is something that only poolmn usually does.
Well, as you see this is not true, don't blame pool.mn again. Either way, whatever we launched and you launched during the last few weeks are all shitcoins, unfortunately. Miners need to understand we work by offer/demand.. If there are no coins to host and no miners mining, our pools won't be there.. but as long as there is a demand, we are offering! +1 |
|
|
|
Honestly I don't see why the pools are jumping on this. Pushing shitcoins with 5000 block premines is something that only poolmn usually does.
Well, as you see this is not true, don't blame pool.mn again. |
|
|
|
Pool is up from 3rd block? LOL. What a fail. Shame. Thank goodness I didn't want to launch the pool immediately right after the launch, although I've found the source on github early. It is better when suchpool is behind the instamining ))) i did not even look @ github when i saw that premine ^^ Yeah, premine is like 3.5 days of mining. Well, it is not the worst premine, after a month the premine will be like 10% )) the block timer is 2 mins I think it is 7 days of mining not 3.5 days. Oh, you are right, my bad. |
|
|
|
Pool is up from 3rd block? LOL. What a fail. Shame. Thank goodness I didn't want to launch the pool immediately right after the launch, although I've found the source on github early. It is better when suchpool is behind the instamining ))) i did not even look @ github when i saw that premine ^^ Yeah, premine is like 3.5 days of mining. Well, it is not the worst premine, after a month the premine will be like 10% )) |
|
|
|
Pool is up from 3rd block? LOL. What a fail. Shame. Thank goodness I didn't want to launch the pool immediately right after the launch, although I've found the source on github early. It is better when suchpool is behind the instamining ))) |
|
|
|
I lost 50K from pool.mn  Only hashharder is ok I think There was a fork in the network. Ask the dev why has this happened. Pools didn't cause this fork. |
|
|
|
Charity is set at 0, but the charity address is taken from ComputerCoin  I dont even bother to open again the pool , if the dev is s.... and he did not announce this even if is 0 donation fk , i'm sick of this shit coin , just copy paste , he did not even bothered to change the donation address lol  P.S: 360 sec post , oh come on ,  ) ups i forget i'm a Newbie What happened to your old account? |
|
|
|
Charity is set at 0, but the charity address is taken from ComputerCoin |
|
|
|
Hey Miners, Always check the support forums of the mining pools. Looking at io.pool.mn for example i can see they have experienced problems before with many other coins, so it is not the first time this has happened.
Any pool that operates long enough will have problems with the coins due to the dynamic nature of the coins. The question is how quickly is the pool solving these problems. I/O wallet update is the culprit in this case - the dev first said that the wallet update is recommended and then suddenly changed the topic to urgent update. Anyways, pool.mn did update the wallet on time and yet the fork happened. What has caused the fork - I have no idea, ask the dev. fuckin mining farm caused it, and will do big dump soon....just guessing This could be the reason. The fork occurred around 15 hours after pool.mn updated the wallet. It could be that someone with large enough hashing power has updated his own wallet and once he started hashing again the fork occurred. I doubt that it was intentional, I've seen forks happening on other coins when large hashrate jumps in. |
|
|
|
Hey Miners, Always check the support forums of the mining pools. Looking at io.pool.mn for example i can see they have experienced problems before with many other coins, so it is not the first time this has happened.
Any pool that operates long enough will have problems with the coins due to the dynamic nature of the coins. The question is how quickly is the pool solving these problems. I/O wallet update is the culprit in this case - the dev first said that the wallet update is recommended and then suddenly changed the topic to urgent update. Anyways, pool.mn did update the wallet on time and yet the fork happened. What has caused the fork - I have no idea, ask the dev. |
|
|
|
I think this is problem of pool, pool didnot update wallet to ver 1.1.0. I can not syn wallet before but after update ver 1.1 + delete all database of wallet (keep wallet.dat) and restart IOCoin wallet. Wallet worked ok.
Pool DID update to the new wallet well before the fork happened. Please check the previous posts. This fork is not due to not updating. |
|
|
|
I also got issues with pool.mn ... the transactions list says: 31797 2014-07-27 09:54:14 Debit_AP Confirmed ijaVtJ1j...p9ai6wpn 2002ecfe...0c046432 n/a 10.34094922 27829 2014-07-27 06:50:14 Debit_AP Confirmed ijaVtJ1j...p9ai6wpn 022ff48b...3c77e4be n/a 10.02686330 24414 2014-07-27 04:20:12 Debit_AP Confirmed ijaVtJ1j...p9ai6wpn b6527707...2bc859fb n/a 10.07334007 17557 2014-07-27 00:50:14 Debit_AP Confirmed ijaVtJ1j...p9ai6wpn 3dbb150c...3efe7d1c n/a 10.04724870
but I only got my first payment...  There was a fork in the network, payments sent from the pool after block 6430 went to the forked chain. |
|
|
|
fuck , pool.mn also didn't pay yet , attentionThis has been fixed. Maturity of new blocks is 190, not 120. Payments at pool.mn went through. Please, next time write to our support. Thank you. |
|
|
|
and BTW i also didn't get pay my fusecoin form pool.mn
Me too. You should really write an e-mail to the support and not in another thread. I've fixed the issue with fuse coin - maturity of the blocks is 190 and not 120 as was setup in the pool. Fusecoin payments went through |
|
|
|
|
You should blame the dev for this fork. We updated the wallet first but that didn't prevent the pool from not going into the fork. What do you want us to do?
|
|
|
|
What exactly is not working? Pool is finding blocks and payouts are running as usual. Pool.mn 7282 Current Block But  { "blocks" : 8076, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : { "proof-of-work" : 314.52278735, "proof-of-stake" : 0.00301229, "search-interval" : 0 }, "blockvalue" : 125000000000, "netmhashps" : 34776.63612887, "netstakeweight" : 200864.40365974, "errors" : "", "pooledtx" : 0, "stakeweight" : { "minimum" : 2909, "maximum" : 0, "combined" : 2909 }, "stakeinterest" : 1001977, "testnet" : false } Ok, there is a fork in the network but which blockchain is the official one? Minep.it and pool.mn are on the same fork. Minerpools has some issues but is on the other chain, the same as hashharder. Yes.This is new wallets. { "version" : "v1.1.0.0-g32a928e", "protocolversion" : 60014, "walletversion" : 60000, "balance" : 182060.93662657, "newmint" : 71250.00260000, "stake" : 0.00000000, "blocks" : 7302, "timeoffset" : -152, "moneysupply" : 2378547.22162302, "connections" : 14, "proxy" : "", "ip" : "37.187.144.69", "difficulty" : { "proof-of-work" : 58.66234021, "proof-of-stake" : 0.00079347 }, "testnet" : false, "keypoololdest" : 1406438531, "keypoolsize" : 101, "paytxfee" : 0.00010000, "mininput" : 0.00000000, "errors" : "" } pool.mn was the first pool to switch to the new wallet. Fork is not due to the new wallet. @pool.mn what's the meaning of this ?
Found that conflict
date: 2014-7-27 12:01
from: unknow
to: iT79z3wWyebNwjEVK99saqCNgc1AnPd338 (own)
: 497.60715284 IO
: +497.60715284 IO
: 58f5b4f32f4969a3aa5331c69b886c948bc3e640ddc0202a62af045348f38e0a
my wallet also is new wallet but what's wrong with this ? it means pool.mn send me ? :Dcan i sell this 497.60715284 IO ? I've resynced the blockchain with only the hardcoded node - now pool.mn is on the same fork as you are. |
|
|
|
What exactly is not working? Pool is finding blocks and payouts are running as usual. Pool.mn 7282 Current Block But  { "blocks" : 8076, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : { "proof-of-work" : 314.52278735, "proof-of-stake" : 0.00301229, "search-interval" : 0 }, "blockvalue" : 125000000000, "netmhashps" : 34776.63612887, "netstakeweight" : 200864.40365974, "errors" : "", "pooledtx" : 0, "stakeweight" : { "minimum" : 2909, "maximum" : 0, "combined" : 2909 }, "stakeinterest" : 1001977, "testnet" : false } Ok, there is a fork in the network but which blockchain is the official one? Minep.it and pool.mn are on the same fork. Minerpools has some issues but is on the other chain, the same as hashharder. Yes.This is new wallets. { "version" : "v1.1.0.0-g32a928e", "protocolversion" : 60014, "walletversion" : 60000, "balance" : 182060.93662657, "newmint" : 71250.00260000, "stake" : 0.00000000, "blocks" : 7302, "timeoffset" : -152, "moneysupply" : 2378547.22162302, "connections" : 14, "proxy" : "", "ip" : "37.187.144.69", "difficulty" : { "proof-of-work" : 58.66234021, "proof-of-stake" : 0.00079347 }, "testnet" : false, "keypoololdest" : 1406438531, "keypoolsize" : 101, "paytxfee" : 0.00010000, "mininput" : 0.00000000, "errors" : "" } pool.mn was the first pool to switch to the new wallet. Fork is not due to the new wallet. |
|
|
|
What exactly is not working? Pool is finding blocks and payouts are running as usual. Pool.mn 7282 Current Block But  { "blocks" : 8076, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : { "proof-of-work" : 314.52278735, "proof-of-stake" : 0.00301229, "search-interval" : 0 }, "blockvalue" : 125000000000, "netmhashps" : 34776.63612887, "netstakeweight" : 200864.40365974, "errors" : "", "pooledtx" : 0, "stakeweight" : { "minimum" : 2909, "maximum" : 0, "combined" : 2909 }, "stakeinterest" : 1001977, "testnet" : false } Ok, there is a fork in the network but which blockchain is the official one? Minep.it and pool.mn are on the same fork. Minerpools has some issues but is on the other chain, the same as hashharder. |
|
|
|
|
Show Posts
