New Ixcoin fork -> I0coin

[doublec]

Is this an error in compilation or is it trying to use the real genesis block but it doesn't exist yet?

It happens when using git HEAD without any blocks downloaded yet. As a workaround I went back to commit c81732, downloaded the existing block chain, then went back to HEAD and it worked.

[1714312279]

1714312279

[1714312279]

1714312279

[1714312279]

1714312279

[1714312279]

1714312279

[hawks5999]

Bitparking Namecoin Pool
Bitparking Namecoin<->BTC Exchange
Bitparking IXCoin Pool
Bitparking IXCoin<->BTC Exchange

Time to update your sig...

[jackjack]

Bitparking Namecoin Pool
Bitparking Namecoin<->BTC Exchange
Bitparking IXCoin Pool
Bitparking IXCoin<->BTC Exchange

Time to update your sig...

I don't think he will have enough space

[Fakeman]

So is compiling the source yourself the only way to have the client ready ahead of time?

[peterpiper]

Should make a few mirrors for client download in case people decide to hammer the shit out of it....

[nelisky]

Seeing as people are already mining and running clients for i0coin I assume you'll change the genesis block and redistribute the client. But what about all those that *don't* update the client because they mined a huge fuckload of i0coins_v0 already? Did you manage to create 2 forks in a single throw?

[deepceleron]

Seeing as people are already mining and running clients for i0coin I assume you'll change the genesis block and redistribute the client. But what about all those that *don't* update the client because they mined a huge fuckload of i0coins_v0 already? Did you manage to create 2 forks in a single throw?

If miners stay with the released blockchain and client, there will be two blockchains bouncing around on the same network, one that doesn't accept the other's blocks as valid. You can't really make orphan chains out of the new client's blocks, since the new client will know to ignore chains with a different 0 block. However, an attack vector if you are a huge pool that is ready to go - jump on after modding the release client to also ignore any chains except ones with a block 1 you just made, you could cause everyone else's work and coins to be discarded by overwhelming the solo miners with consecutive block solves and growing a longer chain than theirs.

[creativex]

...yeah! What the smart spartacus said.

[hawks5999]

Seeing as people are already mining and running clients for i0coin I assume you'll change the genesis block and redistribute the client. But what about all those that *don't* update the client because they mined a huge fuckload of i0coins_v0 already? Did you manage to create 2 forks in a single throw?

If miners stay with the released blockchain and client, there will be two blockchains bouncing around on the same network, one that doesn't accept the other's blocks as valid. You can't really make orphan chains out of the new client's blocks, since the new client will know to ignore chains with a different 0 block. However, an attack vector if you are a huge pool that is ready to go - jump on after modding the release client to also ignore any chains except ones with a block 1 you just made, you could cause everyone else's work and coins to be discarded by overwhelming the solo miners with consecutive block solves and growing a longer chain than theirs.

And so will GuildCoins be born

[nux]

So is compiling the source yourself the only way to have the client ready ahead of time?

I am curious about this as well.

Thanks

[Nasakioto]

With the code adjusted to be 48 coins per 5 min and re adjust the difficulty every 7 days (2016 blocks), the inflation rate should look like this:

http://www.i0coin.org/inflation.png

So we will end with the exact same amount of coins in our blockchain than bitcoin in it blockchain but the maduration period will be much much sooner (maduration: when we reach the ~21M limit)

It will be interesting to see if the generation curve affects the uptake by the community. In any case, best of luck with i0coin.

It would be great to have a i0coin<>ixcoin exchange. DoubleC ? 

one of the problems with ixcoin is that we don't really know when the genesis block was created.

satoshi proved the bitcoin genesis block was no earlier than jan 3, 2009 by putting in a newspaper headline.

ixcoin's genesis block has nothing to help verify the date. see: http://bitcointalk.org/index.php?topic=36218.msg447180#msg447180

if I0coin wants to eliminate this (small, in this case) risk that the genesis block has been getting mined for a long time now, it should include something similar to what satoshi did.

This is not an issue as the Ixcoin client locks in the blockchain and will be update to continue locking it in the future.

[rikur]

It would be great to have a i0coin<>ixcoin exchange. DoubleC ? 

Good idea. Could you also create rikurrCoin <-> i0Coin exchange? I've got some coins to dump.

[Clipse]

It would be great to have a i0coin<>ixcoin exchange. DoubleC ? 

Good idea. Could you also create rikurrCoin <-> i0Coin exchange? I've got some coins to dump.

I could create an rikurrCoin --> toilet exchange for all your dumping needs?

[peterpiper]

LOL....

[afro25]

Just over an hour to go!

Oh god oh god oh god oh god oh god!!!

[SomeoneWeird]

It would be great to have a i0coin<>ixcoin exchange. DoubleC ? 

Good idea. Could you also create rikurrCoin <-> i0Coin exchange? I've got some coins to dump.

I could create an rikurrCoin --> toilet exchange for all your dumping needs?

hahahha

[twobits]

I would highly recommend starting at least difficulty 128 - 512.  Difficulty = 1 will be absolute chaos when I'm guessing 50~100 GH/s coming just from I0 Guild.  Miners are hundreds of times faster than when Bitcoin began at Difficulty=1.

As a pool of course you would.  That is about when solo mining starts to kick out.  I suggest leaving it at 1, letting cpu miners and solo minters have a bit of fun., and pools staying off until it hits 512.

[smoothie]

It would be great to have a i0coin<>ixcoin exchange. DoubleC ? 

Good idea. Could you also create rikurrCoin <-> i0Coin exchange? I've got some coins to dump.

I could create an rikurrCoin --> toilet exchange for all your dumping needs?

This made me laugh so hard! hahaha I gotta take a dump!

 

[colossus]

I would highly recommend starting at least difficulty 128 - 512.  Difficulty = 1 will be absolute chaos when I'm guessing 50~100 GH/s coming just from I0 Guild.  Miners are hundreds of times faster than when Bitcoin began at Difficulty=1.

As a pool of course you would.  That is about when solo mining starts to kick out.  I suggest leaving it at 1, letting cpu miners and solo minters have a bit of fun., and pools staying off until it hits 512.

Fat chance

[twobits]

I would highly recommend starting at least difficulty 128 - 512.  Difficulty = 1 will be absolute chaos when I'm guessing 50~100 GH/s coming just from I0 Guild.  Miners are hundreds of times faster than when Bitcoin began at Difficulty=1.

As a pool of course you would.  That is about when solo mining starts to kick out.  I suggest leaving it at 1, letting cpu miners and solo minters have a bit of fun., and pools staying off until it hits 512.

Fat chance

Woosh.

Of course,  I put that in to show how his post was from a purely pool centric point of view by putting out the complete opposite as a suggestion.