Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMø<div class="post">Bitcoin's p2p network is subject to various kinds of denial of service attacks.<br/><br/>There, I said it.<br/><br/>Do you have constructive suggestions for how to fix it, or are you the kind of person who just enjoys breaking things because you can?<br/><br/>Ideas that have been bouncing around my head that may or may not work:<br/><br/>+ have clients tell each other how many transactions per unit of time they're willing to accept.&nbsp; If a client sends you more (within some fuzz factor), drop it.&nbsp; Compile in a default that's based on estimated number of transactions for a typical user and estimate on the number of current users.<br/><br/>+ require some proof-of-work as part of the client-to-client connection process (helps prevent 'Sybil' attacks).<br/><br/>This is an active area of research; see, for example: <a href="http://scholar.google.com/scholar?q=ddos+attacks+by+subverting+membership">http://scholar.google.com/scholar?q=ddos+attacks+by+subverting+membership</a></div> text/html