-
Notifications
You must be signed in to change notification settings - Fork 67
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
Remove token deploy in anticipation of removal of the soroban only built-in token #798
Conversation
I think this change will make it harder to experiment with contracts that interact with tokens because it'll require every developer wanting to interact with a contract to develop their own. I guess soon enough there will be a standard WASM token contract that people can use for testing? It feels like we're going to have a testing hole though. This doesn't need to block this, just noticing. |
Ignore my message above, I misunderstood. I see that there is still the SAC for testing within the SDK. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One ask, otherwise looks good to me.
… only built-in token (stellar#798)" This reverts commit 62a2030.
### What Revert #798 and update env to pull in this bug fix - stellar/rs-soroban-env#612. I'm reverting the deploy change so we can update our examples with this fix and have a more up to date set of changes that we can release if needed.
What
The soroban-only built-in token is being removed in stellar/rs-soroban-env#607. This is the corresponding sdk change required for updating soroban-test-wasms in rs-soroban-env. This PR does not add support for deploy the Stellar Asset Contract. That can be added in later after we decide what that feature would look like.
Note that the rs-soroban-env version is not being bumped in this PR. That can be done in a later commit once the rs-soroban-env PR is merged.