On Sun, Jul 14, 2013 at 10:12:00PM +0000, John Dillon wrote: > For a non-SPV-mode client we can easily do anti-DoS by requiring the peer to > do > "useful work". As the incoming connections slots get used up, simply kick off > the incoming peers who have relayed the least fee-paying transactions and > valid > blocks, keeping the peers who have relayed the most. We can continue to use > the > usual, randomized, logic for outgoing peers to attempt to preserve the > randomized structure of the bitcoin network. Without an ongoing attack nodes > making new connections are unaffected, and during an attack new connections > are > made somewhat easier by the increased numbers of incoming slots made available > as the attackers connections timeout.
My mempool rewrite defined a CMemPoolTx subclass for CTransaction - it shouldn't be too hard to add the required per-node accounting once nodes get unique identifiers. (can be assigned randomly in the beginning, later can be used for permanent node identifiers w/ ssl and message signing) -- 'peter'[:-1]@petertodd.org 00000000000000214cc4e58adcacd8923d4d37b18e4f6b73556443ae7c88f71a
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
