You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/content/docs/ref/stdlib-deploy.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,9 @@ The trait `Deployable{:tact}` provides a unified mechanism for deployments by im
61
61
62
62
All contracts are deployed by sending them a message. While any message can be used for this purpose, you can use the special [`Deploy{:tact}`](#deploy) message.
63
63
64
-
This message has a single field, `queryId`, provided by the deployer (usually set to zero). If the deployment succeeds, the contract will reply with a [`DeployOk{:tact}`](#deployok) message and echo the same `queryId` in the response.
64
+
This message has a single field, `queryId`, provided by the deployer and is usually set to zero. If the deployment succeeds, the contract will reply with a [`DeployOk{:tact}`](#deployok) message and echo the same `queryId` in the response.
65
+
66
+
Beware that the receiver handling the `Deploy{:tact}` message sends the `DeployOk{:tact}` reply using the [`self.reply(){:tact}`](/ref/core-base#self-reply) function, which returns all excessive funds from the incoming message back to the sender. That is, contracts deployed using the `Deployable{:tact}` trait have a balance of 0 Toncoin after the deployment is completed.
0 commit comments