How much are you trying to send out of Vircurex?  Is it a serious amount like 100,000 i0?

Care to sell any? 

i put though 500 I0C as a test...it went immediately

then I put through the remaining 10K (almost that ).

Nothing. No TXID nothing

its not on the blk chian

i don't care how the do it, if they have screwed their wallet, then they have to to another exchange and buy i0c back.

vircurex robbed me of i0 a while back --- i hate them

ok so do we want do about vircurex.

Class action.

I am sick of this. No communcation

Progress report:

We have a DNS seed node up and a couple of fixed IP's we can hard code into a client.  Plus, we have 2-3 nodes running 0.8.6-2 now.  That sets us up nicely to release a current client with source, Windows and Linux executables.  Stay tuned...

I bought a bit of this coin

Quick update from the wallet upgrade:  I've now a mostly finished version of I0coin implemented on top of the bleeding-edge Bitcoin code, see https://github.com/domob1812/i0coin.  The only thing still missing before we can make a release is a patch I submitted to upstream Bitcoin that is necessary to fix a defect with headers-first syncing.  (The issue is present in Bitcoin as well but much more severe for short block times, long chains and merge-mining -- all combined by I0coin, unfortunately.)  And, of course, some more testing.

If you are not afraid of compiling the code from the repository, you can even give it a try right now.  If you want to do that, please use the "temporary" branch, i. e., https://github.com/domob1812/i0coin/tree/temporary.  You may also need to -connect=51.254.131.226 (my own already updated node) for the initial sync.  After you have all headers, you don't need this anymore and can connect to any other node as you like.  Running (ideally publically reachable) nodes with this code helps strengthen the network for when everyone upgrades.

It may be possible to update without redownloading the chain (i. e., just leave your existing data directory), but I have not tested that.  Be sure to make a backup of everything before you try, in every case!  Also, please do not yet mine with the new client on a larger scale -- you can test mining a few blocks, but not too many consecutive blocks (you definitely shouldn't activate BIP32 or BIP66 on your node).

While mining, you just have to make sure that the BIPs don't activate.  As long as you (and everyone else on the new code combined) have far less than 75% of the hashrate, it is fine.  (It would, in fact, even be good to get testing results from miners!)  The only thing that can happen is that you effectively "51% attack" the network and fork off everyone with the old client, but only if you have more than 75% (or, most probably, actually 95%) of the hashrate.