-
Notifications
You must be signed in to change notification settings - Fork 41
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
An example of sending a Ston.fi swap transaction in Cookbook #149
Comments
Depends on #142 |
* fix: Minor adjustments to optimize space * chore: Removed the basics from the Cookbook * feat: Place for #146 and #149 * chore: Moved all data structures to dedicated page * feat: Jettons and NFTs got their pages * chore: Moved additional examples of primitive types * chore: moved Int <-> String examples * chore: Moved time and date-related stuff * chore: Moved single-contract communication (mostly about sending stuff) * chore: Moved randomness * chore: Stubs for NFT, FT and Mass communication * chore: Invite to contribute * chore: Algo page stub As mentioned in #161 * chore: Moved access control * chore: Data structure enhancements * chore: Miscellaneous and niche things which don't have a dedicated page (yet?) * chore: Moved randomness a bit * feat: New Cookbook Overview! * chore: Rename Primitive types -> Type conversions * chore: Temporarily archive Cell & Slice examples
I implemented this in my code here: https://github.com/crazybee69/TonDcaBot/blob/main/contracts/ton_dca_wallet.tact#L257 I spent a lot of time trying to send messages including structures, but I couldn't make it work. Native messages with CellBuilder it works well. Here is API reference of StonFi: https://docs.ston.fi/docs/developer-section/api-reference/router#swap-0x25938561 |
Hello! Version 2 of ston.fi looks like it's in development. Should I make an example using version 2 contracts or stick to version 1? |
Let's please target v2 as it's around the corner |
Related issue: #146
Also, it would be nice to have an example of adding liquidity (as suggested by @Gusarich)
The text was updated successfully, but these errors were encountered: