Skip to content
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

How check it's deployed? #31

Open
SC-One opened this issue Oct 17, 2023 · 0 comments
Open

How check it's deployed? #31

SC-One opened this issue Oct 17, 2023 · 0 comments

Comments

@SC-One
Copy link
Contributor

SC-One commented Oct 17, 2023

in the explainations: https://tact-by-example.org/06-contract-deploy-another , we have this:
When sending any message to a contract, we can attach its stateInit by specifying the code and data fields of the message. This will deploy the contract if it has not already been deployed. If the contract has already been deployed, these fields will be ignored.

Is that meaning it searches in all block chains to find the same address? or how it's doing? And if we send a value below the minimum requirement for storage, what happens?

@anton-trunov anton-trunov transferred this issue from tact-lang/tact Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant