NXT :: descendant of Bitcoin - Updated Information

[subhead]

im stuck here. is everything alright or should i worry?

24336      4071545868996394636      25.12.2013 05:33:47   
0      0 + 0      0 B   
1      2714685153739703222      1407 %

[S3MKi]

im stuck here. is everything alright or should i worry?

24336      4071545868996394636      25.12.2013 05:33:47   
0      0 + 0      0 B   
1      2714685153739703222      1407 %

same

[davethetrousers]

Node and client both stuck here...

24303      4747512364439223888      25.12.2013 16:57:28   
1      20 + 1      128 B   
1      9313061582945657198      284 %   

[Come-from-Beyond]

Also when it is stuck is it still forging for coins?

It is but on a fork.

Set pullThreshold to 100000. Some hallmarked peers still run 0.4.4 with incorrect blockchain.

[Come-from-Beyond]

24342      6635869272840226493      25.12.2013 19:52:23   
0      0 + 0      0 B   
1      6945809666375691075      1636 %

[gginer]

Can someone send me something so I can start forging?

17070893084359262654

Thanks!

[Anon136]

Will I be rich in 5 years with 500 NXT?  
Also, would you invest right now? are we in a bubble? I have been waiting and it has only gone higher.

Maybe this will help give some perspective. Lets say nxt got to the point where it had the same market cap as bitcoin does now.

(21million/1billion)*500*700=$7,350US

This also means just putting it in your wallet, not forging and just waiting.
Hardly the most profitable way to go about it  

I have my wallet open all day with the 500 sitting on there but I have never recieved anything. what are the chances that you will process any transaction with 500? how do you calculate this

the math is like this:

If you are forging with 500 and the network is forging with 500million (this is just a guess if someone has more reliable data on this please let me know). First divide 500/500million. This gives 0.000001 or 0.0001% chance of forging each block. This means that you would expect to generate your first block on average after forging for 1000000 blocks. So we know that blocks come in at 1 per minute. Meaning that it would take you on average 1000000 minutes. Now all you have to to do is go to google and tell it to convert 1000000 minutes into years. And the answer is that you can expect to forge 1 block every 1.90133 years.

[starik69]

they already have this ability all they have to do is create a new hallmark with a new date and it will invalidate all older hallmark

This is not true. I generated two hallmarks with different dates and both are valid

[heggikawaii]

Can someone send me something so I can start forging?

12039705778998779253

Thanks!

[idev]

Can someone send me something so I can start forging?

12039705778998779253

Thanks!

Get 1 free from the faucet

[bitcoinrocks]

I have two hallmarked nodes running at digitalocean.com.  I noticed they weren't using much more than 100KB/s so I asked around about a VPS provider with more bandwidth and was pointed to swiftslots.com.  I set up a hallmarked node with them but it's also only using about 100KB/s.  The digitalocean nodes have 100NXT and the swiftslots node has 2000NXT.

Why can't I soak up more than that amount of bandwidth?  Do we have enough nodes already?

[starik69]

This is not true. I generated two hallmarks with different dates and both are valid

Is there such possibility CfB?

Check yourself

Code:

2013-12-24
{"hallmark":"b1b1777dd7584ec21a5cbd592ce392e6def372ed4aab7e233b7a3a464adb2e6e000064000000982d330149105a59898c97858eb027e707afe3878e86da95b00aa29193541a6b4e5e549e0914eb8fe273e2851ed1d9da1cc22cfcc9a8fd37d63d8fa11d7976fd06c10a62e4"}

2013-12-10
{"hallmark":"b1b1777dd7584ec21a5cbd592ce392e6def372ed4aab7e233b7a3a464adb2e6e0000640000008a2d330143e4bfb2bc02a08dec8b779677ef04f14ca29f9e3c7e98eeff40231cc0bb62880cd125ec186b5142ab14783cc03f21cd12cb08ce8299aeda49d3c8e37f34afe9a3"}

[Pablito89]

my 3 public nodes are updated and working on 0.4.7e

CfB did you fix the last night problem with the "fake" transactions?

[klee]

Hi guys, I am back at last (Christmas, family etc).
The war is raging I see!

What is the latest files/version I am lost - my client is stopped..

[starik69]

there have been a lot of concerns with Hallmarks (passphrase security, setting up, etc.).

Well, this account has not so much NXT, so it wont be a loss. As I understand, hallmark contains no password or some private key, and what i published has no ip, so it is useless.

[opticalcarrier]

Check yourself

Code:

2013-12-24
{"hallmark":"b1b1777dd7584ec21a5cbd592ce392e6def372ed4aab7e233b7a3a464adb2e6e000064000000982d330149105a59898c97858eb027e707afe3878e86da95b00aa29193541a6b4e5e549e0914eb8fe273e2851ed1d9da1cc22cfcc9a8fd37d63d8fa11d7976fd06c10a62e4"}

2013-12-10
{"hallmark":"b1b1777dd7584ec21a5cbd592ce392e6def372ed4aab7e233b7a3a464adb2e6e0000640000008a2d330143e4bfb2bc02a08dec8b779677ef04f14ca29f9e3c7e98eeff40231cc0bb62880cd125ec186b5142ab14783cc03f21cd12cb08ce8299aeda49d3c8e37f34afe9a3"}

Not doubting YOU... just to be clear because there have been a lot of concerns with Hallmarks (passphrase security, setting up, etc.).

keep in mind that hallmarks are not injected into the blockchain.  The only thing I can guess here is that the hallmark check in the admin page just tests to see if it passes checksum, and doesnt poll the network as a whole to see if there are newer ones.  and that otherwise, when nodes on the network detect other nodes with conflicting hallmarks, that the older one is invalidated.

CfB would have to confirm though, but thats my best guess

[xadidos]

24364      6635869272840226493      25 dec. 2013 г., 18:23:01 GMT+1   
1      0 + 1      134 B   
1      8428208671211163213      2220 %   


Correct?

[Come-from-Beyond]

This is not true. I generated two hallmarks with different dates and both are valid

Is there such possibility CfB?

Only if there is a bug in software. Let's check together:

Code:

		boolean analyzeHallmark(String realHost, String hallmark) {
			
			if (hallmark == null) {
				
				return true;
				
			}
			
			try {
				
				byte[] hallmarkBytes = convert(hallmark);
				
				ByteBuffer buffer = ByteBuffer.wrap(hallmarkBytes);
				buffer.order(ByteOrder.LITTLE_ENDIAN);
				
				byte[] publicKey = new byte[32];
				buffer.get(publicKey);
				int hostLength = buffer.getShort();
				byte[] hostBytes = new byte[hostLength];
				buffer.get(hostBytes);
				String host = new String(hostBytes, "UTF-8");
				if (host.length() > 100 || !host.equals(realHost)) {
					
					return false;
					
				}
				int weight = buffer.getInt();
				if (weight <= 0 || weight > 1000000000) {
					
					return false;
					
				}
				int date = buffer.getInt();
				buffer.get();
				byte[] signature = new byte[64];
				buffer.get(signature);
				
				byte[] data = new byte[hallmarkBytes.length - 64];
				System.arraycopy(hallmarkBytes, 0, data, 0, data.length);
				
				if (Crypto.verify(signature, data, publicKey)) {
					
					this.hallmark = hallmark;
					
					long accountId = Account.getId(publicKey);
					Account account = accounts.get(accountId);
					if (account == null) {
						
						return false;
						
					}
					LinkedList<Peer> groupedPeers = new LinkedList<>();
					int validDate = 0;
					
					synchronized (peers) {
						
						this.accountId = accountId;
						this.weight = weight;
						this.date = date;
						
						for (Peer peer : peers.values()) {
							
							if (peer.accountId == accountId) {
								
								groupedPeers.add(peer);
								if (peer.date > validDate) {
									
									validDate = peer.date;
									
								}
								
							}
							
						}
						
						long totalWeight = 0;
						for (Peer peer : groupedPeers) {
							
							if (peer.date == validDate) {
								
								totalWeight += peer.weight;
								
							} else {
								
								peer.adjustedWeight = 0;
								peer.updateWeight();
								
							}
							
						}
						
						for (Peer peer : groupedPeers) {
							
							peer.adjustedWeight = 1000000000L * peer.weight / totalWeight;
							peer.updateWeight();
							
						}
						
					}
					
					return true;
					
				}
				
			} catch (Exception e) { }
			
			return false;
			
		}

[klee]

Hi guys, I am back at last (Christmas, family etc).
The war is raging I see!

What is the latest files/version I am lost - my client is stopped..

https://asktom.cf/index.php?topic=345619.msg4137380#msg4137380

Thanks!

[davethetrousers]

Good news on NXT on RaspPi:

The server is running quite smoothly on the Oracle SE Embedded JRE. Startup time is down to less than 1 minute (vs. >7min on openJDK7), shutting down takes close to half a minute now. The web client is responsive and fast, unlocking an address takes 1-2 seconds, though.

I used conservative settings, imho. This is what I ran, and what was output:

pi@raspberrypi ~/nxt $ ../ejre1.7.0_45/bin/java -Xms320m -Xmx450m -jar start.jar
2013-12-25 16:48:58.450:INFO:oejs.Server:main: jetty-9.1.0.v20131115
2013-12-25 16:48:58.789:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/pi/nxt/webapps/] at interval 0
[2013-12-25 16:49:01.485] Nxt 0.4.7e started.
[2013-12-25 16:49:01.496] "blockchainStoragePath" = "blockchain.nrs"
[2013-12-25 16:49:01.563] "myScheme" = "http"
[2013-12-25 16:49:01.566] "myPort" = "57874"
[2013-12-25 16:49:01.571] "myAddress" = ""
[2013-12-25 16:49:01.575] "shareMyAddress" = "true"
[2013-12-25 16:49:01.580] "myHallmark" = ""
[2013-12-25 16:49:01.584] "wellKnownPeers" = "109.230.224.65; 78.46.63.221; 95.85.22.142"
[2013-12-25 16:49:01.608] "maxNumberOfConnectedPublicPeers" = "5"
[2013-12-25 16:49:01.612] "connectTimeout" = "2000"
[2013-12-25 16:49:01.616] "readTimeout" = "5000"
[2013-12-25 16:49:01.620] "enableHallmarkProtection" = "true"
[2013-12-25 16:49:01.624] "pushThreshold" = "0"
[2013-12-25 16:49:01.628] "pullThreshold" = "0"
[2013-12-25 16:49:01.632] "allowedUserHosts" = "192.168.1.23; 127.0.0.1; localhost; 0:0:0:0:0:0:0:1;"
[2013-12-25 16:49:01.637] "allowedBotHosts" = "192.168.1.23; 127.0.0.1; localhost; 0:0:0:0:0:0:0:1;"
[2013-12-25 16:49:01.641] "blacklistingPeriod" = "300000"
[2013-12-25 16:49:01.645] "communicationLoggingMask" = "0"
[2013-12-25 16:49:01.651] Loading transactions...
[2013-12-25 16:49:16.831] ...Done
[2013-12-25 16:49:16.835] Loading blocks...
[2013-12-25 16:49:34.681] ...Done
[2013-12-25 16:49:34.692] Scanning blockchain...
[2013-12-25 16:49:53.493] ...Done
2013-12-25 16:49:53.828:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@4bbf80{/,file:/home/pi/nxt/webapps/root/,AVAILABLE}{/root}
2013-12-25 16:49:54.050:INFO:oejs.ServerConnector:main: Started ServerConnector@a5bce1{HTTP/1.1}{0.0.0.0:7874}
2013-12-25 16:49:56.921:INFO:oejs.ServerConnector:main: Started ServerConnector@664140{SSL-http/1.1}{0.0.0.0:7875}
--- here I sent SIGINT (Ctrl+C) to shut down the server ---
2013-12-25 17:01:37.402:INFO:oejs.ServerConnector:Thread-0: Stopped ServerConnector@a5bce1{HTTP/1.1}{0.0.0.0:7874}
2013-12-25 17:01:37.411:INFO:oejs.ServerConnector:Thread-0: Stopped ServerConnector@664140{SSL-http/1.1}{0.0.0.0:7875}
[2013-12-25 17:02:13.742] Nxt stopped.
2013-12-25 17:02:13.780:INFO:oejsh.ContextHandler:Thread-0: Stopped o.e.j.w.WebAppContext@4bbf80{/,file:/home/pi/nxt/webapps/root/,UNAVAILABLE}{/root}

I also set the DDoS protection to somewhat more aggressive settings (10 Req/s, 2s delay).

CPU and RAM usage are more modest than I had expected. The worst case CPU load while idle and synchronized - with the web client open and account unlocked - was 15-20%. Without the client open( still unlocked) it was less than 10% most of the time. There have been some peaks of full load from time to time, probably due to new blocks. RAM usage, which I saw as most critical, is not too bad either. I ran with 320M initial, which is way more than I even need. The mem area is only a third utilized. Are the SE Embedded data structures that much less space complex? Probably, that is a factor.

Running something else on the Pi while running the server should not be much of a problem. While I was testing, I cut back everything as much as possible (GPU RAM share, CLI only), but I think those modest utilization figures leave enough headroom for a GUI. If not, one can always use swap to mitigate.

Next thing I will do is making a ready-to-run-package for Pi users that they can put on their box.