From: Christian Decker <decker.christian@gmail•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Alert System
Date: Fri, 9 Sep 2011 11:15:38 +0200 [thread overview]
Message-ID: <CALxbBHVnwdq7YAGo9pEbQOqy3A=u9ieufozr2T1Y_cuoQa8U6A@mail.gmail.com> (raw)
In-Reply-To: <3658b238-b1bf-4fde-8880-d50c3eaa8ed9@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]
Resending to mailing list as I replied directly...
On Thu, Sep 8, 2011 at 11:03 PM, Christian Decker <
decker.christian@gmail•com> wrote:
>
>
> Will <will@phase•net> wrote:
>
> >> In fact, I think the alert system should relay (note, NOT display)
> >messages
> >> *regardless of the key used*, so it isn't yet another "our client
> >gets
> >> special
> >> status" thing, and can be used for other clients as well.
> >>
> >>
> >> Be careful though, if you relay everything, it suddenly *does* have
> >DDoS
> >potential...
> >
> >no more than other messages such as transactions.
> Only verified and valid trandactions are forwarded which is desired as it
> costs the sender a fee if he attempts to spam, messages have no such
> penalty.
> >
> >>Maybe require a proof-of-work then?
> >
> >kind of defeats the purpose of the alert if it takes a long time to
> >issue
> >one.
> >
> >I think leave the alert in, but relay alert messages even if they don't
> >use
> >the correct key. This means that if we later decide to add new keys to
> >the
> >alert root trust then older clients will still relay these.
> >
> >my .02btc
> >
> >Will
> I'm for keeping it in there as well, maybe even extend it with a mechanism
> to sign other certificates giving alternative client developers the ability
> to issue their own alerts. Think ssl certificates...
>
> Regards,
> Chris
>
> >------------------------------------------------------------------------------
> >Doing More with Less: The Next Generation Virtual Desktop
> >What are the key obstacles that have prevented many mid-market
> >businesses
> >from deploying virtual desktops? How do next-generation virtual
> >desktops
> >provide companies an easier-to-deploy, easier-to-manage and more
> >affordable
> >virtual desktop
> >model.
> http://www.accelacomm.com/jaw/sfnl/114/51426474/_______________________________________________
> >Bitcoin-development mailing list
> >Bitcoin-development@lists•sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>
[-- Attachment #2: Type: text/html, Size: 3116 bytes --]
next prev parent reply other threads:[~2011-09-09 9:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 14:42 David Perry
2011-09-08 15:04 ` Steve
2011-09-08 16:09 ` David Perry
2011-09-08 16:16 ` Matt Corallo
2011-09-08 16:20 ` Pieter Wuille
2011-09-08 16:37 ` John Smith
2011-09-08 16:51 ` Mike Hearn
2011-09-08 16:56 ` Alex Waters
2011-09-08 17:15 ` Luke-Jr
2011-09-08 17:33 ` John Smith
2011-09-08 17:59 ` Luke-Jr
2011-09-08 19:25 ` Will
[not found] ` <3658b238-b1bf-4fde-8880-d50c3eaa8ed9@email.android.com>
2011-09-09 9:15 ` Christian Decker [this message]
2011-09-08 15:20 ` Matt Corallo
2011-09-08 15:25 ` Steve Coughlan
2011-09-08 19:43 ` theymos
2011-09-08 19:45 ` Luke-Jr
2011-09-08 20:17 ` theymos
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='CALxbBHVnwdq7YAGo9pEbQOqy3A=u9ieufozr2T1Y_cuoQa8U6A@mail.gmail.com' \
--to=decker.christian@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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