Did you solve this problem now?
Claude1 using “_” as no-effect number delimiter is pretty standard in many programming languages. So for most developers it would be immediately obvious. But yeah there should be some documentation of these canister functions. Especially when you try something and you get error “3”.
No, I continue to see this.
Ah that makes sense. I come mostly from the nodeJS side so I haven’t seen that before. I appreciate your help a lot, thank you!
I hate to break it to you but 1_234 is perfectly valid in javascript too
hey, Anyone who received the kyc verified email before but still got the “Neuron XXXXXXX is not kyc verified.” error, succeed now? It’s obviously more than 24hours. I’ve opened a ticket but obviously no immediate response. Just want to check that waiting is useful …
Aha! Wow, well there you go. Just proved it in the console. Seriously never seen it in 7 years professional development. knowledge is like swiss cheese.
I’m on that boat as well. Have contacted support with the following answer:
If you received an email confirmation stating that your identity was verified there is no further action required on your end. It may take 1 - 2 business days for your information to be updated in our systems which is likely the cause of the error message you received.
The number of seconds before the neuron will be dissolvable.
Anyone has similar issues? Any way to resolve it beyond just going over each and every neuron?
Also, are there any plans to allow seed change including migration to hardware wallet?
Being vested for 4 years with the same seed presents a lot of risks, especially as it’s unclear how ledger will be supported for the seed claimers.
KYC was approved more than 24H. Still not able to withdraw/dissolve.
error_message = “Neuron xxxx is not kyc verified.”;
I have the same issue. KYC was approved more than 24H and the same error. Please let me know when you know more.
same here KYC issue when I try to disburse
I made a helper script to show you info for all your neurons, like dissolve delay (calculated to days, hours etc), age, voting power, state. You can find it, with instructions, here GitHub - applepiesoft/DfinityManager: dman
It only uses get_account and get_neuron_info, it does not make any calls to change anything, but you should check the source code yourself and decide if you want to use it or not.
Only run what you have checked to be safe, I don’t take any responsibility for any damage. The script is provided as-is.
The script should work if you do not have a private key / seed in use/installed. So I really recommend to run this on a computer where you did not import your private key! Then you don’t need to risk anything. Note you still need to install the dfx SDK first, but keysmith is not required. If you use the air-gapped method, simply run this on your networked computer (no private key) and nothing bad can happen.
PS: at this moment the script might not work if you put it in folders with spaces or weird characters in the folder names. also, if you get network errors (e.g. 504 Gateway Timeout), try again.
Problem solved.
RESULT="$(./dfx canister --network=https://ic0.app --no-wallet call $CANISTER get_account '("$MY_ADDRESS")' --output=raw)"
needs to become RESULT="$(./dfx canister --network=https://ic0.app --no-wallet call $CANISTER get_account '("'$MY_ADDRESS'")' --output=raw)"
Notice the extra ’ around the address variable
That looks great. Thanks.
Do you also have any idea what commands to run to see the ICP lock balance and the ICP reward balance of a given Neuron?
I guess voting power is an approx indication of how many tokens are locked but I don’t have any command ready.
Was someone successful to dissolve a neuron with air-gapped method? If I run the commands from the manual nothing changes in the neuron state.
Great work, just to note that sending ICP via dfx does not appear to be protected in any way for now, hence a malicious version of the script can snatch all the claimed tokens under the current identity.
Absolutely. Hence I wrote that you should check the source code before running it (or decide not to run it, of course).