Topic: New Ixcoin fork -> I0coin - page 50. (Read 217126 times)

1. Deposit 50 BTC into i0exchange
2. Purchase I0C
3.
4. "The connection has timed out - The server at i0exchange.bitparking.com is taking too long to respond."


FFFFFFFUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!

Well, I already sold all my i0coin.

bitparking still works. edit: no, it's not loading again.

bitparking still works.

so is doubleC just sitting on all our deposited i0coins or is i0exchange going down just the final fail in the coffin for i0coin?

I pledge 2BTC to whoever makes an i0coin fork with this implemented.  (and has a much higher starting difficulty)  Heck, if this were done right then the countdown for people to start mining would be automatic!  Everyone would just wait and start mining when the difficulty was low enough.

How about a completely time-based difficulty adjustment with a much smaller range and a comparatively smaller adjustment scope. Perhaps a daily difficulty adjustment by a maximum factor of 0.5 instead of 4?

I really like the changes with i0coin, faster target block solve time, wallet encryption, etc.  But I'm a little concerned that it will still suffer from difficulty yoyo-ing like namecoin does.  I know it's set that it adjusts every 7 days in addition to after a certain number of blocks, but I don't think that will solve the problem.  The biggest problem is that as far as I know the blockchain can still only adjust up or down 4x (or 1/4x) per adjustment. So if after the fad wears off 95% of miners give up, it will still take 3 weeks for the difficulty to adjust to where it should be.

I'm the one that created that post.  My problem was I didn't know you could use i0coin.exe with a -server switch, I was used to the bitcoin/namecoin with the 'D' at the end being the daemon that you could simply run (namecoind.exe) and then open a new command window and run commands against it.  With i0coind.exe it actually tried to launch a new process instead of running commands against the daemon.

The guy that posted below me helped me fix the problem by me running i0coin.exe -server ,  I didn't know the gui client had a -server mode.  (Makes me wonder WTF the i0coin daemon exe is for)

However to answer your question, if someone ran it incorrectly, their solo miners would never have connected at all - they wouldn't have somehow magically connected but lost all the blocks.

poclbm does not write to the wallet....    if a server is not running,  it can not mine.


Or they could have added the port # to the config file. Whatever they put would be what would then have worked for them.



I don't think official launches will work unless the hash is also changed.

Are you sure you just did not put server=1 in your config file for bitcoins and namecoins and not i0coin?

Also, you can't solo mine without a server running, as it would have nothing to get the work from.


Also, since this is a decentralized system, just how do you propose to do a reset?

My mistake. I thought he said bitcoin, not bitcoind.

What platform? 'bitcoind' runs in server mode even if it doesn't return you to the command prompt. The JSON-RPC server is still running. You'd add '-daemon' or 'daemon=1' in the .conf file to get the behaviour to fork itself in the background (on linux anyway).

Yes, it does. All 'server' mode does is enable the JSON-RPC interface. This is automatically done in the programs ending with 'd'.

I've not done solo mining on Bitcoin since I'm late to the party. But for the rest, I always had to start xxxcoind with the -server flag for solo mining. No difference with i0coin except there is too much hash power going into it from the start. Especially with a single pool having what appears to be way more than 50% of the hashrate, it makes absolutely no point to mine solo. Any blocks you get in, will most likely be erased when the pool solve that block before your block reaches their daemon. With multiple blocks per seconds in the beginning, it is almost guaranteed to do so.

Firstly, in case there's a misunderstanding ... the (blocks and) coins you get are in the block-chain.
The wallet is not actually like a normal wallet that contains the actual items of value, it contains the keys that give you access to the items of value in the block-chain.

Secondly, the miner requests work from the server (or pool) and that contains the address (key) that is placed in the block and makes up part of the data that is hashed and tested to see if you win it.
(so also you can't steal a successful block hash and give it to another address (key) - the address (key) is part of it)

Now, if the server code can actually generate a new key, not write it in the wallet and then also pass that key out as a work request, then you could lose a block, but again, I doubt the code is that stupid ...

Still sure about that?  The price hasn't budged.

No.

Well some versions of the code you type in ./bitcoind it starts the daemon and you then get a command prompt below it where you can type things such as ./bitcoind getinfo on this configuration you have to open
another terminal and type ./bitcoind getinfo (or in this case ./i0coind getinfo )  The problem is that people were still able to start poclbm with the username and password in the i0coin.conf file but it would be unable to write to the wallet as the directory would have been in use by the iocoind running in non-server mode. Therefore people were wondering why the hell they were not  getting the blocks they had mined and in fact it looks like they may have lost them completely. I hope there is a way for these people to recover them. I myself believe I mined a few blocks in this situation. They have simple becomes orphans and I may have lost them anyway but I was not running the i0coind in server mode so it appears that I may have lost those blocks simply for that reason. If it was just me then tough luck but if it turns out that many hundreds of people lost entire blocks due to this this is quite a serious issue.

Additionally people were unsure which port to specify in the i0coin.conf leading many to be forced to mine through pools further undermining the open and p2p nature of the currency.


The whole purpose of opening this up and having an official launch  to give as many people as possible a chance to take part in this new block chain has unfortunately been side stepped in some cases by technical errors and unfriendly default configurations and in other cases may have been manipulated by blatant financial gain leaving the rest of us with feeling short changed.

How can you do work requests to a server that isn't a server?

You think someone actually modified the server code to stop it from submitting blocks to the network?
Well if they did, yeah I guess you'd be unhappy about it ... but I seriously doubt someone did that.
When taken in context it sounds exactly like someone trying to blame their orphens on something other than the fact that they are expected.

Again, orphens ran rampant during the early stages I even saw some of those 6 I lost disappear when the network corrected them - that's how it works and it happens with solo and pool mining of course.