From: Einherjar <realeinherjar@proton•me>
To: bitcoin-dev@lists•linuxfoundation.org,
Keagan McClelland <keagan.mcclelland@gmail•com>
Subject: Re: [bitcoin-dev] Concern about "Inscriptions". (Keagan McClelland)
Date: Wed, 02 Aug 2023 13:50:30 +0000 [thread overview]
Message-ID: <EGcuw9I68gwGmFMMw_OstpvAHQ0sWleUi3Jfa8t9A14fa5PGYR2EAxJIjwKd8jo5JtUfmyw9taF1qEsQlVoXBpLUxixdlBpIOEhuXzTUSEc=@proton.me> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1296 bytes --]
About price space in the UTXO set:
I am highly concerned with that proposal.
The reason is this could restrict users to do proper UTXO management and lead to doxing and privacy issues. Now there are few costs associated to having lots of UTXOs, mainly fees associated with spending low-valued UTXOs.
> There is an open question as to whether or not we should figure out a way
> to price space in the UTXO set. I think it is fair to say that given the
> fact that the UTXO set space remains unpriced that we actually have no way
> to determine whether some of these transactions are spam or not. The UTXO
> set must be maintained by all nodes including pruned nodes, whereas main
> block and witness data do not have the same type of indefinite footprint,
> so in some sense it is an even more significant resource than chain space.
> We may very well discover that if we price UTXOs in a way that reflect the
> resource costs that usage of inscriptions would vanish. The trouble though
> is that such a mechanism would imply having to pay "rent" for an "account"
> with Bitcoin, a proposition that would likely be offensive to a significant
> portion of the Bitcoin user base.
>
> Cheers,
> Keags
Einherjar - E7ED 7E35 F072 CA83
Sent with Proton Mail secure email.
[-- Attachment #1.2: publickey - realeinherjar@proton.me - 0xBF60A699.asc --]
[-- Type: application/pgp-keys, Size: 657 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
reply other threads:[~2023-08-02 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='EGcuw9I68gwGmFMMw_OstpvAHQ0sWleUi3Jfa8t9A14fa5PGYR2EAxJIjwKd8jo5JtUfmyw9taF1qEsQlVoXBpLUxixdlBpIOEhuXzTUSEc=@proton.me' \
--to=realeinherjar@proton$(echo .)me \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=keagan.mcclelland@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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