📅 Original date posted:2022-12-02
📝 Original message:If fullRBF would become default and this would become dominant, zero-conf
acceptance would become extremely difficult and would impact significantly
this market share because its not the everyday users who would actually
worry about it however the attackers would be all over it.
As it is today the network has brief periods of stress when trxs are
delayed but in general clears regularly and from time to time there is
stress. Today actors' wallets and merchants etc already have the option of
RBF.
________________________________
Daniel Lipshitz
GAP600| www.gap600.com
Phone: +44 113 4900 117
Skype: daniellipshitz123
Twitter: @daniellipshitz
On Fri, Dec 2, 2022 at 12:04 AM Erik Aronesty <erik at q32.com> wrote:
> There has never been any enforcement of miner preferences. The
> convention is changing quickly, since miners are squeezed for cash and want
> to capture every nickel, plus there are bounties for full rbf being posted
> every day.
>
> I would suggest considering to continue doing business, as usual, as if
> full rbf is present.
>
> This means:
>
> - managing risk
> - waiting for confirmations if the risk is too high
> - using lightning if possible
>
> No other coin or chain offers a safer way to do business than lightning
> over bitcoin.
>
>
>
>
> On Thu, Dec 1, 2022 at 7:32 AM Daniel Lipshitz via bitcoin-dev <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>> HI All
>>
>> I am the CEO of GAP600. We guarantee zero confirmed Bitcoin and other
>> crypto transactions, BTC is a primary part of our business. Our guarantee
>> enables our customers to recognise zero-conf deposits. We reimburse our
>> clients value of the trx should we get it wrong and a transaction we
>> confirmed gets double spent.
>>
>> Should full RBF become default enabled and significantly adopted this
>> would have a major impact on the capacity to accept zerof confs on mainnet.
>> With the end result being this use case will be forced to move to a
>> different chain, with lightning being just another option.
>>
>> I wanted to share some statistics about how significant this use case is.
>> GAP600 clients are primarily payment processors and non custodial
>> liquidity providers; you can see some of our clients on our site
>> www.gap600.com. There are also merchants who have developed their own
>> tools so GAP600 statistics are only a subset of the full use case.
>>
>> I do not know of any wallet, exchange or custodian who accepts zero conf
>> without having some sort of solution in place. The market seems to be fully
>> aware of the risks of zero-conf. The opt-RBF seems to be a solution which
>> gives a clear free choice for actors.
>>
>> Statistics for consideration as a sample of the zero conf use case -
>>
>>
>> 1. As of end of Nov 2022 - GAP600 has processed i.e responded to
>> circa 15M transactions
>> 2. These transactions have a cumulative value of 2.3B USD value.
>> 3. We currently are seeing circa 1.5M transactions queired per month.
>>
>>
>> It's a sizable amount of trxs on mainet and we are by no means the full
>> market of platforms accepting zero-conf. I realise there are other
>> considerations which BTC has, I would urge you to take into account the
>> major risk being placed on this significant market share when deciding to
>> make this feature default enabled and encouraging full adoption.
>>
>> Thank you for your consideration
>> Daniel
>> ________________________________
>>
>> Daniel Lipshitz
>> GAP600| www.gap600.com
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20221202/ed67276b/attachment-0001.html>;
Daniel Lipshitz [ARCHIVE] /
npub1t9…fg2yy
2023-06-07 23:17:10
in reply to nevent1q…gpp5
Author Public Key
npub1t97ak5ltnq0v72nv4jssnhw0fr09axwqvc20623jfdnvrajae7nqufg2yyPublished at
2023-06-07 23:17:10Event JSON
{
"id": "cd22ce189e46ed8edd30846ac0c60302c892921950083cd27b67df5d1a0b6712",
"pubkey": "597ddb53eb981ecf2a6caca109ddcf48de5e99c06614fd2a324b66c1f65dcfa6",
"created_at": 1686179830,
"kind": 1,
"tags": [
[
"e",
"b9aae54f80c20d3478c9cc7678b36901aa6558f8fda81676c267fa0e16d559c6",
"",
"root"
],
[
"e",
"d125a65675bddccf6796b153c95c890450045315e9fad9362584bb9ee882c1dc",
"",
"reply"
],
[
"p",
"22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa"
]
],
"content": "📅 Original date posted:2022-12-02\n📝 Original message:If fullRBF would become default and this would become dominant, zero-conf\nacceptance would become extremely difficult and would impact significantly\nthis market share because its not the everyday users who would actually\nworry about it however the attackers would be all over it.\n\nAs it is today the network has brief periods of stress when trxs are\ndelayed but in general clears regularly and from time to time there is\nstress. Today actors' wallets and merchants etc already have the option of\nRBF.\n________________________________\n\nDaniel Lipshitz\nGAP600| www.gap600.com\nPhone: +44 113 4900 117\nSkype: daniellipshitz123\nTwitter: @daniellipshitz\n\n\nOn Fri, Dec 2, 2022 at 12:04 AM Erik Aronesty \u003cerik at q32.com\u003e wrote:\n\n\u003e There has never been any enforcement of miner preferences. The\n\u003e convention is changing quickly, since miners are squeezed for cash and want\n\u003e to capture every nickel, plus there are bounties for full rbf being posted\n\u003e every day.\n\u003e\n\u003e I would suggest considering to continue doing business, as usual, as if\n\u003e full rbf is present.\n\u003e\n\u003e This means:\n\u003e\n\u003e - managing risk\n\u003e - waiting for confirmations if the risk is too high\n\u003e - using lightning if possible\n\u003e\n\u003e No other coin or chain offers a safer way to do business than lightning\n\u003e over bitcoin.\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e On Thu, Dec 1, 2022 at 7:32 AM Daniel Lipshitz via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e HI All\n\u003e\u003e\n\u003e\u003e I am the CEO of GAP600. We guarantee zero confirmed Bitcoin and other\n\u003e\u003e crypto transactions, BTC is a primary part of our business. Our guarantee\n\u003e\u003e enables our customers to recognise zero-conf deposits. We reimburse our\n\u003e\u003e clients value of the trx should we get it wrong and a transaction we\n\u003e\u003e confirmed gets double spent.\n\u003e\u003e\n\u003e\u003e Should full RBF become default enabled and significantly adopted this\n\u003e\u003e would have a major impact on the capacity to accept zerof confs on mainnet.\n\u003e\u003e With the end result being this use case will be forced to move to a\n\u003e\u003e different chain, with lightning being just another option.\n\u003e\u003e\n\u003e\u003e I wanted to share some statistics about how significant this use case is.\n\u003e\u003e GAP600 clients are primarily payment processors and non custodial\n\u003e\u003e liquidity providers; you can see some of our clients on our site\n\u003e\u003e www.gap600.com. There are also merchants who have developed their own\n\u003e\u003e tools so GAP600 statistics are only a subset of the full use case.\n\u003e\u003e\n\u003e\u003e I do not know of any wallet, exchange or custodian who accepts zero conf\n\u003e\u003e without having some sort of solution in place. The market seems to be fully\n\u003e\u003e aware of the risks of zero-conf. The opt-RBF seems to be a solution which\n\u003e\u003e gives a clear free choice for actors.\n\u003e\u003e\n\u003e\u003e Statistics for consideration as a sample of the zero conf use case -\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e 1. As of end of Nov 2022 - GAP600 has processed i.e responded to\n\u003e\u003e circa 15M transactions\n\u003e\u003e 2. These transactions have a cumulative value of 2.3B USD value.\n\u003e\u003e 3. We currently are seeing circa 1.5M transactions queired per month.\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e It's a sizable amount of trxs on mainet and we are by no means the full\n\u003e\u003e market of platforms accepting zero-conf. I realise there are other\n\u003e\u003e considerations which BTC has, I would urge you to take into account the\n\u003e\u003e major risk being placed on this significant market share when deciding to\n\u003e\u003e make this feature default enabled and encouraging full adoption.\n\u003e\u003e\n\u003e\u003e Thank you for your consideration\n\u003e\u003e Daniel\n\u003e\u003e ________________________________\n\u003e\u003e\n\u003e\u003e Daniel Lipshitz\n\u003e\u003e GAP600| www.gap600.com\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20221202/ed67276b/attachment-0001.html\u003e",
"sig": "419dd7ca6a932da6e0eeac29ac69f2a742ced2f3d98acc45b1b9bb5197b584a1b6154260f66fe032ef867ced5ec6876ffb4e73c5dc90c15bbdddf8c2e3a538c9"
}