I didn't see anything in your link that told me what I needed in order to see witness data and I've never tried to do it so I used an LLM and this is what it told me I needed to extract the data:
-bitcoin-cli (to dump the raw transaction)
-jq or another parser to extract witness fields
-xxd or Python/Go/Rust to reassemble hex into binary
-Knowledge of file formats / scripting skills
Here is for OP_Return:
- copy / paste hex to binary with one command
One seems harder to get as a normie...
Also, as a knots node, I am not forced to send data I don't want to participate in. If it ends up on the chain anyway, atleast I wasn't complicate in propogating it
Login to reply
Replies (1)
The effort is almost the same, for reading OP_RETURN using bitcoin_cli the script would look very similar - i.e. it reads the bytes following "OP_RETURN" (i.e. "6a" in hex), for ordinals/inscriptions the script reads the bytes that follow "ord" (i.e. "6f7264" in hex) and it skips the "4d" bytes every 520 bytes...
Of course people will create viewers like mempool space that make this much easier. Same as they did for the data in witness/inscriptions: 
Transaction eadfab095bfe5bcfde6024126ef139ac0e98f19dcb4c8fc4e96bfa87cc39141e | Ordiscan
Explore ordinals and inscriptions on Bitcoin. Search and browse inscriptions, runes, rare sats, BRC-20, and more...