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: content/docs/stacks/stacks.js/guides/post-conditions.mdx
+47
Original file line number
Diff line number
Diff line change
@@ -201,6 +201,53 @@ Construct a post-condition for sending / not-sending a specific NFT.
201
201
</Tab>
202
202
</Tabs>
203
203
204
+
## Amount SFT sent / not sent
205
+
206
+
Construct a post-condition for sending / not-sending a specific SFT (semi-fungible token).
207
+
208
+
Semi-Fungible-Tokens (SFTs) are an innovative way to bring multiple ownership of a single unique digital item. SFTs are a combination of an NFT portion and an FT portion: where a unique tuple represents the NFT id and the amount units represented as fungible tokens. Therefore, at least two post-conditions are needed to handle the transfer of an SFT.
209
+
210
+
Check out the SFT starter contract template on the Hiro Platform.
Post-conditions can only ensure the transfer of assets and cannot guarantee the end-state after a transaction. To learn more, read the [post-conditions](/stacks/stacks.js/concepts/post-conditions) guide.
0 commit comments