Quote from: gbeirn on December 24, 2013, 04:54:10 PM

Quote from: blackfyre175 on December 24, 2013, 04:50:20 PM

Quote from: Come-from-Beyond on December 24, 2013, 01:40:21 PM

Version 0.4.4 - https://dl.dropboxusercontent.com/u/67242472/nxt.zip

Added Jetty DoSFilter (thx to Edward Elric)
Added myScheme, myPort and shareMyAddress parameters (set them to appropriate values, they will be used in next version)
Added enableHallmarkProtection, set it to "false" if u wish to switch the protection off
blacklistingPeriod is set in milliseconds instead of seconds
logPeerCommunication replaced with communicationLoggingMask (1 - log exceptions, 2 - log responses with non-200 HTTP response codes, 4 - log responses with 200 HTTP response codes), mask values can be combined in standard way
Block feeding chunks increased from 128 KiB to 1 MiB.

NB: Change maxRequestsPerSec value from 3000 to ~30 if u run NRS as a Nxt peer.

Could someone please break some of this down for the less technical. I've read about hallmarks in the wiki, is it recommended that someone who has their wallet open a few hours a day runs a hallmarked node?

If not how does hallmark protection effect those not running a hallmarked node?

myScheme, myPort and shareMyAddress What values should they be set to?

Cheers.

Hallmark nodes are looked to by un-hallmarked nodes for blockchain info. When we were being DDoS attacked, the HallMarked ones were the best targets since taking them offline would effect other non-hall marked nodes. Ideally to prevent that, I think all nodes should be hallmarked.

There is no real benefit with having your wallet open or not. It helps the network, sure, but not your particular account. You need a static IP address to run a hallmarked node, or at least one that doesn't change too often.

But if you're forging for a few hours a day hoping to forge a block then there is a benefit correct?