Delivery-date: Fri, 31 May 2024 19:29:08 -0700
Sender: bitcoindev@googlegroups.com
Date: Fri, 31 May 2024 19:27:46 -0700 (PDT)
From: /dev /fd0 <alicexbtong@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <439a982d-d9c1-4749-bcb6-59cc30add099n@googlegroups.com>
Subject: [bitcoindev] AOPP 2.0 using OP_CAT and OP_CSFS
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_64546_973015483.1717208866101"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_64546_973015483.1717208866101
Content-Type: multipart/alternative; 
	boundary="----=_Part_64547_1875510249.1717208866101"

------=_Part_64547_1875510249.1717208866101
Content-Type: text/plain; charset="UTF-8"

Hi Bitcoin Developers,

I have been following the conversation in BIP 322 thread: 
https://groups.google.com/g/bitcoindev/c/RCi1Exs0ZvQ/m/vp6Xo36aBwAJ and did 
some research about all the undesirable things we can do with proposed 
opcodes.

I think its possible to create a worse protocol in which withdrawal is done 
to a personally identifying string. It can only be claimed by the user if 
they generate a public key and get it certified by an identity verifier.

```
(pushes from scriptsig:  certsig, bpubkey, txsig, 0)
IF                      (certsig, bpubkey, txsig)
  <recovery_pubkey>     -skip-
  CHECKSIGVERIFY        -skip-
  <recovery_time>       -skip-
  CHECKLOCKTIMEVERIFY   -skip-
ELSE
  OVER                  (certsig, bpubkey, txsig, bpubkey)
  CHECKSIGVERIFY        (certsig, bpubkey,)
  SHA256                (certsig, SHA256(bpubkey),)
  <id>                  (certsig, SHA256(bpubkey), id)
  CAT                   (certsig, SHA256(bpubkey)|id)
  <tpubkey>             (certsig, SHA256(bpubkey)|id, tpubkey)
  CHECKDATASIG          (1)
ENDIF
```

CHECKDATASIG would be replaced by CHECKSIGFROMSTACK if testing on signet. 

Here's the link to read more about it: 
https://gist.github.com/markblundeberg/bd28871548108fc66d958018b1bde085

/dev/fd0
floppy disk guy

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/439a982d-d9c1-4749-bcb6-59cc30add099n%40googlegroups.com.

------=_Part_64547_1875510249.1717208866101
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Bitcoin Developers,<div><br /></div><div>I have been following the conve=
rsation in BIP 322 thread:=C2=A0<a href=3D"https://groups.google.com/g/bitc=
oindev/c/RCi1Exs0ZvQ/m/vp6Xo36aBwAJ">https://groups.google.com/g/bitcoindev=
/c/RCi1Exs0ZvQ/m/vp6Xo36aBwAJ</a> and did some research about all the undes=
irable things we can do with proposed opcodes.</div><div><br /></div><div>I=
 think its possible to create a worse protocol in which withdrawal is done =
to a personally identifying string. It can only be claimed by the user if t=
hey generate a public key and get it certified by an identity verifier.</di=
v><div><br /></div><div>```<br /></div><div>(pushes from scriptsig: =C2=A0c=
ertsig, bpubkey, txsig, 0)<br />IF =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(certsig, bpubkey, txsig)<br />=C2=A0=
 &lt;recovery_pubkey&gt; =C2=A0 =C2=A0 -skip-<br />=C2=A0 CHECKSIGVERIFY =
=C2=A0 =C2=A0 =C2=A0 =C2=A0-skip-<br />=C2=A0 &lt;recovery_time&gt; =C2=A0 =
=C2=A0 =C2=A0 -skip-<br />=C2=A0 CHECKLOCKTIMEVERIFY =C2=A0 -skip-<br />ELS=
E<br />=C2=A0 OVER =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0(certsig, bpubkey, txsig, bpubkey)<br />=C2=A0 CHECKSIGVERIFY =C2=A0 =
=C2=A0 =C2=A0 =C2=A0(certsig, bpubkey,)<br />=C2=A0 SHA256 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(certsig, SHA256(bpubkey),)<br />=
=C2=A0 &lt;id&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0(certsig, SHA256(bpubkey), id)<br />=C2=A0 CAT =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (certsig, SHA256(bpubkey)|id)<br =
/>=C2=A0 &lt;tpubkey&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (certsig=
, SHA256(bpubkey)|id, tpubkey)<br />=C2=A0 CHECKDATASIG =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0(1)<br />ENDIF<br />```</div><div><br /></div><div>CHECKDA=
TASIG would be replaced by CHECKSIGFROMSTACK if testing on signet. <br /><b=
r />Here's the link to read more about it:=C2=A0<a href=3D"https://gist.git=
hub.com/markblundeberg/bd28871548108fc66d958018b1bde085">https://gist.githu=
b.com/markblundeberg/bd28871548108fc66d958018b1bde085</a></div><div><br /><=
/div><div>/dev/fd0</div><div>floppy disk guy</div><div><br /></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/439a982d-d9c1-4749-bcb6-59cc30add099n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/439a982d-d9c1-4749-bcb6-59cc30add099n%40googlegroups.com</a>.=
<br />

------=_Part_64547_1875510249.1717208866101--

------=_Part_64546_973015483.1717208866101--