-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Showing
2 changed files
with
18 additions
and
0 deletions.
There are no files selected for viewing
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 |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# OP\_Return | ||
|
||
OP\_Return is a bitcoin feature that provides a memo field for transactions. Usage of OP\_Return is limited to prevent network congestion. | ||
|
||
> ⚠️ OP\_Return transactions make any bitcoin sent with the transaction unspendable. Do not send more than the bare minimum plus a network fee when creating an OP\_Return transaction. | ||
Messages stored on the blockchain will be viewable as long as bitcoin exists and can not be censored. | ||
|
||
#### How to send a message using OP\_Return | ||
|
||
1. Create a transaction by entering a recipient address, amount and fee. | ||
2. Select **Add OP Return** from the ellipsis drop-down menu. | ||
3. Enter your memo into the left text box. On the right, your message will be shown in hexadecimal. | ||
4. Click **Review & Send.** Confirm all details on your Trezor and finish the transaction. | ||
5. Once confirmed, the hexadecimal data can be retrieved and decoded from the bitcoin blockchain. | ||
|
||
> 💡 Learn more about [OP\_Return](https://trezor.io/learn/a/use-op\_return-in-trezor-suite) on the Trezor knowledge base  |