NXT :: descendant of Bitcoin - Updated Information

[blackfyre175]

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?

[1714219392]

1714219392

[hoax]

Started another node with Hallmark on 37.139.12.71, with best wishes to Nxt

[Come-from-Beyond]

Well, I guess you have valid points, but at this time since the blockchain is small, that'll do I guess.
Or maybe it's really best to copy the files.
Let's ask CfB

It's better to copy files. Imagine what will happen if everyone deletes the blockchain simultaneously.

[Come-from-Beyond]

Working on node infrastructure with a full redesign of nxtbase to support 100+.

I'm going to add trusted peers list next to well-known peers. U'll be able to create a mini-cluster that shares all the data. Need to think how to implement it in the best way though.

[laowai80]

It's better to copy files. Imagine what will happen if everyone deletes the blockchain simultaneously.

Ok, I'll update the guide.
So copying the .bak versions is the proper way?

[ZeroTheGreat]

different than other coins which you can mine from scratch

In another words wasting kWh and amortizing you chips (CPU, GPU or even using special types of chips built for one single purpose...) = paying eq. amount of money (which always eq. to human-hours with a few remarks).

[Come-from-Beyond]

Block feeding chunks increased from 128 KiB to 1 MiB

What does this mean exactly, in terms of what it does for the network?

It means that when a feeder gets a request to get new blocks it sends 8 times more blocks at once.

[ferment]

Working on node infrastructure with a full redesign of nxtbase to support 100+.

I'm going to add trusted peers list next to well-known peers. U'll be able to create a mini-cluster that shares all the data. Need to think how to implement it in the best way though.

wellKnownPeers is getting a little crowded with 30 names! I'm interested in this cluster idea.

[Come-from-Beyond]

It's better to copy files. Imagine what will happen if everyone deletes the blockchain simultaneously.

Ok, I'll update the guide.
So copying the .bak versions is the proper way?

No. U must copy *.nxt files. Use *.bak only if *.nxt corrupted.

[laowai80]

It's better to copy files. Imagine what will happen if everyone deletes the blockchain simultaneously.

Ok, I'll update the guide.
So copying the .bak versions is the proper way?

No. U must copy *.nxt files. Use *.bak only if *.nxt corrupted.

Ok, I am just trying to set up a simple guide for users who can't operate in linux at all, so too many options would look too complicated.


One observation.
I downloaded a fresh version of NXT to my home PC, installed with default settings, blockchain synced from 0, all good.

But Active peers tab shows only 14 nodes. Is that not too low? Is the reason - the hallmark protection?

[notsoshifty]

CfB has mentioned that if one gets access to the memory of Java Virtual Machine then your passphrase would be exposed.

That makes forging a *very* risky endeavor!

Wouldn't a big stakeholder have to have the biggest balls in the world to forge?  Everyone knows their IP.  Does everyone know their account number (and balance) if they're forging?  If so, they're a massive target with a huge reward.

To me, this seems key. Has it been addressed?

Putting aside the current client implementation, is it theoretically possible within the API for a node to have enough information to forge/sign a block, but not enough to do anything with the contents of the account (e.g. transfer funds to another account)?

[Come-from-Beyond]

But Active peers tab shows only 14 nodes. Is that not too low? Is the reason - the hallmark protection?

The reason is low value of maxNumberOfConnectedPublicPeers. It was 20, I set it to 10 in 0.4.4. U can see 14 active peers if 4 of them were with red flags at some moment.

[TwinWinNerD]

      24063      5154541454348994634      Dienstag, 24. Dezember 2013 20:54:25   
      
      1      0 + 1      140 B   
      
      1      9348240326299815071      190 %


had some problems with my node, should be back fine now

0.4.4 seems to solve my problems!

[laowai80]

But Active peers tab shows only 14 nodes. Is that not too low? Is the reason - the hallmark protection?

The reason is low value of maxNumberOfConnectedPublicPeers. It was 20, I set it to 10 in 0.4.4. U can see 14 active peers if 4 of them were with red flags at some moment.

Ok, clear now.

[Come-from-Beyond]

Putting aside the current client implementation, is it theoretically possible within the API for a node to have enough information to forge/sign a block, but not enough to do anything with the contents of the account (e.g. transfer funds to another account)?

In future it will be possible to "freeze" an account using multi-sig feature. U can forge but can't do transactions.

[laowai80]

0.4.4 seems to solve my problems!

Yeah, CfB delivers! We get new features and settings as promised!

[Come-from-Beyond]

0.4.4 seems to solve my problems!

Yeah, CfB delivers! We get new features and settings as promised!

Actually, I think it's coz we added more nodes.

[PGPpfKkx]

im a bit paranoid about security. i have 7874 open from the router does this pose any risk?

can in any way my coins be stolen while forging cause i have a pc forging 24/7?

is there any downside of not opening this port? blocks seem to download normally with closed

[TwinWinNerD]

0.4.4 seems to solve my problems!

Yeah, CfB delivers! We get new features and settings as promised!

Actually, I think it's coz we added more nodes.

Looks like we dodged a bullet there. This was like a stresstest and we beat it =)

Gj us all!

[mr_random]

0.4.4 seems to solve my problems!

Yeah, CfB delivers! We get new features and settings as promised!

Actually, I think it's coz we added more nodes.

Looks like we dodged a bullet there. This was like a stresstest and we beat it =)

Gj us all!

+1. I'm liking a lot how the community rallied back from the attack stronger than ever.