elective-stereophonic
elective-stereophonic
NRS v1.7.4  
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 ... 3 4 [5] 6 7 8  All

Author Topic: NRS v1.7.4  (Read 79177 times)

OutSL

  • Sr. Member
  • ****
  • Karma: +60/-0
  • Offline Offline
  • Posts: 332
  • Banned!
    • View Profile
Re: NRS v1.7.4
« Reply #80 on: January 12, 2016, 09:44:10 am »

Hi :)
is this normal? the time between the last blocks: 612898 > 612899 ~17 minutes > 612900 ~5 minutes > some seconds between the lasts...  :o

HD : http://i66.tinypic.com/2qlcun8.png

Thank you all and @++
« Last Edit: January 12, 2016, 01:52:11 pm by OutSL »
Logged
Thank you for your financial help, your donations will be used in the R&D related to the implementation of NXT in the virtual worlds running under OpenSimulator.org | Donations Box : NXT-PC8Q-ZW86-7UYK-CC4XJ
Visit The NXT Community Virtal World! Your NXT 3D Chat Service

EvilDave

  • Hero Member
  • *****
  • Karma: +341/-40
  • Offline Offline
  • Posts: 1789
    • View Profile
    • NXT Foundation
Re: NRS v1.7.4
« Reply #81 on: January 12, 2016, 10:17:13 am »

Yes. irregular block times are a pain in the arse, to be honest. In theory we should have one block per minute, but right now the average is about one per 90 seconds, with some very slow blocks.
NRS 1.7.4 contains some optimisations to block times, but we won't start to see any real improvement until after the hard fork at block 621,000, when we will have a homogenous 1.7.4 network, with no legacy nodes slowing stuff down.

Take a look here for block generation time predictions :

https://nxtportal.org/monitor/
Logged
Nulli Dei, nulli Reges, solum NXT
NXT Donations: NXT-BNZB-9V8M-XRPW-3S3WD
We will ride eternal, shiny and chrome!

OutSL

  • Sr. Member
  • ****
  • Karma: +60/-0
  • Offline Offline
  • Posts: 332
  • Banned!
    • View Profile
Re: NRS v1.7.4
« Reply #82 on: January 12, 2016, 10:34:40 am »

Yes. irregular block times are a pain in the arse, to be honest. In theory we should have one block per minute, but right now the average is about one per 90 seconds, with some very slow blocks.
NRS 1.7.4 contains some optimisations to block times, but we won't start to see any real improvement until after the hard fork at block 621,000, when we will have a homogenous 1.7.4 network, with no legacy nodes slowing stuff down.

Take a look here for block generation time predictions :

https://nxtportal.org/monitor/
Ha! thank you for this info  :D just to be sure that is not on my own machine... (overexploited old one :( )
@++
Logged
Thank you for your financial help, your donations will be used in the R&D related to the implementation of NXT in the virtual worlds running under OpenSimulator.org | Donations Box : NXT-PC8Q-ZW86-7UYK-CC4XJ
Visit The NXT Community Virtal World! Your NXT 3D Chat Service

testdruif

  • Full Member
  • ***
  • Karma: +71/-1
  • Offline Offline
  • Posts: 223
    • View Profile
Re: NRS v1.7.4
« Reply #83 on: January 12, 2016, 01:46:52 pm »

I have a question about prunable messages

case:

* default settings on the node (so it's not an archival node or anything special setup for prunable data)
* a transaction is made with a messages and the message is set as messageIsPrunable: true

Question:

At some time the message will be removed from the transaction on my node (because it does not keep all prunable data, correct?)
when I request the transaction (with the getBlockchainTransactions api and use "includeExpiredPrunable: true"), will that request the message from an archival node?

Really appreaciate any help/input
Logged
**Necessity is the mother of invention**
NXT-NNGD-V8TN-3MZR-DWWBE
https://arguseyes.net

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.4
« Reply #84 on: January 12, 2016, 04:16:30 pm »

At some time the message will be removed from the transaction on my node (because it does not keep all prunable data, correct?)
when I request the transaction (with the getBlockchainTransactions api and use "includeExpiredPrunable: true"), will that request the message from an archival node?
No, this will not request an expired message from archival node. The includeExpiredPrunable parameter only controls whether prunable messages older than 2 weeks (the minimum prunable lifetime) are returned if you still have them, or not. If they have been pruned already, it will have no effect.

You can use retrievePrunedTransaction to request retrieval of a transaction from archival node, but it is better to use the getPrunableMessage API with retrieve=true, or if it is tagged data, getTaggedData or downloadTaggedData with retrieve=true, because those APIs will also return the retrieved prunable part in their JSON response, retrievePrunedTransaction will restore it in the database but not return it in the API response.

There is no way to request retrieval of multiple pruned messages at once, you can only do that globally by increasing nxt.maxPrunableLifetime and then calling retrievePrunedData to retrieve everything missing.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

cayenne

  • Sr. Member
  • ****
  • Karma: +10/-2
  • Offline Offline
  • Posts: 253
    • View Profile
Re: NRS v1.7.4
« Reply #85 on: January 13, 2016, 01:16:25 pm »

I'm seeing the blocks from the future problem also (see message #83). Does this resolve itself? Is there anyway to prevent it?
Logged

k3t3r

  • Jr. Member
  • **
  • Karma: +2/-0
  • Offline Offline
  • Posts: 53
    • View Profile
Re: NRS v1.7.4
« Reply #86 on: January 13, 2016, 05:45:21 pm »

I always have problems with the install. I am sure this one is only a minor one but then I havent got to updating the database yet.

So my problem is: I extracted the new version into the folder with the old version in. then navigate to the folder and then:

Code: [Select]
User@Home:~/nxt/nxt$ ./run.sh
bash: ./run.sh: Permission denied
User@Home:~/nxt/nxt$ ./run.sh
bash: ./run.sh: Permission denied
User@Home:~/nxt/nxt$ sudo ./run.sh
[sudo] password for User:
sudo: ./run.sh: command not found
User@Home:~/nxt/nxt$

I tried replacing the file run.sh file with an identical file created by me. exactly the same issue.
anybody have any ideas?
TIA

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.7.4
« Reply #87 on: January 13, 2016, 05:56:26 pm »

chmod +x run.sh
Logged

k3t3r

  • Jr. Member
  • **
  • Karma: +2/-0
  • Offline Offline
  • Posts: 53
    • View Profile
Re: NRS v1.7.4
« Reply #88 on: January 13, 2016, 09:00:02 pm »

chmod +x run.sh
Hey, Its doing something! thank you!

k3t3r

  • Jr. Member
  • **
  • Karma: +2/-0
  • Offline Offline
  • Posts: 53
    • View Profile
Re: NRS v1.7.4
« Reply #89 on: January 13, 2016, 09:16:22 pm »

So my run.sh now runs. but only this far:
Code: [Select]
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/simple/JSONObject
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
at java.lang.Class.getMethod0(Class.java:3018)
at java.lang.Class.getMethod(Class.java:1784)
at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526)
Caused by: java.lang.ClassNotFoundException: org.json.simple.JSONObject
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 7 more

k3t3r

  • Jr. Member
  • **
  • Karma: +2/-0
  • Offline Offline
  • Posts: 53
    • View Profile
Re: NRS v1.7.4
« Reply #90 on: January 14, 2016, 08:02:55 am »

The fact that you had to use "chmod +x" on your run.sh file suggests to me that there might be a problem in the way you extracted the NRS zip file.

My zip file extracts with an executable run.sh and always has done in previous releases.

Are you sure you haven't done something silly like extracted the zip while logged into the terminal as root? This could be causing the file permission issue you mentioned earlier and would also cause issues when you run NRS because your files may be owned by root and not your home user.
thanks for reply. no never log in as root only use sudo to perform tasks that need it. i will try and extract a different way.

abctc

  • Hero Member
  • *****
  • Karma: +148/-13
  • Offline Offline
  • Posts: 1396
    • View Profile
Re: NRS v1.7.4
« Reply #91 on: January 14, 2016, 01:43:29 pm »

I'm seeing the blocks from the future problem also (see message #83).
- me too.
Code: [Select]
2016-01-14 13:19:33 WARNING: Received block 11212219528517789890 from the future, block timestamp is 257626853, current time is 67472373, system clock may be off
2016-01-14 13:20:36 WARNING: Received block 11212219528517789890 from the future, block timestamp is 257626853, current time is 67472436, system clock may be off
2016-01-14 13:20:42 WARNING: Received block 11212219528517789890 from the future, block timestamp is 257626853, current time is 67472442, system clock may be off
2016-01-14 13:20:49 WARNING: Received block 11212219528517789890 from the future, block timestamp is 257626853, current time is 67472450, system clock may be off
2016-01-14 13:20:54 WARNING: Received block 11212219528517789890 from the future, block timestamp is 257626853, current time is 67472455, system clock may be off
2016-01-14 13:21:03 WARNING: Received block 11212219528517789890 from the future, block timestamp is 257626853, current time is 67472463, system clock may be off
2016-01-14 13:21:35 WARNING: Received block 12225660764336954048 from the future, block timestamp is 257626973, current time is 67472496, system clock may be off
2016-01-14 13:21:49 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472509, system clock may be off
2016-01-14 13:21:58 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472518, system clock may be off
2016-01-14 13:22:16 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472537, system clock may be off
2016-01-14 13:22:34 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472555, system clock may be off
2016-01-14 13:22:48 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472568, system clock may be off
2016-01-14 13:22:49 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472570, system clock may be off
2016-01-14 13:22:56 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472577, system clock may be off
2016-01-14 13:23:04 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472584, system clock may be off
2016-01-14 13:23:36 WARNING: Received block 9948579381817761484 from the future, block timestamp is 257626990, current time is 67472617, system clock may be off
2016-01-14 13:24:07 WARNING: Received block 4336114002285262339 from the future, block timestamp is 257627121, current time is 67472647, system clock may be off
2016-01-14 13:24:41 WARNING: Received block 4336114002285262339 from the future, block timestamp is 257627121, current time is 67472682, system clock may be off
2016-01-14 13:24:44 WARNING: Received block 4952408125608544770 from the future, block timestamp is 257627167, current time is 67472684, system clock may be off
2016-01-14 13:25:28 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472729, system clock may be off
2016-01-14 13:25:39 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472740, system clock may be off
2016-01-14 13:25:57 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472757, system clock may be off
2016-01-14 13:25:57 FINE: Average database transaction time is 0,231 seconds
2016-01-14 13:26:01 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472762, system clock may be off
2016-01-14 13:26:07 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472768, system clock may be off
2016-01-14 13:26:35 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472795, system clock may be off
2016-01-14 13:26:44 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472805, system clock may be off
2016-01-14 13:27:17 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472837, system clock may be off
2016-01-14 13:27:29 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472849, system clock may be off
2016-01-14 13:27:31 WARNING: Received block 5919919148362779785 from the future, block timestamp is 257627177, current time is 67472851, system clock may be off
2016-01-14 13:27:39 WARNING: Received block 15141710975115765657 from the future, block timestamp is 257627338, current time is 67472859, system clock may be off
2016-01-14 13:28:21 WARNING: Received block 15141710975115765657 from the future, block timestamp is 257627338, current time is 67472902, system clock may be off
2016-01-14 13:28:27 WARNING: Received block 973335583441345591 from the future, block timestamp is 257627390, current time is 67472908, system clock may be off
2016-01-14 13:29:34 WARNING: Received block 973335583441345591 from the future, block timestamp is 257627390, current time is 67472974, system clock may be off
2016-01-14 13:29:48 WARNING: Received block 7530537655333492009 from the future, block timestamp is 257627466, current time is 67472989, system clock may be off
2016-01-14 13:29:52 WARNING: Received block 7530537655333492009 from the future, block timestamp is 257627466, current time is 67472993, system clock may be off
2016-01-14 13:29:55 WARNING: Received block 7530537655333492009 from the future, block timestamp is 257627466, current time is 67472995, system clock may be off
2016-01-14 13:29:59 WARNING: Received block 7530537655333492009 from the future, block timestamp is 257627466, current time is 67473000, system clock may be off
2016-01-14 13:30:07 WARNING: Received block 7530537655333492009 from the future, block timestamp is 257627466, current time is 67473007, system clock may be off
2016-01-14 13:30:11 WARNING: Received block 7530537655333492009 from the future, block timestamp is 257627466, current time is 67473012, system clock may be off
2016-01-14 13:30:18 WARNING: Received block 7530537655333492009 from the future, block timestamp is 257627466, current time is 67473018, system clock may be off
2016-01-14 13:30:41 WARNING: Received block 5015740738211527572 from the future, block timestamp is 257627517, current time is 67473041, system clock may be off
2016-01-14 13:31:39 WARNING: Received block 5015740738211527572 from the future, block timestamp is 257627517, current time is 67473100, system clock may be off
2016-01-14 13:31:57 WARNING: Received block 5015740738211527572 from the future, block timestamp is 257627517, current time is 67473118, system clock may be off
2016-01-14 13:32:23 WARNING: Received block 4409055915738088860 from the future, block timestamp is 257627613, current time is 67473143, system clock may be off
2016-01-14 13:33:43 WARNING: Received block 4409055915738088860 from the future, block timestamp is 257627613, current time is 67473223, system clock may be off
2016-01-14 13:34:33 WARNING: Received block 4409055915738088860 from the future, block timestamp is 257627613, current time is 67473273, system clock may be off
2016-01-14 13:34:38 WARNING: Received block 4409055915738088860 from the future, block timestamp is 257627613, current time is 67473279, system clock may be off
2016-01-14 13:35:37 WARNING: Received block 5466893857213416577 from the future, block timestamp is 257627810, current time is 67473337, system clock may be off
2016-01-14 13:35:55 WARNING: Received block 5466893857213416577 from the future, block timestamp is 257627810, current time is 67473356, system clock may be off
2016-01-14 13:36:15 WARNING: Received block 5466893857213416577 from the future, block timestamp is 257627810, current time is 67473375, system clock may be off
2016-01-14 13:36:25 WARNING: Received block 5466893857213416577 from the future, block timestamp is 257627810, current time is 67473386, system clock may be off
2016-01-14 13:37:45 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473466, system clock may be off
2016-01-14 13:37:58 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473478, system clock may be off
2016-01-14 13:38:33 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473514, system clock may be off
2016-01-14 13:38:37 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473518, system clock may be off
2016-01-14 13:39:22 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473563, system clock may be off
2016-01-14 13:39:24 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473564, system clock may be off
2016-01-14 13:39:32 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473573, system clock may be off
2016-01-14 13:40:01 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473601, system clock may be off
2016-01-14 13:40:11 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473611, system clock may be off
2016-01-14 13:40:25 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473626, system clock may be off
2016-01-14 13:40:40 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473640, system clock may be off
2016-01-14 13:40:44 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473645, system clock may be off
2016-01-14 13:40:57 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473658, system clock may be off
2016-01-14 13:40:57 FINE: Average database transaction time is 0,008 seconds
2016-01-14 13:41:18 WARNING: Received block 5086707056336367880 from the future, block timestamp is 257627917, current time is 67473679, system clock may be off
2016-01-14 13:41:57 WARNING: Received block 4993335255153702024 from the future, block timestamp is 257628163, current time is 67473717, system clock may be off
2016-01-14 13:42:18 WARNING: Received block 4993335255153702024 from the future, block timestamp is 257628163, current time is 67473738, system clock may be off
2016-01-14 13:42:37 WARNING: Received block 4993335255153702024 from the future, block timestamp is 257628163, current time is 67473757, system clock may be off
2016-01-14 13:42:52 WARNING: Received block 4993335255153702024 from the future, block timestamp is 257628163, current time is 67473772, system clock may be off
2016-01-14 13:42:55 WARNING: Received block 4993335255153702024 from the future, block timestamp is 257628163, current time is 67473776, system clock may be off
2016-01-14 13:43:36 WARNING: Received block 4993335255153702024 from the future, block timestamp is 257628163, current time is 67473817, system clock may be off
2016-01-14 13:43:59 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67473840, system clock may be off
2016-01-14 13:45:31 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67473932, system clock may be off
2016-01-14 13:45:58 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67473959, system clock may be off
2016-01-14 13:46:07 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67473967, system clock may be off
2016-01-14 13:46:17 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67473978, system clock may be off
2016-01-14 13:46:20 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67473981, system clock may be off
2016-01-14 13:46:45 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474006, system clock may be off
2016-01-14 13:47:30 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474050, system clock may be off
2016-01-14 13:47:48 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474069, system clock may be off
2016-01-14 13:48:01 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474082, system clock may be off
2016-01-14 13:48:03 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474083, system clock may be off
2016-01-14 13:48:25 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474106, system clock may be off
2016-01-14 13:48:31 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474112, system clock may be off
2016-01-14 13:49:12 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474153, system clock may be off
2016-01-14 13:49:21 WARNING: Received block 14436412911523076810 from the future, block timestamp is 257628305, current time is 67474161, system clock may be off
2016-01-14 13:50:16 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474217, system clock may be off
2016-01-14 13:50:40 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474241, system clock may be off
2016-01-14 13:51:18 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474279, system clock may be off
2016-01-14 13:51:32 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474293, system clock may be off
2016-01-14 13:51:45 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474305, system clock may be off
2016-01-14 13:51:49 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474309, system clock may be off
2016-01-14 13:52:52 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474372, system clock may be off
2016-01-14 13:53:59 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474439, system clock may be off
2016-01-14 13:54:06 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474447, system clock may be off
2016-01-14 13:54:07 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474448, system clock may be off
2016-01-14 13:55:27 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474528, system clock may be off
2016-01-14 13:55:32 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474532, system clock may be off
2016-01-14 13:55:48 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474548, system clock may be off
2016-01-14 13:56:14 WARNING: Received block 7337836544412181127 from the future, block timestamp is 257628695, current time is 67474575, system clock may be off
2016-01-14 13:56:14 FINE: Average database transaction time is 0,007 seconds
2016-01-14 13:57:28 WARNING: Received block 11949751780920030739 from the future, block timestamp is 257629111, current time is 67474649, system clock may be off
2016-01-14 13:57:34 WARNING: Received block 11949751780920030739 from the future, block timestamp is 257629111, current time is 67474655, system clock may be off
2016-01-14 13:58:05 WARNING: Received block 9763319086456846238 from the future, block timestamp is 257629143, current time is 67474686, system clock may be off
2016-01-14 13:58:09 WARNING: Received block 9763319086456846238 from the future, block timestamp is 257629143, current time is 67474689, system clock may be off
2016-01-14 13:58:44 WARNING: Received block 9763319086456846238 from the future, block timestamp is 257629143, current time is 67474725, system clock may be off
2016-01-14 13:58:50 WARNING: Received block 9763319086456846238 from the future, block timestamp is 257629143, current time is 67474731, system clock may be off
2016-01-14 13:59:01 WARNING: Received block 9763319086456846238 from the future, block timestamp is 257629143, current time is 67474741, system clock may be off
2016-01-14 13:59:49 WARNING: Received block 15349457409848289475 from the future, block timestamp is 257629258, current time is 67474790, system clock may be off
2016-01-14 13:59:55 WARNING: Received block 15349457409848289475 from the future, block timestamp is 257629258, current time is 67474796, system clock may be off

- shouldn't such nodes be blacklisted ?
Logged
Welcome to the Nxt generation of crypto!   Magis quam Moneta (More than a Coin)
"Do not worry, it is an attack" (c) Jean-Luc

NxtSwe

  • Hero Member
  • *****
  • Karma: +124/-9
  • Offline Offline
  • Posts: 657
    • View Profile
Re: NRS v1.7.4
« Reply #92 on: January 14, 2016, 04:22:27 pm »

- shouldn't such nodes be blacklisted ?

If the node is hallmarked and you are connected directly to that node I guess it would be possible to blacklist the node.
However if that is not the case, you have no way of knowing what node is generating the blocks.
Logged
Check out the NxtLib, the .NET Framework API for the Nxt platform.

TheCoinWizard

  • Hero Member
  • *****
  • Karma: +97/-55
  • Offline Offline
  • Posts: 614
  • Learn by questioning everything!
    • View Profile
Re: NRS v1.7.4
« Reply #93 on: January 14, 2016, 04:51:42 pm »

- shouldn't such nodes be blacklisted ?

If the node is hallmarked and you are connected directly to that node I guess it would be possible to blacklist the node.
However if that is not the case, you have no way of knowing what node is generating the blocks.
seems to be 88.130.197.26, just go to http://localhost:7876/test and add him to blacklistPeer
Logged
Welcome to the After Nxt Calendar era...
Which started in the year 222 of the French Republic, Frost month, on the fifth day of the first week, better known as the 2456621th Julian day,
even better known as 24 November 2013 at 12:00:00 UTC.

martismartis

  • Hero Member
  • *****
  • Karma: +73/-10
  • Offline Offline
  • Posts: 1238
    • View Profile
Re: NRS v1.7.4
« Reply #94 on: January 14, 2016, 05:11:28 pm »

- shouldn't such nodes be blacklisted ?

If the node is hallmarked and you are connected directly to that node I guess it would be possible to blacklist the node.
However if that is not the case, you have no way of knowing what node is generating the blocks.

To be correct, blocks are generated by accounts, not by nodes  ;) I think account, which generated these blocks, has bad time settings at forging PC.
Logged

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: NRS v1.7.4
« Reply #95 on: January 15, 2016, 02:43:21 pm »

Deleted.
Seems I got it.
« Last Edit: January 16, 2016, 12:57:12 pm by allwelder »
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.7.4
« Reply #96 on: January 18, 2016, 06:37:48 pm »

Hi.
I need to sign unsigned bytes from the plugin but cannot access secret phrase when "Remember password" option is active. Could you please add a JS call to sign unsigned bytes into NRS.server.js.
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.7.4
« Reply #97 on: January 18, 2016, 07:05:41 pm »

Hi.
I need to sign unsigned bytes from the plugin but cannot access secret phrase when "Remember password" option is active. Could you please add a JS call to sign unsigned bytes into NRS.server.js.

I think this can open a serious security risk. Not enough that we are storing the passphrase in memory, now it would be accessible to any JavaScript and who knows which other access methods (Java Applets, Flash, Silverlight)
How about you implement plugin specific "Remember password" feature ? Ask the user to enter it the first time and then remember it for reminder of the session. This way at least the risk is localized to your plugin users.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.7.4
« Reply #98 on: January 18, 2016, 08:21:41 pm »

Hi.
I need to sign unsigned bytes from the plugin but cannot access secret phrase when "Remember password" option is active. Could you please add a JS call to sign unsigned bytes into NRS.server.js.

I think this can open a serious security risk. Not enough that we are storing the passphrase in memory, now it would be accessible to any JavaScript and who knows which other access methods (Java Applets, Flash, Silverlight)
How about you implement plugin specific "Remember password" feature ? Ask the user to enter it the first time and then remember it for reminder of the session. This way at least the risk is localized to your plugin users.
What are you talking about? I do not need to access passphrase. I just want to sign unsigned bytes. Just add a call to NRS.server.js since passphrase is stored inside this JS module. I need an API something like this: NRS.signUnsignedBytes(payload)
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.7.4
« Reply #99 on: January 18, 2016, 08:38:08 pm »

Hi.
I need to sign unsigned bytes from the plugin but cannot access secret phrase when "Remember password" option is active. Could you please add a JS call to sign unsigned bytes into NRS.server.js.

I think this can open a serious security risk. Not enough that we are storing the passphrase in memory, now it would be accessible to any JavaScript and who knows which other access methods (Java Applets, Flash, Silverlight)
How about you implement plugin specific "Remember password" feature ? Ask the user to enter it the first time and then remember it for reminder of the session. This way at least the risk is localized to your plugin users.
What are you talking about? I do not need to access passphrase. I just want to sign unsigned bytes. Just add a call to NRS.server.js since passphrase is stored inside this JS module. I need an API something like this: NRS.signUnsignedBytes(payload)

Got it, take a look at nrs.shape.shift.js line 486, you can see how we programmatically invoke sendMoney. You need to call the same method passing signTransaction as the requestType and pass the unsignedTransactionBytes parameter encoded as hex string (I think) as data. The NRS.sendRequest() method should know how to access the remembered passphrase.
Give it a try and let me know.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651
Pages: 1 ... 3 4 [5] 6 7 8  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly