I’ve tried various browsers, clearing my cache, tried from a newly generated wallet, all with the same result. Could someone explain to me why this is happening, how I might be able to prevent such behavior in the future?
Hi Something, thank you for your swift reply. The problem is with generating the transaction in CW. I’ll have to see if other issues appear when I try to sign it but first I need a transaction to sign.
Doesn’t make a difference, coindaddy CW has the same support / functionality but also results in the same error. I’ve had this issue before and after trying periodically it did start working out of the blue after a few months… but now we are back to square one, would hate to have to wait another few months
I don’t know about Armory so I can’t tell if CounterTools can create a CP transaction the way you want ( https://github.com/Jpja/CounterTools ), but I think it would take you a minute to find out, if you don’t mind checking it out.