-
Notifications
You must be signed in to change notification settings - Fork 128
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
.5 pBTC is not distinguishable after sending through the wormhole eth to solana #426 #1086 #543
Comments
Can you please take a look at this issue that you have seen previously and commented that the token picker was the issue. I have worked at getting this fixed many times by sending it back through v1 but the problem is the pBTC is no longer distinguishable. The token picker will only choose a token that it has been configured to choose. This token is no longer recognizable as a one of the tokens configured in the v1 token picker. |
Leoluc has worked on this issue previously trying to tag him but can't seem to get it right. As far as sending the pBTC back through v1. That's not working as there is no way to pick a token that has not been previously configured. Having said that, I am NOT a devloper. So what I have said or observed is speculation. I have spent much time tring to figure out how to resolve the issue but as stated. NOT a developer, I only play one on TV. After working on this and trying to figure out how to fix this, that is all I am qulified for. This is going to take some real developer time and probably coding. Even if I was able to choose the token, I'm afraid of what to do next. And even if I did get it to go back through there is no gaurantee that it would come out on the other side as btc. ` |
@apollo711, I was able to recreate your issue and think your pBTC is still recoverable. Take a look at this run-through: |
I have been in contact with Susu from Wormhole discord for some time. I have tried to make it clear many times that the v1 UI will never be able to select the token in it's current state. I will paste in here what my latest response to Susu.
All of this information is also in the github issue log. Probably in two different places as over the period of time I was redirected by Developer leoluk to contact a different github repository. I think this originated in certusone/wormhole repository and Leo advised me to solana-labs/oyster. Anyway there are issues open in both repositories with all info. But you should be able to possibly make some concussions based on the following response to Susu.
Crypto-BANG — 07/05/2022
Bro do you know how many times I have tried to send the token back through. This has been addressed so many times. You guys just go back take a look and assume, "oh, he just needs to go back and send the token back through" THAT WILL NOT WORK. I KNOW THIS BECAUSE I SPENT ENDLESS HOURS TRYING TO DO THIS!! Not a one of you guys have even read the issue and the details. the v1 token picker can NOT pick the token because it is no longer reckegnized. The v1 protocol was designed specifically for a set of tokens. The formerly pBTC no longer looks like pBTC, therefore the protocol will never be able to select the token in it's current state. Atleast not without what I would think would be some serious coding. I have made many attempts at trying to make this known. What I do know is that for every wrapped token, there is the original somewhere on a blockchain waiting for the time when the wrapped token will be unwrapped. Is this correct? If it is, like I think it is, why doesn't someone do some coordination, find out where the original is and return it to me! All the info should be in all of the blockchain exploreres that I have previously provided. I have been very patient with trying to get this resolved and all I have gotten is the run around. I want to bring this to someone at Sol or wormhole or Saber or pBTC or all all of the above that can understand what has been going on for coming up on two years. This needs to be brought to someone with authority. And I will will not settle for some line of bullshit that would blame it on a decentralized protocol.
[9:29 PM]These things are NOT decentralized. You yourself on a daily basis help things along. If it were not for you and many others these things would never work, 95% of all what is said to be decentralized are so far away from decentralization and most will never be. otherwise the protocols would just simply cease to operate. Please, please bring this to someone with authority who will take a few minutes to review the issue and understand what the problem is. This will not go away, I promise you it will be resolved. These things need to be solved internally. We the community need to self-regulate. If things like this are left to politicians or regulators...we will all be in a world of hurt, going down a path of regulation that we DO NOT want. Not sure why so many do not get this!! Please HELP!!
Crypto-BANG — 07/06/2022
Crypto-BANG — Today at 12:33 AM
Have you heard anything from the dev's. I recieved an email Monday from someone at solana-labs/oyster basically asking me if I am interested in spinning up my own UI and transfering the pBTC from Solana back to ethereum. Sound familair? Yes I would love to transfer the pBTC back to Ethereum. I hate to sound like a broken record but one more time. The pBTC no longer looks like pBTC. So spinning up my own UI, oh and by the way, I'm not a developer so even if I was able to spin up a UI, I'm guessing it will basically be v1 wormhole. As near as I can tell, not being a developer and all, the v1 token picker can NOT pick the token because it is no longer reckegnized. Again assuming the The v1 protocol was designed specifically for a set of tokens, and it was. The formerly pBTC no longer looks like pBTC, therefore the protocol will never be able to select the token in it's current state. I am going to reply to the email with my post that I made to you on 07/05/2022. Also Is this the righrt github solana-labs/oyster ? I never really understood that whole thing with the issue. Please let me know if you have heard anything. The Dev's should be back from there time off? (edited)
July 7, 2022
I look forward to your response that will bring resolution to this very old issue.
CB
Sent with [Proton Mail](https://proton.me/) secure email.
…------- Original Message -------
On Monday, July 18th, 2022 at 12:52 PM, ckeun ***@***.***> wrote:
***@***.***(https://github.com/apollo711), I was able to recreate your issue and think your pBTC is still recoverable. Take a look at this run-through:
[pBTC_recovery.pdf](https://github.com/solana-labs/oyster/files/9133790/pBTC_recovery.pdf)
Let me know if you are interested in instructions on spinning up your own UI and transferring your pBTC from solana back to ethereum.
—
Reply to this email directly, [view it on GitHub](#543 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALKJOQDFMFSKZOHXYKBMOHTVUWDUVANCNFSM5VLHONMQ).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Leo I hate to keep opening new issues but I don't seem to be getting any tracktion. Trying to give all relevent info but having troub;le finding all the info.
#370
Somewhere there is another issue with the same gripe but I have not been able to find it. Still looking
The text was updated successfully, but these errors were encountered: