-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Withdrawal error #105
Comments
Make sure you update to DET v0.5.0 which was released yesterday. If same error occurs check your det.log (with v0.5.0 explorer.log will be changed into det.log), in most cases the error is about withdrawing too much with DET. If that is indeed the case according det.log then try withdrawing with max button, but then subtract 0.01 dash from that max amount. |
@qwizzie I'm using latest one , I see only explorer.log and it's empty , also I did use different amount like 11 without digits and it's doesn't work |
I don't know how to check version on my PC and I don't know why this version doesn't show DashEvoTool-aarch64-mac % ls -l |
I would just download it again from here : https://github.com/dashpay/dash-evo-tool/releases/tag/v0.5.0 |
2024-11-28T09:05:17.569149Z WARN request routine: rs_dapi_client::dapi_client: retrying error with sleeping 0.01 secs error=ExecutionError { inner: Transport(Grpc(Status { code: Unavailable, message: "invalid peer certificate: Expired", source: Some(tonic::transport::Error(Transport, ConnectError(Custom { kind: InvalidData, error: InvalidCertificate(Expired) }))) })), retries: 0, address: Some(Address { ban_count: 0, banned_until: None, uri: https://167.88.169.16:443/ }) } |
Insufficient identity xxxxx balance is main error. Make sure you refreshed your Evonode so you have latest balance. |
It's issue with DMT , 11 dash doesn't work but 10 was done and another node I removed |
Well, at least you got it out now. I mentioned this withdrawal issue where users need to bypass DET by subtracting a small amount from max amount on Discord in the Dash Core Group channel. So hopefully QE will look into this. |
strange, right now I had 0.015 and I did withdraw request for 0.01. Looks like there some issues with Grpc or something else |
Error: Withdrawal error: Protocol error: platform deserialization error: unable to deserialize ConsensusError : UnexpectedVariant { type_name: "ConsensusError", allowed: Range { min: 0, max: 4 }, found: 65 }
The text was updated successfully, but these errors were encountered: