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.

Sign up for GitHub

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

Jump to bottom

Update 4_the_coin_resource_and_create_currency.md #49

Merged
merged 1 commit into from
Oct 26, 2023
Merged

Update 4_the_coin_resource_and_create_currency.md #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions unit-three/lessons/4_the_coin_resource_and_create_currency.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# The `Coin` Resource and `create_currency` Method

Now we know how generics and witness pattern work, let's revisit the `Coin` resource and the `create_currency` method.
Now we know how generics and witness patterns work, let's revisit the `Coin` resource and the `create_currency` method.

## The `Coin` Resource

Expand Down Expand Up @@ -93,7 +93,7 @@ It wraps a singleton field `total_supply` of type `Balance::Supply`:
}
```

`Supply<T>` tracks the total amount of the given custom fungible token of type `T` that is currently in circulation. You can see why this field must be a singleton, as having multiple `Supply` instances for a single token type makes no sense.
`Supply<T>` tracks the total amount of the given custom fungible token of type `T` currently circulating. You can see why this field must be a singleton, as having multiple `Supply` instances for a single token type makes no sense.

### `CoinMetadata`

Expand Down
Loading