name_update failing

[wwh]

Hi All.

I've been having various problems with namecoin recently, so I decided to start fresh this morning. I created a new wallet, downloaded the latest Linux 64-bit namecoin client from dot-bit.org, and I transferred my namecoins and <names> into it.

After verifying that everything transferred okay I ran:
./namecoind name_update p/<name> '{"key":"<base64 encoded pgp key ~3000 bytes>"}'

I got:
error: {"code":-4,"message":"Error: The transaction was rejected. This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here."}

However, a new transaction still appeared in my "./namecoin listtransactions". Now, several blocks later the transaction still sits with zero confirmations, but my client is up to date with the latest block and has 12 connections.

I had this problem before, and I was hoping that migrating to the new wallet and client would fix it, but it didn't.

Any idea what is causing this error?

[JohnDoe]

The value field can be 1023 bytes at most if I'm not mistaken. That would be my guess of what's causing the error.

[wwh]

It seems you're right that I'm going over the value length limit.

I did some grepping of the source tree:

DESIGN-namecoin.md:* value is a byte array of max length 1023
namecoin.cpp:static const int MAX_VALUE_LENGTH = 1023;

However, it seems like a bug that the transaction would still find its way into my "listtransactions" list and charge my account 0.04 NMC.

[JohnDoe]

Yeah that's definitely a bug.

[khal]

You can "deletetransaction" for now.

[wwh]

./namecoind deletetransaction <txid>
error: {"code":-1,"message":"transaction not in memory - is already in blockchain?"}

When I encountered this before I did: 1) db4.8_dump of wallet.dat 2) deleted all entry pairs starting with 0x02747 3) db4.8_load.

Is that still my best option?

UPDATE: did the dump/edit/load. Everything is working.