Delivery-date: Fri, 31 May 2024 19:29:08 -0700 Received: from mail-yw1-f192.google.com ([209.85.128.192]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sDEUV-0004TI-Qs for bitcoindev@gnusha.org; Fri, 31 May 2024 19:29:08 -0700 Received: by mail-yw1-f192.google.com with SMTP id 00721157ae682-629f8a92145sf29408607b3.0 for ; Fri, 31 May 2024 19:29:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1717208940; x=1717813740; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:sender:from:to:cc:subject:date :message-id:reply-to; bh=P3LEuQxwpAN4uy9jHfYGh54Os+Q0xQ/KdEqOEjOnkrE=; b=lTVCvhHF/HaN2+vL8B28xnIZdKsTpFZKUuiFDhMEZabeTI3Ag+l3L3P3aDul4Ydade ASqXzDqCP2krrZ6LIHQ8BG2OQzSQPyM48v5FitdVnpUAq59amtK/96VfdfA/se3MqhYC J4hfFcceQOUeQhbcZYo8rnMXPOK+uqWOC5wtGh9KbCgf1qIUBwxPvw2uzwVnEr0NW/KU /RpOiBIzZf4s0SK9WK5Zg0tEO4Ym4LsL1Wbh/gh69wHHg5EQSsi1T5qVzX4lBusStteB +/jvs76rAtA+gkcr8ZIpQAliuSh0cMQtZ8QQ0xedgPZUORjy5ibiU/Wqc25t+Mz6C4o8 9Obg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717208940; x=1717813740; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:from:to:cc:subject:date:message-id :reply-to; bh=P3LEuQxwpAN4uy9jHfYGh54Os+Q0xQ/KdEqOEjOnkrE=; b=XlkUge9Sk6awNLHyIWlVhjwlFNIRYwmYBB0DD8JmbbA/d9/92v0O0Ss30fdCU6e9cg IPictRYUHSm/r5IOzhvCK9VQDkKP5kSguItUm/NhAwlFYe11wqBmUQZtPflB9pwXGGj3 d5EVdwAm8Q4jIl9ZbYzwTkAimsh8VsFl7uyqHKiy9q7StQfCFp2D/OcFFEDy8mVfxBhb JnkZam4liJVm0/npbfYwC1x9d0RfFASVc49fdadqRm6yYoJ838oEXuR2gwSHnQW2X9s2 loQndjTVadzapvOd3Rg5BsfyYQ3/lFYpvPUemoZ1D89tsUfUijng49R3dkeehr/V1DcP lazg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717208940; x=1717813740; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=P3LEuQxwpAN4uy9jHfYGh54Os+Q0xQ/KdEqOEjOnkrE=; b=bErZiOHKqJbzPQogNuyaVn8fWpNIGfhemIqHDNfjceS3YtaTHFptsYKXgsC4IdiSke VgOiBwd3dIe6uVZ7ZH2En/TtJPfF5jGCUZKp5UE+OXV4CqXrZrOVFtNSwWLCVcz3Lisl o99zB8n2OLOxFub68WPUMdgWTKV2m2WkpC6id8NubkzOTIjFJRlgeVmEDxnMGTvZ4TRb kHFb/d+bHz+CpiR5FAFVKHGVQbXW1iueHnH0FqjNTTmrh8Nve/nbycDyl4LuC0d9SzqQ rOy++AoDjVmJOGcf6oGKFtu1tEkdD0y9we0ZCY7a019q11cDEcXp6Yt74IFim/cARAEj 6Quw== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCVhO9DpXiP2epr4A4y8CCM08IuAmobvcRtjxGNVtj1+pQvZIYWFYYAeoXHRXHp8krvZUJCjfCqHHbdbW0F3ldfhRyaoY2k= X-Gm-Message-State: AOJu0Yx+nBJgHP3y7MJYCMCtOb3+OeYopEq7xc5QRaK97e+69C8n7634 P47X7wNVbkrT7GK43vLzNGEekf/ouFtxyvqS7mamNuiYBC42F1q7 X-Google-Smtp-Source: AGHT+IFpctBzvJ1Cc7sVGzYvlTDA2XA90aVBExKtmz9td+F2Ony9kPdR0iJDNEUDmD9sQyCsfr7MRg== X-Received: by 2002:a25:868f:0:b0:dee:7c5c:e353 with SMTP id 3f1490d57ef6-dfa73d906ddmr3718299276.40.1717208940330; Fri, 31 May 2024 19:29:00 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:7452:0:b0:dfa:8028:8bc9 with SMTP id 3f1490d57ef6-dfa80288e02ls397022276.1.-pod-prod-06-us; Fri, 31 May 2024 19:28:58 -0700 (PDT) X-Received: by 2002:a05:690c:d83:b0:61b:e678:2591 with SMTP id 00721157ae682-62c7970174fmr8863307b3.4.1717208938537; Fri, 31 May 2024 19:28:58 -0700 (PDT) Received: by 2002:a81:ae05:0:b0:622:b23d:3cdf with SMTP id 00721157ae682-62c7812934ems7b3; Fri, 31 May 2024 19:27:47 -0700 (PDT) X-Received: by 2002:a05:6902:1547:b0:df7:9a4b:fe1b with SMTP id 3f1490d57ef6-dfa73be3efbmr787183276.2.1717208866467; Fri, 31 May 2024 19:27:46 -0700 (PDT) Date: Fri, 31 May 2024 19:27:46 -0700 (PDT) From: /dev /fd0 To: Bitcoin Development Mailing List 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" X-Original-Sender: alicexbtong@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_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) -skip- CHECKSIGVERIFY -skip- -skip- CHECKLOCKTIMEVERIFY -skip- ELSE OVER (certsig, bpubkey, txsig, bpubkey) CHECKSIGVERIFY (certsig, bpubkey,) SHA256 (certsig, SHA256(bpubkey),) (certsig, SHA256(bpubkey), id) CAT (certsig, SHA256(bpubkey)|id) (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,

I have been following the conve= rsation in BIP 322 thread:=C2=A0https://groups.google.com/g/bitcoindev= /c/RCi1Exs0ZvQ/m/vp6Xo36aBwAJ and did some research about all the undes= irable 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 t= hey generate a public key and get it certified by an identity verifier.

```
(pushes from scriptsig: =C2=A0c= ertsig, bpubkey, txsig, 0)
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)
=C2=A0= <recovery_pubkey> =C2=A0 =C2=A0 -skip-
=C2=A0 CHECKSIGVERIFY = =C2=A0 =C2=A0 =C2=A0 =C2=A0-skip-
=C2=A0 <recovery_time> =C2=A0 = =C2=A0 =C2=A0 -skip-
=C2=A0 CHECKLOCKTIMEVERIFY =C2=A0 -skip-
ELS= E
=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)
=C2=A0 CHECKSIGVERIFY =C2=A0 = =C2=A0 =C2=A0 =C2=A0(certsig, bpubkey,)
=C2=A0 SHA256 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(certsig, SHA256(bpubkey),)
= =C2=A0 <id> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0(certsig, SHA256(bpubkey), id)
=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)
=C2=A0 <tpubkey> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (certsig= , SHA256(bpubkey)|id, tpubkey)
=C2=A0 CHECKDATASIG =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0(1)
ENDIF
```

CHECKDA= TASIG would be replaced by CHECKSIGFROMSTACK if testing on signet.
Here's the link to read more about it:=C2=A0https://gist.githu= b.com/markblundeberg/bd28871548108fc66d958018b1bde085

<= /div>
/dev/fd0
floppy disk guy

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg= id/bitcoindev/439a982d-d9c1-4749-bcb6-59cc30add099n%40googlegroups.com.=
------=_Part_64547_1875510249.1717208866101-- ------=_Part_64546_973015483.1717208866101--