Open
Description
Issue To Be Solved
There are many ways a fungible token can be used and we want more transaction templates to be defined for them.
Suggest A Solution
Please leave comments in this issue if you think of a transaction that you would like to be added as a template.
This issue will also be updated with ideas as they are added.
When adding a new template:
- Create an issue for the template you are adding and assign it to yourself. Leave a comment on this post that you are working on it. Include any relevant questions or discussion about your template in the issue that you create.
- Write the template as a
.cdc
file and save it in thetransactions
directory. - Save the fungible token address as
0xFUNGIBLETOKENADDRESS
- Save the example token address as
0xTOKENADDRESS
- Use
ExampleToken
as the token name andexampleTokenVault
, etc. as the token and storage name - Use transaction parameters instead of hard-coded values.
- Write a go template getter in
lib/go/templates/
and runmake generate
in that directory. - Write a test for your transaction in
lib/go/test/
and make sure the test passes. - Ensure that your template and test are well commented.
Template Suggestions
Feel free to choose a template from this list to work on, or make a comment to add your own idea.
- Send tokens to multiple addresses. The addresses and amounts can be configurable parameters to the transaction.
- Remove the public receiver capability from an account.
- Remove the balance capability from an account.
- Create a provider capability and store it in another account's
/private/
domain. - Use an account's provider capability in your
/private/
domain to withdraw tokens from their account and deposit it in your account.