default fundable hook per-app
#209
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Motivation
Each app written using the SVM SDK should have exactly one
fundable hookmarked as the default one.When an
endpoint/ctoris annotated with#[fundable]without specifying an explicitfundable hookname - the default one will be used.Moreover, when sending coins using a simple-coin transaction to an App account - SVM will execute the logic of the
default fundable hook(giving a chance for the running app to update its internal storage).Future apps that will be written without using the SVM Rust SDK will have to expose a Wasm function named
svm_fund.This function's signature is
fn () -> (). In other words, the function expects no input and it returns nothing.The SVM SDK will auto-generate the
svm_fundexport behind the scenes.