Namecoin Forum

Posted: **Wed May 25, 2011 11:40 pm**

Anyone else seeing these? Happens periodically, not very often.

received: inv (37 bytes)
  got inventory: tx 8356f24d4b6316bf32e8  new
askfor tx 8356f24d4b6316bf32e8   0
sending getdata: tx 8356f24d4b6316bf32e8
sending: getdata (37 bytes) 
received: tx (2711 bytes)
ERROR: invalid number of arguments for name op
ERROR: ConnectInputsHook() : name_firstupdate on an unexpired name
ERROR: AcceptToMemoryPool() : ConnectInputs failed 8356f24d4b
storing orphan tx 8356f24d4b

Posted: **Thu May 26, 2011 10:31 am**

Yes, i receive those transactions too.
Maybe some people still use an old version which don't automatically purge bad transactions in their wallet and their client send again and again ?

Posted: **Fri May 27, 2011 9:10 am**

If so this may help (I did not test it yet):
http://m0ray.net/sites/default/files/bi ... tx.tar.bz2
http://m0ray.net/sites/default/files/bi ... c_tx64.bin

Posted: **Fri May 27, 2011 11:00 am**

Vince has added a deltransaction method too.
But that bad transaction is not in our wallet... It can be anywhere, and that guy's namecoin send it over and over until it will be accepted or expired, or he updates his software :p

The good question is : if the transaction is considered as invalid, why is it transmitted by the network. I guess vince should add the verifications before relaying the tx.

Namecoin Forum

Errors in debug.log

Errors in debug.log

Re: Errors in debug.log

Re: Errors in debug.log

Re: Errors in debug.log