elective-stereophonic
elective-stereophonic
NRS v1.7.3e singapore
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Pages: [1] 2 3  All

Author Topic: NRS v1.7.3e  (Read 19754 times)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
NRS v1.7.3e
« on: December 20, 2015, 07:08:58 pm »

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.3e

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

sha256:

07be795bb6b64df7dbe73072544ddb9236c57d827147a7eb3a98e34929698a65  nxt-client-1.7.3e.zip

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

sha256:

ef6e145e4ba631238c8bef054e94af6d85e2be983756815fcc9f3e86b09de92b  nxt-client-1.7.3e.jar

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

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


This is an experimental release for testing only. Source code is not provided.


Change log:

This is an experimental bugfix release. It is a mandatory update for testnet
nodes.

Added retrievePrunedTransaction API. This API can be used to force retrieval
of the prunable data for a given transaction, even if past the configured
nxt.maxPrunableLifetime. Using this API to retrieve pruned data however does
not increase its lifetime, i.e. at the next scheduled table trimming the data
will be pruned again if expired. This API queries all currently available
archival peers, until the missing data is found, therefore it can take some
time to complete, and can also return no results if there are no such peers
online, or none of them has the requested data. Consistent with the behavior
of getTransaction and related API, the returned transaction JSON will not have
the prunable parts included if they have already expired and
nxt.includeExpiredPrunable=false (default is true), but if those parts have
been successfully restored, they can be requested using the more specific APIs
such as getPrunableMessage, getTaggedData, etc.

The getPrunableMessage, getTaggedData, and downloadTaggedData APIs now support
optional "retrieve" parameter, default false. If the corresponding data has
been pruned and retrieve is true, an attempt will be made to retrieve the data
from archival peers, as if using the retrievePrunedTransaction API.

Added getReferencingTransactions API, returning the transactions referencing a
given transaction id.

Added getLinkedPhasedTransactions API, returning the phased transactions with
by-transaction voting model for a given linkedFullHash, regardless of their
phasing status (pending, approved or rejected). Since the corresponding table
is trimmed after finish height however, the result will not include those
transactions that finished before the last trimming height.

Increased maximum leasing period to 65535 blocks, to take effect after the
hard fork.

Shuffling UI improvements.

Added UI for the Tagged Data feature, now known as Data Cloud.

The Exchange Booth UI has been improved. The user must only enter the number
of currency units to be bought or sold, and the server determines the maximum
or minimum rate required in order to obtain or sell this amount, based on the
current market offers available. This avoids the creation of exchange requests
that cannot be filled, and eliminates the need for manually calculating the
required exchange rate.

To prevent clickjacking exploits, a new http header is now added by default to
all http API responses, X-FRAME-OPTIONS: SAMEORIGIN. This can be turned off by
setting nxt.apiFrameOptionsSameOrigin=false in nxt.properties.


Incompatible changes:

The taggedData field in the getAllTaggedData API response has been renamed to
data, for consistency with the other get*TaggedData APIs.

The behaviour of the currencyBuy API has been fixed, to exchange no more than
the number of currency units specified in the units parameter. Currently, the
total amount of NXT as calculated from rate * units is exchanged for currency,
even if this results in purchasing more than the number of units requested,
which is non intuitive and not consistent with the way currencySell works.
This change will take effect after the hard fork.


Updated Jetty to version 9.3.6 and slf4j to version 1.7.13. Make sure to
delete the old lib folder if unpacking over a previous installation.

This release will do a blockchain rescan on testnet and may delete blocks
after certain height, to resolve testnet forks.


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

iQIcBAEBCgAGBQJWdvZCAAoJENqvaxkWiP4Z+acQAL/1OPMFGbmUUkLeFlBbzKVP
M+xbtEel3RjZlnN1Q5ca1SCrNsEUgigDYY/LxRre7QdqYQ/rpkzbQB3TYx39hHSO
/G3dXt7aLJ/4vd8QI6r6/AtO5FW1tdCXW7ag8+hqb1g0tBoWDf+2FyLaSggjjExN
tznnhVlCM2HooqMKUNv9nF/Y8cuejN69Ph5IpixLzmZN3mxynZc73KhZA5bGQRCp
kRvgy9eD4aTlGEBzBy7PuIVASFQZfRuFI8Caa8Yjj9hV7uZAxt5kSYIjappgKeMV
voCSgCuSQknzleyuBdjrS295KyPygasGKQz99goYKDWcRf7DXNL+fD0NIOtgDyXS
SwK5cMgUQFckSGXfv2QouSTlDz1U5m9FBhPdGFDDY3ysj+p0Cmo+KsvusK/zlWGE
8+36UjWev1EGpH0oAcKekxYHxpdGHZxGRqTSdxNIt9ZKH8tr2bGRU2Aps+EnVGCU
8PDkB5320SU9Q+f5v1LLmL9UUVcZ26CGC0tg/n/Gs5AVjdkWWlbY2HYRNHaNxDi0
etaGgw5nIOSNizt+3scLvvqzsyQ2f8/p0VggkWnDs6aZpTYjneR1+N73rd3CplEP
uLOjb6Msv0k9nKwNj1nz3NjwaBuMqL/zhchT+TwxZTunZ57Eu/H9qnuFEJzX5eXa
eRc3l21PA3TuGzLNLCKx
=HrOr
-----END PGP SIGNATURE-----
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

yassin54

  • Hero Member
  • *****
  • Karma: +240/-14
  • Offline Offline
  • Posts: 2498
  • I am Homer, Sorry my english is Bad!!
    • View Profile
Re: NRS v1.7.3e
« Reply #1 on: December 20, 2015, 07:38:53 pm »

Thank you!!  ;)

abctc

  • Hero Member
  • *****
  • Karma: +148/-13
  • Offline Offline
  • Posts: 1396
    • View Profile
Re: NRS v1.7.3e
« Reply #2 on: December 20, 2015, 09:04:51 pm »

Great!
Logged
Welcome to the Nxt generation of crypto!   Magis quam Moneta (More than a Coin)
"Do not worry, it is an attack" (c) Jean-Luc

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1794
    • View Profile
Re: NRS v1.7.3e
« Reply #3 on: December 20, 2015, 09:59:50 pm »

Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

TheCoinWizard

  • Hero Member
  • *****
  • Karma: +97/-55
  • Offline Offline
  • Posts: 614
  • Learn by questioning everything!
    • View Profile
Re: NRS v1.7.3e
« Reply #4 on: December 20, 2015, 10:34:52 pm »

Sweet, I will give it a try...
Logged
Welcome to the After Nxt Calendar era...
Which started in the year 222 of the French Republic, Frost month, on the fifth day of the first week, better known as the 2456621th Julian day,
even better known as 24 November 2013 at 12:00:00 UTC.

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: NRS v1.7.3e
« Reply #5 on: December 21, 2015, 01:10:29 am »

No wonder I can't connect to testnet last night.Already update,thank you!
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: NRS v1.7.3e
« Reply #6 on: December 21, 2015, 04:00:50 am »

o,good works. :)
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1763
    • View Profile
Re: NRS v1.7.3e
« Reply #7 on: December 21, 2015, 09:04:38 am »

Data Cloud feature is looking nice...
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.3e
« Reply #8 on: December 21, 2015, 10:33:15 am »

The Data Cloud feature is already fully usable on main net with 1.7.3e, as it doesn't depend on hard fork changes. The improved exchange booth UI also is, except for the Buy Currency side where before the hard fork it will only work for requests matching a single offer.

We expect this to be the last experimental release, and to have 1.7.4 stable before end of the year. Now is the last chance to find and report critical bugs.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

RocketBunny

  • Jr. Member
  • **
  • Karma: +5/-2
  • Offline Offline
  • Posts: 65
  • Big engines fan
    • View Profile
    • Stocks.exchange - where real business meet with crypto world
Re: NRS v1.7.3e
« Reply #9 on: December 21, 2015, 11:24:47 am »

What data cloud max size limit?
Logged
NXT: Vadym
https://stocks.exchange
mailto: vk@stocks.exchange

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1794
    • View Profile
Re: NRS v1.7.3e
« Reply #10 on: December 21, 2015, 11:47:04 am »

What data cloud max size limit?

The file size limit is 42K per transaction.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: NRS v1.7.3e
« Reply #11 on: December 21, 2015, 11:52:11 am »

Where is Account Control in the UI? I've tried reloading, and I can see Account Properties.
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1794
    • View Profile
Re: NRS v1.7.3e
« Reply #12 on: December 21, 2015, 12:07:47 pm »

Where is Account Control in the UI? I've tried reloading, and I can see Account Properties.

It's in the account details modal. From the dashboard click on the "account balance" box (top/left) on the resulting "account details" modal click the "account control" tab.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: NRS v1.7.3e
« Reply #13 on: December 21, 2015, 01:04:53 pm »

Where is Account Control in the UI? I've tried reloading, and I can see Account Properties.

It's in the account details modal. From the dashboard click on the "account balance" box (top/left) on the resulting "account details" modal click the "account control" tab.
Thanks. That's well hidden. It might be an idea to combine the account balance/details with the Details button that is underneath the main account number. Or something.

Currently, clicking the account number does nothing. Clicking the account name "Brangdon TestNet" sets Account Info (ie name and description). Clicking Details gives historical info (transactions and ledger) and current state (currencies owned, etc). Clicking the balance gives another group of settings (balances, leasing, account control). There is also Account Properties underneath the Dashboard, which is something else again. This is all a bit messy and unobvious in my view. Maybe it would be better if Leasing and Account Control were together with Account Ledger, Account Properties and Approval Requests in the Dashboard section. Better organisation would make clearer what options are available to set, and the difference between "info", "details" and "properties", and which are historical, and which are current state. Or whatever, I'm not great at UI. It just really needs an overhaul at the moment. It's just growed.
Logged

TheCoinWizard

  • Hero Member
  • *****
  • Karma: +97/-55
  • Offline Offline
  • Posts: 614
  • Learn by questioning everything!
    • View Profile
Re: NRS v1.7.3e
« Reply #14 on: December 21, 2015, 03:11:50 pm »

Thanks for the new experimental release.

I tried to do some shuffling, and now I may no longer switch of my pc  :P

Please join my shuffle 13704879857907371065 on the testnet



I got some questions though:

Why can I not close my account after creating/joinging a shuffle?

Why is there a prefixed number of participants in a created shuffle?

Why can I not shut down my node after creating/joining a shuffle?

Why can I not shuffle to other peoples account? In other words:
Why do I need the private key of the receivers account?

What happens with shuffle joined account that must pay the 1000 fee since he closed off his node, but only have 200 nxt on his account.

Seems to me shuffling would be much better without these limitations.

keep up the good work, nxters
Logged
Welcome to the After Nxt Calendar era...
Which started in the year 222 of the French Republic, Frost month, on the fifth day of the first week, better known as the 2456621th Julian day,
even better known as 24 November 2013 at 12:00:00 UTC.

coretechs

  • Sr. Member
  • ****
  • Karma: +161/-1
  • Offline Offline
  • Posts: 436
    • View Profile
Re: NRS v1.7.3e
« Reply #15 on: December 21, 2015, 07:04:36 pm »

UI suggestions/notes:

1. rename "Deletes History" subsection of AE to "Delete History" or "Deletion History" to be more consistent with the singular form "Trade History" and "Transfer History" (they aren't Trades History or Transfers History).

2. Under Account Properties, the buttons in the upper right, "incoming" is not capitalized, but "Outgoing" and "Set" are capitalized.
« Last Edit: December 21, 2015, 07:13:30 pm by coretechs »
Logged
https://ardorportal.org - Ardor blockchain explorer | https://nxtportal.org - Nxt blockchain explorer | http://bitcoindoc.com - The Rise and Rise of Bitcoin
ARDOR-T43P-R2K9-8W79-9W2AL | NXT-WY9K-ZMTT-QQTT-3NBL7

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: NRS v1.7.3e
« Reply #16 on: December 21, 2015, 09:51:12 pm »

I'm not a dev, but I'll have a go at answering these, since no-one else has.

Why can I not close my account after creating/joinging a shuffle?
If by "close your account" you mean close the browser window, you can, provided your node keeps running the shuffler that the browser started.

Quote
Why is there a prefixed number of participants in a created shuffle?
Because the number is a trade-off that needs a human to decide. If it is too low, then the anonymity provided by shuffling is weak. For example, with three participants, if I am one of them, I have a 50:50 chance of guessing which way around the two are. So larger numbers of participants are more secure. However, if the number is too large, there may not be enough other people who want to join the shuffle, and it's more likely one of them will go offline and break the shuffle.

I suppose it could be made more flexible. We could specify a minimum number of participants, and a start block, and then have the shuffle start processing at the start block provided at least that minimum had joined. Then shuffles would not be arbitrarily limited in number, which would be more secure. Maybe that could be supported later. For now the devs have kept it simple.

Quote
Why can I not shut down my node after creating/joining a shuffle?
The protocol is quite a complex, multi-stage affair. It involves monitoring the blockchain, and several transactions being issued from your account. This is done by an automated process called a "shuffler" that runs on your node. If the node is shut down, the shuffler doesn't run, and when it's your turn to issue a transaction that won't happen, and the shuffle will fail.

Quote
Why can I not shuffle to other peoples account? In other words:
Why do I need the private key of the receivers account?
I think the devs thought it too error-prone. The danger is that naive users will reuse an account of their own, that can be linked to them somehow, which would defeat the object. Even reusing the same recipient account for shuffling more than once, A ==shuffle==> B, A ==shuffle==> B, would be vulnerable to statistical analysis which could undo the shuffling and link accounts A and B.

(However, personally I'd like to have the option to send to someone else's existing account - in effect, anonymous one-off payments. I'd also like to be able to send less than 1000 NXT, with the remainder of the deposit being returned to the participating account. Maybe this could be supported later. It's not urgent for me.)

Quote
What happens with shuffle joined account that must pay the 1000 fee since he closed off his node, but only have 200 nxt on his account.
The 1000 NXT deposit is deducted from the available balance as soon as the account joins the shuffle. The account can't join the shuffle if the coins aren't there. So the situation you describe can't arise.

Quote
Seems to me shuffling would be much better without these limitations.
Anonymity is hard. Shuffling is inherently complex. The current design looks to be about the simplest possible. If it turns out well, maybe it can be made more flexible, and hence even more complex, later.
« Last Edit: December 21, 2015, 10:01:56 pm by Brangdon »
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1794
    • View Profile
Re: NRS v1.7.3e
« Reply #17 on: December 22, 2015, 08:59:19 am »

UI suggestions/notes:

1. rename "Deletes History" subsection of AE to "Delete History" or "Deletion History" to be more consistent with the singular form "Trade History" and "Transfer History" (they aren't Trades History or Transfers History).

2. Under Account Properties, the buttons in the upper right, "incoming" is not capitalized, but "Outgoing" and "Set" are capitalized.

Fixed for 1.7.4
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1794
    • View Profile
Re: NRS v1.7.3e
« Reply #18 on: December 22, 2015, 09:21:49 am »

Where is Account Control in the UI? I've tried reloading, and I can see Account Properties.

It's in the account details modal. From the dashboard click on the "account balance" box (top/left) on the resulting "account details" modal click the "account control" tab.
Thanks. That's well hidden. It might be an idea to combine the account balance/details with the Details button that is underneath the main account number. Or something.

Currently, clicking the account number does nothing. Clicking the account name "Brangdon TestNet" sets Account Info (ie name and description). Clicking Details gives historical info (transactions and ledger) and current state (currencies owned, etc). Clicking the balance gives another group of settings (balances, leasing, account control). There is also Account Properties underneath the Dashboard, which is something else again. This is all a bit messy and unobvious in my view. Maybe it would be better if Leasing and Account Control were together with Account Ledger, Account Properties and Approval Requests in the Dashboard section. Better organisation would make clearer what options are available to set, and the difference between "info", "details" and "properties", and which are historical, and which are current state. Or whatever, I'm not great at UI. It just really needs an overhaul at the moment. It's just growed.

We decided to leave the account number as a non-clickable label so that power users can triple click it then press Ctrl+C to copy it, which I find myself doing very often. Until 1.6 this was available using an Adobe Flash extension which we had to remove due to security and compatibility reasons.
We actually put a lot of thought (and work) on setting the name and details links so that these functions are easily accessible.

I agree that something has to be done about all these account related modals and pages which we inherited from the original Wesley design. Currently, whenever we need to add something we decide ad hoc about the appropriate modal or page but rarely alter to overall design.

We are also missing quite a few account specific tables in the account info dialog which should have been part of this modal tabs like "Asset Delete", "Currency Exchanges" etc which we  can only see for the current account, not for other accounts.
But we already have 7 tabs on this modal and if we add all these tables there, we'll end up with 15 tabs or more.
And I also agree that there is no reason for having separate "account details" modals with yet more hidden account specific functionality.
Need to think about a better design for this.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.3e
« Reply #19 on: December 22, 2015, 09:47:08 am »

I see another shuffling created on testnet, 13334123818548070566 for 30 participants. Unless 18 more accounts register in the next 100 minutes, it will not enroll enough participants and fail. If you create shufflings for testing, it is better to announce them on the forum too, and allow a long registration period, I guess nobody bothers to check frequently if there are any new active shufflings on testnet.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322
Pages: [1] 2 3  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly