From: vjudeu <vjudeu@gazeta.pl>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Tweaking tapscript instead of public key
Date: Sun, 23 May 2021 18:02:45 +0200 [thread overview]
Message-ID: <132101705-ebaab3ce4df3e652b9f8ce0ce856f62e@pmq7v.m5r2.onet> (raw)
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
As far as I know, P2TR address contains 32-byte public key. It can be used directly by creating Schnorr signature or indirectly, by revealing tapscript. Does it mean that any taproot output could be modified on-the-fly after being confirmed without changing an address? I mean, if we have base point as the private key with P2TR address tb1p0xlxvlhemja6c4dqv22uapctqupfhlxm9h8z3k2e72q4k9hcz7vqqzj3dz, then the owner of that key can modify spending conditions without moving on-chain coins?
[-- Attachment #2: Type: text/html, Size: 502 bytes --]
next reply other threads:[~2021-05-23 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 16:02 vjudeu [this message]
2021-05-23 17:58 ` [bitcoin-dev] Tweaking tapscript instead of public key Ruben Somsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=132101705-ebaab3ce4df3e652b9f8ce0ce856f62e@pmq7v.m5r2.onet \
--to=vjudeu@gazeta.pl \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox