public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: raymo@riseup•net
To: Erik Aronesty <erik@q32•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Boost Bitcoin circulation, Million Transactions Per Second with stronger privacy
Date: Fri, 18 Jun 2021 13:22:08 -0700	[thread overview]
Message-ID: <fa12f4c65dc9806eb9bca7d4a12165a2@riseup.net> (raw)
In-Reply-To: <CAJowKg+aeWARPDtOrFdwRi2qUuUhSwX-=U3=PY8OUSLgVZzLQA@mail.gmail.com>

I think I respond to sybil attack implicitly in Max response. Since the
only consensus must be between issuer and creditor and they already are
in a kind of web of trust connection.
By the way it would be great if you explain the attack scenario in more
detail and our conventional terms such as issuer, creditor, MT, GT, CT,
etc...
definitely we can solve it as well.


On 2021-06-18 13:37, Erik Aronesty wrote:
> It is vulnerable to sybil attacks or where the recipient is a victim
> of a proxy attack.  If the recipient is not connected to a valid
> Network, then double spends could be allowed.
> 
>  as long as this protocol is intended for use of transactions around a
> dollar or so I don't see that being a financially lucrative attack.
> 
> However consider a large department store.  If I put a "fence" around
> that store and control all of its outbound peer connections, I can
> then allow double spends for the duration of my visit at the store.
> 
> In order to defend against this large retailers would have to use
> distributed / trusted nodes and certificates.
> 
> On Thu, Jun 17, 2021, 4:14 PM raymo via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 
>> Hi,
>> I have a proposal for improve Bitcoin TPS and privacy, here is the
>> post.
>>
> https://raymo-49157.medium.com/time-to-boost-bitcoin-circulation-million-transactions-per-second-and-privacy-1eef8568d180
>> https://bitcointalk.org/index.php?topic=5344020.0
>> Can you please read it and share your idea about it.
>>
>> Cheers
>> Raymo
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


  reply	other threads:[~2021-06-18 20:22 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 13:44 raymo
2021-06-18  1:42 ` Erik Aronesty
2021-06-18 13:44   ` Alex Schoof
2021-06-18 20:00     ` raymo
2021-06-19 21:14       ` Erik Aronesty
2021-06-18 13:37 ` Erik Aronesty
2021-06-18 20:22   ` raymo [this message]
2021-06-20  0:53 ` ZmnSCPxj
2021-06-26 21:54   ` raymo
2021-06-27  4:53     ` ZmnSCPxj
2021-06-27 11:05       ` raymo
2021-06-28  5:20         ` ZmnSCPxj
2021-06-28  6:29           ` raymo
2021-06-28  8:23             ` James Hilliard
2021-06-28  9:52               ` raymo
2021-06-28 11:28                 ` James Hilliard
2021-06-28 16:33                   ` raymo
2021-06-28 15:28             ` ZmnSCPxj
2021-06-28 16:58               ` raymo
2021-06-28 17:58                 ` Alex Schoof
2021-06-28 19:07                   ` raymo
2021-06-29 21:42                     ` ZmnSCPxj
2021-06-30 12:21                       ` raymo
2021-06-28 17:29               ` Tao Effect
2021-06-28 17:38                 ` raymo
2021-06-28 18:05                   ` Ricardo Filipe
2021-06-20  1:59 ` James Hilliard
2021-06-22 18:20   ` Billy Tetrud
2021-07-01 20:11     ` raymo
2021-07-01 20:49       ` Erik Aronesty
2021-07-01 22:15         ` raymo
2021-07-02 17:57           ` Billy Tetrud
2021-07-03  8:02             ` raymo
2021-07-07  3:20               ` Billy Tetrud
2021-07-17 15:50                 ` raymo
2021-07-17 18:54                   ` Tao Effect
2021-08-08  9:11                   ` raymo
2021-08-09  0:03                     ` s7r
2021-08-09 16:22                       ` raymo
     [not found]                         ` <CAL5BAw2f=xJBO743sTb-Cms80ZLsNNbGPAsWsR_Z3JDF51ssoQ@mail.gmail.com>
2021-08-09 20:22                           ` raymo
2022-11-02 17:30                       ` Erik Aronesty

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=fa12f4c65dc9806eb9bca7d4a12165a2@riseup.net \
    --to=raymo@riseup$(echo .)net \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=erik@q32$(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