📅 Original date posted:2011-09-08
🗒️ Summary of this message: The alert system should relay messages regardless of the key used, but be cautious of DDoS potential and consider proof-of-work.
📝 Original message:> 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.
>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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110908/584a4849/attachment.html>;
Will [ARCHIVE] /
npub1xe…zrjrx
2023-06-07 04:23:51
in reply to nevent1q…wfc7
Author Public Key
npub1xe4sg9zgsm90v8ge3r0h29jmwjuudcldxfwczaazuph5y5020jvqpzrjrxPublished at
2023-06-07 04:23:51Event JSON
{
"id": "d8e0bd5510bb788d432ebdb5fbadf0ee38ca4d3fd3311975caa85883433ee744",
"pubkey": "366b04144886caf61d1988df75165b74b9c6e3ed325d8177a2e06f4251ea7c98",
"created_at": 1686104631,
"kind": 1,
"tags": [
[
"e",
"ca408b8b7b03516434afb6ed3ea91dc7bfaee26114c11ca355743da9846401b2",
"",
"root"
],
[
"e",
"5e46b770986440627fee3eb2f428ddf01068ab8ea7a416a459aafc8b84beff07",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2011-09-08\n🗒️ Summary of this message: The alert system should relay messages regardless of the key used, but be cautious of DDoS potential and consider proof-of-work.\n📝 Original message:\u003e In fact, I think the alert system should relay (note, NOT display) messages\n\u003e *regardless of the key used*, so it isn't yet another \"our client gets\n\u003e special\n\u003e status\" thing, and can be used for other clients as well.\n\u003e\n\u003e\n\u003e Be careful though, if you relay everything, it suddenly *does* have DDoS\npotential...\n\nno more than other messages such as transactions.\n\n\u003eMaybe require a proof-of-work then?\n\nkind of defeats the purpose of the alert if it takes a long time to issue\none.\n\nI think leave the alert in, but relay alert messages even if they don't use\nthe correct key. This means that if we later decide to add new keys to the\nalert root trust then older clients will still relay these.\n\nmy .02btc\n\nWill\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110908/584a4849/attachment.html\u003e",
"sig": "c7f9205324f2dac66bf4f75792687fa875eedcf0bdb33d4f9e512c2e569764417c6b5b2e10705a67c5d7164952e72e7f4b52c463067421e49a2a3ea03f200caa"
}