Quote from: tiker on March 19, 2015, 03:18:38 PM

Quote from: patapato on March 19, 2015, 11:13:06 AM

Done, I sent you 111NAS, tx 1252390869854816059, I can see it on your web client. I forged it Sad

because I don't see the other forger now. Please, send 10 NAS to NAS-AXUZ-74SZ-9SB8-5SFUT, so that you will keep 100 NAS for you, and your account will get a strong public key. Tomorrow I will lease my balance to you for a short time to test if everything works, then I can lease for more time.

Thanks. I see the transaction but I'm not able to send them to the account as asked. The client is returning an error "Could not verify transaction bytes (server side).".

Keep forging if you can. I'm hoping it just needs a set number of confirmations before sending but if not I'll poke around a bit to see if I can figure out why.

Odd... The error above appears when I attempt to send NAS from funkyvps3. When sending from my local node, it worked.

Transaction ID   Date   Type   Amount   Fee   Account   Confirmations
10231787055063096754   19/03/2015 12:06:58   Ordinary payment      10   1   NAS-AXUZ-74SZ-9SB8-5SFUT   /
1252390869854816059   19/03/2015 06:07:50   Ordinary payment      111   1   NAS-H5AW-7J9F-7VCY-DJ8NB   221

10 NAS has been sent to NAS-AXUZ-74SZ-9SB8-5SFUT as requested.

With the 100 left, I'm thinking of sending 90 to another account for forging. My local node can forge with the 90 NAS, while funkyvps3 can forge with the last 10 + leased balance. This will add another forger to the network.

Since these are your NAS coins, are you ok with this?