Nope, really sad indeed. First i made my key in keygens command, and i was not able to export it, but the new testnet was released so this time i created it in an sdk, i saw a python one and i said, why not?! Not knowing that the SDK-JS had the aecli command. OH but it does not stop there, the wallet programs on one and the other are incompatible. you can’t move the wallet from the python one to the nodejs one and viceversa.
Then i dabbed into the python code to make it show me the private key, since i saw there was a “save” command that allowed me to input a hex private key. and Sure enough, I was able to recreate the wallet in python aecli with that string of hex numbers. (Oh, i needed this because you can’t possible change your password once you create it, and I added spaces by mistake. that makes it really hard to process.
So now i know that there is an aecli in node, (which is not in the develop branch because it is gonna be removed, or rather, separated) so i go happily with my recently extracted private key and it says “Secret key size invalid”. I kid you not, that was the whole error message. I had to dive into the code to find out it is using another algorithm, another library (this time from NaCL or libsodium) and it requires (OH NO!) 64bytes, when my key for the python program was only 32bytes.
SIGH. So now, even when i have mined enough to gift you a bit so you can practice, I am still at a loss because I can’t use the tokens i have fined for anything.
I can’t believe the use of wallets in this network is so complicated right now.
Any other suggestions on how i can get tokens from my account to yours?
I have a 32Bytes private key i can the aepp-sdk-python aecli tool. but that tool is currently broken.