To validate the new `NFT\0` protocol pattern, the following dummy transactions were constructed and decoded:
#### Example 1: Basic NFToa message
```
[OP_RETURN] [NFT\0] [OP_FALSE] ["Login to Gaudio App"] [0x01]
```
**Hex representation:**
```
6a // OP_RETURN
04 4e465400 // push 4 bytes: "NFT\0"
00 // OP_FALSE
11 4c6f67696e20746f2047617564696f20417070 // push "Login to Gaudio App" (17 bytes)
01 01 // push nonce = 0x01
```
**Decoded structure:**
* Protocol ID: `NFT\0` (`4E465400`)
* Marker: `OP_FALSE` (`00`)
* Message: `"Login to Gaudio App"`
* Nonce: `0x01`
---
#### Example 2: Binary metadata
```
[OP_RETURN] [NFT\0] [OP_FALSE] [0xDEADBEEF] [0xA5]
```
**Hex representation:**
```
6a
04 4e465400
00
04 deadbeef
01 a5
```
**Decoded structure:**
* Protocol ID: `NFT\0`
* Marker: `OP_FALSE`
* Message: `DE AD BE EF` (binary payload, 4 bytes)
* Nonce: `A5`
---
### ✅ Expected Results
* OP\_RETURN parsers should detect `NFT\0` as a valid protocol ID.
* Payload is consistently parsed into `[message]` and `[nonce]`.
* Transactions can be rendered with the NFToa brand logo in Cashtab.
* Nonce guarantees uniqueness even if the message content is repeated.