<?xml version="1.0"?>
<oembed><version>1.0</version><provider_name>&#x30AF;&#x30EA;&#x30D7;&#x30C8;&#x30C9;&#x30C3;&#x30C8;&#x30A4;&#x30F3;</provider_name><provider_url>https://cryptd.in/ja</provider_url><author_name>cryptd.in</author_name><author_url>https://cryptd.in/ja/author/cryptd-in/</author_url><title>Bitcoin Covenants: OP_CAT (BIP 347) - cryptd.in</title><type>rich</type><width>600</width><height>338</height><html>&lt;blockquote class="wp-embedded-content" data-secret="fpMgI98YJk"&gt;&lt;a href="https://cryptd.in/ja/bitcoin-covenants-op_cat-bip-347/"&gt;Bitcoin Covenants: OP_CAT (BIP 347)&lt;/a&gt;&lt;/blockquote&gt;&lt;iframe sandbox="allow-scripts" security="restricted" src="https://cryptd.in/ja/bitcoin-covenants-op_cat-bip-347/embed/#?secret=fpMgI98YJk" width="600" height="338" title="&#x201C;Bitcoin Covenants: OP_CAT (BIP 347)&#x201D; &#x2014; cryptd.in" data-secret="fpMgI98YJk" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"&gt;&lt;/iframe&gt;&lt;script&gt;
/*! This file is auto-generated */
!function(d,l){"use strict";l.querySelector&amp;&amp;d.addEventListener&amp;&amp;"undefined"!=typeof URL&amp;&amp;(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&amp;&amp;!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret="'+t.secret+'"]'),o=l.querySelectorAll('blockquote[data-secret="'+t.secret+'"]'),c=new RegExp("^https?:$","i"),i=0;i&lt;o.length;i++)o[i].style.display="none";for(i=0;i&lt;a.length;i++)s=a[i],e.source===s.contentWindow&amp;&amp;(s.removeAttribute("style"),"height"===t.message?(1e3&lt;(r=parseInt(t.value,10))?r=1e3:~~r&lt;200&amp;&amp;(r=200),s.height=r):"link"===t.message&amp;&amp;(r=new URL(s.getAttribute("src")),n=new URL(t.value),c.test(n.protocol))&amp;&amp;n.host===r.host&amp;&amp;l.activeElement===s&amp;&amp;(d.top.location.href=t.value))}},d.addEventListener("message",d.wp.receiveEmbedMessage,!1),l.addEventListener("DOMContentLoaded",function(){for(var e,t,s=l.querySelectorAll("iframe.wp-embedded-content"),r=0;r&lt;s.length;r++)(t=(e=s[r]).getAttribute("data-secret"))||(t=Math.random().toString(36).substring(2,12),e.src+="#?secret="+t,e.setAttribute("data-secret",t)),e.contentWindow.postMessage({message:"ready",secret:t},"*")},!1)))}(window,document);
//# sourceURL=https://cryptd.in/wp-includes/js/wp-embed.min.js
&lt;/script&gt;</html><thumbnail_url>https://bitcoinmagazine.com/wp-content/uploads/2025/05/Bitcoin-Covenants_-OP_CAT-BIP-347.webp</thumbnail_url><thumbnail_width>600</thumbnail_width><thumbnail_height>315</thumbnail_height><description>Bitcoin Magazine Bitcoin Covenants: OP_CAT (BIP 347) This is the fifth article in a series deep diving into individual covenant proposals that have reached a point of maturity meriting an in-depth breakdown. OP_CAT, put forward for reactivation in tapscript by Ethan Heilman and Armin Sabouri in BIP 347, is not a covenant. It was an opcode that was originally included in the first release of Bitcoin for manipulating data elements on the stack. It was deactivated in 2010 with the release of Bitcoin 0.3.10 along with a number of other opcodes due to concerns of denial of service attacks that could crash nodes. A global maximum limit of 520 bytes [&hellip;]</description></oembed>
