Skip to content

Commit 3d5c11c

Browse files
authored
Remove bounces from SBT standard (#99)
Actually we do not need to describe bounce behaviour in standard, it should depend on specific implementation.
1 parent 68a1dc5 commit 3d5c11c

File tree

1 file changed

+0
-15
lines changed

1 file changed

+0
-15
lines changed

text/0085-sbt-standard.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -54,12 +54,6 @@ data:^Cell revoked_at:uint64 content:(Maybe ^Cell) = InternalMsgBody;
5454

5555
`content` - NFT's content, it is passed if `with_content` was true in `prove_ownership`.
5656

57-
In case when `ownership_proof` was bounced back to NFT, NFT should send message to owner with schema:
58-
```
59-
ownership_proof_bounced#c18e86d2 query_id:uint64 item_id:uint256 owner:MsgAddress
60-
data:^Cell content:(Maybe ^Cell) = InternalMsgBody;
61-
```
62-
6357
#### 2. `request_owner`
6458

6559
TL-B schema of inbound message:
@@ -97,12 +91,6 @@ data:^Cell revoked_at:uint64 content:(Maybe ^Cell) = InternalMsgBody;
9791

9892
`content` - SBT's content, it is passed if `with_content` was true in `request_owner`.
9993

100-
In case when `owner_info` was bounced back to SBT, SBT should send message to **initiator** with schema:
101-
```
102-
owner_info_bounced#7ca7b0fe query_id:uint64 item_id:uint256 initiator:MsgAddress owner:MsgAddress
103-
data:^Cell content:(Maybe ^Cell) = InternalMsgBody;
104-
```
105-
10694
#### 3. `destroy`
10795

10896
TL-B schema of an internal message:
@@ -169,7 +157,6 @@ After that SBT will send transfer to `dest` with scheme:
169157
ownership_proof#0524c7ae query_id:uint64 item_id:uint256 owner:MsgAddress
170158
data:^Cell revoked_at:uint64 content:(Maybe ^Cell)
171159
```
172-
If something goes wrong and target contract not accepts message, and it will be bounced back to SBT, SBT will proxy this bounce to owner, this way coins will not stuck on SBT.
173160

174161
##### Ownership info
175162
**anyone** can send message to SBT with this schema:
@@ -182,7 +169,6 @@ After that SBT will send transfer to `dest` with scheme:
182169
owner_info#0dd607e3 query_id:uint64 item_id:uint256 initiator:MsgAddress owner:MsgAddress
183170
data:^Cell revoked_at:uint64 content:(Maybe ^Cell)
184171
```
185-
If something goes wrong and target contract not accepts message, and it will be bounced back to SBT, SBT will proxy this bounce to initiator, this way coins will not stuck on SBT.
186172

187173
#### Verify SBT contract example
188174

@@ -273,4 +259,3 @@ In ETH ([EIP-4973 ABT](https://eips.ethereum.org/EIPS/eip-4973)) - SBT was done
273259
# Future possibilities
274260
275261
Standard looks finalized.
276-

0 commit comments

Comments
 (0)