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

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: [1] 2 3 4  All

Author Topic: NRS v1.2.8  (Read 17699 times)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
NRS v1.2.8
« on: September 03, 2014, 08:57:02 pm »

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 1.2.8

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

sha256:

7d234c912b451c375b10b8ceefbd9053697532c49d4e469c7fc36294c91c591d  nxt-client-1.2.8.zip


Change log:

API changes:

The timestamp parameter in getAccountTransactionIds and getAccountTransactions
now refers to the timestamp of the block in which the transaction was included
rather than the transaction timestamp itself. Transactions are sorted in
descending order of block timestamp and transaction id, instead of transaction
timestamp. This is so that the sorting matches the order in which transactions
are processed, and because transactions with earlier timestamps may appear in
the blockchain after transactions with later timestamps have already been
processed, thus being unintentionally skipped while navigating the transactions
list by transaction timestamp.

The getAccountTransactionIds and getAccountTransactions requests now accept an
optional numberOfConfirmations parameter, which can be used to retrieve only
transactions with at least numberOfConfirmations number of confirmations.

The getBlock API now optionally accepts height instead of block parameter, to
retrieve the block at that height. If both block and height are specified,
height parameter is ignored.

The getBlock API now also accepts includeTransactions parameter, if set to
true, full transaction JSON is returned instead of only transaction ids.

There are no other changes between 1.2.7 and 1.2.8, so those who rely on the
old behavior of the above APIs can continue to use 1.2.7 for the time being.

Client GUI:

Added the option for merchants to specify a specially formatted message that
is required to be added to a payment transaction or an asset transfer.

To activate this behavior, you must set your account info description to the
following format: #merchant:[0-9]+#

This example will only accept a numeric message.

If the message should be of a particular length use this:
#merchant:[a-zA-Z0-9]{4,8}#

This format will only allow messages that have a length of 4 to 8 characters
and is alphanumeric.

Note that the regex is case sensitive.

Fixed issue with public key field not showing when using a contact in the
recipient field.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJUB2WmAAoJEFOhyXc7+e2AEUwP/1arAFOz+ZECTIeqZnT13Mp4
7pqU7abdX7xrP8h/tAxfonRaUPj202FlFQ4sWsSGlOBg4VF6uR+skFNLq9rf+R27
WkusKLA7mHvXfqWlUyJhKeVHPeYuLkBQmuYWHy/K391LhJeetcEGNLlDAjFqlyVa
+ulGqFldaC1mcMSZpBBFWsiefg004t6Rr5sY4SWjzausTdNYn1fOyHoZJhqHoLSX
3Jm+//tGGwe6De6T2XB272S6Xu1F0g6jq4+9baI32n4sXWub7nrgcMqabMjx5dnF
5GSjGcGZfO177QpOlP0/0BAvce+HGXNoVpsbORU2EYWtzDlERBmUnH1WZO9OWA22
3idSbxaSbnPanlfwWqa7mMRt9+RuF2WCbn2Yf0WM1CbfKcGTJ0GXrhyTWxJ6Yuux
uVvQh+ZVictisMo/sgOItxfYmqY/I1SKxYQtxHKL2PeLuZaPC5bQ2HUKXGJymDz2
zZfLRiN6tIWbH3YE1U00KMuSx+8XsrUgqDPl/LM4k/AGpE/87SDyJ2yEgMOIukqM
thdrQs0G7cUdEkPrtkMPZF+oHJsdjUJlJMUFKsv5zdnC6yc4ibbARkKjgQxZ+RFe
n9ua6X+yBY3PqCgIjhxbsKFZYm2iN1JhB/DGOU/4sJY+8cqG4kECWxO5Q27zNNio
PwRu8XJkV3KMHVbun+q3
=+2o/
-----END PGP SIGNATURE-----
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

yanlap

  • Jr. Member
  • **
  • Karma: +15/-2
  • Offline Offline
  • Posts: 36
    • View Profile
Re: NRS v1.2.8
« Reply #1 on: September 04, 2014, 01:23:39 am »

Great! :)
Logged

Eadeqa

  • Hero Member
  • *****
  • Karma: +83/-68
  • Offline Offline
  • Posts: 1888
    • View Profile
Re: NRS v1.2.8
« Reply #2 on: September 04, 2014, 01:31:09 am »

Client GUI:

Added the option for merchants to specify a specially formatted message that
is required to be added to a payment transaction or an asset transfer.

To activate this behavior, you must set your account info description to the
following format: #merchant:[0-9]+#

This example will only accept a numeric message.

If the message should be of a particular length use this:
#merchant:[a-zA-Z0-9]{4,8}#

This format will only allow messages that have a length of 4 to 8 characters
and is alphanumeric.

This isn't good enough. The change should be enforced at core level. Nxt remains unusable for merchants.

 
Logged
NXT-GZYP-FMRT-FQ9K-3YQGS

msin

  • Hero Member
  • *****
  • Karma: +138/-18
  • Offline Offline
  • Posts: 1288
    • View Profile
Re: NRS v1.2.8
« Reply #3 on: September 04, 2014, 01:37:50 am »

Thanks JL
Logged

Dontclick

  • Newbie
  • *
  • Karma: +6/-7
  • Offline Offline
  • Posts: 8
    • View Profile
Re: NRS v1.2.8
« Reply #4 on: September 04, 2014, 01:59:59 am »

Thank you for all your hard work
Logged

a7594li

  • Full Member
  • ***
  • Karma: +7/-10
  • Offline Offline
  • Posts: 109
    • View Profile
    • bite01
Re: NRS v1.2.8
« Reply #5 on: September 04, 2014, 03:30:53 am »

Lower fees for the next version?
Logged
LOWER FEES TO 0.1NXT PLS (:

renat0

  • Jr. Member
  • **
  • Karma: +7/-18
  • Offline Offline
  • Posts: 76
    • View Profile
Re: NRS v1.2.8
« Reply #6 on: September 04, 2014, 03:47:22 am »

Logged
Buying Qora for 12 satoshi each / Selling Nxt for 6600 satoshi each / Exchanging my nxt with your qora at a ratio of 1 nxt = 550 qora / Send me a private message if you're interested in any of these deals

coolfish

  • Full Member
  • ***
  • Karma: +6/-0
  • Offline Offline
  • Posts: 140
    • View Profile
Re: NRS v1.2.8
« Reply #7 on: September 04, 2014, 02:06:57 pm »

Nice !!
Logged
MyNxt: 6869673164215466219

wesley

  • Hero Member
  • *****
  • Karma: +204/-3
  • Offline Offline
  • Posts: 1159
    • View Profile
Re: NRS v1.2.8
« Reply #8 on: September 04, 2014, 02:08:15 pm »

This isn't good enough. The change should be enforced at core level. Nxt remains unusable for merchants.

It will be... We try to not have too many hardforks - you know ;)
Logged

instacash

  • Full Member
  • ***
  • Karma: +10/-1
  • Offline Offline
  • Posts: 249
    • View Profile
Re: NRS v1.2.8
« Reply #9 on: September 04, 2014, 02:26:51 pm »

Thank you for all the work
Logged

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.2.8
« Reply #10 on: September 04, 2014, 05:45:04 pm »

nxt.org has NRS 1.2.5 in downloads sections. Please update to the latest version.
Logged

TheCryptoWoman

  • Ex-Staff Member
  • Hero Member
  • *****
  • Karma: +165/-26
  • Offline Offline
  • Posts: 623
    • View Profile
    • Twitter
Re: NRS v1.2.8
« Reply #11 on: September 04, 2014, 07:12:08 pm »

nxt.org has NRS 1.2.5 in downloads sections. Please update to the latest version.

The Linux / NRS version was updated shortly after the release of v1.2.8 and I'm waitng for a notice that the installers for Windows and Mac have been updated. No doubt, those are the ones you mean :)
Logged

hash

  • Jr. Member
  • **
  • Karma: +22/-1
  • Offline Offline
  • Posts: 90
    • View Profile
Re: NRS v1.2.8
« Reply #12 on: September 04, 2014, 09:40:15 pm »

Is the beginning and the end of string is implied or we can/should use ^$ ?

Thanks.

johnna

  • Jr. Member
  • **
  • Karma: +8/-3
  • Offline Offline
  • Posts: 78
    • View Profile
Re: NRS v1.2.8
« Reply #13 on: September 05, 2014, 10:31:11 pm »

Is it me or this version, 1.2.8, doesn't connect to nodes with version below 1.2.5?
Logged

Squeaker

  • Jr. Member
  • **
  • Karma: +1/-0
  • Offline Offline
  • Posts: 30
    • View Profile
Re: NRS v1.2.8
« Reply #14 on: September 06, 2014, 04:28:22 am »

No reason to stay connected to forked nodes...

=squeak=
Logged

rriky92

  • Jr. Member
  • **
  • Karma: +9/-1
  • Offline Offline
  • Posts: 84
    • View Profile
Re: NRS v1.2.8
« Reply #15 on: September 06, 2014, 10:04:52 am »

My node always rescan blockchain with this version, why?
Logged
iOS & Website Developer - iNxt - NXT-8T4Z-6NRS-PBGB-6UWU9

hash

  • Jr. Member
  • **
  • Karma: +22/-1
  • Offline Offline
  • Posts: 90
    • View Profile
Re: NRS v1.2.8
« Reply #16 on: September 06, 2014, 10:44:30 am »

UI bug:
If an alias used instead of an account number in sending NXT (or assets) dialog, the following warning appears:

Code: [Select]
The alias links to account NXT-XXXX-XXXX-XXXX-XXXXX. The recipient account is an unknown account,
meaning it has never had an incoming or outgoing transaction. To submit this request you must supply
the recipient public key also. The alias was last adjusted on [...].

Which does not make any sense of course: the fact that the account has an alias means there was at least one incoming and one outgoing transaction.

The transaction sending works fine though, without a public key, so it's a pure UI problem.

Thanks.
« Last Edit: September 06, 2014, 08:59:22 pm by hash »
Logged

johnna

  • Jr. Member
  • **
  • Karma: +8/-3
  • Offline Offline
  • Posts: 78
    • View Profile
Re: NRS v1.2.8
« Reply #17 on: September 06, 2014, 10:59:39 am »

No reason to stay connected to forked nodes...

=squeak=

Still, I am currently connected to some nodes with “NRS 1.2.5b” and “NRS-R 1.2.5f”.
And even strange, the node I add in “nxt.wellKnownPeers” are not displayed in the NRS client, section "Peers".

But what about the API "/nxt?requestType=getPeers"? I have 1423 entries of IP address, but this is not current nodes, right?
« Last Edit: September 06, 2014, 11:33:40 am by johnna »
Logged

Squeaker

  • Jr. Member
  • **
  • Karma: +1/-0
  • Offline Offline
  • Posts: 30
    • View Profile
Re: NRS v1.2.8
« Reply #18 on: September 06, 2014, 11:23:00 am »

If I remember the announcements right, 1.2.5 is supposed to follow the new fork, while versions before would not.

Admittedly, I have not been keeping current on the specifics of which versions come in at various stages of development, but when I set my client up, I believe that this is what I had read, and that I had to update very soon to 1.2.5 at least, by a block that was expected to be reached within a few days.

If I remember that correctly, this could explain why you are not staying connected to previous versions anymore, if the client is programmed to drop misbehaving peers... which I assume it is.

=squeak=
Logged

Jimmy2011

  • Sr. Member
  • ****
  • Karma: +24/-19
  • Offline Offline
  • Posts: 329
    • View Profile
Re: NRS v1.2.8
« Reply #19 on: September 06, 2014, 12:23:28 pm »


A problem on Nxt shut down occasionally.

The computer (linux system) was shut down by accident the other day, and I can't start Nxt(1.2.6) now with the following error:

Exception in thread "Thread-0" java.lang.NullPointerException
        at nxt.util.ThreadPool.shutdownExecutor(ThreadPool.java:70)
        at nxt.util.ThreadPool.shutdown(ThreadPool.java:64)
        at nxt.Nxt.shutdown(Nxt.java:145)
        at nxt.Nxt$1.run(Nxt.java:125)
        at java.lang.Thread.run(Thread.java:744)

So what should I do to repair the database? The database file nxt.h2.db is 1.5G now.

Logged
NXT-LX5G-L63N-ST8S-9LVZY
Pages: [1] 2 3 4  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly