Inconsistency in Larynx Token Claim Process - why do we need active password ?
While exploring my @threespeak dashboard, I saw the Claim Larynx Token area and it reminded me to claim my Larynx Token for April. Clicking on the Claim button, it prompts to open HIVE keychain and I opened the HIVE keychain with my password and the transaction was broadcasted. However, the dashboard does not reflect any claim. I have saved only my posting password on HIVE keychain, and add my active password only when I require. Then I remove it, just for a safety precaution. I was not sure, if I needed to add my active key to claim my Larynx Token from @threespeak dashboard, but given that, it told me that it was success, so I assumed, it must have claimed the tokens. But to my surprise, nothing changes on the dashboard.
It was good to have the link to the detailed post on the dashboard, you may need to scroll down a bit and click on the link as highlighted above. It will open the link on a new tab. The first process tells to visit the website (https://spk.dlux.io/), click on the GIFT button, and wait for the transaction to process. I claimed my Larynx Token this way last month. The site expects you to have Hive Keychain installed. However, from my experience, last time when I claimed through the dlux site, it prompted me to add the active password to Hive Keychain, which I am not comfortable to store on Hive Keychain always.
Now there is a second way, to claim the Larynx Token using a direct link that validates using HiveSigner, but the good thing is that, it uses the posting key. If you are using HiveSigner to log in using the posting key, then its already saved being protected by a password. So its just a matter of providing that password and it successfully broadcasts the transaction.
You can also see the transaction on hiveblocks, this is mine - https://hiveblocks.com/@sanjeevm . Now going back to my threespeak dashboard, it still does not reflect anything. It still tells me that I claimed last in March, i.e. last month. However, if I go to https://spk.dlux.io/ to check my balance, I can see it has claimed the tokens.
It shows me that I have 16605.64 Larynx Tokens and I have not added my active key to the Hive Keychain, so its still able to fetch these details using my posting password.
So I request the @threespeak team to make this process better and seamless and remove the inconsistency. In your blog you say "HiveSigner Link can be added by any frontend to help users to claim their LARYNX quickly." Then why not you add this ? If there is a reason for keeping the dlux link there, then please provide another option with HiveSigner Link as well. They are different, the HiveSigner Link needs only the posting password so it is much safer option. Also please improve the code behind to show the updated balance, showing the old balance is pretty odd and inconsistent. It should refresh, because if dlux can fetch the balance then why not you ? If we are building a product, then we should build a flawless product, these first steps will impress the future users.
copyrights @sanjeevm - content created uniquely with passion for #HIVE platform — NOT posted anywhere else! #HIVE is my only social diary - my blog is my life.
Posted Using LeoFinance Beta
Hey, can you tell me please how to sell larynx for hive ? It seems not working on dlux exchange.
Honestly I don't know, and plan to hold them. I could not find them on hive-engine as well, so dlux may be the only place that has the market.
Yes the interfaces can be a little confusing. With centralization comes a budget for a well-thought-out interface with someone accountable to make sure it works well. With blockchain, it is like volunteers and speculators do the best they can sometimes. I take it as a right of passage and a way to get there first before others who would be confused out of the process.
Make sure you claim your DUAT tokens (airdrop from Ragnarok that will be turned into tokens to claim NFTs when the game goes live later this year. https://vue.dlux.io/dex/?api=https://inconceivable.hivehoneycomb.com#duat is the link and https://hive.blog/hive-100039/@ragnarok.game/the-ragnarok-claim-drop-is-here#@zekepickleman/rann8s has the instructions. Along the lines of the Larynx claim.
I agree with all the points you have made. The whole process is utterly confusing, lagging, and slow. Should have been much easier UI/UX like our Hive wallet.
Posted Using LeoFinance Beta
I had to claim my own larynx token through hive keychains because i notice I can't claim it elsewhere
If it can be claimed using a posting pwd, then why force someone to use an active password - the team must make the process better.
I'm having troubles with claiming the Ragnarok tokens. As much sa I love Hive some things are really laggy and so over the hand to use in here...
that should not be the case when we are building a product - how can we sell a product that is laggy to outside users !!
Posted Using LeoFinance Beta
True
Posted Using LeoFinance Beta
I have claimed my Larynx token for march. But not this months yet. I used keychain as there's no other ways I can !
Use the direct link that would take you to HiveSigner - I like that way because its safer to use a posting pwd.
Posted Using LeoFinance Beta
There is more complication with Ragnorak claim...there are surpruse changes in the last moment...
Yet to try that, what are those surprise changes ? Is there a post outlining the details ?
Yes there is a post...now u need to collect #duat and that too using Keychain....there is still wip for hivesigner and more in the post.....
https://peakd.com/hive-100039/@ragnarok.game/the-ragnarok-claim-drop-is-here
using keychain login is more easier and faster. Though I am not entitle it,but I helped some friends to set up the keychain and redeem their larynx token. so I prefer the keychain process.
But the point is using the posting key vs active key - posting key is much safer option. If it can be claimed using posting key, then that will be fine, but dlux prompts to add active key.
I think they're working harder to making it seamless, it's probably issues with the UI I guess.
Posted Using LeoFinance Beta
The point is that, they should also embed that link that works with Hivesigner - because its safer and uses posting pwd.
So threespeak is like your favorite frontend, that's cool. I know how frustrating it can be not to be able to view things like these on your favorite frontend. You've claimed these tokens and seen it on keychain, so you know it is there but not seeing it on threespeak just gives you this off feeling. Hehehe. I've been there. Hopefully they fix this soon.
They themselves tell that any front end can embed the HiveSigner link, but then they do not do the same - its like telling someone - hey this is nice but I have not used.
You're right, I totally get it.
I haven't claimed any of the Larynx claims yet. Do the claims stake or they are lost ?
They are distributed over several months, and started in March. You will be able to claim for this month, its lost if you do not claim.
I prefer using my keychain method it's fast and secure but why sometimes we must put public keys information it's safe or dangerous?
Well, the active password should be used carefully, only when needed. Because someone can steal your funds, if they have that.
This post has been manually curated by @bhattg from Indiaunited community. Join us on our Discord Server.
Do you know that you can earn a passive income by delegating your Leo power to @india-leo account? We share 100 % of the curation rewards with the delegators.
Please contribute to the community by upvoting this comment and posts made by @indiaunited.
Your content has been voted as a part of Encouragement program. Keep up the good work!
Use Ecency daily to boost your growth on platform!
Support Ecency
Vote for new Proposal
Delegate HP and earn more