Topic: [I0C] I0coin - The Best Choice In Digital Currency - page 45. (Read 82730 times)

Any update on this problem? My coins are still missing & Cryptopia are a bit too quiet for comfort........

This probably means that your port 7000 is already in use; do you have accidentally a daemon still running?  Or some other software that uses this port?  If this is not the case and you think that this may be a bug with rpcallowip, the same bug is most probably present also in upstream Bitcoin - in this case you could try to look for information for this problem in Bitcoin or even file an upstream bug if you can reproduce it there.

Are you running in prune mode or not?

If I remember correctly, this branch connects to both old & new clients, v11.9.9:

https://github.com/domob1812/i0coin/tree/temporary


Or use:


..for the older version.

Does anyone know where we can get hold of the developer, We have compile the new i0coin wallet on the exchange but it seems to have in issue with RPC binding



Everything works fine until re try add an ip via rpcallowip, soon as we add an ip we get the following error message, changing the port is fine



Or if anyone has a link to the old version source cone we can reinstall the old wallet


Thanks

Missing deposits:

If someone can recommend a faucet I'll try to get I0coin added.

Not that I've heard.  What kind of problems are you referring to?

Wallet problems on Cryptopia?

Just wanted to update that 2 days ago, all 10C deposits I was waiting for from CryptoBlox finally DID confirm.
I now have the coins and just wanted to say thanks to who ever made this possible!

Yes, hopefully all is well with the Admin. I sent him another email the other day. That makes 3 now, but still no reply. I seen the adservers error messages too and now 10C faucet button is no longer on Cryptoblox. Maybe another faucet will be started soon, we can hope for that too anyways!

me too
not had any of the payouts confirm since about dec.23rd.
i also sent a message with no response.
i also see that one of the adservers ('adbit') used on the pages is throwing up error messages too. looks
like cryptoblox admin has just not been around for a while... hope it isnt health issues or anything like that

Thanks for checking into the faucet. Hope Cryptoblox restarts or updates wallet, I'd really like the coins, haha :p
If not yeah, another faucet would be great!

CryptoBlox hasn't logged in since early November, but I PM'ed him anyway.  The wallet doesn't seem to be syncing with the block chain even though payouts are still being generated and posted.  If CryptoBlox updates the wallet or just restarts it should come back online.  In the mean time, I wouldn't use the faucet.  We may need to get another one.

I've been a bit curious about them because their payouts are not showing up on the block explorer.  I'll send a PM and ask.

Based on four years of operation I don't see any immediate problems.  Nevertheless, we should do a review of parameters.  Maybe 'sidhujag' would like to be an independent, unbiased reviewer.  The best way to improve a coin is to try to find weaknesses, and even do stress tests.

Been using the 10C faucet @ cryptoblox.com. Payouts is alright for a faucet. Unfortunately I have 9 deposits now that are not confirmed. Last confirmed deposit was on 12/26/15. Sent an email a week ago to faucet support, but as of date no reply. Does anyone know if there's a problem with this faucet? It's depositing, just not confirming   Thanks in advance for you time

If you change block times you probably need to adjust size of block and all other params that go with that.

Point taken.

It wouldn't hurt to do a review to ensure parameters are optomized.  And optomized parameters today may not be in a year.  They may need to evolve based on a number of factors.  Average transactions per block, average block size, etc.

I'd expect it's a continuous, iterative process.

Thanks for the heads up.


domob, brooksby,
Do you know of any questionable parameter settings?

Here is an example for you. It may or may not apply to this project but applies to one that I'm working on.

If you modify the block time from say 10 minutes to 1 minute you must assess bloat. The max size of a tx is 100k and max size of 1M per block. Logically you shoudl consider reducing max tx size of 10k and max block size of 100k, however with max tx size of 10k you can't fit a standard tx with anything above 50 or so txins so you need to keep that at 100k. Now you have the ability for a single tx to fill up an entire block (which may or may not open up other security ramifications in the system as a black box). Another thing to consider is the amount of blocks to keep by default with bitcoin's IBD push, since by default its set to a certain "size" in MB and changing max block size will affect this change because it seems optimized for this "size". It is set to 288 by default but if you reduce max block to 100k then you would want to set this to 2880 to match the same amount of data stored before pruning.

If you keep block size to 1M then you have 10x more bloat than bitcoin and that may invalidate any hope for it to survive under the logical pretense that storage efficiency will outweigh the network bandwidth constraints that would exist with 10x more bloat (this is because bandwidth costs more than storage in a blockchain network).

THis is just an example of 1 single parameter changing, now multiply that with x number of ramifications for every parameter now you have atleast 1000x extra checks to do by making something like 5 changes to the consensus model (that is an over-exaggeration but you get what I mean now?)