OP_DATA_32(32) 1e19085136cb747d151c53f97ed1778a9631147fe0ce38d12a4236e3c77bc394

OP_CHECKSIG(172)

OP_0(0)

OP_IF(99)

OP_DATA_3(3) ord

OP_DATA_1(1)

OP_DATA_24(24) text/plain;charset=utf-8

OP_0(0)

OP_PUSHDATA2(77) entirely funded by donations. If you can, please consider donating! The donation address is [bc1qguzk63exy7h5uygg8m2tcenca094a8t464jfyvrmr0s6wkt74wls3zr5m3](https://mempool.space/address/bc1qguzk63exy7h5uygg8m2tcenca094a8t464jfyvrmr0s6wkt74wls3zr5m3). This address is 2 of 4 multisig wallet with keys held by [raphjaph](https://twitter.com/raphjaph), [erin](https://twitter.com/realizingerin), [rodarmor](https://twitter.com/rodarmor), and [ordinally](https://twitter.com/veryordinally). Bitcoin received will go towa

OP_PUSHDATA2(77) rds funding maintenance and development of `ord`, as well as hosting costs for [ordinals.com](https://ordinals.com). Thank you for donating! Wallet ------ `ord` relies on Bitcoin Core for private key management and transaction signing. This has a number of implications that you must understand in order to use `ord` wallet commands safely: - Bitcoin Core is not aware of inscriptions and does not perform sat control. Using `bitcoin-cli` commands and RPC calls with `ord` wallets may lead to loss of inscription

OP_DATA_3(3) s.

OP_ENDIF(104)