<oembed><type>rich</type><version>1.0</version><author_name>npub1wjr0w3nzmsn3m706j3n0e5wumjajg7san4pvw3arqjgez0ztnerqjrv6nq</author_name><author_url>https://nostr.ae/npub1wjr0w3nzmsn3m706j3n0e5wumjajg7san4pvw3arqjgez0ztnerqjrv6nq</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2023-01-27&#xA;🗒️ Summary of this message: The writer questions the wisdom of allowing unlimited storage for NFT content as witness data and suggests imposing a size limit for such inscriptions. They propose linking a sat to a deed for proof of ownership but storing the property itself on the blockchain seems nonsensical.&#xA;📝 Original message:I&#39;m curious what opinions exist and what actions might be taken by core&#xA;developers regarding storing unlimited amounts of NFT (or other?) content&#xA;as witness data (https://docs.ordinals.com/inscriptions.html). The ordinal&#xA;scheme is elegant and genius IMHO, but when I think about the future disk&#xA;use of all unpruned nodes, I question whether unlimited storage is wise to&#xA;allow for such use cases. Wouldn&#39;t it be better to find a way to impose a&#xA;size limit similar to OP_RETURN for such inscriptions?&#xA;&#xA;I think it would be useful to link a sat to a deed or other legal construct&#xA;for proof of ownership in the real world, so that real property can be&#xA;transferred on the blockchain using ordinals, but storing the property&#xA;itself on the blockchain seems nonsensical to me.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230127/a6a99a6c/attachment.html&gt;</html></oembed>