path: root/4a/9791c6da9306e34597c77a86c335f650e0229e

Return-Path: <gamedevalice256@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 89DAFC0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  3 Aug 2023 13:33:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 64E7483A41
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  3 Aug 2023 13:33:48 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 64E7483A41
Authentication-Results: smtp1.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20221208 header.b=aVVDZtL0
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.838
X-Spam-Level: 
X-Spam-Status: No, score=-1.838 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001, T_MIME_MALF=0.01] autolearn=ham autolearn_force=no
Received: from smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Rb-Iq5cEqYs7
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  3 Aug 2023 13:33:46 +0000 (UTC)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com
 [IPv6:2a00:1450:4864:20::42f])
 by smtp1.osuosl.org (Postfix) with ESMTPS id E98CB8211D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  3 Aug 2023 13:33:45 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org E98CB8211D
Received: by mail-wr1-x42f.google.com with SMTP id
 ffacd0b85a97d-31783d02093so885266f8f.0
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 03 Aug 2023 06:33:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1691069623; x=1691674423;
 h=to:subject:message-id:date:from:mime-version:from:to:cc:subject
 :date:message-id:reply-to;
 bh=eLmr6XurrfEMp/7gNe8rCsBlNXXUrTZ6/kyf4xOMGzQ=;
 b=aVVDZtL00jPGzWTiSVauS6jBkZGHgBlgkd9+nkrVlVPA4s2rwfGbsosvdN8qqCSAhk
 WEwVO8w0TxdmFiHzS8PjK2w9JMPKLOs+/vgJ1EupbHorFq4nNS0xy8ic62PVOIQYawsJ
 iQUNto1PWj9+byB6PjUTGceyypitVewx2UHScX2oZdN8O9mDgVnnQiUzFKMM7r09qytf
 6RGMCQnn5UjFthfHrURmKSrEb+xP35mxl/Qv7NPKSpfR4oN4hTsPXhzQz5pbO2lw5QOK
 RPanfPfg6JRazz6T5azmxeMheZCzhyUL6k2mfPfC4cnwTuKvJXUvaqkcqfjLIVZCn2Bz
 1GHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1691069623; x=1691674423;
 h=to:subject:message-id:date:from:mime-version:x-gm-message-state
 :from:to:cc:subject:date:message-id:reply-to;
 bh=eLmr6XurrfEMp/7gNe8rCsBlNXXUrTZ6/kyf4xOMGzQ=;
 b=BR+ZFnph7HECtZqE4jghg3+Afknv87dmo5Xllhf4QArCkJ/5UHrfpOTlSX50MVVNlb
 22jnsm9SlbyHE0IFb1HaMwiWdBCjV8Q6EKWbq4k7gmtioQIJ/SQZrDZkHrcY3D/kYqV4
 H5SXT9VtoVimdwf9IiejeUoX2r1zMYYvVmwUcq7HaAHNQY/HOSWpRFOIP3OZKm97q/jA
 Y7+0mGAmoXuUlh8eHciohCVEGYjSLQPxm+Uqm6pSNkcsgSsiRSlW+mv+HHoUkos1LVG+
 5L4Lc54y5G5338FehkKvyWVoE9hcAzxlLt42Ng7necV1ZuyBSWrI1jC+iuFkn9cjiVMM
 g2EQ==
X-Gm-Message-State: ABy/qLYp+yw2PWNXZ4ERgMICQNicPaeo3fO21ySfa8aWUkHLxF0Cl2Dx
 l8nKcJij994uBM3lfGfqdqb75P4+Fqp3HgWBqotPQyvT
X-Google-Smtp-Source: APBJJlFCYe81MyTR2jZ1xVM/LS5xhCGcB3xrEGPvJeCaoEyQDS7IuKsonMZuRIzSoD0MnRcUo8raWErrDXwO5somJtQ=
X-Received: by 2002:a5d:490f:0:b0:317:61af:d64a with SMTP id
 x15-20020a5d490f000000b0031761afd64amr8321153wrq.3.1691069623326; Thu, 03 Aug
 2023 06:33:43 -0700 (PDT)
MIME-Version: 1.0
From: GamedevAlice <gamedevalice256@gmail.com>
Date: Thu, 3 Aug 2023 09:33:32 -0400
Message-ID: <CAJCwDN8gLwSG+y1gMD37TrbYvi7M+q6ub3Eamx3wzQqVbatJDw@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="000000000000305a5b060204d44e"
X-Mailman-Approved-At: Thu, 03 Aug 2023 14:11:54 +0000
Subject: Re: [bitcoin-dev] Concern about "Inscriptions".
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Aug 2023 13:33:48 -0000

--000000000000305a5b060204d44e
Content-Type: text/plain; charset="UTF-8"

After looking into this more deeply (thanks to Luke Dashjr for pointing me
in the right direction) it is now clear to me that storage isn't the real
issue, but rather the "initial blockchain sync" time - in which storage
certainly has a significant role to play, at least currently.

At the moment, UTreeXO seems like a promising first step. Perhaps there is
a more efficient way to sync the chain without having to download
everything and while still verifying it trustlessly.



On Thu, Aug 3, 2023, 7:43 AM , <
bitcoin-dev-request@lists.linuxfoundation.org> wrote:

> Send bitcoin-dev mailing list submissions to
>         bitcoin-dev@lists.linuxfoundation.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> or, via email, send a message with subject or body 'help' to
>         bitcoin-dev-request@lists.linuxfoundation.org
>
> You can reach the person managing the list at
>         bitcoin-dev-owner@lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of bitcoin-dev digest..."
>
>
> Today's Topics:
>
>    1. Re: Concern about "Inscriptions". (Keagan McClelland) (Einherjar)
>    2. Re: Pull-req to enable Full-RBF by default (Daniel Lipshitz)
>    3. Pull-req to remove the arbitrary limits on OP_Return      outputs
>       (Peter Todd)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 02 Aug 2023 13:50:30 +0000
> 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)
> Message-ID:
>
> <EGcuw9I68gwGmFMMw_OstpvAHQ0sWleUi3Jfa8t9A14fa5PGYR2EAxJIjwKd8jo5JtUfmyw9taF1qEsQlVoXBpLUxixdlBpIOEhuXzTUSEc=@
> proton.me>
>
> 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
> 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.
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: publickey - realeinherjar@proton.me - 0xBF60A699.asc
> Type: application/pgp-keys
> Size: 657 bytes
> Desc: not available
> URL: <
> http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230802/cf726d41/attachment-0001.bin
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 249 bytes
> Desc: OpenPGP digital signature
> URL: <
> http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230802/cf726d41/attachment-0001.sig
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 2 Aug 2023 18:29:54 +0300
> From: Daniel Lipshitz <daniel@gap600.com>
> To: Peter Todd <pete@petertodd.org>
> Cc: Bitcoin Protocol Discussion
>         <bitcoin-dev@lists.linuxfoundation.org>
> Subject: Re: [bitcoin-dev] Pull-req to enable Full-RBF by default
> Message-ID:
>         <
> CACkWPs_jKUCBPhvj3mGYQu6erLE5qKxXorXAtJpuGCKSaSjVwQ@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> For clarity purposes.
>
>    1. Our research is based on monitoring main net transactions and network
>    activity - as too is our risk engine. We do not engage in specific
> hashing
>    pool assessments or research.
>    2. It is not easily possible or comfortable to engage with our clients
>    to offer up their client names and applications - the competition is
> fierce
>    and like other industries it is not an acceptable approach to ask.
>    3. The information offered by Coinpaid and posted on this list, provides
>    root addresses which using tools like Chainanlysis, or
>    similar service providers can confirm these addresses are associated
> with
>    Coinspaid. This can validate a significant amount of our traffic.
>    4. Based on the information provided it will be very possible to reach
>    out to Max at Coinpaid - and will be able to confirm GAP600 use with
>    Coinspaid. This is in addition to me posting an email from Max back in
> Dec
>    2022 to this list confirming all of this information.
>    5.  It is more than likely that Changelly has not implemented our
>    service across all irts offerings, a large section of their business is
>    servicing partners.
>
> ________________________________
>
> Daniel Lipshitz
> GAP600| www.gap600.com
> Phone: +44 113 4900 117
> Skype: daniellipshitz123
> Twitter: @daniellipshitz
>
>
> On Wed, Aug 2, 2023 at 1:38?PM Daniel Lipshitz <daniel@gap600.com> wrote:
>
> > Your assessment of my dishonesty is based on your assumption of how I
> > should be running GAP600, your assumptions are baseless and lack
> commercial
> > experience and likewise your conclusions are false.
> >
> > I have provided already back in December clear access to clarify opposite
> > our clients corroborated with easily verifiable trxs activity of a major
> > client of ours. This is more than enough to corroborate our statistics.
> >
> > As far as validating real RBF adoption I have offered a clear option here
> > https://github.com/bitcoin/bitcoin/pull/28132#issuecomment-1661960440
> > something like this or similar would offer a clear assessment of
> adoption.
> > Since you are not able to provide documents or public emails of hashing
> > pools confirming there adoption of Full RBF.
> > ________________________________
> >
> > Daniel Lipshitz
> > GAP600| www.gap600.com
> > Phone: +44 113 4900 117
> > Skype: daniellipshitz123
> > Twitter: @daniellipshitz
> >
> >
> > On Wed, Aug 2, 2023 at 4:28?AM Peter Todd <pete@petertodd.org> wrote:
> >
> >> On Wed, Aug 02, 2023 at 01:27:24AM +0300, Daniel Lipshitz wrote:
> >> > Your research is not thorough and reaches an incorrect conclusion.
> >> >
> >> > As stated many times - we service payment processors and some
> merchants
> >> > directly  - Coinspaid services multiple merchants and process a
> >> > significant amount of BTC they are a well known and active in the
> space
> >> -
> >> > as I provided back in December 2022 a email from Max the CEO of
> >> Coinspaid
> >> > confirming their use of 0-conf as well as providing there cluster
> >> addresses
> >> > to validate there deposit flows see here again -
> >> >
> >>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-December/021239.html
> >> > - if this is not sufficient then please email support@coinspaid.com
> >> and ask
> >> > to be connected to Max or someone from the team who can confirm
> >> Conspaid is
> >> > clients of GAP600. Max also at the time was open to do a call, I can
> >> check
> >> > again now and see if this is still the case and connect you.
> >> >
> >> > That on its own is enough of a sample to validate our statistics.
> >>
> >> Why don't you just give me an example of some merchants using Coinspaid,
> >> and
> >> another example using Coinpayments, who rely on unconfirmed
> transactions?
> >> If
> >> those merchants actually exist it should be very easy to give me some
> >> names of
> >> them.
> >>
> >> Without actual concrete examples for everyone to see for themselves, why
> >> should
> >> we believe you?
> >>
> >> > I have also spoken to Changelly earlier today and they offered to
> email
> >> pro
> >> > @ changelly.com and they will be able to confirm GAP600 as a service
> >>
> >> Emailed; waiting on a reply.
> >>
> >> > provider. Also please send me the 1 trx hash you tested and I can see
> >> if it
> >> > was queried to our system and if so offer some info as to why it wasnt
> >> > approved. Also if you can elaborate how you integrated with Changelly
> -
> >> I
> >> > can check with them if that area is not integrated with GAP600.
> >>
> >> Why don't you just tell me exactly what service Changelly offers that
> >> relies on
> >> unconfirmed transactions, and what characteristics would meet GAP600's
> >> risk
> >> criteria? I and others on this mailing list could easily do test
> >> transactions
> >> if you told us what we can actually test. If your service actually
> works,
> >> then
> >> you can safely provide that information.
> >>
> >> I'm not going to give you any exact tx hashes of transactions I've
> already
> >> done, as I don't want to cause any problems for the owners of the
> >> accounts I
> >> borrowed for testing. Given your lack of honesty so far I have every
> >> reason to
> >> believe they might be retalliated against in some way.
> >>
> >> > As the architect of such a major change to the status of 0-conf
> >> > transactions I would think you would welcome the opportunity to speak
> to
> >> > business and users who actual activities will be impacted by full RBF
> >> > becoming dominant.
> >>
> >> Funny how you say this, without actually giving any concrete examples of
> >> businesses that will be affected. Who exactly are these businesses?
> >> Payment
> >> processors obviously don't count.
> >>
> >> > Are you able to provide the same i.e emails and contacts of people at
> >> > the mining pools who can confirm they have adopted FULL RBF ?
> >>
> >> I've already had multiple mining pools complain to me that they and
> their
> >> employees have been harassed over full-rbf, so obviously I'm not going
> to
> >> provide you with any private contact information I have. There's no need
> >> to
> >> expose them to further harassment.
> >>
> >> If you actually offered an unconfirmed transaction guarantee service,
> >> with real
> >> customers getting an actual benefit, you'd be doing test transactions
> >> frequently and would already have a very good idea of what pools do
> >> full-rbf.
> >> Why don't you already have this data?
> >>
> >> --
> >> https://petertodd.org 'peter'[:-1]@petertodd.org
> >>
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230802/06762493/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Thu, 3 Aug 2023 11:42:40 +0000
> From: Peter Todd <pete@petertodd.org>
> To: bitcoin-dev@lists.linuxfoundation.org
> Subject: [bitcoin-dev] Pull-req to remove the arbitrary limits on
>         OP_Return       outputs
> Message-ID: <ZMuSsBkWqVXO9qoN@petertodd.org>
> Content-Type: text/plain; charset="us-ascii"
>
> https://github.com/bitcoin/bitcoin/pull/28130
>
> Sjors Provoost suggested that I email this mailing list as notice of my
> intent
> to get a pull-req merged that would remove the arbitrary 80-byte, 1 output
> /
> tx, standardness restrictions on OP_Return outputs. His rationale was that
> removing these standardness restrictions could potentially open up
> additional
> transaction pinning(1) vectors. Since this is a potential problem with any
> relaxation of standardness rules, I don't consider this to be an important
> concern. But consider this email your notice.
>
> At least some miners appear to be mining non-bitcoin-core-standard
> transactions. So with respect to the hash power of those miners these
> pinning
> vectors may in fact exist already.
>
>
> # References
>
> 1) https://bitcoinops.org/en/topics/transaction-pinning/
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 833 bytes
> Desc: not available
> URL: <
> http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230803/33786fbc/attachment.sig
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> ------------------------------
>
> End of bitcoin-dev Digest, Vol 99, Issue 6
> ******************************************
>

--000000000000305a5b060204d44e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto">After looking into this more deeply (th=
anks to Luke Dashjr for pointing me in the right direction) it is now clear=
 to me that storage isn&#39;t the real issue, but rather the &quot;initial =
blockchain sync&quot; time - in which storage certainly has a significant r=
ole to play, at least currently.=C2=A0</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">At the moment, UTreeXO seems like a promising first step. Pe=
rhaps there is a more efficient way to sync the chain without having to dow=
nload everything and while still verifying it trustlessly.=C2=A0</div><div =
dir=3D"auto"><br></div><div dir=3D"auto"><br></div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Aug 3, 2023, 7:43 AM ,=
 &lt;<a href=3D"mailto:bitcoin-dev-request@lists.linuxfoundation.org" rel=
=3D"noreferrer noreferrer" target=3D"_blank">bitcoin-dev-request@lists.linu=
xfoundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send=
 bitcoin-dev mailing list submissions to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-dev@lists.linuxfounda=
tion.org" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">bitcoi=
n-dev@lists.linuxfoundation.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://lists.linuxfoundation.org/ma=
ilman/listinfo/bitcoin-dev" rel=3D"noreferrer noreferrer noreferrer norefer=
rer" target=3D"_blank">https://lists.linuxfoundation.org/mailman/listinfo/b=
itcoin-dev</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-dev-request@lists.lin=
uxfoundation.org" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank=
">bitcoin-dev-request@lists.linuxfoundation.org</a><br>
<br>
You can reach the person managing the list at<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-dev-owner@lists.linux=
foundation.org" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">=
bitcoin-dev-owner@lists.linuxfoundation.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of bitcoin-dev digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
=C2=A0 =C2=A01. Re: Concern about &quot;Inscriptions&quot;. (Keagan McClell=
and) (Einherjar)<br>
=C2=A0 =C2=A02. Re: Pull-req to enable Full-RBF by default (Daniel Lipshitz=
)<br>
=C2=A0 =C2=A03. Pull-req to remove the arbitrary limits on OP_Return=C2=A0 =
=C2=A0 =C2=A0 outputs<br>
=C2=A0 =C2=A0 =C2=A0 (Peter Todd)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 02 Aug 2023 13:50:30 +0000<br>
From: Einherjar &lt;<a href=3D"mailto:realeinherjar@proton.me" rel=3D"noref=
errer noreferrer noreferrer" target=3D"_blank">realeinherjar@proton.me</a>&=
gt;<br>
To: <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"norefer=
rer noreferrer noreferrer" target=3D"_blank">bitcoin-dev@lists.linuxfoundat=
ion.org</a>, Keagan McClelland<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"mailto:keagan.mcclelland@gmail.c=
om" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">keagan.mccle=
lland@gmail.com</a>&gt;<br>
Subject: Re: [bitcoin-dev] Concern about &quot;Inscriptions&quot;. (Keagan<=
br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 McClelland)<br>
Message-ID:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;EGcuw9I68gwGmFMMw_OstpvAHQ0sWleUi3Jfa8t9A14=
fa5PGYR2EAxJIjwKd8jo5JtUfmyw9taF1qEsQlVoXBpLUxixdlBpIOEhuXzTUSEc=3D@<a href=
=3D"http://proton.me" rel=3D"noreferrer noreferrer noreferrer noreferrer" t=
arget=3D"_blank">proton.me</a>&gt;<br>
<br>
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br>
<br>
About price space in the UTXO set:<br>
<br>
I am highly concerned with that proposal.<br>
The reason is this could restrict users to do proper UTXO management and le=
ad to doxing and privacy issues. Now there are few costs associated to havi=
ng lots of UTXOs, mainly fees associated with spending low-valued UTXOs.<br=
>
<br>
&gt; There is an open question as to whether or not we should figure out a =
way<br>
&gt; to price space in the UTXO set. I think it is fair to say that given t=
he<br>
&gt; fact that the UTXO set space remains unpriced that we actually have no=
 way<br>
&gt; to determine whether some of these transactions are spam or not. The U=
TXO<br>
&gt; set must be maintained by all nodes including pruned nodes, whereas ma=
in<br>
&gt; block and witness data do not have the same type of indefinite footpri=
nt,<br>
&gt; so in some sense it is an even more significant resource than chain sp=
ace.<br>
&gt; We may very well discover that if we price UTXOs in a way that reflect=
 the<br>
&gt; resource costs that usage of inscriptions would vanish. The trouble th=
ough<br>
&gt; is that such a mechanism would imply having to pay &quot;rent&quot; fo=
r an &quot;account&quot;<br>
&gt; with Bitcoin, a proposition that would likely be offensive to a signif=
icant<br>
&gt; portion of the Bitcoin user base.<br>
&gt; <br>
<br>
&gt; Cheers,<br>
&gt; Keags<br>
<br>
<br>
Einherjar - E7ED 7E35 F072 CA83<br>
<br>
Sent with Proton Mail secure email.<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: publickey - <a href=3D"mailto:realeinherjar@proton.me" rel=3D"norefer=
rer noreferrer noreferrer" target=3D"_blank">realeinherjar@proton.me</a> - =
0xBF60A699.asc<br>
Type: application/pgp-keys<br>
Size: 657 bytes<br>
Desc: not available<br>
URL: &lt;<a href=3D"http://lists.linuxfoundation.org/pipermail/bitcoin-dev/=
attachments/20230802/cf726d41/attachment-0001.bin" rel=3D"noreferrer norefe=
rrer noreferrer noreferrer" target=3D"_blank">http://lists.linuxfoundation.=
org/pipermail/bitcoin-dev/attachments/20230802/cf726d41/attachment-0001.bin=
</a>&gt;<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 249 bytes<br>
Desc: OpenPGP digital signature<br>
URL: &lt;<a href=3D"http://lists.linuxfoundation.org/pipermail/bitcoin-dev/=
attachments/20230802/cf726d41/attachment-0001.sig" rel=3D"noreferrer norefe=
rrer noreferrer noreferrer" target=3D"_blank">http://lists.linuxfoundation.=
org/pipermail/bitcoin-dev/attachments/20230802/cf726d41/attachment-0001.sig=
</a>&gt;<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 2 Aug 2023 18:29:54 +0300<br>
From: Daniel Lipshitz &lt;<a href=3D"mailto:daniel@gap600.com" rel=3D"noref=
errer noreferrer noreferrer" target=3D"_blank">daniel@gap600.com</a>&gt;<br=
>
To: Peter Todd &lt;<a href=3D"mailto:pete@petertodd.org" rel=3D"noreferrer =
noreferrer noreferrer" target=3D"_blank">pete@petertodd.org</a>&gt;<br>
Cc: Bitcoin Protocol Discussion<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfo=
undation.org" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">bi=
tcoin-dev@lists.linuxfoundation.org</a>&gt;<br>
Subject: Re: [bitcoin-dev] Pull-req to enable Full-RBF by default<br>
Message-ID:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"mailto:CACkWPs_jKUCBPhvj3mGYQu6e=
rLE5qKxXorXAtJpuGCKSaSjVwQ@mail.gmail.com" rel=3D"noreferrer noreferrer nor=
eferrer" target=3D"_blank">CACkWPs_jKUCBPhvj3mGYQu6erLE5qKxXorXAtJpuGCKSaSj=
VwQ@mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br>
<br>
For clarity purposes.<br>
<br>
=C2=A0 =C2=A01. Our research is based on monitoring main net transactions a=
nd network<br>
=C2=A0 =C2=A0activity - as too is our risk engine. We do not engage in spec=
ific hashing<br>
=C2=A0 =C2=A0pool assessments or research.<br>
=C2=A0 =C2=A02. It is not easily possible or comfortable to engage with our=
 clients<br>
=C2=A0 =C2=A0to offer up their client names and applications - the competit=
ion is fierce<br>
=C2=A0 =C2=A0and like other industries it is not an acceptable approach to =
ask.<br>
=C2=A0 =C2=A03. The information offered by Coinpaid and posted on this list=
, provides<br>
=C2=A0 =C2=A0root addresses which using tools like Chainanlysis, or<br>
=C2=A0 =C2=A0similar service providers can confirm these addresses are asso=
ciated with<br>
=C2=A0 =C2=A0Coinspaid. This can validate a significant amount of our traff=
ic.<br>
=C2=A0 =C2=A04. Based on the information provided it will be very possible =
to reach<br>
=C2=A0 =C2=A0out to Max at Coinpaid - and will be able to confirm GAP600 us=
e with<br>
=C2=A0 =C2=A0Coinspaid. This is in addition to me posting an email from Max=
 back in Dec<br>
=C2=A0 =C2=A02022 to this list confirming all of this information.<br>
=C2=A0 =C2=A05.=C2=A0 It is more than likely that Changelly has not impleme=
nted our<br>
=C2=A0 =C2=A0service across all irts offerings, a large section of their bu=
siness is<br>
=C2=A0 =C2=A0servicing partners.<br>
<br>
________________________________<br>
<br>
Daniel Lipshitz<br>
GAP600| <a href=3D"http://www.gap600.com" rel=3D"noreferrer noreferrer nore=
ferrer noreferrer" target=3D"_blank">www.gap600.com</a><br>
Phone: +44 113 4900 117<br>
Skype: daniellipshitz123<br>
Twitter: @daniellipshitz<br>
<br>
<br>
On Wed, Aug 2, 2023 at 1:38?PM Daniel Lipshitz &lt;<a href=3D"mailto:daniel=
@gap600.com" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">dan=
iel@gap600.com</a>&gt; wrote:<br>
<br>
&gt; Your assessment of my dishonesty is based on your assumption of how I<=
br>
&gt; should be running GAP600, your assumptions are baseless and lack comme=
rcial<br>
&gt; experience and likewise your conclusions are false.<br>
&gt;<br>
&gt; I have provided already back in December clear access to clarify oppos=
ite<br>
&gt; our clients corroborated with easily verifiable trxs activity of a maj=
or<br>
&gt; client of ours. This is more than enough to corroborate our statistics=
.<br>
&gt;<br>
&gt; As far as validating real RBF adoption I have offered a clear option h=
ere<br>
&gt; <a href=3D"https://github.com/bitcoin/bitcoin/pull/28132#issuecomment-=
1661960440" rel=3D"noreferrer noreferrer noreferrer noreferrer" target=3D"_=
blank">https://github.com/bitcoin/bitcoin/pull/28132#issuecomment-166196044=
0</a><br>
&gt; something like this or similar would offer a clear assessment of adopt=
ion.<br>
&gt; Since you are not able to provide documents or public emails of hashin=
g<br>
&gt; pools confirming there adoption of Full RBF.<br>
&gt; ________________________________<br>
&gt;<br>
&gt; Daniel Lipshitz<br>
&gt; GAP600| <a href=3D"http://www.gap600.com" rel=3D"noreferrer noreferrer=
 noreferrer noreferrer" target=3D"_blank">www.gap600.com</a><br>
&gt; Phone: +44 113 4900 117<br>
&gt; Skype: daniellipshitz123<br>
&gt; Twitter: @daniellipshitz<br>
&gt;<br>
&gt;<br>
&gt; On Wed, Aug 2, 2023 at 4:28?AM Peter Todd &lt;<a href=3D"mailto:pete@p=
etertodd.org" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">pe=
te@petertodd.org</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; On Wed, Aug 02, 2023 at 01:27:24AM +0300, Daniel Lipshitz wrote:<b=
r>
&gt;&gt; &gt; Your research is not thorough and reaches an incorrect conclu=
sion.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; As stated many times - we service payment processors and some=
 merchants<br>
&gt;&gt; &gt; directly=C2=A0 - Coinspaid services multiple merchants and pr=
ocess a<br>
&gt;&gt; &gt; significant amount of BTC they are a well known and active in=
 the space<br>
&gt;&gt; -<br>
&gt;&gt; &gt; as I provided back in December 2022 a email from Max the CEO =
of<br>
&gt;&gt; Coinspaid<br>
&gt;&gt; &gt; confirming their use of 0-conf as well as providing there clu=
ster<br>
&gt;&gt; addresses<br>
&gt;&gt; &gt; to validate there deposit flows see here again -<br>
&gt;&gt; &gt;<br>
&gt;&gt; <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev=
/2022-December/021239.html" rel=3D"noreferrer noreferrer noreferrer norefer=
rer" target=3D"_blank">https://lists.linuxfoundation.org/pipermail/bitcoin-=
dev/2022-December/021239.html</a><br>
&gt;&gt; &gt; - if this is not sufficient then please email <a href=3D"mail=
to:support@coinspaid.com" rel=3D"noreferrer noreferrer noreferrer" target=
=3D"_blank">support@coinspaid.com</a><br>
&gt;&gt; and ask<br>
&gt;&gt; &gt; to be connected to Max or someone from the team who can confi=
rm<br>
&gt;&gt; Conspaid is<br>
&gt;&gt; &gt; clients of GAP600. Max also at the time was open to do a call=
, I can<br>
&gt;&gt; check<br>
&gt;&gt; &gt; again now and see if this is still the case and connect you.<=
br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; That on its own is enough of a sample to validate our statist=
ics.<br>
&gt;&gt;<br>
&gt;&gt; Why don&#39;t you just give me an example of some merchants using =
Coinspaid,<br>
&gt;&gt; and<br>
&gt;&gt; another example using Coinpayments, who rely on unconfirmed transa=
ctions?<br>
&gt;&gt; If<br>
&gt;&gt; those merchants actually exist it should be very easy to give me s=
ome<br>
&gt;&gt; names of<br>
&gt;&gt; them.<br>
&gt;&gt;<br>
&gt;&gt; Without actual concrete examples for everyone to see for themselve=
s, why<br>
&gt;&gt; should<br>
&gt;&gt; we believe you?<br>
&gt;&gt;<br>
&gt;&gt; &gt; I have also spoken to Changelly earlier today and they offere=
d to email<br>
&gt;&gt; pro<br>
&gt;&gt; &gt; @ <a href=3D"http://changelly.com" rel=3D"noreferrer noreferr=
er noreferrer noreferrer" target=3D"_blank">changelly.com</a> and they will=
 be able to confirm GAP600 as a service<br>
&gt;&gt;<br>
&gt;&gt; Emailed; waiting on a reply.<br>
&gt;&gt;<br>
&gt;&gt; &gt; provider. Also please send me the 1 trx hash you tested and I=
 can see<br>
&gt;&gt; if it<br>
&gt;&gt; &gt; was queried to our system and if so offer some info as to why=
 it wasnt<br>
&gt;&gt; &gt; approved. Also if you can elaborate how you integrated with C=
hangelly -<br>
&gt;&gt; I<br>
&gt;&gt; &gt; can check with them if that area is not integrated with GAP60=
0.<br>
&gt;&gt;<br>
&gt;&gt; Why don&#39;t you just tell me exactly what service Changelly offe=
rs that<br>
&gt;&gt; relies on<br>
&gt;&gt; unconfirmed transactions, and what characteristics would meet GAP6=
00&#39;s<br>
&gt;&gt; risk<br>
&gt;&gt; criteria? I and others on this mailing list could easily do test<b=
r>
&gt;&gt; transactions<br>
&gt;&gt; if you told us what we can actually test. If your service actually=
 works,<br>
&gt;&gt; then<br>
&gt;&gt; you can safely provide that information.<br>
&gt;&gt;<br>
&gt;&gt; I&#39;m not going to give you any exact tx hashes of transactions =
I&#39;ve already<br>
&gt;&gt; done, as I don&#39;t want to cause any problems for the owners of =
the<br>
&gt;&gt; accounts I<br>
&gt;&gt; borrowed for testing. Given your lack of honesty so far I have eve=
ry<br>
&gt;&gt; reason to<br>
&gt;&gt; believe they might be retalliated against in some way.<br>
&gt;&gt;<br>
&gt;&gt; &gt; As the architect of such a major change to the status of 0-co=
nf<br>
&gt;&gt; &gt; transactions I would think you would welcome the opportunity =
to speak to<br>
&gt;&gt; &gt; business and users who actual activities will be impacted by =
full RBF<br>
&gt;&gt; &gt; becoming dominant.<br>
&gt;&gt;<br>
&gt;&gt; Funny how you say this, without actually giving any concrete examp=
les of<br>
&gt;&gt; businesses that will be affected. Who exactly are these businesses=
?<br>
&gt;&gt; Payment<br>
&gt;&gt; processors obviously don&#39;t count.<br>
&gt;&gt;<br>
&gt;&gt; &gt; Are you able to provide the same i.e emails and contacts of p=
eople at<br>
&gt;&gt; &gt; the mining pools who can confirm they have adopted FULL RBF ?=
<br>
&gt;&gt;<br>
&gt;&gt; I&#39;ve already had multiple mining pools complain to me that the=
y and their<br>
&gt;&gt; employees have been harassed over full-rbf, so obviously I&#39;m n=
ot going to<br>
&gt;&gt; provide you with any private contact information I have. There&#39=
;s no need<br>
&gt;&gt; to<br>
&gt;&gt; expose them to further harassment.<br>
&gt;&gt;<br>
&gt;&gt; If you actually offered an unconfirmed transaction guarantee servi=
ce,<br>
&gt;&gt; with real<br>
&gt;&gt; customers getting an actual benefit, you&#39;d be doing test trans=
actions<br>
&gt;&gt; frequently and would already have a very good idea of what pools d=
o<br>
&gt;&gt; full-rbf.<br>
&gt;&gt; Why don&#39;t you already have this data?<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; <a href=3D"https://petertodd.org" rel=3D"noreferrer noreferrer nor=
eferrer noreferrer" target=3D"_blank">https://petertodd.org</a> &#39;peter&=
#39;[:-1]@<a href=3D"http://petertodd.org" rel=3D"noreferrer noreferrer nor=
eferrer noreferrer" target=3D"_blank">petertodd.org</a><br>
&gt;&gt;<br>
&gt;<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: &lt;<a href=3D"http://lists.linuxfoundation.org/pipermail/bitcoin-dev/=
attachments/20230802/06762493/attachment-0001.html" rel=3D"noreferrer noref=
errer noreferrer noreferrer" target=3D"_blank">http://lists.linuxfoundation=
.org/pipermail/bitcoin-dev/attachments/20230802/06762493/attachment-0001.ht=
ml</a>&gt;<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 3 Aug 2023 11:42:40 +0000<br>
From: Peter Todd &lt;<a href=3D"mailto:pete@petertodd.org" rel=3D"noreferre=
r noreferrer noreferrer" target=3D"_blank">pete@petertodd.org</a>&gt;<br>
To: <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"norefer=
rer noreferrer noreferrer" target=3D"_blank">bitcoin-dev@lists.linuxfoundat=
ion.org</a><br>
Subject: [bitcoin-dev] Pull-req to remove the arbitrary limits on<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 OP_Return=C2=A0 =C2=A0 =C2=A0 =C2=A0outputs<br>
Message-ID: &lt;<a href=3D"mailto:ZMuSsBkWqVXO9qoN@petertodd.org" rel=3D"no=
referrer noreferrer noreferrer" target=3D"_blank">ZMuSsBkWqVXO9qoN@petertod=
d.org</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;us-ascii&quot;<br>
<br>
<a href=3D"https://github.com/bitcoin/bitcoin/pull/28130" rel=3D"noreferrer=
 noreferrer noreferrer noreferrer" target=3D"_blank">https://github.com/bit=
coin/bitcoin/pull/28130</a><br>
<br>
Sjors Provoost suggested that I email this mailing list as notice of my int=
ent<br>
to get a pull-req merged that would remove the arbitrary 80-byte, 1 output =
/<br>
tx, standardness restrictions on OP_Return outputs. His rationale was that<=
br>
removing these standardness restrictions could potentially open up addition=
al<br>
transaction pinning(1) vectors. Since this is a potential problem with any<=
br>
relaxation of standardness rules, I don&#39;t consider this to be an import=
ant<br>
concern. But consider this email your notice.<br>
<br>
At least some miners appear to be mining non-bitcoin-core-standard<br>
transactions. So with respect to the hash power of those miners these pinni=
ng<br>
vectors may in fact exist already.<br>
<br>
<br>
# References<br>
<br>
1) <a href=3D"https://bitcoinops.org/en/topics/transaction-pinning/" rel=3D=
"noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">https://bit=
coinops.org/en/topics/transaction-pinning/</a><br>
<br>
-- <br>
<a href=3D"https://petertodd.org" rel=3D"noreferrer noreferrer noreferrer n=
oreferrer" target=3D"_blank">https://petertodd.org</a> &#39;peter&#39;[:-1]=
@<a href=3D"http://petertodd.org" rel=3D"noreferrer noreferrer noreferrer n=
oreferrer" target=3D"_blank">petertodd.org</a><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 833 bytes<br>
Desc: not available<br>
URL: &lt;<a href=3D"http://lists.linuxfoundation.org/pipermail/bitcoin-dev/=
attachments/20230803/33786fbc/attachment.sig" rel=3D"noreferrer noreferrer =
noreferrer noreferrer" target=3D"_blank">http://lists.linuxfoundation.org/p=
ipermail/bitcoin-dev/attachments/20230803/33786fbc/attachment.sig</a>&gt;<b=
r>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"noreferrer =
noreferrer noreferrer" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.=
org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">https=
://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
End of bitcoin-dev Digest, Vol 99, Issue 6<br>
******************************************<br>
</blockquote></div></div>

--000000000000305a5b060204d44e--