Topic: New Ixcoin fork -> I0coin - page 14. (Read 217119 times)

Not to worry, trading in this coin will continue at my Open Transactions server. A huge amount of work has been done on the Open Transactions engine but the results are mostly in so it is looking like it will be up and running robustly any time now. This extended testing revealed a lot of fixes to make but the bulk of them are now done and we should be mostly just shaking out any bugs put in during the latest set of changes today.

-MarkM-

i0c gets shut down again ...

Meanwhile - it's not Jan 30 yet

https://btc-e.com/news/54

mmpool has 70 Ghash mining i0coin. Transactions are going through and blocks are being processed so the chain is not dead. This is different from CLC whereby Luke was not allowing any other blocks at all.

Well however, at the moment is anyone mining i0coin at all? (other than Luke?)

I don't see how having only one person mining something (i.e the chain is dead) is better than the chain being at risk of a 51% takeover and still working normally otherwise.

It is only recently that merged mining has been going - yet it's been OK up until then for the past months.

Current certainly of a dead chain or possible risk of a 51% takeover?
Possible risk seems way better than no chain at all like it is at the moment.

Unfortunately removing MM results in the chain getting owned by someone else when the hash rate drops. Another fun idea is to make mining blocks cost coins, rather than gain them. Eventually the merge miners will run out of money and can't mine blocks anymore. Solving the problem of no one wanting to mine at that point is an exercise for the reader

Well looking at the difficulty and the hash rate shown on allchains, Luke's pool is still mining i0coins (and iXcoins and CLC)

There is a reasonably straight forward fix to that ...
Remove merged mining and get everyone to switch to a new version without it.
Set the block number for the change over about 1,000 or even 10,000 blocks in the future and with the rate he is generating blocks it will happen quite quickly
Then finally also add a difficulty reset with that block number to down to say 50 or there abouts.

Lastly, there is one other simple change to make: ever so slightly change the hash algorithm - even as simple as XOR 1 bit in the answer.

Just a few ideas

Dynamic checkpoints

this is a really forward-looking idea and has to be tested on a testnet, because it gives more safety to all user and chains. This possible roll-back of all(?) chains is harmful+unproductive and destroys the trust in it.

i had a little idea in this direction, though i asked myself, why doublec has to do the setup so often manually of these checkpoints for the chain to be safe.

So an attacker could not destroy all the work that has been done right now.

When - captured - pools attack a chain, then only transactions could be stopped and when these attacking - captured - pools loose their hashrate, because the miners don't agree with that attack, then there is not much damage made to the chain and it could go on with it...

just a little time to rest for the chain

Websites can go down or be DOS'd. I used the P2P messaging to avoid this, but if that isn't important then yes, a website URL is an option.

If you are going to trust some 'random' key you can also trust some 'random' web site.
i.e. get the list from a 'trusted' URL instead.
No difference in trust, but easier to see what the checkpoints are by simply getting the URL.
Though, of course, it is really only the last checkpoint that matters since that will only be correct if all the previous ones are also correct.

One of the issues with low hash rate chains is dealing with having to add checkpoints regularly and getting users to upgrade to keep the network secure. Here's a work-in-progress proof of concept of 'dynamic checkpoints': https://github.com/doublec/i0coin/tree/dynamic_checkpoints

This provides the ability for a trusted entity with a key to send a checkpoint out to nodes. These 'checkpoint' messages are passed to all nodes. Nodes that are operating in 'trust' mode will check the signature on the message and if it is from the trusted entity it will install the checkpoint. No need to upgrade the software.

The patch provides:

- All nodes relay the "checkpoint" messages
- Only nodes with the "-trust" command line argument will check the signature and install the checkpoint
- Nodes can add "-trustkey=foo" arguments where "foo" is an address to override the default key and trust some other entity for checkpoints
- a JSON-RPC command to sign and send checkpoint messages
- Only checkpoints higher than existing checkpoints can be added so no chain rollback can be done.

At least the following should be added:

- a JSON-RPC command to return the latest checkpoint. Nodes like exchanges could use this to know for certain a chain won't rollback past a point. This could be used to feel confident to accept large deposits.
- Flood control to deal with "checkpoint" messages being sent around

Thoughts on this model? it centralizes the aspect of checkpoints but provides the ability for nodes to override. And isn't different to a trusted developer releasing versions with checkpoints. Maybe only have it enabled when the chain hash rate is low?

Note the patch is an experiment and shouldn't be used in production right now.

http://blockexplorer.sytes.net/ usually works. I've bumped the dev's thread.

Any I0Coin block explorer out there that work? 

I'm not giving an estimate. Quicker if someone actually does the legwork and converts the files so all I have to do is build.

I'm sure it will be done before Xmas arrives ... (next)

Hmm the i0coin price is pretty crap on both BTC-e and Vircurex ... considering the network hash rate (based on the current difficulty)

When will your i0coin patch into the client be ready? Estimates? Day, week, month?

Merry Christmas btw

Best regards
lightlord

I'm working on it (for the client). I suck at graphics and am having issues. If anyone wants to prepare a patch it'd be much appreciated!

When is the new i0coin logo going to be used for the client?
Still don't see it.

And also maybe put it on http://i0coin.bitparking.com/
As every currency has its coin on its home page.
This should have its as well.

And this coin is well made, put it to good use.
I want to see more of it used.

I've released source and binaries for v32509 of i0coin. The only change is a checkpoint added at block 161,000 to give a checkpoint past the merged mining switch on point. Downloads are at http://i0coin.bitparking.com.

The bitparking merged mining pool solved its first bitcoin and namecoin blocks recently so I can confirm that merge mining of the three chains (bitcoin, namecoin and i0coin) are working on the live networks. It worked in testing of course but it's nice to get confirmation that it works 'for real'.