[I0C] I0coin - The Best Choice In Digital Currency

[tinderbox]

Website looks great brooks.  It's more compact and cleaner.  Looks even better than before.

[1715311493]

1715311493

[tinderbox]

I0coin difficulty has increased 10 fold in the last five days.  It hasn't been that high for six months.  Does anyone know who is doing the extra mining.

https://chainz.cryptoid.info/i0c/#@diff

[brooksby]

Success!!!

We've surpassed 95% mining with 0.11.9 clients.  This means all the BIP's have kicked in, so the old 0.8.x client should no longer be used for mining.  If you're still mining with 0.8.x please upgrade.

For non-miners it's also recommended that you upgrade although it's not as urgent.  If you start having trouble syncing (attaching to other clients) then you should upgrade immediately.

I'd like to thank domob for engineering a great new client and tools to make this upgrade go so smoothly.

[brooksby]

... and of course the pools need to be thanked for making the quick upgrade and boosting their hash rate for i0coin to get us over the 95% mark.

[altcoiner-]

I lose all my peers at 900k blocks
speeds to 900k, then everything just stops there
any one have addnode='s ?

[p3yot33at3r]

I lose all my peers at 900k blocks
speeds to 900k, then everything just stops there
any one have addnode='s ?

Code:

addnode=1.34.180.245
addnode=187.190.232.113
addnode=51.254.131.226
addnode=77.249.199.235
addnode=82.200.205.30
addnode=92.3.37.224
addnode=92.3.41.135

Make sure you are using the latest v0.11.9 

[brooksby]

domob,

The 20,000 I0C bounty that I owe you has been sent.  That should complete the payment of the total 25,000 I0C bounty.  Thanks again for your quality work.

[domob]

domob,

The 20,000 I0C bounty that I owe you has been sent.  That should complete the payment of the total 25,000 I0C bounty.  Thanks again for your quality work.

I got everything, thanks a lot!  As discussed privately, I'll keep the code updated with Bitcoin's 0.12 branch and release a 0.12 version when Bitcoin does.

[brooksby]

domob,

The 20,000 I0C bounty that I owe you has been sent.  That should complete the payment of the total 25,000 I0C bounty.  Thanks again for your quality work.

I got everything, thanks a lot!  As discussed privately, I'll keep the code updated with Bitcoin's 0.12 branch and release a 0.12 version when Bitcoin does.

Thanks for your continued support!

[brooksby]

Success!!!

We've surpassed 95% mining with 0.11.9 clients.  This means all the BIP's have kicked in, so the old 0.8.x client should no longer be used for mining.  If you're still mining with 0.8.x please upgrade.

For non-miners it's also recommended that you upgrade although it's not as urgent.  If you start having trouble syncing (attaching to other clients) then you should upgrade immediately.

I'd like to thank domob for engineering a great new client and tools to make this upgrade go so smoothly.

We've been seeing 100% blocks mined by the new 0.11.9 clients for well over a week now.  The transition appears to be complete and holding, even with network hash rate declining back to pre-transition levels. 

[brooksby]

Here are some newly posted graphics you may download from izerocoin.org in two different file resolutions.

[I0coiner]

we need votes for i0coin on these three exchange


https://bter.com/voting

https://c-cex.com/?id=vote

https://askcoin.net/votes

[markm]

If I do a git clone of https://github.com/domob1812/i0coin.git will that give me the correct/latest version? Then go git pull periodically to stay up to date?

-MarkM-

[domob]

If I do a git clone of https://github.com/domob1812/i0coin.git will that give me the correct/latest version? Then go git pull periodically to stay up to date?

-MarkM-

You can do that, but it would be better to pull the i0coin-0.11.9 tag.  In the future, there will be a 0.12 release with corresponding tag as well, at which point you can update (but probably won't have to).

[markm]

If I do a git clone of https://github.com/domob1812/i0coin.git will that give me the correct/latest version? Then go git pull periodically to stay up to date?

-MarkM-

You can do that, but it would be better to pull the i0coin-0.11.9 tag.  In the future, there will be a 0.12 release with corresponding tag as well, at which point you can update (but probably won't have to).

And thus does git suddenly become a complicated mess.

The way I tell whether I need to update is simple cycle through all the coin sourcegode directories doing a git pull in each one; those where the pull got somehing are the ones that need to be re-built and re-distributed to all the machines running them. As one certainly cannot count on seeing any announcements on bitcointalk, everythign scrolls out of sight way to fast to have a reasonable chance of catching sight of something while it happens momentarily to be on the first page of posts.

How the heck would one even go about pulling from a specific tag? For all I know ome of the coin sourcecode dirs already might do that, unfortunately; I don't think git indicates that, at least not very out in your face obviously, so maybe some things already are only being updated when the specific tag that I pulled is updated, and might have entirely new tags in place by now that the old tag I am pulling is not telling me to to pull instead.

Thus usually it is much better if a given repository simple always has whatever it wants passers-by to download be right there as the default thing that anyone not trying to study up on how tags work and re-learn all over again whatever stuff they had to learn way back when they last were forced to resort to tags wil just simply get so that is all just works...

I have pulled tags before, gosh knows how though, I inevitably forget all that complexity that should in any event be avoided.

-MarkM-

[domob]

And thus does git suddenly become a complicated mess.

Well, you most definitely can keep pulling from the master branch or the 0.12 branch (https://github.com/domob1812/i0coin/tree/0.12) and it should work for you (although I'll mostly update the 0.12 branch from now on, as this is what I consider still part of my bounty).  The tags are just an added service in case you want to make sure that you have the same version as everyone else and not run into any bugs produced during recent development.  If you want to pull the latest code, just do it and it should be fine.

[markm]

That still sounds a bit risky, guess I will wait until things stabilise and a stable version is set up as the default.

(It seems like you are saying the development branch is what people currently get at the main URL?)

-MarkM-

[domob]

(It seems like you are saying the development branch is what people currently get at the main URL?)

It is, and that is the same as just about any other software project out there (including Bitcoin).  If you want stable code, use the releases (tags).  If you want to stay on the latest code, use the main branch.  Note that I believe the branches to be mostly bugfree, but they are nevertheless no explicitly created and tested releases.

[sidhujag]

(It seems like you are saying the development branch is what people currently get at the main URL?)

It is, and that is the same as just about any other software project out there (including Bitcoin).  If you want stable code, use the releases (tags).  If you want to stay on the latest code, use the main branch.  Note that I believe the branches to be mostly bugfree, but they are nevertheless no explicitly created and tested releases.

Did you write unit tests that pass on risky code? Bitcoin is not the same as yours because the code is tested and isnt put in a state where ppl can pull broken code especially if test coverage is above 95%... The releases happen after integration testing. So you should not recommend pullimg master or dev branch unless ots unit tested at the least

[domob]

(It seems like you are saying the development branch is what people currently get at the main URL?)

It is, and that is the same as just about any other software project out there (including Bitcoin).  If you want stable code, use the releases (tags).  If you want to stay on the latest code, use the main branch.  Note that I believe the branches to be mostly bugfree, but they are nevertheless no explicitly created and tested releases.

Did you write unit tests that pass on risky code? Bitcoin is not the same as yours because the code is tested and isnt put in a state where ppl can pull broken code especially if test coverage is above 95%... The releases happen after integration testing. So you should not recommend pullimg master or dev branch unless ots unit tested at the least

Isn't that exactly what I wrote?  I suggest to use the release tags, unless you know what you are doing and insist on pulling the branches (but I'm definitely not recommending doing that).  This is what I wrote.  Note that I actually do test the code before I push, but of course not as thoroughly as the release tags are tested.