Skip to content

Commit 938cd86

Browse files
Krishang NadgaudaKrishang Nadgauda
authored andcommitted
update signature mint design doc
1 parent fc36235 commit 938cd86

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

contracts/token/signatureMint.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Signature mint design document.
1+
# Signature minting design document.
22

33
This is a live document that explains the 'signature minting' mechanism used in [thirdweb](https://thirdweb.com/) `Token` smart contracts.
44

@@ -21,16 +21,16 @@ The following diagram illustrates how the 'signature minting' flow looks like. F
2121

2222
### Why we're developing `Signature Minting`
2323

24-
We’ve observed that there are largely three distinct contexts under which one mints tokens
24+
We’ve observed that there are largely three distinct contexts under which one mints tokens:
2525

2626
1. Minting tokens for yourself on a contract you own. E.g. a person wants to mint their Twitter profile picture as an NFT.
2727
2. Having an audience mint tokens on a contract you own.
28-
i. The nature of tokens to be minted by the audience is pre-determined by the contract admin. E.g. a 10k NFT drop where the contents of the NFTs to be minted by the audience is already known and determined by the contract admin before the audience comes in to mint NFTs.
29-
ii. The nature of tokens to be minted by the audience is *not* pre-determined by the contract admin. E.g. a course ‘certificate’ dynamically generated with the name of the course participant, to be minted by the course participant at the time of course completion.
28+
1. The nature of tokens to be minted by the audience is pre-determined by the contract admin. E.g. a 10k NFT drop where the contents of the NFTs to be minted by the audience is already known and determined by the contract admin before the audience comes in to mint NFTs.
29+
2. The nature of tokens to be minted by the audience is *not* pre-determined by the contract admin. E.g. a course ‘certificate’ dynamically generated with the name of the course participant, to be minted by the course participant at the time of course completion.
3030

3131
The thirdweb `Drop` contracts serve the cases described in 2(i).
3232

33-
The thirdweb `Token` contracts serve the case described in 2(ii). And the 'signature minting' mechanism is particularly designed to serve the case described in 2(ii).
33+
The thirdweb `Token` contracts serve the cases described in (1) and 2(ii). And the 'signature minting' mechanism is particularly designed to serve the case described in 2(ii).
3434

3535
## Technical Details
3636

0 commit comments

Comments
 (0)