Skip to content
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

Unable to Un-Delegate HNT after lock period ended #699

Closed
JThobbyist opened this issue Aug 26, 2024 · 2 comments
Closed

Unable to Un-Delegate HNT after lock period ended #699

JThobbyist opened this issue Aug 26, 2024 · 2 comments

Comments

@JThobbyist
Copy link

As the title says, I locked HNT and delegated to MOBILE Sub-Dao for like 6 months. Now the lock period is over and I've already claimed all my rewards but I can't un-delegate my HNT (and therefore I can't unlock them and return them to my wallet).

Here is the simulation error output which is essentially identical to the live output (I've just tried it so many times I don't want to waste any more of my SOL on the transaction fees)

I'm using the Helium Wallet App v2.8.5 on Mainnet-Beta.

Helium Sub Daos Instruction

Program logged: "Instruction: CloseDelegationV0"
Program logged: "Vehnt calculations: VehntInfo { has_genesis: false, vehnt_at_curr_ts: 213082178304160324708269, pre_genesis_end_fall_rate: 0, post_genesis_end_fall_rate: 13476661593099949, genesis_end_vehnt_correction: 0, genesis_end_fall_rate_correction: 0, end_vehnt_correction: 323332064941653982749, end_fall_rate_correction: 13476661593099949 }"
Program logged: "panicked at 'assertion failed: (ctx.accounts.delegated_position.last_claimed_epoch >= to_claim_to_epoch) ||\n TESTING', programs/helium-sub-daos/src/instructions/delegation/close_delegation_v0.rs:129:3"
Program consumed: 47044 of 219701 compute units
Program returned error: "SBF program panicked"

@JThobbyist
Copy link
Author

Well, I waited an extra day after the lock period ended and tried again and, lo and behold, it worked properly. I was able to undelegate and unlock. Weird because the lock countdown got pretty specific towards the end, denoting the hours, so it was definitely over when I created this issue.

I guess the next big issue is how to auto-perma-ban these scammers (or scam-bots?) lol

@abhay
Copy link
Contributor

abhay commented Aug 27, 2024

Indeed. The scam bots are quick. Sorry you had to deal with that and I'm glad you're all settled.

@github-staff github-staff deleted a comment from JThobbyist Aug 27, 2024
@github-staff github-staff deleted a comment from ZhianLin Aug 27, 2024
@github-staff github-staff deleted a comment from masooddahmedd Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@abhay @JThobbyist and others