Date: Wed, 02 Aug 2023 13:50:30 +0000
To: bitcoin-dev@lists.linuxfoundation.org,
 Keagan McClelland <keagan.mcclelland@gmail.com>
From: Einherjar <realeinherjar@proton.me>
Message-ID: <EGcuw9I68gwGmFMMw_OstpvAHQ0sWleUi3Jfa8t9A14fa5PGYR2EAxJIjwKd8jo5JtUfmyw9taF1qEsQlVoXBpLUxixdlBpIOEhuXzTUSEc=@proton.me>
Feedback-ID: 78313584:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg=pgp-sha512;
 boundary="------eca7aca6586fc1a5718219ad8c421bd264fea599bca2397156c1b1300dcddc95";
 charset=utf-8
Subject: Re: [bitcoin-dev] Concern about "Inscriptions". (Keagan McClelland)
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------eca7aca6586fc1a5718219ad8c421bd264fea599bca2397156c1b1300dcddc95
Content-Type: multipart/mixed;boundary=---------------------1060113ebabf863df03e9b80653437fe

-----------------------1060113ebabf863df03e9b80653437fe
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

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 l=
ead to doxing and privacy issues. Now there are few costs associated to ha=
ving 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 wa=
y
> 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 w=
ay
> to determine whether some of these transactions are spam or not. The UTX=
O
> 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 spac=
e.
> We may very well discover that if we price UTXOs in a way that reflect t=
he
> resource costs that usage of inscriptions would vanish. The trouble thou=
gh
> is that such a mechanism would imply having to pay "rent" for an "accoun=
t"
> with Bitcoin, a proposition that would likely be offensive to a signific=
ant
> portion of the Bitcoin user base.
> =


> Cheers,
> Keags


Einherjar - E7ED 7E35 F072 CA83

Sent with Proton Mail secure email.
-----------------------1060113ebabf863df03e9b80653437fe
Content-Type: application/pgp-keys; filename="publickey - realeinherjar@proton.me - 0xBF60A699.asc"; name="publickey - realeinherjar@proton.me - 0xBF60A699.asc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="publickey - realeinherjar@proton.me - 0xBF60A699.asc"; name="publickey - realeinherjar@proton.me - 0xBF60A699.asc"

LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tCgp4ak1FWkl6YnlSWUpLd1lCQkFI
YVJ3OEJBUWRBWFVRS3dqTXRTdDJEMm1WaDhjbUpMY0pIOVI5bUgrMUgKbW1USWxQUFpyNHJOTVhK
bFlXeGxhVzVvWlhKcVlYSkFjSEp2ZEc5dUxtMWxJRHh5WldGc1pXbHVhR1Z5CmFtRnlRSEJ5YjNS
dmJpNXRaVDdDakFRUUZnb0FQZ1dDWkl6YnlRUUxDUWNJQ1pEbjdYNDE4SExLZ3dNVgpDQW9FRmdB
Q0FRSVpBUUtiQXdJZUFSWWhCTDlncHBrNE1kUUJtQ2hLTytmdGZqWHdjc3FEQUFEU2dnRC8KYXpC
SWZ2dXhHMko0UGVQYTNKK2tIZWdhbW1uejhCRWFIWFB4WU4xb3dRb0JBTDcwSGVPY1VhU2JwTitC
Cm5YRDVIUC8rMitNK1FvSVRHSW03S2JCdExhZ0p6amdFWkl6YnlSSUtLd1lCQkFHWFZRRUZBUUVI
UUIxMApMSFVqOUhFazdEcHJkVnp4aDRSVkRQVElYRDVwK1pNdVl0ditFQnBJQXdFSUI4SjRCQmdX
Q0FBcUJZSmsKak52SkNaRG43WDQxOEhMS2d3S2JEQlloQkw5Z3BwazRNZFFCbUNoS08rZnRmalh3
Y3NxREFBQVEvUUQrCkpkaEJxS1JVNEtpNUVUQUM2VnN6aGhsbmxJWWlTSnhMN1gvaEw5cXZwWWdB
L1JybldpQXgrb3U1dXU2aAo5K2RWTkdHRDkybStHQmdOUjh6QkkxZXhRMFVDCj1aUHRzCi0tLS0t
RU5EIFBHUCBQVUJMSUMgS0VZIEJMT0NLLS0tLS0K
-----------------------1060113ebabf863df03e9b80653437fe--

--------eca7aca6586fc1a5718219ad8c421bd264fea599bca2397156c1b1300dcddc95
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmTKXwYJkOftfjXwcsqDFiEEv2CmmTgx1AGYKEo75+1+NfBy
yoMAAOR9AP9beKIFnucZ/C6E4ZAmddc9uYVTPPUlQwnhORXQUU+3/gD/YCqj
AEH5ImDig9XGoEHr0uShUazItjrUulxcEjUktQ0=
=6nge
-----END PGP SIGNATURE-----


--------eca7aca6586fc1a5718219ad8c421bd264fea599bca2397156c1b1300dcddc95--