-
Notifications
You must be signed in to change notification settings - Fork 221
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
f38af3a
commit 2a91d0a
Showing
10 changed files
with
154 additions
and
120 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,32 +1 @@ | ||
# Priority Fees | ||
|
||
To specify priority fees on Metaboss transactions, use the `--priority/-p` flag. The current priority values are set at: | ||
|
||
|
||
| Priority | MicroLamport Units | | ||
|------------|--------------------| | ||
| "none" | 20 | | ||
| "low" | 20_000 | | ||
| "medium" | 200_000 | | ||
| "high" | 1_000_000 | | ||
| "max" | 2_000_000 | | ||
|------------|--------------------| | ||
|
||
The default value if no priority is specified is `None`. | ||
|
||
The total amount spennt on priority fees per transaction is the microlamports multiplied by the compute units used. The approximate value of each priority level for the `update` subcommands are given below with a hard-coded compute unit value of 50k: | ||
|
||
| Priority | MicroLamport Units | Approximate Value @ $150 | | ||
|------------|-----------|-----------------------------------| | ||
| "none" | 20 | 1 lamport/update | | ||
| "low" | 20_000 | ~$1 for 10k updates | | ||
| "medium" | 200_000 | ~$10 for 10k updates | | ||
| "high" | 1_000_000 | ~$0.01/update @ $150 SOL | | ||
| "max" | 2_000_000 | ~$0.02/update @ $150 SOL | | ||
|------------|-----------|-----------------------------------| | ||
|
||
Currently only `update` subcommands support priority fees. | ||
|
||
**When running large batch updates be sure to consider the cost of priority fees for the level you set!!** | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Priority Fees | ||
|
||
To specify priority fees on Metaboss transactions, use the `--priority/-p` flag. The current priority values are set at: | ||
|
||
|
||
| Priority | MicroLamport Units | | ||
|------------|--------------------| | ||
| "none" | 20 | | ||
| "low" | 20_000 | | ||
| "medium" | 200_000 | | ||
| "high" | 1_000_000 | | ||
| "max" | 2_000_000 | | ||
|------------|--------------------| | ||
|
||
The default value if no priority is specified is `None`. | ||
|
||
The total amount spennt on priority fees per transaction is the microlamports multiplied by the compute units used. Metaboss simulates each tranasaction to determine the compute units required, and then uses that value or a default. | ||
|
||
Setting higher levels of priority fees are unlikely to make a significant difference in the getting transactions confirmed, so it's recommended to use "none" or "low" until Solana network performance improves. However, higher levels are included to give users options. | ||
|
||
**When running large batch updates be sure to consider the cost of priority fees for the level you set!! Medium, High and Max could cost significant amounts of SOL when updating thousands of NFTs.** | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.