Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jean-Luc on January 01, 2016, 11:22:42 am

Title: NRS v1.7.4
Post by: Jean-Luc on January 01, 2016, 11:22:42 am
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.4

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.4.zip

sha256:

baf0286983fee3f718ea755dd76f5e9bb3d6a2962560368d513ffc9517d10c9b  nxt-client-1.7.4.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.4.jar

sha256:

13a4437bce4941b06f9ce3b0bf8f2371f2240db264712371094e22fc5152b34b  nxt-client-1.7.4.jar

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.4.exe


https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.4.dmg

The exe, dmg, and jar packages must have a digital signature by "Stichting NXT".


Change log:

This is the first stable release in the 1.7 series. It is a mandatory update
for everyone. There is a hard fork scheduled for block 621000, estimated to
occur around Jan 21, 2016, at which new features will be enabled. Nodes that
do not update to 1.7.4 or later by this date will be left on a fork.

On testnet, the hard fork block is already passed, and all new features are
fully functional.

There were incompatible API changes introduced in the 1.6 series. API users
still on 1.5.15 and earlier should make sure to read the 1.6 series changelogs
and forum announcements, before upgrading to 1.7. These changes do not affect
regular end users who just run the NRS client on their desktop or VPS node.

The new features and improvements in the 1.7 series have been documented in
the 1.7.0e through 1.7.3e changelogs, available in the changelogs directory.


Here is a high level summary of the new features to be enabled after the
hard fork:

Coin Shuffling, a fully decentralized coin mixing, to improve account privacy.

Account Control for phased transactions, the Nxt equivalent of multisignature.

Immediate release of certain types of phased transactions on approval.

Improved block times, 60 s average, long block times now extremely unlikely.

Account Properties, assigning arbitrary name/value metadata to user accounts.

Singleton Assets, useful for representing single tradeable objects.

Dynamic fees, proportional to the relative transaction size.

Improved Exchange Booth UI.

Data Cloud, adding a UI and multiple enhancements to the existing Tagged Data
feature, to allow decentralized, censorship-free and tamper-proof publication
and retrieval of small files, documents, or arbitrary data. This feature is
not dependent on the hard fork and will be fully usable immediately on update
to this release.


Changes added since the 1.7.3e release:

Added detectMimeType utility API, allowing auto-detection of the mime type of
uploaded file or data, using the Apache Tika library.

The uploadTaggedData API now uses such mime type auto-detection to determine
the mime type of uploaded data when the user has not explicitly provided a
type parameter. It also automatically sets the isText property to true for
data of type text/plain only.

Made the maximum permitted number of forgers or shufflers running at the same
time configurable, default 100 each, using the nxt.maxNumberOfForgers and
nxt.maxNumberOfShufflers properties.

The default value of includeCounts parameter in the searchDGSGoods API is now
also false, this API was inadvertently missed when globally changing the
defaults to false in the 1.6 branch.

Various UI improvements.

Updated Bouncy Castle library to version 1.54.


-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJWhlCtAAoJENqvaxkWiP4ZlJwQAM6XodzaiUeyjdOVQhqYTmTr
H2jioMMyuYpztRlzhzv6UjTuCETDjtUX9a7cHTX4c44Q7WnM1aiIV9/lYsgRa4Aq
my2pSK91OL++/w173rIKbFamw83DWKzU5ozm3pnyIGYiJv6HP1VxajOk8R2E6R2G
haazNDp7IoMBssHWev4uY4O2gJEIqRu2l9s9pXKe5A93o/pSReIQvWx6HY0/3WyP
qkmuSGv9K78SR8JIWrNAU97nFyZ6edBkLnHJH6RwfWkoQhqvXWEomAln1stDN8Xi
FhBTqy1s9utMSl5gMg4Dy9xpB+Fsdo6gCMsoY6R5fgeVnkthv87kXecBETqZCPYm
e74qYjUWCqRsrXsjd239cYCq4f2l25QcppKdj0vZAapGK5RyNhHSV78r7FL3e6+e
s4Xw6YwlDiw2cQTtBnY/jyC7sTVwkKxmP/ifRMDFTjpiJvnOwoOI/J66Pr8oOYDy
HWXNXAspv9bNSJum1NQ2gWvPdjvbKdiZTBq9nfpcUkq2v6rgUgpRqY7sO8aB7OKN
mdXxSyiNNPLM3xEkkUC11JWROlvGgnIAf8T1tkr3QKsrkR9o3CjrvBzktTNNUR2h
bmQTnQ1BR2g61Wbvjn76no+VeNOYfhh8q+FLZXLFGYSPi+Pv9C3jS76xqU7+oy2o
u0vEoIUc1B4S4h3Y1GWB
=t7Nb
-----END PGP SIGNATURE-----
Title: Re: NRS v1.7.4
Post by: Sebastien256 on January 01, 2016, 11:27:07 am
Great work and happy 2016!
Title: Re: NRS v1.7.4
Post by: Jean-Luc on January 01, 2016, 11:35:05 am
You should delete the lib folder (or just lib/bcprov-jdk15on-153.jar) because of the updated bouncy castle library. I don't think there will be a rescan from 1.7.3e to 1.7.4.
Title: Re: NRS v1.7.4
Post by: Riker on January 01, 2016, 11:40:31 am
Mac installer is not ready yet. I will post here when it's uploaded.
Title: Re: NRS v1.7.4
Post by: yassin54 on January 01, 2016, 11:49:23 am
Thanks and Happy New Year!!  ;) 8)
Title: Re: NRS v1.7.4
Post by: phideas on January 01, 2016, 01:33:17 pm
Thanks and Happy New Year to all Nxters!  :)
Title: Re: NRS v1.7.4
Post by: chevdor on January 01, 2016, 02:35:39 pm
Docker container on its way: https://hub.docker.com/r/chevdor/docker-nxt

If you don´t want to wait, you can set NRSVersion to 1.7.4 and the previous image will work as expected.

The new image will default to 1.6.4 and manage the upgrades in the case of using volumes a bit better.
Title: Re: NRS v1.7.4
Post by: jones on January 01, 2016, 05:12:35 pm
The countdown:

http://jnxt.org/countdown/?block=621000
Title: Re: NRS v1.7.4
Post by: sigwo on January 01, 2016, 05:23:14 pm
Looks fantastic. I like the new UI for switching accounts.

Are there coin shuffling instructions?
Title: Re: NRS v1.7.4
Post by: Riker on January 01, 2016, 06:56:06 pm
Mac installer uploaded https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.4.dmg
SHA256 8a56e81aef05a3e2306e90bbcce9b0018ac0145dff1655d5d52a9e709e51de6b
Title: Re: NRS v1.7.4
Post by: Ludom on January 01, 2016, 08:38:27 pm
Thank you so much. I update my node.
Title: Re: NRS v1.7.4
Post by: EvilDave on January 01, 2016, 10:42:12 pm
Thanks, J-L....starting with updates right about now.

And to everyone: we'll be spreading the word about the hardfork as much as possible over the next 3 weeks. I'm pretty sure that most important projects/exchanges are ready to go to 1.7, but every bit of help we can get with ensuring that we have a smooth hardfork on the 21st would be appreciated. So spread the word...

Everyone can help.....post on social media, tweet, use trollboxes, crypto-forums, tell your neighbours ( ;D)
Title: Re: NRS v1.7.4
Post by: Klokan on January 01, 2016, 11:13:07 pm
Is it possible to update from 1.5.15 directly to 1.7.X, without a step with 1.6.2 version ? So just copy nxt_db/ directory to the new install of 1.7.4, make ./compile.sh, ./run.sh and (probably) wait for SQL update and re-scan ?
Title: Re: NRS v1.7.4
Post by: Jean-Luc on January 01, 2016, 11:49:04 pm
Yes, update directly from 1.5.15 to 1.7.4 should be possible.
Title: Re: NRS v1.7.4
Post by: Fern on January 02, 2016, 03:26:52 am
Impressed, Thank-you
Title: Re: NRS v1.7.4
Post by: allwelder on January 02, 2016, 03:30:30 am
Updated and Shared. (http://weibo.com/3938426719/DbeztDlkv?from=page_1005053938426719_profile&wvr=6&mod=weibotime)
Thanks.
Title: Re: NRS v1.7.4
Post by: qq2536007339 on January 02, 2016, 06:00:48 am
Thank you as always!
Title: Re: NRS v1.7.4
Post by: theB on January 02, 2016, 03:14:18 pm
nxt.org still links to 1.6.2
Title: Help with MAC installer
Post by: neofelis on January 02, 2016, 05:27:30 pm
Mac installer uploaded https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.4.dmg
SHA256 8a56e81aef05a3e2306e90bbcce9b0018ac0145dff1655d5d52a9e709e51de6b

Needs some help please.  I downloaded and ran the installer per the link above and now I have a folder called NXT that's filled with a bunch of "code" type files.  What do I do next?  I did try opening the file called NXT_Wallet.url and it opened a webpage with a NXT login but when I entered my passphrase (or anything for that matter), nothing happens.

Thanks in advance for any help.


Up and running now. Awesome release. Proud to be a NXTer!
Title: Re: NRS v1.7.4
Post by: Maurice_WJ113 on January 02, 2016, 05:34:52 pm
Hello,

So, if I'm running a 32-bit machine, am I out of luck with this new release?
Title: Re: NRS v1.7.4
Post by: Jean-Luc on January 02, 2016, 06:01:59 pm
I wouldn't bother with my torrent link. I've had mixed results with a failed tracker. I think I generated the link wrong.
For such cases, there is no way to modify tagged data already uploaded. What we could do, without adding new transaction types, is use referenced transactions to add a comment to existing data, by submitting a plain text message with no recipient and referring to the data upload transaction, and then use the recently added getReferencingTransactions API to find and display such messages as comments for the data they refer to. This would be just an UI change, worth doing only if there is demand.

Downloading the full blockchain from scratch takes exactly 2 hours for me. The limiting factor is not the network, but disk and possibly CPU.
Title: Re: NRS v1.7.4
Post by: Jean-Luc on January 02, 2016, 06:05:26 pm
So, if I'm running a 32-bit machine, am I out of luck with this new release?
You would need to install a 32-bit JRE manually, and then use the zip package instead of the exe installer.
Title: Re: NRS v1.7.4
Post by: Jean-Luc on January 02, 2016, 08:11:25 pm
Of course there is a security issue, this is why I don't encourage such downloading of the blockchain from a torrent or website. If the normal way of downloading it with the client takes 2 hours on modern hardware, this is fast enough. I have heard stories of users taking days to download the full blockchain, those must be on slow machines, I have no other explanation. For such users doing a rescan will also take very long, but without a rescan (and also comparing the last block with the network) they must trust the provider of that torrent or zip archive.
Title: Re: NRS v1.7.4
Post by: farl4bit on January 02, 2016, 09:14:55 pm
Great way to start 2016 for Nxt. This one goes in the books (again)!  :)
Title: Re: NRS v1.7.4
Post by: shmoula on January 03, 2016, 11:34:26 am
upgrade from 1.6.2 on macos throws exception:

Quote
2016-01-03 12:33:02 FINE: Will apply sql:
CREATE TABLE referenced_transaction (db_id IDENTITY, transaction_id BIGINT NOT NULL, FOREIGN KEY (transaction_id) REFERENCES transaction (id) ON DELETE CASCADE, referenced_transaction_id BIGINT NOT NULL)
2016-01-03 12:33:02 SEVERE: Database error executing CREATE TABLE referenced_transaction (db_id IDENTITY, transaction_id BIGINT NOT NULL, FOREIGN KEY (transaction_id) REFERENCES transaction (id) ON DELETE CASCADE, referenced_transaction_id BIGINT NOT NULL)
java.lang.RuntimeException: Database error executing CREATE TABLE referenced_transaction (db_id IDENTITY, transaction_id BIGINT NOT NULL, FOREIGN KEY (transaction_id) REFERENCES transaction (id) ON DELETE CASCADE, referenced_transaction_id BIGINT NOT NULL)
   at nxt.db.DbVersion.apply(DbVersion.java:83)
   at nxt.NxtDbVersion.update(NxtDbVersion.java:1117)
   at nxt.db.DbVersion.init(DbVersion.java:55)
   at nxt.db.BasicDb.init(BasicDb.java:137)
   at nxt.Db.init(Db.java:39)
   at nxt.Nxt$Init.<clinit>(Nxt.java:323)
   at nxt.Nxt.init(Nxt.java:295)
   at nxt.Nxt.main(Nxt.java:282)
Caused by: org.h2.jdbc.JdbcSQLException: Table "REFERENCED_TRANSACTION" already exists; SQL statement:
CREATE TABLE referenced_transaction (db_id IDENTITY, transaction_id BIGINT NOT NULL, FOREIGN KEY (transaction_id) REFERENCES transaction (id) ON DELETE CASCADE, referenced_transaction_id BIGINT NOT NULL) [42101-176]
   at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
   at org.h2.message.DbException.get(DbException.java:178)
   at org.h2.message.DbException.get(DbException.java:154)
   at org.h2.command.ddl.CreateTable.update(CreateTable.java:110)
   at org.h2.command.CommandContainer.update(CommandContainer.java:79)
   at org.h2.command.Command.executeUpdate(Command.java:254)
   at org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:132)
   at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:117)
   at nxt.db.FilteredStatement.executeUpdate(FilteredStatement.java:45)
   at nxt.db.TransactionalDb$DbStatement.executeUpdate(TransactionalDb.java:288)
   at nxt.db.DbVersion.apply(DbVersion.java:74)
   ... 7 more
2016-01-03 12:33:02 INFO: Shutting down...
Title: Re: NRS v1.7.4
Post by: Jose on January 03, 2016, 02:56:20 pm
On my Raspberry Pi1 node the blockchain took days to download.

True, the same happened to me.
It's funny to see how a node can be run (quite smoohtly) on a low-end hardware, like an old Raspberry Pi or a cheap (or even free) VPS but, on the other side, it can even take a couple of days to fully download the blockchain (<2GB) and be ready for action.
Title: Re: NRS v1.7.4
Post by: chevdor on January 03, 2016, 04:03:02 pm
Just for the record, I upgraded from 1.6.2. It worked in the end but took a while.

I run my node in a docker container running on a rather powerful NAS (Synology 1815+).
I always backup my db to avoid having to re-download it.
The db upgrade from 1.6.2 to 1.7.4 was rather quick (couple of minutes I would say) but the rescan boy.... from 14:12 to 06:21 next day :)

But all worked fine. Today the compressed db is about 500MB, this is not worth spending the time to download it. I suggest you make your own copy. Even if this is a month old, it is still much quicker. It would be a nice option in the client to be able to dump a copy of the db periodically in a folder (for the lazy :))
Title: Re: NRS v1.7.4
Post by: rubenbc on January 03, 2016, 07:50:54 pm
Hi, I just upgraded from 1.6.2 and i don't see left menu bar. :-X
Linux+chromium.
any help¿? thanks
Title: Re: NRS v1.7.4
Post by: Riker on January 03, 2016, 08:26:55 pm
Hi, I just upgraded from 1.6.2 and i don't see left menu bar. :-X
Linux+chromium.
any help¿? thanks

Is the left bar completely hidden or just covered partially by center area ? Can you try to click one of the transaction links on the dashboard to see if this fixes the problem ? Do you see an error message in the JavaScript console ?
If this still occurs please post a screen shot.
Title: Re: NRS v1.7.4
Post by: rubenbc on January 03, 2016, 08:32:29 pm
Hi, I just upgraded from 1.6.2 and i don't see left menu bar. :-X
Linux+chromium.
any help¿? thanks

Is the left bar completely hidden or just covered partially by center area ? Can you try to click one of the transaction links on the dashboard to see if this fixes the problem ? Do you see an error message in the JavaScript console ?
If this still occurs please post a screen shot.

forgiveness to all, problems with cache ;D ;D

thanks
Title: Re: NRS v1.7.4
Post by: allwelder on January 04, 2016, 02:33:48 am
With 'Delete Shares' function,where did these deleted assets go instead of sending to genesis account?
Title: Re: NRS v1.7.4
Post by: Riker on January 04, 2016, 05:38:48 am
With 'Delete Shares' function,where did these deleted assets go instead of sending to genesis account?

After block 621000 these deleted shares will disappear. You'll be able to track these transactions using the account ledger or using the delete history page in the asset exchange menu.
Title: Re: NRS v1.7.4
Post by: xchrix on January 04, 2016, 08:19:58 am
thx for the new release. i have one suggestion for the client but didnt found a suitable sub forum here for it:
in the marketplace (and anywhere else) we only see NXT amounts. would be nice to also show EUR or USD amount. especially in the marketplace. its easy to poll the price API from www.cryptocoincharts.info for example. one quick thing would be to show the other currencies amounts as tooltip when hovering over NXT amounts.
Title: Re: NRS v1.7.4
Post by: farl4bit on January 04, 2016, 08:32:47 am
Mac installer uploaded https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.4.dmg
SHA256 8a56e81aef05a3e2306e90bbcce9b0018ac0145dff1655d5d52a9e709e51de6b

I don't understand this one... It's not the same as the Nxt Mac Wallet?
Title: Re: NRS v1.7.4
Post by: testdruif on January 04, 2016, 09:38:10 am
Is there any way for the ledger to show more than (for me) 106 items?

When I go to my ledger it stops at 106 entries (about a month ago)

I already put nxt.ledgerTrimKeep=0 in my config

# Specify the number of blocks to keep when trimming the account ledger table.  A value
# of zero will cause all blocks to be kept.
nxt.ledgerTrimKeep=3000

(http://i68.tinypic.com/2ut56l1.jpg)
Title: Re: NRS v1.7.4
Post by: MrCluster87 on January 04, 2016, 01:39:07 pm
Hi J-L!

2 Questions about the current 1.7.4 release:

1) I see data cloud: can you compare it with storj, maidsafe and opal drive? Do we need http://www.nxttechnologytree.com/nxt-technology/nxt-distributed-storage in order to be a distributed Google Drive?

2) Account Control, how does it work?
With Bitcoin I had to download Armory wallet, create at least 3 new accounts and magically I had a multisig address starting with the number 3. How do I achieve it in NXT?

Thanks!!
Title: Re: NRS v1.7.4
Post by: allwelder on January 04, 2016, 03:53:22 pm
With 'Delete Shares' function,where did these deleted assets go instead of sending to genesis account?

After block 621000 these deleted shares will disappear. You'll be able to track these transactions using the account ledger or using the delete history page in the asset exchange menu.
Thanks. :)
Title: Re: NRS v1.7.4
Post by: Brangdon on January 04, 2016, 03:56:25 pm
Is there any way for the ledger to show more than (for me) 106 items?
I think you need to rescan the blockchain. Which I believe you can do from http://localhost:7876/test?requestTag=DEBUG and explore the scan API. Setting height to 0 will rescan from the genesis block. The database will get a bit bigger.

(When I needed this, I set nxt.forceScan=true in the nxt.properties instead, but the API is probably better.)
Title: Re: NRS v1.7.4
Post by: Brangdon on January 04, 2016, 04:11:23 pm
2) Account Control, how does it work?
From the home page, click on the Account Balance More Info >, then the Account Control tab. This will let you set up mandatory approval for the account, which essentially means all its out-going transactions must be phased transactions, which means they must be approved according to the rules you set up here.

For example, if you wanted three signatures needed, then add the other two accounts to the whitelist under the second tab, and set the Number of Accounts to 2. If you wanted two out of three, then set Number of Accounts to 1. The current accounts signature will always be needed. If that's a problem, you can add a fourth account, set Number of Accounts to 2, and share the pass phrase for the current account with the other three people.

You really need to understand how phased transactions work first, before using account control.
Title: Re: NRS v1.7.4
Post by: Brangdon on January 04, 2016, 05:45:14 pm
Once account control has been setup can it be removed at a later time to restore an account back to basic?
Yes. The transaction that does this is subject to the existing account control, of course.

(I don't think there's any way to set account control to expire, although that might be useful as a safety net.)
Title: Re: NRS v1.7.4
Post by: testdruif on January 04, 2016, 07:10:03 pm
Is there any way for the ledger to show more than (for me) 106 items?
I think you need to rescan the blockchain. Which I believe you can do from http://localhost:7876/test?requestTag=DEBUG and explore the scan API. Setting height to 0 will rescan from the genesis block. The database will get a bit bigger.

(When I needed this, I set nxt.forceScan=true in the nxt.properties instead, but the API is probably better.)

Nr1 :)

That worked
Title: Re: NRS v1.7.4
Post by: Riker on January 04, 2016, 07:59:46 pm
Mac installer uploaded https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.4.dmg
SHA256 8a56e81aef05a3e2306e90bbcce9b0018ac0145dff1655d5d52a9e709e51de6b

I don't understand this one... It's not the same as the Nxt Mac Wallet?

This is a new Mac installer introduced in version 1.7, it is based on the same installer currently used by the Windows and Jar installers, it is created directly from the core code (so that anyone including Jeff can reproduce it) and it's digitally signed using the NXT stitching certificate (to prove to Jeff that it wasn't tampered with after it was generated)
Title: Re: NRS v1.7.4
Post by: farl4bit on January 04, 2016, 08:28:23 pm
Mac installer uploaded https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.4.dmg
SHA256 8a56e81aef05a3e2306e90bbcce9b0018ac0145dff1655d5d52a9e709e51de6b

I don't understand this one... It's not the same as the Nxt Mac Wallet?

This is a new Mac installer introduced in version 1.7, it is based on the same installer currently used by the Windows and Jar installers, it is created directly from the core code (so that anyone including Jeff can reproduce it) and it's digitally signed using the NXT stitching certificate (to prove to Jeff that it wasn't tampered with after it was generated)

Thanks for your answer. I never use Nxt with localhost/terminal stuff. I am used to the Mac App, which is just doubleclick and it starts. Which is how it should be to gain more Nxters.

The new "Mac Installer" gives me (and probably others) wrong expectations. Maybe we should communicate it differently?
Title: Re: NRS v1.7.4
Post by: allwelder on January 05, 2016, 07:31:43 am
How to issue Singleton Asset?
Did not find the button.

or just set quality=1,Decimals=0 with issue asset function?
Title: Re: NRS v1.7.4
Post by: MrCluster87 on January 05, 2016, 10:33:48 am
Thanks Brangdon!! This will be usefull when I will make the video for 1.7.4 release!!


2) Account Control, how does it work?
From the home page, click on the Account Balance More Info >, then the Account Control tab. This will let you set up mandatory approval for the account, which essentially means all its out-going transactions must be phased transactions, which means they must be approved according to the rules you set up here.

For example, if you wanted three signatures needed, then add the other two accounts to the whitelist under the second tab, and set the Number of Accounts to 2. If you wanted two out of three, then set Number of Accounts to 1. The current accounts signature will always be needed. If that's a problem, you can add a fourth account, set Number of Accounts to 2, and share the pass phrase for the current account with the other three people.

You really need to understand how phased transactions work first, before using account control.
Title: Re: NRS v1.7.4
Post by: Jean-Luc on January 05, 2016, 10:42:26 am
1) I see data cloud: can you compare it with storj, maidsafe and opal drive? Do we need http://www.nxttechnologytree.com/nxt-technology/nxt-distributed-storage in order to be a distributed Google Drive?

Our feature is much simpler and we cannot claim that we provide distributed storage, we don't plan to compete with those specialized distributed storage systems. What we have right now is a simple all or nothing choice, a node can either archive all prunable data, or none. In the long term, this is not scalable of course, but is sufficient for now. If and when the data volume increases, we can first start improving the granularity of selecting what types of data to keep for how long, e.g. a node might want to archive prunable messages, but not tagged data, or only tagged data for some specific channel, or only data submitted from specific accounts, and so on. When we reach a data volume that even this is not enough, we can decide either to dedicate development efforts to implement real distributed storage, or consider not reinventing the wheel but partnering with one of those platforms and store data on it, with some cross-blockchain transactions to pay for the storage.

What is important is that once data is created as prunable, we have the flexibility to later change exactly which data is stored for how long and on which nodes. So as long as the data volume is low, we can keep it simple, and later when the need arises, spend efforts on doing it more efficiently.
Title: Re: NRS v1.7.4
Post by: altsheets on January 05, 2016, 07:53:19 pm
Block times:

(https://raw.githubusercontent.com/altsheets/chaincountdown/master/tools/blocktimes-NXT.png) (https://raw.githubusercontent.com/altsheets/chaincountdown/master/tools/blocktimes-NXT.png)

Not important. I have only had a look at them, because I fine-tuned
my ChainCountDown (CCD) image server
     (nxtforum (https://nxtforum.org/nxt-projects/chaincountdown-blockchain-aware-countdown-timer-with-image-server/), bitcointalk (https://bitcointalk.org/index.php?topic=1147294.0), github (https://github.com/altsheets/chaincountdown), live server (http://altsheets.ddns.net:8888/)).

...

BUT these CCD images ... might be interesting for you ...
perhaps you put one of these images into a prominent place,
to remind people to upgrade to 1.7.4 before block 621000 ?

http://altsheets.ddns.net:8888/nxt/621000.png?heading=NXT%20hardfork%20@%20621000&fontsize=35&headingfontsize=42&bgcolor=F1F2F4&color=476C8E&font=Pecita
   or 
http://altsheets.ddns.net:8888/nxt/621000.png?heading=Upgrade%20before%20NXT%20hardfork!&headingfontsize=28
   or   
(http://altsheets.ddns.net:8888/nxt/621000.png?heading=Upgrade%20your%20NXT&headingfontsize=40&color=ffffff&bgcolor=476C8E)
   or design your own!


The images are rendered on the fly.

You can change their size, colour, and fonts easily.
See the examples and parameters (http://altsheets.ddns.net:8888/#examples).


If/As you expect heavy traffic, please run the server yourself. Very easy.
With docker, it is actually a one-liner only, to get it running (https://github.com/altsheets/chaincountdown#docker)!

ChainCountDown (CCD) image server: threads nxtforum (https://nxtforum.org/nxt-projects/chaincountdown-blockchain-aware-countdown-timer-with-image-server/), bitcointalk (https://bitcointalk.org/index.php?topic=1147294.0), github (https://github.com/altsheets/chaincountdown), live server (http://altsheets.ddns.net:8888/).

If you like this, show it:   NXT-CMKU-ZQYK-V6CD-9UHF4   - thanks.


Happy New Year, everybody

 ;)

Title: Re: NRS v1.7.4
Post by: qq2536007339 on January 06, 2016, 12:36:18 am
Our feature is much simpler and we cannot claim that we provide distributed storage, we don't plan to compete with those specialized distributed storage systems. What we have right now is a simple all or nothing choice, a node can either archive all prunable data, or none. In the long term, this is not scalable of course, but is sufficient for now. If and when the data volume increases, we can first start improving the granularity of selecting what types of data to keep for how long, e.g. a node might want to archive prunable messages, but not tagged data, or only tagged data for some specific channel, or only data submitted from specific accounts, and so on. When we reach a data volume that even this is not enough, we can decide either to dedicate development efforts to implement real distributed storage, or consider not reinventing the wheel but partnering with one of those platforms and store data on it, with some cross-blockchain transactions to pay for the storage.

What is important is that once data is created as prunable, we have the flexibility to later change exactly which data is stored for how long and on which nodes. So as long as the data volume is low, we can keep it simple, and later when the need arises, spend efforts on doing it more efficiently.

Well said!
Title: Re: NRS v1.7.4
Post by: farl4bit on January 06, 2016, 06:52:54 pm
I don't see average block times of 60s. Why is this? Is it a fault?
Title: Re: NRS v1.7.4
Post by: farl4bit on January 06, 2016, 06:56:52 pm
Oh sorry, I thought it was active in version 1.7.4 already. Please excuse my comment.  :-[
Title: Re: NRS v1.7.4
Post by: phideas on January 08, 2016, 11:45:07 pm
Bug in UI.
If you try to send NXT (currency or message) to your contact, the recipient input filed population fails.
All action buttons are affected.

(http://i.imgur.com/GfIg7i4.png)
Title: Re: NRS v1.7.4
Post by: icoin on January 09, 2016, 12:22:56 pm
getting this error while running Nxt on open jdk 8 on ubuntu

2016-01-09 12:19:43 FINE: Got 1 confirmations
2016-01-09 12:19:43 INFO: Downloaded 719 blocks in 32 s, 49 per s, 194 min left
2016-01-09 12:19:44 FINE: Database transaction required 44.598 seconds at height 30198
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1050)
  nxt.BlockchainProcessorImpl.lambda$null$24(BlockchainProcessorImpl.java:975)
Title: Re: NRS v1.7.4
Post by: OutSL on January 09, 2016, 12:31:16 pm
getting this error while running Nxt on open jdk 8 on ubuntu

2016-01-09 12:19:43 FINE: Got 1 confirmations
2016-01-09 12:19:43 INFO: Downloaded 719 blocks in 32 s, 49 per s, 194 min left
2016-01-09 12:19:44 FINE: Database transaction required 44.598 seconds at height 30198
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1050)
  nxt.BlockchainProcessorImpl.lambda$null$24(BlockchainProcessorImpl.java:975)

is not an error  :D is normal to see this lines... you must wait the full download of the blockchain! (will take time)
Title: Re: NRS v1.7.4
Post by: SamIbandii on January 09, 2016, 02:01:58 pm
Hello,
Maybe someone can help me?

This morning I installed NRS 1.7.4.
Before that I first deleted the lib folder of the previous NRS client (v1.6.2).
Installing and waiting for blockchain download went smoothly (approx. 2,5 hours).
Now I want to login to the client but it wont start-up.
Tried also to login with my passphrase without succes.
???
Title: Re: NRS v1.7.4
Post by: Riker on January 09, 2016, 02:12:06 pm
Hello,
Maybe someone can help me?

This morning I installed NRS 1.7.4.
Before that I first deleted the lib folder of the previous NRS client (v1.6.2).
Installing and waiting for blockchain download went smoothly (approx. 2,5 hours).
Now I want to login to the client but it wont start-up.
Tried also to login with my passphrase without succes.
???

Are you able to reach the login screen if not which URL are you using ? Any error messages in your nxt.log ?
Title: Re: NRS v1.7.4
Post by: SamIbandii on January 09, 2016, 02:42:32 pm
Hello,
Maybe someone can help me?

This morning I installed NRS 1.7.4.
Before that I first deleted the lib folder of the previous NRS client (v1.6.2).
Installing and waiting for blockchain download went smoothly (approx. 2,5 hours).
Now I want to login to the client but it wont start-up.
Tried also to login with my passphrase without succes.
???

Are you able to reach the login screen if not which URL are you using ? Any error messages in your nxt.log ?

Thanks Riker for replying so quickly.
Yes, I can acces the login screen in my browser. NXT-server says: "online".
The only thing wat is different from the previous version is that I have no nxt.log (black screen) where I can see the processes.

Title: Re: NRS v1.7.4
Post by: SamIbandii on January 09, 2016, 02:50:54 pm
Hello,
Maybe someone can help me?

This morning I installed NRS 1.7.4.
Before that I first deleted the lib folder of the previous NRS client (v1.6.2).
Installing and waiting for blockchain download went smoothly (approx. 2,5 hours).
Now I want to login to the client but it wont start-up.
Tried also to login with my passphrase without succes.
???

Are you able to reach the login screen if not which URL are you using ? Any error messages in your nxt.log ?

Thanks Riker for replying so quickly.
Yes, I can acces the login screen in my browser. NXT-server says: "online".
The only thing wat is different from the previous version is that I have no nxt.log (black screen) where I can see the processes.

Oh, and I forgot to mention:

I use: http://localhost:7876/index.html
And tried also: http://127.0.0.1:7876/index.html


Title: Re: NRS v1.7.4
Post by: OutSL on January 09, 2016, 03:05:40 pm
Hello,
Maybe someone can help me?

This morning I installed NRS 1.7.4.
Before that I first deleted the lib folder of the previous NRS client (v1.6.2).
Installing and waiting for blockchain download went smoothly (approx. 2,5 hours).
Now I want to login to the client but it wont start-up.
Tried also to login with my passphrase without succes.
???

Are you able to reach the login screen if not which URL are you using ? Any error messages in your nxt.log ?

Thanks Riker for replying so quickly.
Yes, I can acces the login screen in my browser. NXT-server says: "online".
The only thing wat is different from the previous version is that I have no nxt.log (black screen) where I can see the processes.

Oh, and I forgot to mention:

I use: http://localhost:7876/index.html
And tried also: http://127.0.0.1:7876/index.html

Purge the browser cache, if you use CCleaner run it clean your box and retry  :D
Title: Re: NRS v1.7.4
Post by: SamIbandii on January 09, 2016, 07:06:08 pm
Hello,
Maybe someone can help me?

This morning I installed NRS 1.7.4.
Before that I first deleted the lib folder of the previous NRS client (v1.6.2).
Installing and waiting for blockchain download went smoothly (approx. 2,5 hours).
Now I want to login to the client but it wont start-up.
Tried also to login with my passphrase without succes.
???

Are you able to reach the login screen if not which URL are you using ? Any error messages in your nxt.log ?

Thanks Riker for replying so quickly.
Yes, I can acces the login screen in my browser. NXT-server says: "online".
The only thing wat is different from the previous version is that I have no nxt.log (black screen) where I can see the processes.

Oh, and I forgot to mention:

I use: http://localhost:7876/index.html
And tried also: http://127.0.0.1:7876/index.html

Purge the browser cache, if you use CCleaner run it clean your box and retry  :D

Stil no succes.
I used CCleaner.
Any other options?
I have windows 7 (64 bit).
Title: Re: NRS v1.7.4
Post by: mikesbmw on January 09, 2016, 07:09:37 pm
Same happens to me.

I use a passphrase as always. I paste the passphrase, hit ENTER or click the arrow and nothing happens.
The passphrase box is automatically cleared and that's it.

Same result in IE 11 and Firefox 43.0.1

I cleared the cache on both browsers, redownloaded the blockchain after a fresh install of 1.7.4

Oh, I use the latest available Java version and Windows 7 64bit (up to date with patches).

(EDIT) on my Mac it's running just fine, but I hardly use it there. I normally leave NRS running on one of my MS VM's fulltime.
Title: Re: NRS v1.7.4
Post by: mikesbmw on January 09, 2016, 07:30:53 pm
Sorry for constantly updating, but I also notice this.
My clock is in sync with time.windows.com.

"2016-01-09 20:26:40 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073201, system clock may be off

2016-01-09 20:26:42 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073202, system clock may be off

2016-01-09 20:26:43 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073203, system clock may be off

2016-01-09 20:26:44 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073204, system clock may be off

2016-01-09 20:26:45 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073206, system clock may be off

2016-01-09 20:26:46 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073207, system clock may be off

2016-01-09 20:26:48 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073208, system clock may be off

2016-01-09 20:26:49 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073209, system clock may be off"
Title: Re: NRS v1.7.4
Post by: Riker on January 09, 2016, 09:36:58 pm
Stil no succes.
I used CCleaner.
Any other options?
I have windows 7 (64 bit).

In case you installed version 1.7.4 using the Windows installer and run it using nxt.exe, you'll no longer see the (black) console window. Instead you'll see an NXT status icon in the Windows tray icon. Use it to monitor the server. This is normal.
Title: Re: NRS v1.7.4
Post by: Riker on January 09, 2016, 09:46:42 pm
Sorry for constantly updating, but I also notice this.
My clock is in sync with time.windows.com.

"2016-01-09 20:26:40 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073201, system clock may be off

2016-01-09 20:26:42 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073202, system clock may be off

2016-01-09 20:26:43 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073203, system clock may be off

2016-01-09 20:26:44 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073204, system clock may be off

2016-01-09 20:26:45 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073206, system clock may be off

2016-01-09 20:26:46 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073207, system clock may be off

2016-01-09 20:26:48 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073208, system clock may be off

2016-01-09 20:26:49 WARNING: Received block 11404298989650619675 from the future
, block timestamp is 67073279, current time is 67073209, system clock may be off"

Forger NXT-K5KL-23DJ-3XLK-22222 is trying to game the network by trying to forge a block before it's turn. This is a forging pool with 54 lessee accounts and effective balance of 28'213'099 NXT
This account is normally forging around 2-3 blocks an hour which is reasonable, I don't think that a source of concern at the moment.
Title: Re: NRS v1.7.4
Post by: Riker on January 09, 2016, 09:51:16 pm
Same happens to me.

I use a passphrase as always. I paste the passphrase, hit ENTER or click the arrow and nothing happens.
The passphrase box is automatically cleared and that's it.

Same result in IE 11 and Firefox 43.0.1

I cleared the cache on both browsers, redownloaded the blockchain after a fresh install of 1.7.4

Oh, I use the latest available Java version and Windows 7 64bit (up to date with patches).

(EDIT) on my Mac it's running just fine, but I hardly use it there. I normally leave NRS running on one of my MS VM's fulltime.

Ok, I reproduced this with IE11, doesn't happen with Chrome on Windows though. Perhaps it's related to fixes we made to data entry on Android. Please create a ticket for this on https://bitbucket.org/JeanLucPicard/nxt/issues
Title: Re: NRS v1.7.4
Post by: SamIbandii on January 09, 2016, 10:28:50 pm
Stil no succes.
I used CCleaner.
Any other options?
I have windows 7 (64 bit).

In case you installed version 1.7.4 using the Windows installer and run it using nxt.exe, you'll no longer see the (black) console window. Instead you'll see an NXT status icon in the Windows tray icon. Use it to monitor the server. This is normal.


Hello Riker,
The problem I have is the same as MikesBMW (see his post today at 07:09:37 p.m.).
My browser is IE version 11.
When I enter the passphrase to start the NXT Wallet and hit ENTER or the Arrow, nothing happens.
(cache is clean and NXT server says "online").

Tomorrow I 'll retry: uninstall everything and then proceed with fresh reinstall. 
Would appreciate any help?
Title: Re: NRS v1.7.4
Post by: mikesbmw on January 09, 2016, 11:09:25 pm
Same happens to me.

I use a passphrase as always. I paste the passphrase, hit ENTER or click the arrow and nothing happens.
The passphrase box is automatically cleared and that's it.

Same result in IE 11 and Firefox 43.0.1

I cleared the cache on both browsers, redownloaded the blockchain after a fresh install of 1.7.4

Oh, I use the latest available Java version and Windows 7 64bit (up to date with patches).

(EDIT) on my Mac it's running just fine, but I hardly use it there. I normally leave NRS running on one of my MS VM's fulltime.

Ok, I reproduced this with IE11, doesn't happen with Chrome on Windows though. Perhaps it's related to fixes we made to data entry on Android. Please create a ticket for this on https://bitbucket.org/JeanLucPicard/nxt/issues

You are right!

I downloaded chrome and everything is working as it's supposed to be  ;)

By the way: in Firefox the passphrase line is greyed-out.
I will create a ticket. Thanks for your help!
Title: Re: NRS v1.7.4
Post by: TheCoinWizard on January 10, 2016, 01:35:06 am
Do we know who controls 2222? Why isn't this a problem? Are the owners of 2222 trying to break the network, causing a block with illegitimate transactions in it to be accepted?
SELL SELL SELL  :D  :D  :D

Noo, just kidding... Here are your answers:

ForkedChain
What problem?
No, I assume he is just trying to optimize the amount of blocks he forges by adjusting parameters in the config-file.
Code: [Select]
#### Blocks and transactions ####

# Delay generation of next block in order to accumulate more transactions in it.
# Waiting for much more than 15 s is not useful as transactions are allowed at
# most 15 s timestamp difference from the block they can be included in.
nxt.forgingDelay=20

# Generate and submit the next block before its hit time in response to
# receiving a lower difficulty block. Submitting the block more than 15 s before
# its time however will lead to its rejection.
nxt.forgingSpeedup=3
No illegitimate transactions can be written in the chain as no forger would accept such a block..
So take a chill pill dude  8)
Title: Re: NRS v1.7.4
Post by: Riker on January 10, 2016, 06:30:43 am
I guess it goes to show the trust he has in network protocol that it doesn't matter if a large forger is tweaking about with forging times.

Exactly, NXT is trying to guarantee that as long as 50% of the stake is controlled by honest forgers, one forger trying to game the system will always fail.
Currently, we do not penalize such attempts and frankly I even like it when people are trying as long as if they find something they announce it in public and not use extortion techniques like we had in the past (not in this case of course).
Title: Re: NRS v1.7.4
Post by: SamIbandii on January 10, 2016, 09:30:36 am
Same happens to me.

I use a passphrase as always. I paste the passphrase, hit ENTER or click the arrow and nothing happens.
The passphrase box is automatically cleared and that's it.

Same result in IE 11 and Firefox 43.0.1

I cleared the cache on both browsers, redownloaded the blockchain after a fresh install of 1.7.4

Oh, I use the latest available Java version and Windows 7 64bit (up to date with patches).

(EDIT) on my Mac it's running just fine, but I hardly use it there. I normally leave NRS running on one of my MS VM's fulltime.

Ok, I reproduced this with IE11, doesn't happen with Chrome on Windows though. Perhaps it's related to fixes we made to data entry on Android. Please create a ticket for this on https://bitbucket.org/JeanLucPicard/nxt/issues

You are right!

I downloaded chrome and everything is working as it's supposed to be  ;)

By the way: in Firefox the passphrase line is greyed-out.
I will create a ticket. Thanks for your help!

With Chrome everything is working fine.
I actually have an operational NXT Client vs 1.7.4 now!  Hooray!!! :D
Thanks for the help.

Title: Re: NRS v1.7.4
Post by: ron on January 10, 2016, 12:45:52 pm
hello,

with NRS v1.7.4 opera browser 12.xx can't open account via h****//localhost:7876/index.html
firefox and chrome have no problem with login.
I'm on win7x64 and all others versions up to 1.6.xx worked before without such problems.

this shows in error console with various other unknown class and property messages:

sorry can't post code directly because "Sorry, you are not allowed to post external links."

I copied errors to h***//pastebin.com/d2SHphfe

Title: Re: NRS v1.7.4
Post by: Roiman on January 11, 2016, 07:59:07 am
Same happens to me.

I use a passphrase as always. I paste the passphrase, hit ENTER or click the arrow and nothing happens.
The passphrase box is automatically cleared and that's it.

Same result in IE 11 and Firefox 43.0.1

I cleared the cache on both browsers, redownloaded the blockchain after a fresh install of 1.7.4

Oh, I use the latest available Java version and Windows 7 64bit (up to date with patches).

(EDIT) on my Mac it's running just fine, but I hardly use it there. I normally leave NRS running on one of my MS VM's fulltime.

Ok, I reproduced this with IE11, doesn't happen with Chrome on Windows though. Perhaps it's related to fixes we made to data entry on Android. Please create a ticket for this on https://bitbucket.org/JeanLucPicard/nxt/issues

You are right!

I downloaded chrome and everything is working as it's supposed to be  ;)

By the way: in Firefox the passphrase line is greyed-out.
I will create a ticket. Thanks for your help!

With Chrome everything is working fine.
I actually have an operational NXT Client vs 1.7.4 now!  Hooray!!! :D
Thanks for the help.

Same happened to me but i updated firefox (in firefox - Help- About Firefox) and now it works fine
chrome doesn't work but maybe that needs updating too
the java nrs was working when the browser wasnt
Title: Re: NRS v1.7.4
Post by: Riker on January 11, 2016, 10:28:59 am
We were using a JavaScript API which might not be supported across all browsers, especially old versions.
This should be fixed in 1.7.5
Title: Re: NRS v1.7.4
Post by: coretechs on January 11, 2016, 02:19:21 pm
In the settings in the client (gear icon) when you enter your administrator password, would it be possible to have the form field override/preventdefault pressing "enter" (char 13)?  Right now if you press enter after typing the password it will refresh the browser page and kick you back to the login screen.



Also a super minor punctuation fix, under Shuffling->My Shufflings the notification message ends with a comma instead of a period - "There are no shufflings,"
Title: Re: NRS v1.7.4
Post by: EvilDave on January 11, 2016, 08:23:37 pm
Starting on really annoying random people about the update:

https://twitter.com/NxtCommunity/status/686643629096583168

Please RT and spread the word.
Title: Re: NRS v1.7.4
Post by: CryptKeeper on January 11, 2016, 08:59:44 pm
Done!
Title: Re: NRS v1.7.4
Post by: Riker on January 11, 2016, 10:01:38 pm
In the settings in the client (gear icon) when you enter your administrator password, would it be possible to have the form field override/preventdefault pressing "enter" (char 13)?  Right now if you press enter after typing the password it will refresh the browser page and kick you back to the login screen.

Also a super minor punctuation fix, under Shuffling->My Shufflings the notification message ends with a comma instead of a period - "There are no shufflings,"

Both issues should be fixed in 1.7.5
Title: Re: NRS v1.7.4
Post by: JPred on January 12, 2016, 03:02:11 am
Jeez, I got a fright when I had the same issue as mikesbmw [#76,82] when I tried out 1.7.4 for the first time. Luckily chrome solved all, lol, feel much better now.



Happy New Year, everybody

 ;)

Happy New Year altsheets. :)

Title: Re: NRS v1.7.4
Post by: icoin on January 12, 2016, 06:27:44 am
This looks like exception?

2016-01-12 06:22:36 INFO: Blockchain download in progress
2016-01-12 06:23:13 FINE: SQL statement required 14.648 seconds at height 530622:
DELETE FROM account WHERE height < ? AND height >= 0 AND latest = FALSE  AND (id) NOT IN (SELECT (id) FROM account WHERE height >= ?)
  nxt.db.TransactionalDb$DbPreparedStatement.executeUpdate(TransactionalDb.java:330)
  nxt.db.VersionedEntityDbTable.trim(VersionedEntityDbTable.java:150)
  nxt.db.EntityDbTable.trim(EntityDbTable.java:440)
  nxt.BlockchainProcessorImpl.doTrimDerivedTables(BlockchainProcessorImpl.java:1060)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1043)
  nxt.BlockchainProcessorImpl.lambda$null$24(BlockchainProcessorImpl.java:975)
2016-01-12 06:24:07 FINE: Database transaction required 320.069 seconds at height 530622
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1050)
  nxt.BlockchainProcessorImpl.lambda$null$24(BlockchainProcessorImpl.java:975)
Title: Re: NRS v1.7.4
Post by: CryptKeeper on January 12, 2016, 08:47:47 am
I'm on Windows 10 64bit, using the client in a hyper-v session with edge browser.
If the blockchain download is not completed, there should be an appropriate message. On my system, this message is sometimes shown, sometimes not. Yesterday I've created a tx and got the error message "tx timed out" after a while, IMHO that was related to the blockchain not completely loaded.
Title: Re: NRS v1.7.4
Post by: Riker on January 12, 2016, 08:55:49 am
This looks like exception?

2016-01-12 06:22:36 INFO: Blockchain download in progress
2016-01-12 06:23:13 FINE: SQL statement required 14.648 seconds at height 530622:
DELETE FROM account WHERE height < ? AND height >= 0 AND latest = FALSE  AND (id) NOT IN (SELECT (id) FROM account WHERE height >= ?)
  nxt.db.TransactionalDb$DbPreparedStatement.executeUpdate(TransactionalDb.java:330)
  nxt.db.VersionedEntityDbTable.trim(VersionedEntityDbTable.java:150)
  nxt.db.EntityDbTable.trim(EntityDbTable.java:440)
  nxt.BlockchainProcessorImpl.doTrimDerivedTables(BlockchainProcessorImpl.java:1060)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1043)
  nxt.BlockchainProcessorImpl.lambda$null$24(BlockchainProcessorImpl.java:975)
2016-01-12 06:24:07 FINE: Database transaction required 320.069 seconds at height 530622
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1050)
  nxt.BlockchainProcessorImpl.lambda$null$24(BlockchainProcessorImpl.java:975)

This is not an exception just a warning about very slow database performance. The trim derived table function here took 320 seconds to complete. It could because your node downloaded the blockchain at the same time or was doing other, non NXT, IO intensive work at the time.
If this is a "one of" message it should be safe to ignore.
Otherwise you'll need to tune your node performance.
Title: Re: NRS v1.7.4
Post by: OutSL 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
(http://i66.tinypic.com/2qlcun8.png)
HD : http://i66.tinypic.com/2qlcun8.png

Thank you all and @++
Title: Re: NRS v1.7.4
Post by: EvilDave 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/
Title: Re: NRS v1.7.4
Post by: OutSL 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 :( )
@++
Title: Re: NRS v1.7.4
Post by: testdruif 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
Title: Re: NRS v1.7.4
Post by: Jean-Luc 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.
Title: Re: NRS v1.7.4
Post by: cayenne 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?
Title: Re: NRS v1.7.4
Post by: k3t3r 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
Title: Re: NRS v1.7.4
Post by: blackyblack1 on January 13, 2016, 05:56:26 pm
chmod +x run.sh
Title: Re: NRS v1.7.4
Post by: k3t3r on January 13, 2016, 09:00:02 pm
chmod +x run.sh
Hey, Its doing something! thank you!
Title: Re: NRS v1.7.4
Post by: k3t3r 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
Title: Re: NRS v1.7.4
Post by: k3t3r 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.
Title: Re: NRS v1.7.4
Post by: abctc 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 ?
Title: Re: NRS v1.7.4
Post by: NxtSwe 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.
Title: Re: NRS v1.7.4
Post by: TheCoinWizard 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
Title: Re: NRS v1.7.4
Post by: martismartis 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.
Title: Re: NRS v1.7.4
Post by: allwelder on January 15, 2016, 02:43:21 pm
Deleted.
Seems I got it.
Title: Re: NRS v1.7.4
Post by: blackyblack1 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.
Title: Re: NRS v1.7.4
Post by: Riker 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.
Title: Re: NRS v1.7.4
Post by: blackyblack1 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)
Title: Re: NRS v1.7.4
Post by: Riker 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.
Title: Re: NRS v1.7.4
Post by: blackyblack1 on January 18, 2016, 08:42:40 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.
I've already tried signing transaction with signTransaction call but it does not work with client-side signing (when calling from remote node).
Title: Re: NRS v1.7.4
Post by: Riker on January 18, 2016, 08:50:50 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.
I've already tried signing transaction with signTransaction call but it does not work with client-side signing (when calling from remote node).

I see, so you want to call NRS.signBytes(converters.byteArrayToHexString(transactionBytes) and let the client use the remembered passphrase.
I can add this to 1.7.5
Title: Re: NRS v1.7.4
Post by: blackyblack1 on January 18, 2016, 08:53:03 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.
I've already tried signing transaction with signTransaction call but it does not work with client-side signing (when calling from remote node).

I see, so you want to call NRS.signBytes(converters.byteArrayToHexString(transactionBytes) and let the client use the remembered passphrase.
I can add this to 1.7.5
Yes. Thanks.
Title: Re: NRS v1.7.4
Post by: whale on January 19, 2016, 11:56:44 am
My wallet no longer loads properly since the update (I also had to re-download the blockchain). Recent transactions constantly load and the side bar is just blank. When I try to 'Send NXT' it just returns an error 'Deadline not specified'. I am using windows 10.

Any idea what I can do to fix this?
Title: Re: NRS v1.7.4
Post by: martismartis on January 19, 2016, 12:08:28 pm
My wallet no longer loads properly since the update (I also had to re-download the blockchain). Recent transactions constantly load and the side bar is just blank. When I try to 'Send NXT' it just returns an error 'Deadline not specified'. I am using windows 10.

Any idea what I can do to fix this?

Did you try refresh/clean browser cache before log in to your updated wallet?
Title: Re: NRS v1.7.4
Post by: whale on January 19, 2016, 01:08:31 pm
My wallet no longer loads properly since the update (I also had to re-download the blockchain). Recent transactions constantly load and the side bar is just blank. When I try to 'Send NXT' it just returns an error 'Deadline not specified'. I am using windows 10.

Any idea what I can do to fix this?

Did you try refresh/clean browser cache before log in to your updated wallet?

That worked, thanks!!
Title: Re: NRS v1.7.4
Post by: lopalcar on January 20, 2016, 09:11:53 pm
One question about account control:
Can I set the control only for a certain type of transactions? For example, I want to control the asset operations but not the simple send, MS or any other kind of transactions.
If so, could I also choose a single asset ID to control? And allow the rest of assets to operate without restrictions?
Title: Re: NRS v1.7.4
Post by: P2PGuy on January 20, 2016, 09:34:51 pm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.4

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.4.zip


Unfortunately, the last 4 NRS releases haven't worked on Mac / OSX Mavericks, for me. The nxt-client/wallet app loads but just hangs. Even after re-downloading the blockchain, several restarts, re-installing and updating Java, Terminal commands etc. I have tried virtually everything but still it just hangs without actually opening the app fully. 

I see it is trying to work via the : Tools--> View Sever Log  pop-up window but it never gets past the 'busy wheel' welcome screen even after a fresh blockchain download and restarts.

New users must be a bit apprehensive if this is a wider issue for Mac users?

Any thoughts appreciated.


Title: Re: NRS v1.7.4
Post by: Riker on January 21, 2016, 07:56:09 am
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.4

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.4.zip


Unfortunately, the last 4 NRS releases haven't worked on Mac / OSX Mavericks, for me. The nxt-client/wallet app loads but just hangs. Even after re-downloading the blockchain, several restarts, re-installing and updating Java, Terminal commands etc. I have tried virtually everything but still it just hangs without actually opening the app fully. 

I see it is trying to work via the : Tools--> View Sever Log  pop-up window but it never gets past the 'busy wheel' welcome screen even after a fresh blockchain download and restarts.

New users must be a bit apprehensive if this is a wider issue for Mac users?

Any thoughts appreciated.

I'm not familiar with these problems ... I'm able to run NXT on mac without problem even though the initial download and/or re-scans can take a lot of time.
Can you post your nxt.log ?
Title: Re: NRS v1.7.4
Post by: P2PGuy on January 21, 2016, 04:11:59 pm
Hi @Riker, it was to long to post so I sent you a PM

Thanks,

P2Pguy
Title: Re: NRS v1.7.4
Post by: Riker on January 21, 2016, 08:28:13 pm
Hi @Riker, it was to long to post so I sent you a PM

Thanks,

P2Pguy

Note that your database response times are extremely slow, for example:
2016-01-21 17:22:00 FINE: Database transaction required 975.823 seconds at height 619927
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1050)
  nxt.BlockchainProcessorImpl.lambda$null$24(BlockchainProcessorImpl.java:975)

I assume you are running on decent hardware and that your disk is not full and your operating system is not swapping memory to disk.
If so, the most likely explanation is that your database needs cleanup.
Run compact.sh to cleanup your database. Hopefully this will improve performance.

Title: Re: NRS v1.7.4
Post by: qq2536007339 on January 22, 2016, 03:30:40 am
If I set nxt.adminPassword=mypw,when I click "Active Shufflings" page,a error message come out.

Quote
"Cannot check shuffler status. Incorrect administrator password. (the specified password does not match nxt.adminPassword)"

Is this the correct behavior or a bug? If this is suppose to be,how can I get rid of this error?
Title: Re: NRS v1.7.4
Post by: qq2536007339 on January 22, 2016, 10:54:02 am
Are you setting the password in two different places? First you should stop NRS and put nxt.adminPassword in the config file, then log in and add it to settings in the UI.

I use raspberry to run NRS,and login from my PC.Thanks,I didn't notice adminPassword set in UI before.
Title: Re: NRS v1.7.4
Post by: farl4bit on January 22, 2016, 11:04:33 pm
Good night.  ;D

(http://i65.tinypic.com/2e2mq6w.jpg)
Title: Re: NRS v1.7.4
Post by: lurker10 on January 23, 2016, 08:27:28 am
How did the hard fork go?
Title: Re: NRS v1.7.4
Post by: chanc3r on January 23, 2016, 08:50:21 am
I have noticed the client can be a little temperamental in Safari, after entering the passphrase sometimes safari just sits there and does nothing. In these cases I simply switch to firefox.

I use a mac running on vmware on a mac (so a mac within a mac) to run NRS and it still performs fine, the virtual mac only has 2GB of memory and 2 cores allocated to it.
Title: Re: NRS v1.7.4
Post by: abctc on January 23, 2016, 09:06:06 am
How did the hard fork go?
- It seems everything is going well.
The only unusual thing is that my Nxt server produces a lot of such messages:
Code: [Select]
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"6aa444e976c56e0a60919c4e6c02a85203cc46a661715c0342f6d26b5fd1aa0effbe1401e28b81ac299e493c2bf79cc55ce3c34f3ece8b5f0f6be66cef7f5039","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"Vy0qwm9swZTj0bvBV3FCrlG4wm9xKmGuwszcy9hPk+C219Se9q36QMb8BFATu9mlnTlx1Cr\/N13BNAP97BsduZfd9RsHGCAYYiJALTdfM9okwv10zZ1RmcXKf4zFkkzEx59zZGncVlCXJZgGLu03XnH\/Blqcy4Desp+\/gCfIMcBOIul1MNpaKfbBgyzRyk6luVNVwkzfzso7Q0979STBZ0qE0wkasrgU9AtdCvGM1\/O4rIvVKPVfEawz5U25hgM0ScAf0\/6A8A9res1pSWnCVa5LFnfKTAtnVt34\/O5DRajDIsam7jgcNQRUTG5wPyMtV3NyPsccmNisFW4clWUws1vX\/ihBzA1rFicg++O4pl8bgdl80ue5cCM88iJ9MSz+cLOEDPf3jWw3Cr+BLu8cOPmhBrczPWKf\/ZcUcoHwuZ4olQHkP7CBRwdBcdXaleVAj54huzCNEjzd2xXhtOR9GtJ5QPHxNLRkEUgcLn6CujLQ5c1+4fSUSa3YYGYTyrFPhVSyUFRiYh7GvGReje3b+umhetJuKz1YlCalFHbAuQLaLR6d3sNAGHwL0CyAs2AgF0YySqmt16uSr0cNS5XWCuKK+dl0Y+1DWnLXJomhMBiJPhSKIpD2cfVfCPM0ksx3QxP\/JcxhtgSZcz9rRzfi7JOUJGNNLqDPMZWJHr\/0pc\/ksUpNSm++0OYho+21PjhCGgXIDmdxjTXg3A0ZSsFzNiYVrC\/v+TIT05zeD1ypoYrjB\/+lZqNADZ314+sOsJhK8jLnW6cXvozXXG0x8b3kas9ZfQTuezvR9oAYKOvafC+Pdw1WG7KttvT+EDSGEW+eer2jzK9CoxdO\/GWUrtHCeg=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68232596}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"71f17fc10e025d9ebf64be9b1695f780ed6a2ad722e8d71057a6f098d50c0d06682bb6b4ab11fb924a6947e1c95736e4db95c2c485ae3f41ba126fc7e02c8a26","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"oabbagI846wafnY\/1iKlG98xAysON2EKHuAHJcssVIvT3oHOM0E24tZpjxDLNqVDUSke7FFI1juibQ6HO+82KLzB8QcMTDCs9JQT0HZOpvY60r79qqfop1IuKKWDxygS+uoSBERQq9aPYFmDaor4fMLlMAWWQm+kDzLoCy3XwItooo1vrBqlQ23i+YP8yzsdCB4mY0xu7SDu51DGabAYnTx4KibOntXUWwQ2KnvkFOZVxGQsS6cAD+WLVAtqhguaMf3u9QVqcyyJbDO1zem7Hkfmj9lshmDaTMD6NVDv4XRKfD9sqVm9WU9eumkhRRyMtL7p8u\/1hcYxTqCZzSpAp\/kZqIk+Bjm1J09lJmAg+3eq4FoSyip6KelvhxnaRYvOhAuYEgHEKxvBW3hI\/OJfAs6M2N4mMW3xyJj1Hu\/cfUtvkc4M0tKw87rO0utMquxj+0\/FuxT8KJTKbH4kO+cYL2jm9DqBMweGiZZms3No\/Lrn3BNryGB69YynW1HPuoO19msbiCkSok7Rzk5Op5hd6WTusgLThvtkD8JvagGw3q4CLkf5YVZxSQKNB55D7uwT\/QQU1ju9dkkhl\/qSDMK\/dMTaRwEAM\/Tw1Ytqu\/nEnqMTPetCHFjNEfxPJi9NKigrGUM5+1dJa8VPXznCgpxCSsIIh6a7MDvMrXoHN91Ctbcw\/YLqUA5o596Z+u\/75LWwjgkQJSV\/Vv8wUsLOhBXo243FJcKr2LEWDuNmekYB1mBjxWLyXFgvrAFzZxFrtxzIMSaQPhshoRV8hO\/vd4oz6cWBlMU+YnQs9ZzTjghptk17mOc04khq1rQ\/GggOR+te8DMX5TCLSLXrvBI\/CO+SGA=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68232833}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
....................
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"33c95b2980075edcfb4e1244cebcca3c5c29ee57da077bb72fa3608caafdd707d210ea08d847ed1f42d7073493e67bd16f60881f99f1f6b4a91643e5daaa300b","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"1futgRzpyUwgwZ\/PTXl7m0x0woWowHLDZeD87Zl\/n6VYb4AhOGUvkepQwisY8cMXX+ouWniYCAyoxtq9b4YwcjDUzbBcuiLgmh32nOAc5BmAq04ZrPlSn6cBNp5pr9B11Qm5NXmBuPlwBPL0OyUFBpYVtFb8usdw8flXXyLAoi0KG1DRvHDbwI7kIDl1so4zkKP74mX3fsoAw2GERiq96zgkMfLcSJufVhksze8b1Bp4CXkQaAag15qiQ\/d+3rONVZPIAGY0Iz\/OlQjVX1N3BPjiRazkqt6xlbDuHM73FWTHRoZIuBJVBxxhTn8zcwju\/oehBhbhuyw01TofuKTqx9jbV1c0t6yWIieZSbJRwfb8jgpgxqa0C0epT35DzDQHK1uBbw8t1IqJzvn4ra1rZf1\/viQ4gqa5tjetcEV6XWsPpmcWFhXvEyb6B4iCaNaflTlFmMZEXkeKXTJ0whsZnSdgYL3LGiLuXxb5qINP+Pb2Tc57rxjbUYbgRQuMGI6vQIJQjTXiC4zpUY+A3ws\/+fnyDLg8qHq419+cMxfG+1ZEw3qpqgq8xZegqRwK7UjairO5hOiC6E4qL7g\/mpNPaVTEKYL3QzYAVEYT3o4rmDbtnwELNJihABvx2oWVPPZoU1RhjV2CzFS6kzSmhkKmOKYxX0R1omyOxylGEgh++KkTExiJg9l2tb5BAiKXUQCMJ\/iOnTCMUBXR08ImxcNI99FJmAte+4MQ32QFFeVJrnXKvXgqLCtjY6xA6EVM\/8FGD04V4RCJzRvPIL26FEW2YUceNF1V+BS4ZiEZKH+g28usfvoY1gWgypH1tufEwu+vJyz\/h8Fu6HMa7AQkEOiZoA=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68233388}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"fab4232c37fe7ba4f8163c669b2c26ec8e90ec0c5e9cc94ebd15b84049a255011a99e25a9dcceb025175d3c52f334403a50fc02ea9eb2321edc0afe908cd359b","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"AVba0DlJaIhqa3Fl4R7RGOJJrcN2KIhqup+sVT93Dq83ytVgm9wuamJbYWo2qImFCvr\/XwDY0SKdBGh+fTGhLB7yI26JP7v714y1HbRyIHCoiM7tbxJAL3t85MakrMSKuJHbLYzdGEpjCq\/OquGCR9\/727KSomeRLU9CH9rEkMLa82+81tZRr7MOPNLlM2xqGecHgFP7RvdEPUiuOjMjwvKbrLAWdXTxqswWLGvtBzeYMjlQqIvc9ypLt9yIC8X7cjq0HR22IjFVh3LhBi8V94R4ro6o0IN9jzFtE9GQhsYETSMCLMD1UfjjEKZ7\/jwyAvgh1GJVSgVnGp\/as+Pu6xDkhW8PI7yOJq6kUSPrgav2ZtQSCsPA7xyJFhrclSDD+iTxTNhy17ZHjYANYUTSCZSIn4NrCU\/8AoX2FCQ9DJuVNnFBJOS5qTScPS3hBsz4xvRJGO1fZeWwUDFVG\/KDYJLucwVmy6fm\/gSSqHXTfwjjjvuFunFe7RTxB+0M\/pYs\/h3WqzHMgWDa12VcbJhzNN4e6raxFqmw6gsJdQQUrUQhCaswVtej3gfvYbDh2YHa9pE19Bpt\/rmF94KuvJiJzgX0MSiNuep1NYHp6m+VmbkCjF2etOckLyU8\/isWlvMcwfEsyDYWKpJAx8S30VOoETPZXCT3pIvjqm2QEWdi3t2LyZNpob\/2+umbhG8cf+qSM9d+kJyyWgJ766kAgXNh4UEKdWaUwsJXat5PlkCRFJJBwCboIs8RE7RHxpWDDlUsJ3w48Hor6D5ud0GutjJ3r7U718zctjj9PVMu\/M8L5UJ3To4DilFs7qhdynPJ8MQjsRXZSWymvgdjfFyOG1Ei2Q=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68232991}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"f0ce16cc57ff13e3c47228db2de40dcde0bcf33e8b7cbf79ae375a393e54fa039d575a659e7d37e5d6ceac500f65621bdab18b3f9fb9cec04502eec492560f62","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"wHGetf7WrxrxbrMa4z+32wBNeRBOy5kDLOrskFz3cDiVeskF3R6DZq1+XiAblXJAQkbbRRpXaRhrh7DTsuU9IXVZzbOXpTObiBTxez9D7Xd1xPidtg\/sNIKJA4FnTCmqMXV0FFDgkNMYmQqSayPT8YwY+0BlgOieeXKATy+dA91pXYvr6v0\/KWqztUjwnDAT1W\/eHTi0SaN3z5DcvpJhKzSrk8MC9MNejOu\/lJyUd6qZWiomStcJOKFLrRUs7azCqxSIQEWiuAHUql3IfRA4U2pf1S0Vexrc3BFLUQ5WklbHnofFY4Hikcej1hyrDfvGfaKz1TBv9OAw7BISmO0qUd6jcq+F3wwQRAu2mHEv9ygvwmzHZnF5NNR18f421nwRrf91wtscuNuFmP1fwuT8FJgUzICAOESocczEOz5mkKBkmQNgPKf5QDqVwLG9c3goTd9vaRZU7dhf9oVzFskfxgFf6scPyoqkU7xWHMco\/IbWb9DAlEGodRxi1b4qX1c5e4IHv5EKIW5mlaZNVClHqEda88Sxz5trSjZYeTAUMdWNrVj0tFWiLShhYceEgYK\/3zhevKMdrM78WsyZVMwByvd9XGgpYoJlIOz5w00rid8F2AOmXSrvU\/KoyeTCIq\/RrcCLBSTPZa\/zKRIPMpJskYLywtL7hWgcSBnuwQqS8d0LmGsKTs1ySlg3zVmQIxKeCQM7JcxqKSBFK3PJWFwaxpJV0HTfvLzWSmzMOFvOMc2MEiXi++VX0dOIjaOUIaSWIiOC8AIPPQtSKCvXZnfCSBvabu98U9qNibpBwx6Q2S7IPcOe+HH+wJl\/2eVbMJ7XqL3t\/mkH+FfnoXbA0invig=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68233151}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"7a502a1749010546d2aeb14a8bcb2b64548e40f3b2adc7fb5eae94cde19d5d0e5d86f1b172543532f015d58ed46bba005019326df9d54b06447d211718fb653a","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"w3XLZbY7yt4Iu+BpnZkm8V30IC6kOHNjDRXn+bHBnG7nXrsRgUW4mnl05rTJ9JY7wsHhe4iJGZP7LMPENAZzaNuU2Nv+\/n\/TJjpF2bcYIwaaCUE46Oc\/fx57sLgHaDSKKB3hjlE5uQoywGONFrgkOnALbRN3VkBfx93tC1sUTY5OJnFLy\/nGNkgVQhIUOp0t+utRmRy77wdqo4PzL8VIK\/5cB\/TxX4Ht0mcuIn+O4hfHmVAxgqntl380oTUAERY5p61vGeGbtfkOv9Sc6yTaugoMOSNG0MSmvElfiVr2yULVlDRS3MPDGPo5fIpq0cBk8nIzslT3kUD5ThIskkEJibX356L3CGwoUcJ0oGJdm\/6Tv42tdt94g0gIwWMD0hyyYdiw6MyMUt0aZCvSHLxLGNp6RRIHCmdtP863rlXc4ZHDX8NxCNy3H0ZrcGtfz3v8BCgyxZeVf5Cm5t8HvpCkkV0bkJGqft0aGzoEOw9sc8LvtZrsi7kTnwfZ7s+itYM\/o5V1riq6a2uy88NS8I38VXHTO6+72nLfVKjW\/UZBHvP5lDyNa6zBK5yhucoYTFw5wqIn9NlsLHVz0267aasEQGXgAfvza59qu9\/+7cvK1krZshWXziuvf8\/aY\/bB95otIOiZaBqvj417+qorwQE7aLx3pE0stg8nnRT7AnS\/+z5DWS97Rv4gCYtQME5KP1JyQennRrqtGfbHIqhzgJOFjVepDEIQN1wx8TAjNQlOL0OCkAcjsne58iU56+tYSpMibE\/WOHrvutdYBhFxLfcuHiyvjbrnBZmO6VeUyht+q22HhKxYpC\/69aqCJEptGtzaNIDxE4O1I2zAz4ROZVcSQHWE\/oAbJd2ykFJUNymTceU="},"subtype":0,"amountNQT":0,"recipient":"4692641630405905408","ecBlockHeight":621089,"deadline":604,"timestamp":68231996}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 876
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Blacklisting 92.222.65.159 because of: nxt.NxtException$NotValidException: Peer sends invalid transactions: [nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 876]
nxt.NxtException$NotValidException: Peer sends invalid transactions: [nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 876]
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:637)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Title: Re: NRS v1.7.4
Post by: lurker10 on January 23, 2016, 09:14:35 am
Amazing how innovations roll into Nxt like clockwork while the Bitcoin community argues ad nauseam about a tiny change.
Title: Re: NRS v1.7.4
Post by: Riker on January 23, 2016, 09:21:20 am
How did the hard fork go?
- It seems everything is going well.
The only unusual thing is that my Nxt server produces a lot of such messages:
Code: [Select]
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"6aa444e976c56e0a60919c4e6c02a85203cc46a661715c0342f6d26b5fd1aa0effbe1401e28b81ac299e493c2bf79cc55ce3c34f3ece8b5f0f6be66cef7f5039","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"Vy0qwm9swZTj0bvBV3FCrlG4wm9xKmGuwszcy9hPk+C219Se9q36QMb8BFATu9mlnTlx1Cr\/N13BNAP97BsduZfd9RsHGCAYYiJALTdfM9okwv10zZ1RmcXKf4zFkkzEx59zZGncVlCXJZgGLu03XnH\/Blqcy4Desp+\/gCfIMcBOIul1MNpaKfbBgyzRyk6luVNVwkzfzso7Q0979STBZ0qE0wkasrgU9AtdCvGM1\/O4rIvVKPVfEawz5U25hgM0ScAf0\/6A8A9res1pSWnCVa5LFnfKTAtnVt34\/O5DRajDIsam7jgcNQRUTG5wPyMtV3NyPsccmNisFW4clWUws1vX\/ihBzA1rFicg++O4pl8bgdl80ue5cCM88iJ9MSz+cLOEDPf3jWw3Cr+BLu8cOPmhBrczPWKf\/ZcUcoHwuZ4olQHkP7CBRwdBcdXaleVAj54huzCNEjzd2xXhtOR9GtJ5QPHxNLRkEUgcLn6CujLQ5c1+4fSUSa3YYGYTyrFPhVSyUFRiYh7GvGReje3b+umhetJuKz1YlCalFHbAuQLaLR6d3sNAGHwL0CyAs2AgF0YySqmt16uSr0cNS5XWCuKK+dl0Y+1DWnLXJomhMBiJPhSKIpD2cfVfCPM0ksx3QxP\/JcxhtgSZcz9rRzfi7JOUJGNNLqDPMZWJHr\/0pc\/ksUpNSm++0OYho+21PjhCGgXIDmdxjTXg3A0ZSsFzNiYVrC\/v+TIT05zeD1ypoYrjB\/+lZqNADZ314+sOsJhK8jLnW6cXvozXXG0x8b3kas9ZfQTuezvR9oAYKOvafC+Pdw1WG7KttvT+EDSGEW+eer2jzK9CoxdO\/GWUrtHCeg=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68232596}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"71f17fc10e025d9ebf64be9b1695f780ed6a2ad722e8d71057a6f098d50c0d06682bb6b4ab11fb924a6947e1c95736e4db95c2c485ae3f41ba126fc7e02c8a26","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"oabbagI846wafnY\/1iKlG98xAysON2EKHuAHJcssVIvT3oHOM0E24tZpjxDLNqVDUSke7FFI1juibQ6HO+82KLzB8QcMTDCs9JQT0HZOpvY60r79qqfop1IuKKWDxygS+uoSBERQq9aPYFmDaor4fMLlMAWWQm+kDzLoCy3XwItooo1vrBqlQ23i+YP8yzsdCB4mY0xu7SDu51DGabAYnTx4KibOntXUWwQ2KnvkFOZVxGQsS6cAD+WLVAtqhguaMf3u9QVqcyyJbDO1zem7Hkfmj9lshmDaTMD6NVDv4XRKfD9sqVm9WU9eumkhRRyMtL7p8u\/1hcYxTqCZzSpAp\/kZqIk+Bjm1J09lJmAg+3eq4FoSyip6KelvhxnaRYvOhAuYEgHEKxvBW3hI\/OJfAs6M2N4mMW3xyJj1Hu\/cfUtvkc4M0tKw87rO0utMquxj+0\/FuxT8KJTKbH4kO+cYL2jm9DqBMweGiZZms3No\/Lrn3BNryGB69YynW1HPuoO19msbiCkSok7Rzk5Op5hd6WTusgLThvtkD8JvagGw3q4CLkf5YVZxSQKNB55D7uwT\/QQU1ju9dkkhl\/qSDMK\/dMTaRwEAM\/Tw1Ytqu\/nEnqMTPetCHFjNEfxPJi9NKigrGUM5+1dJa8VPXznCgpxCSsIIh6a7MDvMrXoHN91Ctbcw\/YLqUA5o596Z+u\/75LWwjgkQJSV\/Vv8wUsLOhBXo243FJcKr2LEWDuNmekYB1mBjxWLyXFgvrAFzZxFrtxzIMSaQPhshoRV8hO\/vd4oz6cWBlMU+YnQs9ZzTjghptk17mOc04khq1rQ\/GggOR+te8DMX5TCLSLXrvBI\/CO+SGA=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68232833}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
....................
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"33c95b2980075edcfb4e1244cebcca3c5c29ee57da077bb72fa3608caafdd707d210ea08d847ed1f42d7073493e67bd16f60881f99f1f6b4a91643e5daaa300b","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"1futgRzpyUwgwZ\/PTXl7m0x0woWowHLDZeD87Zl\/n6VYb4AhOGUvkepQwisY8cMXX+ouWniYCAyoxtq9b4YwcjDUzbBcuiLgmh32nOAc5BmAq04ZrPlSn6cBNp5pr9B11Qm5NXmBuPlwBPL0OyUFBpYVtFb8usdw8flXXyLAoi0KG1DRvHDbwI7kIDl1so4zkKP74mX3fsoAw2GERiq96zgkMfLcSJufVhksze8b1Bp4CXkQaAag15qiQ\/d+3rONVZPIAGY0Iz\/OlQjVX1N3BPjiRazkqt6xlbDuHM73FWTHRoZIuBJVBxxhTn8zcwju\/oehBhbhuyw01TofuKTqx9jbV1c0t6yWIieZSbJRwfb8jgpgxqa0C0epT35DzDQHK1uBbw8t1IqJzvn4ra1rZf1\/viQ4gqa5tjetcEV6XWsPpmcWFhXvEyb6B4iCaNaflTlFmMZEXkeKXTJ0whsZnSdgYL3LGiLuXxb5qINP+Pb2Tc57rxjbUYbgRQuMGI6vQIJQjTXiC4zpUY+A3ws\/+fnyDLg8qHq419+cMxfG+1ZEw3qpqgq8xZegqRwK7UjairO5hOiC6E4qL7g\/mpNPaVTEKYL3QzYAVEYT3o4rmDbtnwELNJihABvx2oWVPPZoU1RhjV2CzFS6kzSmhkKmOKYxX0R1omyOxylGEgh++KkTExiJg9l2tb5BAiKXUQCMJ\/iOnTCMUBXR08ImxcNI99FJmAte+4MQ32QFFeVJrnXKvXgqLCtjY6xA6EVM\/8FGD04V4RCJzRvPIL26FEW2YUceNF1V+BS4ZiEZKH+g28usfvoY1gWgypH1tufEwu+vJyz\/h8Fu6HMa7AQkEOiZoA=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68233388}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"fab4232c37fe7ba4f8163c669b2c26ec8e90ec0c5e9cc94ebd15b84049a255011a99e25a9dcceb025175d3c52f334403a50fc02ea9eb2321edc0afe908cd359b","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"AVba0DlJaIhqa3Fl4R7RGOJJrcN2KIhqup+sVT93Dq83ytVgm9wuamJbYWo2qImFCvr\/XwDY0SKdBGh+fTGhLB7yI26JP7v714y1HbRyIHCoiM7tbxJAL3t85MakrMSKuJHbLYzdGEpjCq\/OquGCR9\/727KSomeRLU9CH9rEkMLa82+81tZRr7MOPNLlM2xqGecHgFP7RvdEPUiuOjMjwvKbrLAWdXTxqswWLGvtBzeYMjlQqIvc9ypLt9yIC8X7cjq0HR22IjFVh3LhBi8V94R4ro6o0IN9jzFtE9GQhsYETSMCLMD1UfjjEKZ7\/jwyAvgh1GJVSgVnGp\/as+Pu6xDkhW8PI7yOJq6kUSPrgav2ZtQSCsPA7xyJFhrclSDD+iTxTNhy17ZHjYANYUTSCZSIn4NrCU\/8AoX2FCQ9DJuVNnFBJOS5qTScPS3hBsz4xvRJGO1fZeWwUDFVG\/KDYJLucwVmy6fm\/gSSqHXTfwjjjvuFunFe7RTxB+0M\/pYs\/h3WqzHMgWDa12VcbJhzNN4e6raxFqmw6gsJdQQUrUQhCaswVtej3gfvYbDh2YHa9pE19Bpt\/rmF94KuvJiJzgX0MSiNuep1NYHp6m+VmbkCjF2etOckLyU8\/isWlvMcwfEsyDYWKpJAx8S30VOoETPZXCT3pIvjqm2QEWdi3t2LyZNpob\/2+umbhG8cf+qSM9d+kJyyWgJ766kAgXNh4UEKdWaUwsJXat5PlkCRFJJBwCboIs8RE7RHxpWDDlUsJ3w48Hor6D5ud0GutjJ3r7U718zctjj9PVMu\/M8L5UJ3To4DilFs7qhdynPJ8MQjsRXZSWymvgdjfFyOG1Ei2Q=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68232991}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"f0ce16cc57ff13e3c47228db2de40dcde0bcf33e8b7cbf79ae375a393e54fa039d575a659e7d37e5d6ceac500f65621bdab18b3f9fb9cec04502eec492560f62","feeNQT":400000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"wHGetf7WrxrxbrMa4z+32wBNeRBOy5kDLOrskFz3cDiVeskF3R6DZq1+XiAblXJAQkbbRRpXaRhrh7DTsuU9IXVZzbOXpTObiBTxez9D7Xd1xPidtg\/sNIKJA4FnTCmqMXV0FFDgkNMYmQqSayPT8YwY+0BlgOieeXKATy+dA91pXYvr6v0\/KWqztUjwnDAT1W\/eHTi0SaN3z5DcvpJhKzSrk8MC9MNejOu\/lJyUd6qZWiomStcJOKFLrRUs7azCqxSIQEWiuAHUql3IfRA4U2pf1S0Vexrc3BFLUQ5WklbHnofFY4Hikcej1hyrDfvGfaKz1TBv9OAw7BISmO0qUd6jcq+F3wwQRAu2mHEv9ygvwmzHZnF5NNR18f421nwRrf91wtscuNuFmP1fwuT8FJgUzICAOESocczEOz5mkKBkmQNgPKf5QDqVwLG9c3goTd9vaRZU7dhf9oVzFskfxgFf6scPyoqkU7xWHMco\/IbWb9DAlEGodRxi1b4qX1c5e4IHv5EKIW5mlaZNVClHqEda88Sxz5trSjZYeTAUMdWNrVj0tFWiLShhYceEgYK\/3zhevKMdrM78WsyZVMwByvd9XGgpYoJlIOz5w00rid8F2AOmXSrvU\/KoyeTCIq\/RrcCLBSTPZa\/zKRIPMpJskYLywtL7hWgcSBnuwQqS8d0LmGsKTs1ySlg3zVmQIxKeCQM7JcxqKSBFK3PJWFwaxpJV0HTfvLzWSmzMOFvOMc2MEiXi++VX0dOIjaOUIaSWIiOC8AIPPQtSKCvXZnfCSBvabu98U9qNibpBwx6Q2S7IPcOe+HH+wJl\/2eVbMJ7XqL3t\/mkH+FfnoXbA0invig=="},"subtype":0,"amountNQT":0,"recipient":"1035644405997062927","ecBlockHeight":621089,"deadline":603,"timestamp":68233151}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 856
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Invalid transaction from peer: {"senderPublicKey":"c5e071ef7633698dd6597ed5ef929c5b276946041abb5ee62bc05e78d2b69648","signature":"7a502a1749010546d2aeb14a8bcb2b64548e40f3b2adc7fb5eae94cde19d5d0e5d86f1b172543532f015d58ed46bba005019326df9d54b06447d211718fb653a","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"8687524384430118913","attachment":{"version.Message":1,"version.ArbitraryMessage":0,"messageIsText":true,"message":"w3XLZbY7yt4Iu+BpnZkm8V30IC6kOHNjDRXn+bHBnG7nXrsRgUW4mnl05rTJ9JY7wsHhe4iJGZP7LMPENAZzaNuU2Nv+\/n\/TJjpF2bcYIwaaCUE46Oc\/fx57sLgHaDSKKB3hjlE5uQoywGONFrgkOnALbRN3VkBfx93tC1sUTY5OJnFLy\/nGNkgVQhIUOp0t+utRmRy77wdqo4PzL8VIK\/5cB\/TxX4Ht0mcuIn+O4hfHmVAxgqntl380oTUAERY5p61vGeGbtfkOv9Sc6yTaugoMOSNG0MSmvElfiVr2yULVlDRS3MPDGPo5fIpq0cBk8nIzslT3kUD5ThIskkEJibX356L3CGwoUcJ0oGJdm\/6Tv42tdt94g0gIwWMD0hyyYdiw6MyMUt0aZCvSHLxLGNp6RRIHCmdtP863rlXc4ZHDX8NxCNy3H0ZrcGtfz3v8BCgyxZeVf5Cm5t8HvpCkkV0bkJGqft0aGzoEOw9sc8LvtZrsi7kTnwfZ7s+itYM\/o5V1riq6a2uy88NS8I38VXHTO6+72nLfVKjW\/UZBHvP5lDyNa6zBK5yhucoYTFw5wqIn9NlsLHVz0267aasEQGXgAfvza59qu9\/+7cvK1krZshWXziuvf8\/aY\/bB95otIOiZaBqvj417+qorwQE7aLx3pE0stg8nnRT7AnS\/+z5DWS97Rv4gCYtQME5KP1JyQennRrqtGfbHIqhzgJOFjVepDEIQN1wx8TAjNQlOL0OCkAcjsne58iU56+tYSpMibE\/WOHrvutdYBhFxLfcuHiyvjbrnBZmO6VeUyht+q22HhKxYpC\/69aqCJEptGtzaNIDxE4O1I2zAz4ROZVcSQHWE\/oAbJd2ykFJUNymTceU="},"subtype":0,"amountNQT":0,"recipient":"4692641630405905408","ecBlockHeight":621089,"deadline":604,"timestamp":68231996}
nxt.NxtException$NotValidException: Invalid arbitrary message length: 876
at nxt.Appendix$Message.validate(Appendix.java:284)
at nxt.TransactionImpl.validate(TransactionImpl.java:1011)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:612)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-01-23 11:30:20 FINE: Blacklisting 92.222.65.159 because of: nxt.NxtException$NotValidException: Peer sends invalid transactions: [nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 876]
nxt.NxtException$NotValidException: Peer sends invalid transactions: [nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 856, nxt.NxtException$NotValidException: Invalid arbitrary message length: 876]
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:637)
at nxt.TransactionProcessorImpl.lambda$new$76(TransactionProcessorImpl.java:271)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Arbitrary message length is now limited to 160 bytes. According to http://www.peerexplorer.com/info?node=92.222.65.159 the node which submitted this transaction is running 1.6.2
Title: Re: NRS v1.7.4
Post by: farl4bit on January 23, 2016, 09:51:50 am
The block times look very nice!  :)

https://www.mynxt.info/blocks/

Congratulations!! Thanks developers!  :-*
Title: Re: NRS v1.7.4
Post by: alex0909 on January 23, 2016, 01:55:49 pm
Great job, a lot of improvements ! Thanks to the devs
Title: Re: NRS v1.7.4
Post by: estepario on January 24, 2016, 03:25:11 pm
Hello upgrade to 1.7.4 and I get all my asset 0
In the 1.5.15 me out well.
Update 621000 before arriving at and I came out all my assets to 0. 621000 thought it would be settled after the single, but my assets remain at 0.
Someone can help me thank you very much
My account is NXT-P3KT-WP6T-CY3U-ADX3Q
Title: Re: NRS v1.7.4
Post by: TheCoinWizard on January 24, 2016, 03:32:00 pm
Hello upgrade to 1.7.4 and I get all my asset 0
In the 1.5.15 me out well.
Update 621000 before arriving at and I came out all my assets to 0. 621000 thought it would be settled after the single, but my assets remain at 0.
Someone can help me thank you very much
My account is NXT-P3KT-WP6T-CY3U-ADX3Q
Don't worry, all your assets are still there.
https://www.mynxt.info/account/10018164897379681849 (https://www.mynxt.info/account/10018164897379681849)

You probably have the same problem as described here...
https://nxtforum.org/nxt-helpdesk/cant-find-any-assets-on-ae-or-ms-please-help!/
 (https://nxtforum.org/nxt-helpdesk/cant-find-any-assets-on-ae-or-ms-please-help!/)

care to give us the response when you hit submit on this?
http://localhost:7876/test?requestType=getBlockchainStatus (http://localhost:7876/test?requestType=getBlockchainStatus)

And also the content of your nxt.properties file?
Title: Re: NRS v1.7.4
Post by: DrCharles on January 24, 2016, 03:49:27 pm
so I definitely wasn't keeping up and missed the fork. Am I screwed?
Title: Re: NRS v1.7.4
Post by: TheCoinWizard on January 24, 2016, 03:53:45 pm
so I definitely wasn't keeping up and missed the fork. Am I screwed?
[sarcasm]Yes, all your nxt have been burned and you will be banned on all nxt sites including this forum[/sarcasm]
 :D

No, just update and I guess you should be fine.
Title: Re: NRS v1.7.4
Post by: DrCharles on January 24, 2016, 04:19:16 pm
so I definitely wasn't keeping up and missed the fork. Am I screwed?
[sarcasm]Yes, all your nxt have been burned and you will be banned on all nxt sites including this forum[/sarcasm]
 :D

No, just update and I guess you should be fine.

I just keep getting the message that I cannot connect to server.
Title: Re: NRS v1.7.4
Post by: TheCoinWizard on January 24, 2016, 04:42:13 pm
so I definitely wasn't keeping up and missed the fork. Am I screwed?
[sarcasm]Yes, all your nxt have been burned and you will be banned on all nxt sites including this forum[/sarcasm]
 :D

No, just update and I guess you should be fine.
I just keep getting the message that I cannot connect to server.
You mean that after you updated you could no longer connect to any peers?
I suppose that all peers banned you for a day after seeing you were on a fork due to not updating in time.
Maybe just wait till tomorrow and try again?
Title: Re: NRS v1.7.4
Post by: abctc on January 24, 2016, 05:31:15 pm
This would benefit people that don't want to take the 'expert' approach and install NRS.
- and who would install full nodes (and open API-port to such parasites)?
Title: Re: NRS v1.7.4
Post by: TheCoinWizard on January 24, 2016, 05:33:59 pm
This would benefit people that don't want to take the 'expert' approach and install NRS.
- and who would install full nodes (and open API-port to such parasites)?
forgers? Or whales? Or people that run full nodes as they don't thrust 3rd parties? Or the same guys running blockexplorers for the "info-parasites" :)
Since when are basic users or noobs parasites ???
Title: Re: NRS v1.7.4
Post by: Jean-Luc on January 24, 2016, 05:38:44 pm
I just keep getting the message that I cannot connect to server.
If you are getting this message in the browser, it probably just means your server hasn't started yet, because the database upgrade from 1.6 or 1.5 to 1.7 takes long time, up to a few hours depending on your hardware. Just wait, and you can look at the logfile to check what the server is doing, in logs/nxt.log.
Title: Re: NRS v1.7.4
Post by: TheCoinWizard on January 24, 2016, 05:44:30 pm
I just keep getting the message that I cannot connect to server.
If you are getting this message in the browser, it probably just means your server hasn't started yet, because the database upgrade from 1.6 or 1.5 to 1.7 takes long time, up to a few hours depending on your hardware. Just wait, and you can look at the logfile to check what the server is doing, in logs/nxt.log.
Nice, that sounds logical  :)

Can you figure this one out, please?
https://nxtforum.org/nxt-helpdesk/cant-find-any-assets-on-ae-or-ms-please-help!/msg207073/#msg207073
Title: Re: NRS v1.7.4
Post by: Brangdon on January 24, 2016, 06:53:54 pm
I just keep getting the message that I cannot connect to server.
If you are getting this message in the browser, it probably just means your server hasn't started yet, because the database upgrade from 1.6 or 1.5 to 1.7 takes long time, up to a few hours depending on your hardware. Just wait, and you can look at the logfile to check what the server is doing, in logs/nxt.log.
It would be nice if the server started immediately, and the database upgrade happened in parallel. The user experience could be similar to when the block chain is being downloaded.
Title: Re: NRS v1.7.4
Post by: bgcaffe on January 24, 2016, 08:12:13 pm
Hi!

Can someone explain how todo a dividend payment with the new client 1.7.4. I used to use the Supernet client but I am not sure if there is an updated one that workswith 1.7.4 with the dividend payments.

Is it built into 1.7.4 or do you have to download and install a plugin?
Title: Re: NRS v1.7.4
Post by: Tosch110 on January 24, 2016, 08:13:06 pm
Hi!

Can someone explain how todo a dividend payment with the new client 1.7.4. I used to use the Supernet client but I am not sure if there is an updated one that workswith 1.7.4 with the dividend payments.

Is it built into 1.7.4 or do you have to download and install a plugin?

Hi bgcaffe, the SuperNET-Lite module is not fixed. But testdruif has worked out the thing as a plugin:

https://nxtforum.org/nxt-plugins/(plugin)-dividend-payout-plugin-(via-normal-transactions)-for-nrs/
Title: Re: NRS v1.7.4
Post by: Riker on January 24, 2016, 08:20:19 pm
Hi!

Can someone explain how todo a dividend payment with the new client 1.7.4. I used to use the Supernet client but I am not sure if there is an updated one that workswith 1.7.4 with the dividend payments.

Is it built into 1.7.4 or do you have to download and install a plugin?

There is a "dividends payments" link below the header of the asset exchange page in the standard client wallet. This link exists since release 1.4
From the changelog:
"Asset issuers can make a dividend payment to all asset holders with a single transaction. Required parameters are the blockchain height at which asset holders shares will be counted (must be less than 1440 blocks in the past), and the amount to be paid per share."
Title: Re: NRS v1.7.4
Post by: bgcaffe on January 24, 2016, 08:26:36 pm
Ahhh thanks found the link, not very evident but now that I know where it is I will use that rather than the plugin.

Thanks, sending you a tip :)

Hi!

Can someone explain how todo a dividend payment with the new client 1.7.4. I used to use the Supernet client but I am not sure if there is an updated one that workswith 1.7.4 with the dividend payments.

Is it built into 1.7.4 or do you have to download and install a plugin?

There is a "dividends payments" link below the header of the asset exchange page in the standard client wallet. This link exists since release 1.4
From the changelog:
"Asset issuers can make a dividend payment to all asset holders with a single transaction. Required parameters are the blockchain height at which asset holders shares will be counted (must be less than 1440 blocks in the past), and the amount to be paid per share."
Title: Re: NRS v1.7.4
Post by: forkedchain on January 25, 2016, 01:58:05 am
theres a very odd bug Ive noticed since moving to 1.5.15 directly to 1.7.4.  I noticed it because since moving, my leased forging pool's accounting software chokes and dies a lot.  not sure when it was introduced since ive been on 1.5.15 for some time.  fairly frequently, when doing getBlock API, the latest 5 or so blocks in the blockchain do not have any nxtBlock field in the returned JSON.  Here is an example:

Quote
{"previousBlockHash":"fe77fab8805b5a2c3cb1ad63bf2bd94f16bbf2ef617cec780548d9a650832cf4","payloadLength":0,"totalAmountNQT":"0","generationSignature":"d12ded5340eed101931fd757298d9353df5b0a9c9f8637c2b6784f74a48e97f2","generator":"1480789515119544614","generatorPublicKey":"65a79960f8736afba25aba6a1b04d62fd88bce1beb721ae0bcd7ae76c6dfa061","baseTarget":"608382683","payloadHash":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","generatorRS":"NXT-7LB8-8ZPX-3YR9-3L85B","requestProcessingTime":0,"numberOfTransactions":0,"blockSignature":"105fb0954be35ffb32226fa5bc3cffb5b44ad64000348bd32e3985aacf547009e9bc52070a9d649fe4176205b310026c68b84f798f53bacc0dabc9dae0398348","transactions":[],"version":3,"totalFeeNQT":"0","previousBlock":"3195967493990152190","cumulativeDifficulty":"25848719705757307","block":"15067109432641433242","height":623800,"timestamp":68392099}

it doesnt happen all the time, but when it does, its easy to notice.  its easy to duplicate, it happens frequently wnough that just 5 minutes will show this.

it happens on both win8PC and on linux; it seems much more severe on the win PC
Title: Re: NRS v1.7.4
Post by: qq2536007339 on January 25, 2016, 04:00:28 am
The max lease period is now 65535 blocks,can you change default value to that,thank you!
Title: Re: NRS v1.7.4
Post by: Jean-Luc on January 25, 2016, 11:58:06 am
The missing nextBlock bug is fixed in 1.7.5.
Title: Re: NRS v1.7.4
Post by: Twarden on February 10, 2016, 05:06:10 pm
When I was upgrading NRS from 1.5.15 to 1.7.5, an error stated that the hashes do not match and to not proceed.  I then noticed that the error stated was supposed to upgrade to version 1.7.4.  I downloaded that release and attempted to update to 1.7.4 and I was greeted with this very strange error message:

https://imgur.com/QcjjTqx
Title: Re: NRS v1.7.4
Post by: Riker on February 10, 2016, 06:57:24 pm
When I was upgrading NRS from 1.5.15 to 1.7.5, an error stated that the hashes do not match and to not proceed.  I then noticed that the error stated was supposed to upgrade to version 1.7.4.  I downloaded that release and attempted to update to 1.7.4 and I was greeted with this very strange error message:

https://imgur.com/QcjjTqx
Its because you need to upgrade to 1.7.5 not to 1.7.4 please posr the exact error  you are getting with 1.7.5
Title: Re: NRS v1.7.4
Post by: Twarden on February 11, 2016, 10:14:33 pm
When I was upgrading NRS from 1.5.15 to 1.7.5, an error stated that the hashes do not match and to not proceed.  I then noticed that the error stated was supposed to upgrade to version 1.7.4.  I downloaded that release and attempted to update to 1.7.4 and I was greeted with this very strange error message:

https://imgur.com/QcjjTqx
Its because you need to upgrade to 1.7.5 not to 1.7.4 please posr the exact error  you are getting with 1.7.5

I can guarantee you that the software is asking for 1.7.4 and not 1.7.5.

NRS asks for version 1.7.4 or 1.7.3e:  http://imgur.com/34ghq8t
NRS refuses 1.7.5 for this reason:  http://imgur.com/exiwJ0f
NRS matches the hashes of 1.7.4 and refuses to upgrade:  http://imgur.com/Dd2BiQU

Suggestions for a hot-fix, please?
Title: Re: NRS v1.7.4
Post by: Riker on February 13, 2016, 08:06:36 am
When I was upgrading NRS from 1.5.15 to 1.7.5, an error stated that the hashes do not match and to not proceed.  I then noticed that the error stated was supposed to upgrade to version 1.7.4.  I downloaded that release and attempted to update to 1.7.4 and I was greeted with this very strange error message:

https://imgur.com/QcjjTqx
Its because you need to upgrade to 1.7.5 not to 1.7.4 please posr the exact error  you are getting with 1.7.5

I can guarantee you that the software is asking for 1.7.4 and not 1.7.5.

NRS asks for version 1.7.4 or 1.7.3e:  http://imgur.com/34ghq8t
NRS refuses 1.7.5 for this reason:  http://imgur.com/exiwJ0f
NRS matches the hashes of 1.7.4 and refuses to upgrade:  http://imgur.com/Dd2BiQU

Suggestions for a hot-fix, please?

The version update function relies on the NRSversionWin alias. If you have a fully updated blockchain this is the alias you should see:
NRSversionWin   1.7.5 902aba12461b0d83e19c6fc8821a5cbeaeaee8f7f975fd2189785cbdeb08b740
This alias should match the Windows installer.

Therefore I suspect that your blockchain is not up to date. Which block do you see in the UI ? The updated blockchain is currently at block 651357.
Probably what you need to do is use the /popOff API to pop all blocks up to height 621000 then let the blockchain update.
Once you have an up to date blockchain you would also see the correct 1.7.5 hash.
Title: Re: NRS v1.7.4
Post by: Twarden on February 13, 2016, 11:22:03 pm
Thank you for your response.  I can see that the last block is 635094 at this time so that is the reason why the error is occurring.  I installed NRS on a Ubuntu machine so that hash won't match in my case.  There seems to be an issue with the popOff command,  I am getting a response timed out error when I try to POST https://185.82.201.85:7876/nxt?requestType=popOff&numBlocks=621000 can you please confirm that the api server is unresponsive?

EDIT:  This worked once I used the height option instead of numBlocks.  Will wait for the blockchain to update and I will try to upgrade again soon.
Title: Re: NRS v1.7.4
Post by: Teddy W. on March 24, 2016, 03:36:36 am
Many thanks to my request for information  ;D ;D ;D ;D ;D ;D
Title: Re: NRS v1.7.4
Post by: altsheets on April 02, 2016, 12:39:27 pm
Update about block times:

Code: [Select]
   ago    height    timestamp    seconds  seconds per block
------  --------  -----------  ---------  -------------------
     0    721965     74306107          0
     1    721964     74306093         14  14.0
     3    721962     74306045         62  20.7
    10    721955     74305422        685  68.5
    31    721934     74304515       1592  51.4
   100    721865     74299957       6150  61.5
   316    721649     74286868      19239  60.9
  1000    720965     74246059      60048  60.0
  3162    718803     74117234     188873  59.7
 10000    711965     73707756     598351  59.8
 31622    690343     72411570    1894537  59.9
100000    621965     68282370    6023737  60.2
200000    521965     57049514   17256593  86.3
300000    421965     45775263   28530844  95.1
400000    321965     34748946   39557161  98.9
500000    221965     24085192   50220915  100.4
600000    121965     13181331   61124776  101.9
700000     21965      2404926   71901181  102.7
800000         0            0   74306107  102.9

Looks like the 60 seconds has become really reliable, on average.

 ;)

EDIT: tweeted (https://twitter.com/altsheets/status/716247003785732096)



Block times:

(https://raw.githubusercontent.com/altsheets/chaincountdown/master/tools/blocktimes-NXT.png) (https://raw.githubusercontent.com/altsheets/chaincountdown/master/tools/blocktimes-NXT.png)

Not important. I have only had a look at them, because I fine-tuned
my ChainCountDown (CCD) image server
     (nxtforum (https://nxtforum.org/nxt-projects/chaincountdown-blockchain-aware-countdown-timer-with-image-server/), bitcointalk (https://bitcointalk.org/index.php?topic=1147294.0), github (https://github.com/altsheets/chaincountdown), live server (http://altsheets.ddns.net:8888/)).

...

BUT these CCD images ... might be interesting for you ...
perhaps you put one of these images into a prominent place,
to remind people to upgrade to 1.7.4 before block 621000 ?

http://altsheets.ddns.net:8888/nxt/621000.png?heading=NXT%20hardfork%20@%20621000&fontsize=35&headingfontsize=42&bgcolor=F1F2F4&color=476C8E&font=Pecita
   or 
http://altsheets.ddns.net:8888/nxt/621000.png?heading=Upgrade%20before%20NXT%20hardfork!&headingfontsize=28
   or   
(http://altsheets.ddns.net:8888/nxt/621000.png?heading=Upgrade%20your%20NXT&headingfontsize=40&color=ffffff&bgcolor=476C8E)
   or design your own!


The images are rendered on the fly.

You can change their size, colour, and fonts easily.
See the examples and parameters (http://altsheets.ddns.net:8888/#examples).


If/As you expect heavy traffic, please run the server yourself. Very easy.
With docker, it is actually a one-liner only, to get it running (https://github.com/altsheets/chaincountdown#docker)!

ChainCountDown (CCD) image server: threads nxtforum (https://nxtforum.org/nxt-projects/chaincountdown-blockchain-aware-countdown-timer-with-image-server/), bitcointalk (https://bitcointalk.org/index.php?topic=1147294.0), github (https://github.com/altsheets/chaincountdown), live server (http://altsheets.ddns.net:8888/).

If you like this, show it:   NXT-CMKU-ZQYK-V6CD-9UHF4   - thanks.


Happy New Year, everybody

 ;)
Title: Re: NRS v1.7.4
Post by: lurker10 on May 28, 2017, 02:13:21 pm
windows XP dont work nrs v1.7.4

Do not use Windows XP.

Use https://nxtforum.org/nrs-releases/nrs-v1-11-5/
1.7.4 is many hard forks behind, it's for Nrs software museum.
Title: Re: NRS v1.7.4
Post by: VanBreuk on May 28, 2017, 04:42:57 pm
i have XP i havent anymore ???

Microsoft support for Windows XP ended over three years ago. It has phased out for many applications and it is not secure to use. If you want to run cryptocurrency clients like Nxt, update to a supported, recent OS version.

And as lurker10 said, Nxt Client 1.7.4 is very old and would not run anyways in the current Nxt network. Get the latest, 1.11.5 (https://nxtforum.org/nrs-releases/nrs-v1-11-5/).
elective-stereophonic
elective-stereophonic
assembly
assembly