Author

Topic: I/O Coin - Ticker: IOC - Stealth Blockchain Ecosystem - Dions - Chameleon - page 234. (Read 719067 times)

sr. member
Activity: 364
Merit: 250
Lost more coin in  pool.mn
full member
Activity: 153
Merit: 100
yeah we all did hashharder is working now though
newbie
Activity: 8
Merit: 0
i lost my coin in io.pool.mn and now i can't withdraw coin to wallet.
full member
Activity: 153
Merit: 100
yep receiving payments from hashharder confirmed takes an hour or so but its working fine
full member
Activity: 270
Merit: 150
iOC Development Team
ANN Updated New Exchange

I/O Coin on Cryptsy - https://www.cryptsy.com/markets/view/272

If you have a custom config for the nodes please delete :

69.164.201.129
37.187.144.69
83.233.170.32

They seem to be on the wrong chain
full member
Activity: 380
Merit: 100
Community Manager - Blockchain analyst
legendary
Activity: 1470
Merit: 1010
Join The Blockchain Revolution In Logistics
this coin got cryptsied?  Shocked


Launched: 23rd July  2014
PoW Ends After: 7 days [+DDOS of the pools]
PoW: 16.000.000-22.000.000
full member
Activity: 182
Merit: 100
I believe we're on the right chain over here https://www.minep.it/pool/IO/ but need more workers too.
full member
Activity: 153
Merit: 100
io.poo.mn isnt finding blocks for some reason, hasharder http://www.hashharder.com/x11/iocoin is and is on the right block. we need miners there. it will only show half your hashrate but its working fine behind the scenes it seems
hero member
Activity: 565
Merit: 500
Pool.mn seems to be running the right chain I think
"blocks" : 8624, thats from my wallet
full member
Activity: 380
Merit: 100
Community Manager - Blockchain analyst
Can someone please tell me what's the latest block with hash? Are there still multiple chains out there?

My wallet currently has

Block 8615 with hash 00000000006ac8eb70244d16a2101e1c25ad1ffef1c47c4ec4df00b0fbe278e8

Is this the right chain?


{
"hash" : "00000000006ac8eb70244d16a2101e1c25ad1ffef1c47c4ec4df00b0fbe278e8",
"confirmations" : 4,
"size" : 246,
"height" : 8615,
"version" : 6,
"merkleroot" : "afb60f9a3468b5a24cdb7b951815a599149dffcf25527b2eba159673d375129c",
"mint" : 1250.00000000,
"time" : 1406464546,
"nonce" : 4779478,
"bits" : "1b73c17f",
"difficulty" : 566.14852149,
"blocktrust" : "236283ba951",
"chaintrust" : "1d7b4b16fa58d7",
"previousblockhash" : "0c40a69363dd08379c37c5f1b057b9978bcb4e4d89cd4a518600876ddf0f7d93",
"nextblockhash" : "00000000003b692fec40f624601b3c2a431b9b102b7fd22cb1e2c43e21884b85",
"flags" : "proof-of-work",
"proofhash" : "00000000006ac8eb70244d16a2101e1c25ad1ffef1c47c4ec4df00b0fbe278e8",
"entropybit" : 0,
"modifier" : "ddaa303a5d13483b",
"modifierchecksum" : "45ea6467",
"tx" : [
"afb60f9a3468b5a24cdb7b951815a599149dffcf25527b2eba159673d375129c"
]
}
member
Activity: 89
Merit: 10
full member
Activity: 153
Merit: 100
ok hashharder is showing found blocks
full member
Activity: 270
Merit: 150
iOC Development Team
1. All pools were contacted to update to the new wallet.

2. If you download the new wallet from here : https://github.com/IOCoin/iocoin/releases/tag/v1.1.0.0 to see if the pool is mining on the correct fork
go into Help>Debug Window>Console and type getinfo then press enter  (somewhere you will find "blocks" : X).
If the pool is on the same block as the wallet you should be ok with mining there. (Any other questions about payments etc you would have to check with the pools).

3. Make sure to uninstall the original wallet and delete everything in the %Approam% folder except for wallet.dat (make sure you have a backup so you dont lose your coins) before updating to the new wallet.

4. Logo contest is a 1BTC reward that ends 08/02 as mentioned in OP (has to be a modification of the original I/O logo)

5. Send a pm after you have posted a translation and a BTC addy to get your reward.(lock your translation by posting in the thread so we dont have duplicates)

6.We have contacted bigger exchanges and are awaiting code review and addition.

sr. member
Activity: 364
Merit: 250
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.
sr. member
Activity: 364
Merit: 250
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.
member
Activity: 117
Merit: 10
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.

Would be great if one of the bigger pools added us, maybe we can send some requests to the bigger pools?

Always make sure you have the updated wallet, in this case version 1.1 found here - https://github.com/IOCoin/iocoin/releases/tag/v1.1.0.0

Like someone previously said.  Make sure to backup your old wallet, then remove all the files from previous wallet.  Except the wallet.dat.  Then load new wallet.qt and put the saved wallet.dat in the new folders for version 1.1.

i am sure we will get a update on the pools soon.  Remember to keep checking the first post, 'ann' for updates.
What are you talking about?  Huh the list @ first post shows which pools have updated and which have not... also the payouts worked fine before the fork.
full member
Activity: 168
Merit: 100
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.

Would be great if one of the bigger pools added us, maybe we can send some requests to the bigger pools?

Always make sure you have the updated wallet, in this case version 1.1 found here - https://github.com/IOCoin/iocoin/releases/tag/v1.1.0.0

Like someone previously said.  Make sure to backup your old wallet, then remove all the files from previous wallet.  Except the wallet.dat.  Then load new wallet.qt and put the saved wallet.dat in the new folders for version 1.1.

i am sure we will get a update on the pools soon.  Remember to keep checking the first post, 'ann' for updates.
full member
Activity: 153
Merit: 100
yeah i was on hasharder at the start. it does show half hashing power but theres only under 10 workers on there if i remember right. im back at io.pool.mn as it seems to be working with the highest hash rate on the pools provided.
hero member
Activity: 561
Merit: 500
kittehcoin.info
I m on http://www.hashharder.com/x11/iocoin but I can't confirm that this one is working. I didn't received anything from the pool yet and also my hash rate is reported much lower than it should be.
Jump to: