-
Notifications
You must be signed in to change notification settings - Fork 51
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
[BUG] Astroport Smart Contract Update #262
Comments
Interesting. It remind me to start thinking strategically about how to deal with existing dApps in the future. What should we do with native tokens left in dApp wallets? |
@inon-man this is definitely a philosophical question, and I think we'll need to set up a separate issue as a discussion thread for it -- with respect to native tokens left in dApp wallets. Another example, what should be done with the value locked in MIR? Both are really good discussion items. |
Agreed. I think the community needs a debate on this. |
all syntax errors are cleared, moving on to unit testing |
based on this deprecation warning: https://github.com/classic-terra/cw-storage-plus/blob/38e23673958b5e56f2138ca9c1e893cfd4d90034/src/keys.rs#L342 maybe, there is a chance that u64 and U64Key is the same. Nope, it can't be the same. However, there is a version that matches with current wasmd which has legacy supports for U64Key: cw-storage-plus = "0.11.1" Testing about this specific case at: https://github.com/nghuyenthevinh2000/contract-playground/tree/main/contracts/u64key-migrate |
Looks like decent progress, I'm going to make an issue here that sort of just like collects whining from the community and let's go from there |
Which sounds awesome! |
Describe the bug
Astroport has stated that they will not update their existing smart contract to support parity. An solution to provide the ability for end-users to swap LUNC to and from USTC is required.
The text was updated successfully, but these errors were encountered: