[I0C] I0coin - The Best Choice In Digital Currency

[Laamadeus]

My IOC wallet says there is no block source available. What is the most new wallet version?

The latest wallet is version 0.8.6-1 here.
http://i0coin.snel.it/
or
https://izerocoin.org/downloads/


For your block source problem, the best source of current addnodes is here...

https://chainz.cryptoid.info/i0c/#!network

Click on the "node list" buttons to get addnodes for your i0coin.conf file.

Thanks! It is now synchronizing with network.

[1715178143]

1715178143

[1715178143]

1715178143

[1715178143]

1715178143

[1715178143]

1715178143

[1715178143]

1715178143

[brooksby]

My IOC wallet says there is no block source available. What is the most new wallet version?

The latest wallet is version 0.8.6-1 here.
http://i0coin.snel.it/
or
https://izerocoin.org/downloads/


For your block source problem, the best source of current addnodes is here...

https://chainz.cryptoid.info/i0c/#!network

Click on the "node list" buttons to get addnodes for your i0coin.conf file.

Thanks! It is now synchronizing with network.

Welcome to i0coin!

[brooksby]

I've been thinking about item 2. on the i0coin client upgrade bounty.

2. OP_RETURN must be set to 80 bytes (to allow financial platform development)

I think it may be best to keep OP_RETURN at 40 bytes like Bitcoin.  There are a few reasons for my change of mind.  First, financial platforms are working fine on Bitcoin using 40 bytes.  Second, it reduces the number of differences, even if minor, between i0coin and Bitcoin so there are less chances for bugs.  Third, i0coin has a 90 second block time compared to Bitcoin's 10 minutes, so i0coin's block chain is growing faster.  I0coin's block chain is already over 11 GB even with small numbers of transactions.  I'm worried that a larger OP_RETURN could balloon the block chain even more.  Of course, if and when Bitcoin updates the OP_RETURN byte size, so will i0coin.

Feedback is welcome.

Bitcoin 0.11.0 has enabled block chain pruning.  If we upgrade i0coin to 0.11.0 then we could use larger OP_RETURN byte sizes.

Read about block file pruning here.
https://bitcoin.org/en/release/v0.11.0

Pruning definitely helps for those who can do it, but i0coin will need to maintain some nodes with full block chains.  So I would still prefer to keep the block chain as small as possible with OP_RETURN at 40 bytes.

I do like the idea of pruning.  It may attract users who don't like large block chains taking up room on their hard drives.  I'd be ok with changing the bounty instructions to require version 0.11.0.

[BlackPanda]

the network block sometimes do not fit?

[brooksby]

the network block sometimes do not fit?

Doesn't fit where?  Are you saying the block chain is getting too big?

[I0coiner]

We need a new exchange soon.  Vircurex is delisting i0coin next month.

[Laamadeus]

We need a new exchange soon.  Vircurex is delisting i0coin next month.

Yep, but that is also means that buy orders will be filled. Some people think if there is no exchange the coin is dead, which is not actually true 

[brooksby]

I've been thinking about item 2. on the i0coin client upgrade bounty.

2. OP_RETURN must be set to 80 bytes (to allow financial platform development)

I think it may be best to keep OP_RETURN at 40 bytes like Bitcoin.  There are a few reasons for my change of mind.  First, financial platforms are working fine on Bitcoin using 40 bytes.  Second, it reduces the number of differences, even if minor, between i0coin and Bitcoin so there are less chances for bugs.  Third, i0coin has a 90 second block time compared to Bitcoin's 10 minutes, so i0coin's block chain is growing faster.  I0coin's block chain is already over 11 GB even with small numbers of transactions.  I'm worried that a larger OP_RETURN could balloon the block chain even more.  Of course, if and when Bitcoin updates the OP_RETURN byte size, so will i0coin.

Feedback is welcome.

Bitcoin 0.11.0 has enabled block chain pruning.  If we upgrade i0coin to 0.11.0 then we could use larger OP_RETURN byte sizes.

Read about block file pruning here.
https://bitcoin.org/en/release/v0.11.0

Pruning definitely helps for those who can do it, but i0coin will need to maintain some nodes with full block chains.  So I would still prefer to keep the block chain as small as possible with OP_RETURN at 40 bytes.

I do like the idea of pruning.  It may attract users who don't like large block chains taking up room on their hard drives.  I'd be ok with changing the bounty instructions to require version 0.11.0.

I've been playing with pruning on Bitcoin 0.11.0.  It does reduce the Bitcoin folder from 46 GB to about 1.5 GB, but it's not much use in this mode.  You CANNOT run a wallet, which means you can't send or receive coins.  (A future release will provide wallets with pruning enabled.)  

The main use I can see for running a client with pruning enabled is to create a "lite" node which can relay transactions and the latests block data.  You can also mine using pruning, but there are potential cons to doing this.  

"...550 blocks is not exactly a major buffer to prevent a potential Bitcoin fork. And if the majority of mining pools end up on on a fork of the network for a lengthy period of time, all hell will break loose."

https://www.bitcoin.com/news/pros-and-cons-on-bitcoin-block-pruning/


I can see this may help i0coin down the road to create more "lite" nodes to expand the network, but I'm not so sure this is a big advantage at this time until we can run a wallet too.

[tinderbox]

We need a new exchange soon.  Vircurex is delisting i0coin next month.

Yep, but that is also means that buy orders will be filled. Some people think if there is no exchange the coin is dead, which is not actually true  

i0coin still has plenty of life.  We just need some community help to get on more exchanges.  

If you can spare some time please contact some exchanges to get i0coin added.  If you need help with votes, post it on this thread.

[I0coiner]

vote for i0coin at cryptopia

https://www.cryptopia.co.nz/HomeAction/Voting

[tinderbox]

@brooksby

I'll contribute 5,000 I0C to the upgrade bounty.

[I0coiner]

vote for i0coin at cryptopia

https://www.cryptopia.co.nz/HomeAction/Voting

we came in 2nd place

better luck next week

[Laamadeus]

Remember to withdraw your I0Cs at Vircurex before end of the month folks. Just take big chunk of I0Cs to my wallet.  Someones dumping their coins, other thanks for the cheap coins

[brooksby]

25,000 I0C Client Upgrade Bounty

   20,000 I0C    brooksby
     5,000 I0C   tinderbox  
   -----------
   25,000 I0C   Total Bounty

We need to move forward on the next version of the i0coin client.  It will bring added security and more potential for developing the i0coin economy.  The following criteria need to be met to claim the bounty.

1.  Update must bring client up to Bitcoin version 0.10.0 (or later)
2.  Maintain block retarget = 120 blocks (3 hours)
3.  Merge mining must be operational
4.  At least one major merge mining pool must start using client (to prove it works)
5.  Maintain the memory streamlining features of i0coin version 0.8.x to keep memory usage to a minimum
     (memory issue info here https://bitcointalk.org/index.php?topic=224744.msg2830598#msg2830598)

[brooksby]

I changed 1 and 2 on the bounty criteria.  I bumped the minimum version up to 0.10.0, and removed the OP_RETURN byte size change.  We'll leave it the same a Bitcoin.

[brooksby]

25,000 I0C Client Upgrade Bounty

   20,000 I0C    brooksby
     5,000 I0C   tinderbox  
   -----------
   25,000 I0C   Total Bounty

We need to move forward on the next version of the i0coin client.  It will bring added security and more potential for developing the i0coin economy.  The following criteria need to be met to claim the bounty.

1.  Update must bring client up to Bitcoin version 0.10.0 (or later)
2.  Maintain block retarget = 120 blocks (3 hours)
3.  Merge mining must be operational
4.  At least one major merge mining pool must start using client (to prove it works)
5.  Maintain the memory streamlining features of i0coin version 0.8.x to keep memory usage to a minimum
     (memory issue info here https://bitcointalk.org/index.php?topic=224744.msg2830598#msg2830598)

Good news!  We've got a taker on the bounty to update the i0coin client.  I've asked him to post on this thread shortly.

[brooksby]

We need DNS seed nodes.

If there is anyone who would like to be a seed node for i0coin please let me know.  Post your IP here or PM me.  We need a few seed nodes so we don't have to depend on addnodes in the config file so much.  All I ask is that you be willing to keep your node active for a year or more since your IP will be hard coded into the i0coin client.

[domob]

I can confirm that I'm working on upgrading I0coin to the latest Bitcoin upstream code.  I've not yet created the Github repository for that, but my username there is domob1812, so it will probably be https://github.com/domob1812/i0coin.

[domob]

We need DNS seed nodes.

If there is anyone who would like to be a seed node for i0coin please let me know.  Post your IP here or PM me.  We need a few seed nodes so we don't have to depend on addnodes in the config file so much.  All I ask is that you be willing to keep your node active for a year or more since your IP will be hard coded into the i0coin client.

Let me add to this from the developer perspective:  There are actually two kinds of "seed nodes" that can be hardcoded in the code.  One is fixed IP addresses of stable nodes, which is reflected in the post above.  You can also run the node behind a Tor hidden service (.onion address) if you want, and I can hardcode these as well if you post their onion address.  These can be run behind a firewall and with a dynamic IP, and they help specifically users that proxy their I0coin connection through Tor.

The other is DNS seeds, which are set up by running a special script on a server (not an ordinary node).  They monitor the network and dynamically keep a list of current peers.  They are identified by a domain name (like i0coin.seed.mydomain.net) and those can also be hardcoded.  This is the primary mechanism for node discovery in Bitcoin.  If you are interested in setting up one of these, this would also be great.  Let me know your domain name and I can add the seed to the code as well.

[cryptoVoodoo]

awesome  

i've been waiting for a wallet update