Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Thibault Martinez <[email protected]>
  • Loading branch information
PhilippGackstatter and thibault-martinez authored Nov 27, 2023
1 parent e9bb13c commit e8765c7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions tips/TIP-0038/tip-0038.md
Original file line number Diff line number Diff line change
Expand Up @@ -964,7 +964,7 @@ the transaction:

## Native Token Migration

The capability to hold Native Tokens is removed from Alias and NFT Outputs. In Basic and Foundry Outputs the capabaility
The capability to hold Native Tokens is removed from Alias and NFT Outputs. In Basic and Foundry Outputs the capability
is moved from a field to the _Native Token Feature_. Moreover, each output can only hold one Native Token instead of up
to 64. This section specifies the migration.

Expand Down Expand Up @@ -1021,7 +1021,7 @@ of 8 and 15 of possible commitments, then neither one of them can unlock the out
**Backdating blocks**

One variable that was not mentioned yet is how a client can set a block's `Issuing Time`, relative to which the chosen
commitment is validated, which allows for _backdating_ blocks. Backdating blocks by a singificant amount is only
commitment is validated, which allows for _backdating_ blocks. Backdating blocks by a significant amount is only
possible when there is liveness. The most that someone can backdate a block is to
`Accepted Tangle Time - Liveness Threshold Upper Bound`, so if there is liveness (`ATT ~= Wall Clock Time`), then the
most someone could backdate their block is by `Liveness Threshold Upper Bound`.
Expand Down

0 comments on commit e8765c7

Please sign in to comment.