Bitcoin Forum
November 14, 2024, 05:04:59 AM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: i0 Coin Issues  (Read 1571 times)
mike85123 (OP)
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
August 17, 2011, 08:41:19 PM
 #1

There have been a bunch of issues noted in many different threads regarding the i0 coin clients. I just wanted to make a thread to discuss issues in a central location.

i0coind also seems to have a bug regarding it's NTP implementation.

One of the changes between i0coin and bitcoin was that it was trying to keep the clock more accurate by polling an NTP time server every 5 minutes. It looks like the code to do this isn't very well thought out, and will hang if the ntp server it randomly picks doesn't respond. It doesn't retry, and it doesn't give up after a while, it just freezes.

Since it's choosing a different NTP server each time from a random pool of volunteer NTP servers on the internet, it's not improbable that one of them will stop responding occasionally. Eventually all iocoind processes will hang due to this.

Before the launch, he did say the coind was locking up on him randomly for no reason.
It seems i0coin was made with a branch of bitcoin that has known locking issues when it generates new a new address.

Is anyone else's Win64 client crashing for them in -server mode? I'm running i0coin.exe in -server mode and have my i0coin.conf setup correctly with the following:

rpcuser=user
rpcpassword=pass
rpcallowip=192.168.1.*
rpcport=7332
server=1

Every hour (or less) I notice that my miners return "Problem communicating with Bitcoin RPC". I'm 100% certain that I'm hitting the correct i0coin instance, since I've already managed to generate 4 confirmed blocks, and they are now in my wallet.

Killing i0coin.exe and then restarting it seems to fix the issue. Anyone reason as to why this might occur? Right now I have 14 connections, but I had ~52 connections earlier.

Having the exact same issue, although about every 20 mins.  Doesn't look like anything is wrong, but the i0coin client stops downloading blocks. Terminate the process and restart and it downloads 50 blocks real quick and starts accepting shares from my miners again.

Add any other issues you are having...
mike85123 (OP)
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
August 17, 2011, 08:51:39 PM
 #2

I think I just found another issue.  Seems big to me, maybe not others...

I have my client set to NOT pay transaction fees.

I sent 167.98375486 i0c to the exchange very shortly after receiving them into my wallet (maybe 20 confirmations), but it looks like the client rounded it off to 5 decimal places and took the remaining and tacked it on as a txn fee. or for all of the conspiracy theorists, maybe it is rounding and sending the remainder to another address a la Office Space. In bitcoin, when you send a transaction too early (not enough confirms) it prompts you that it needs a transaction fee. I was never prompted.  I know losing .00000486 i0c is nothing, but if everyone is losing them times thousands of transactions, it starts to smell like some bullshit.

Code:
Status: 3865 confirmations
Date: 8/16/2011 23:29
Debit: -167.98375
Transaction fee: -0.00000486
Net amount: -167.98375486

Since the exchange is down, I can't login to see if I was credited the full amount or the rounded amount, but I bet it is the rounded amount... I only have 1 transaction in my client that includes i0cents, so I can't really check to see if other transactions were similar.

Check your clients to see if you have similar circumstances.
julz
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001



View Profile
August 17, 2011, 10:07:02 PM
 #3

I think I just found another issue.  Seems big to me, maybe not others...

I have my client set to NOT pay transaction fees.

I sent 167.98375486 i0c to the exchange very shortly after receiving them into my wallet (maybe 20 confirmations), but it looks like the client rounded it off to 5 decimal places and took the remaining and tacked it on as a txn fee. or for all of the conspiracy theorists, maybe it is rounding and sending the remainder to another address a la Office Space. In bitcoin, when you send a transaction too early (not enough confirms) it prompts you that it needs a transaction fee. I was never prompted.  I know losing .00000486 i0c is nothing, but if everyone is losing them times thousands of transactions, it starts to smell like some bullshit.

Code:
Status: 3865 confirmations
Date: 8/16/2011 23:29
Debit: -167.98375
Transaction fee: -0.00000486
Net amount: -167.98375486

Since the exchange is down, I can't login to see if I was credited the full amount or the rounded amount, but I bet it is the rounded amount... I only have 1 transaction in my client that includes i0cents, so I can't really check to see if other transactions were similar.

Check your clients to see if you have similar circumstances.

You can set it in these *coin clients all you want to not pay fee it will still take it if you have more than amount sent for balance it does it automatically or if sending all of balance refuse to send until you pay fee it is in I repeat all of them I have ever used and that would be five so far..

The client program ripping off bitdust is the most unconscionable act.
It would be tolerable if the user interface warned what was happening and gave an option to cancel etc. 
As it stands, I think it's a strong seed for mistrust in the program and hurts the image of bitcoin and bitcoin-based systems.
It doesn't matter that the amount is small - it throws off calculations.

It's pretty pointless to moan about it here in an obscure fork thread though I guess.



@electricwings   BM-GtyD5exuDJ2kvEbr41XchkC8x9hPxdFd
mike85123 (OP)
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
August 18, 2011, 01:13:52 AM
 #4

You can set it in these *coin clients all you want to not pay fee it will still take it if you have more than amount sent for balance it does it automatically or if sending all of balance refuse to send until you pay fee it is in I repeat all of them I have ever used and that would be five so far..

Can you explain that a little more.  So if I have 100.95 in my wallet and I send 100, it could possibly take my .95 as a txn fee?
mike85123 (OP)
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
August 18, 2011, 03:13:47 AM
 #5

You can set it in these *coin clients all you want to not pay fee it will still take it if you have more than amount sent for balance it does it automatically or if sending all of balance refuse to send until you pay fee it is in I repeat all of them I have ever used and that would be five so far..

Can you explain that a little more.  So if I have 100.95 in my wallet and I send 100, it could possibly take my .95 as a txn fee?

No though have seen all my .000?.... disappear when sending an even amount in the bitcoin client even with agreeing to pay the fees and having more that that there to cover fee, what I mean is if you send say 1.234 and have 2.345 in your wallet you will be charged the .0005 that is now in effect for the fee so the balance will have decreased 1.2345. That would be without you agreeing to it and having set the paytax=0 in the .conf file.

Never noticed that..  Kind of bullshit. Any way to absolutely prohibit the client from sending the txn fee other than always wiping out your entire balance???

I just went through all of my bitcoin transactions and sure enough what you explain above is true. Not just an i0coin issue as you said.  Kind of feel cheated...  It should ask if you want to pay the fee or not.  Super bullshit when you tell the client that you DON'T want to pay the fee and it sneakily takes it anyways.
Maged
Legendary
*
Offline Offline

Activity: 1204
Merit: 1015


View Profile
August 18, 2011, 03:25:27 AM
 #6

That issue is a regression that is to be fixed in the next Bitcoin version. If you're curious, the fix was originally lost in a code reorganization.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!