If you're going to be making announcements and whatever, you probably should have taken the time to characterize your observations completely! The failure to do so makes it kinda just look like more lamesauce attempts at market manipulation (not to lob an accusation, it's just what it looks like -- there is a long history of that kind of activity).
> it's too early, at least for me, to know whether peers would drop a node under attack over timeouts,
Do your homework! You're not the first person who ever thought of attacking a bitcoin node. While I'm sure there are areas for improvement, you're not likely to be able to make useful suggestions from a position of almost total ignorance.
again, i've successfully found remote crashes and dos issues in 25 - 30 blockchains. i don't care if you're a biased developer who takes this to heart. i'm going to see to brutalizing bitcoind and making it clear to you what happens when i attack nodes. cocky academics like you motivate me. he who laughs last etc.
This is a great opportunity to get your ego in check. If you're really interested in security, follow the right path. No one here is impressed that you RCE'd slack (likely using someone else's research, and exploit dev nonetheless). No one is impressed with your Twitter or livejournal handle. And btw fuck anti and rj2 and the rest of those spam/scammers.
You probably smell bad. Dork.