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

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 ... 6 7 [8] 9 10 ... 18  All

Author Topic: NRS v1.6.2  (Read 90448 times)

martismartis

  • Hero Member
  • *****
  • Karma: +73/-10
  • Offline Offline
  • Posts: 1238
    • View Profile
Re: NRS v1.6.2
« Reply #140 on: November 06, 2015, 06:22:02 pm »

1.5.15 database for download would be good thing for reversal to 1.5.15, I'll just update back my public node.
Logged

prometheus

  • Sr. Member
  • ****
  • Karma: +23/-3
  • Offline Offline
  • Posts: 431
    • View Profile
Re: NRS v1.6.2
« Reply #141 on: November 06, 2015, 07:15:23 pm »

Staying on 1.5.15...how will businesses be built around NXT with this happening? NXT has little value without an ecosystem to support it
Logged

abctc

  • Hero Member
  • *****
  • Karma: +148/-13
  • Offline Offline
  • Posts: 1396
    • View Profile
Re: NRS v1.6.2
« Reply #142 on: November 06, 2015, 07:33:26 pm »

I will not revert to 1.5.15.
I'm staying on 1.6.2
There were a lot of time since 1.6.0e to discuss this issue.
And it is a bad idea to rely on public nodes.
BCNext wanted vice-versa: the common people to use nodes of different services (such as exchanges and shops).
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

Tosch110

  • Hero Member
  • *****
  • Karma: +211/-18
  • Offline Offline
  • Posts: 2365
    • View Profile
Re: NRS v1.6.2
« Reply #143 on: November 06, 2015, 07:43:20 pm »

I will not revert to 1.5.15.
I'm staying on 1.6.2
There were a lot of time since 1.6.0e to discuss this issue.
And it is a bad idea to rely on public nodes.
BCNext wanted vice-versa: the common people to use nodes of different services (such as exchanges and shops).

The problem is that this issue has not been raised on 1.6.0e and following experimental releases because the API has not been depricated. It was still functional as before but the parameters that have been returning false by default on 1.6.2 were still displaying all information on the previous experimental releases.

IMO this is how 1.6.2 or 1.6.3 need to look like.

abctc

  • Hero Member
  • *****
  • Karma: +148/-13
  • Offline Offline
  • Posts: 1396
    • View Profile
Re: NRS v1.6.2
« Reply #144 on: November 06, 2015, 08:10:33 pm »

.. this issue has not been raised on 1.6.0e and following experimental releases because the API has not been depricated. It was still functional as before ..
- if this is true then it is VERY strange and unacceptable.

Jean-Luc, is this true?
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

wiser

  • Full Member
  • ***
  • Karma: +7/-1
  • Offline Offline
  • Posts: 129
    • View Profile
Re: NRS v1.6.2
« Reply #145 on: November 06, 2015, 08:28:25 pm »

I just downloaded and installed the latest version of NXT. I used the Windows installer. When I try to start the NXT server, it stays on "loading resources" for hours and hours. I'm wondering how long I should expect it to be loading resources before I'll be able to run the wallet. Is this a matter of leave it running overnight and check back in the morning, or is something wrong?

Thanks.
Logged

wiser

  • Full Member
  • ***
  • Karma: +7/-1
  • Offline Offline
  • Posts: 129
    • View Profile
Re: NRS v1.6.2
« Reply #146 on: November 06, 2015, 08:35:18 pm »

I just downloaded and installed the latest version of NXT. I used the Windows installer. When I try to start the NXT server, it stays on "loading resources" for hours and hours. I'm wondering how long I should expect it to be loading resources before I'll be able to run the wallet. Is this a matter of leave it running overnight and check back in the morning, or is something wrong?

Thanks.

I think it took me 2 hours or something like that.

It's already been longer than two hours for me. Once it's done "loading resources" what happens next? What should I expect? At what point do I give up if nothing seems to be changing? There doesn't seem to be an easy way to check on the progress, and the "status" doesn't tell me anything that I can discern. Thanks :)
Logged

chanc3r

  • Hero Member
  • *****
  • Karma: +124/-50
  • Offline Offline
  • Posts: 1019
  • NXTInspect
    • View Profile
Re: NRS v1.6.2
« Reply #147 on: November 06, 2015, 08:41:23 pm »

The software landscape is littered with software that has died because of discontinuous changes.
Software continues to thrive based on its user base not just because of its developers.
Software without users is just an interesting lab project that no one will remember.

The technology reasons in this case or the rights and wrongs of the technical changes are irrelevant.
The strategy to provide a discontinuous upgrade for a platform that is young and still vulnerable is flawed as it disconnects a user base which is critical to its continued growth and adoption.

Positions seem to be becoming entrenched and people are threatening which is not helping.
This needs to be fixed or NXT will suffer at a time when it is positioning itself to grow again.

If the 1.5.x API cannot be supported by the core of 1.6.x what can be done to mitigate the impact of this?
 
Can we provide a legacy translator where people can continue to call 1.5.x API and it connects to the core via a translator 1.6.x rather than people running 2 versions of NXT?
Logged
NXT: 29996814460165 (NXT-JTA7-B2QR-8BFC-2V222)
@imrimr @NXTinspect

neofelis

  • Hero Member
  • *****
  • Karma: +74/-12
  • Offline Offline
  • Posts: 568
    • View Profile
Re: NRS v1.6.2
« Reply #148 on: November 06, 2015, 08:44:39 pm »

Being strictly a MAC guy and not understanding code, I am still lost on running any version of the client on my computer.  Has anybody created an easy way to get NXT running on a mac or do I need to go buy a Windows machine?  I really want to support the network but geez, it's getting harder.

Logged

chanc3r

  • Hero Member
  • *****
  • Karma: +124/-50
  • Offline Offline
  • Posts: 1019
  • NXTInspect
    • View Profile
Re: NRS v1.6.2
« Reply #149 on: November 06, 2015, 08:47:41 pm »

Being strictly a MAC guy and not understanding code, I am still lost on running any version of the client on my computer.  Has anybody created an easy way to get NXT running on a mac or do I need to go buy a Windows machine?  I really want to support the network but geez, it's getting harder.

I run it on a mac
Download and install java runtime (you should already have it)
Download NXT from the forum
unzip it somewhere in your filesystem
execute run.sh from the nxt folder
point your browser to 127.0.0.1:7876
Logged
NXT: 29996814460165 (NXT-JTA7-B2QR-8BFC-2V222)
@imrimr @NXTinspect

farl4bit

  • Hero Member
  • *****
  • Karma: +210/-45
  • Offline Offline
  • Posts: 3466
    • View Profile
    • Crypto Advies
Re: NRS v1.6.2
« Reply #150 on: November 06, 2015, 08:53:47 pm »

Being strictly a MAC guy and not understanding code, I am still lost on running any version of the client on my computer.  Has anybody created an easy way to get NXT running on a mac or do I need to go buy a Windows machine?  I really want to support the network but geez, it's getting harder.

I have the same problem too. A solution has te be made soon, very soon and communication and updates even sooner. What is this silence from the devs? This is not good for the trust in Nxt!  :(
Logged

wiser

  • Full Member
  • ***
  • Karma: +7/-1
  • Offline Offline
  • Posts: 129
    • View Profile
Re: NRS v1.6.2
« Reply #151 on: November 06, 2015, 08:55:27 pm »

I don't really understand any of the part referring to old and new API, but I agree with what I understand to be the sentiment. I struggle with the NXT client every time there is an upgrade, and if I haven't been "in the loop" for a few weeks or months, then it's even worse. It's really frustrating that I can't just install my wallet, run it, and expect it to work. I have to wait hours for stuff to download. With this new version, I'm waiting and waiting on the "loading resources" part but I have absolutely no indication of the progress or how long it will take. NXT has been around for almost two years and the wallet has NEVER been truly user friendly. Who exactly are you expecting to adopt and use NXT? People with lots of technical know how? Or would you like people like me who are decent with computers and can edit a line of code here and there but would rather not to be able to use it? How about those people who use computers but have no actual technical expertise? Or the ones who aren't willing to fight with a wallet just to be able to make it work?

The software landscape is littered with software that has died because of discontinuous changes.
Software continues to thrive based on its user base not just because of its developers.
Software without users is just an interesting lab project that no one will remember.

The technology reasons in this case or the rights and wrongs of the technical changes are irrelevant.
The strategy to provide a discontinuous upgrade for a platform that is young and still vulnerable is flawed as it disconnects a user base which is critical to its continued growth and adoption.

Positions seem to be becoming entrenched and people are threatening which is not helping.
This needs to be fixed or NXT will suffer at a time when it is positioning itself to grow again.

If the 1.5.x API cannot be supported by the core of 1.6.x what can be done to mitigate the impact of this?
 
Can we provide a legacy translator where people can continue to call 1.5.x API and it connects to the core via a translator 1.6.x rather than people running 2 versions of NXT?
Logged

neofelis

  • Hero Member
  • *****
  • Karma: +74/-12
  • Offline Offline
  • Posts: 568
    • View Profile
Re: NRS v1.6.2
« Reply #152 on: November 06, 2015, 09:08:31 pm »

Being strictly a MAC guy and not understanding code, I am still lost on running any version of the client on my computer.  Has anybody created an easy way to get NXT running on a mac or do I need to go buy a Windows machine?  I really want to support the network but geez, it's getting harder.

I run it on a mac
Download and install java runtime (you should already have it)
Download NXT from the forum
unzip it somewhere in your filesystem
execute run.sh from the nxt folder
point your browser to 127.0.0.1:7876

Well, pointed my browser to 127.0.0.1:7876 and that seemed to do the trick.  Downloading block chain now.  I was used to the stand alone app and prefer it.  Does running this on a browser compromise my passphrase?

Logged

wiser

  • Full Member
  • ***
  • Karma: +7/-1
  • Offline Offline
  • Posts: 129
    • View Profile
Re: NRS v1.6.2
« Reply #153 on: November 06, 2015, 09:22:35 pm »

It looks like I did find the progress status on the "status" tab. It currently has me on January 16, 2015, but moving forward, so I guess I just have almost a year to go on downloading blocks. That's reassuring :)

Hopefully I can open my wallet once the status tells me all the blocks up to right now have been downloaded.
Logged

NXTinspect

  • Jr. Member
  • **
  • Karma: +5/-1
  • Offline Offline
  • Posts: 34
    • View Profile
Re: NRS v1.6.2
« Reply #154 on: November 06, 2015, 09:25:18 pm »


Well, pointed my browser to 127.0.0.1:7876 and that seemed to do the trick.  Downloading block chain now.  I was used to the stand alone app and prefer it.  Does running this on a browser compromise my passphrase?

The stand-alone app simply packaged the activation of nxt (run.sh) inside a mac app and provided a browser plug-in in a screen so it looked like an app... Essentially you are doing the same thing un-bundled so its as safe as before as long as you dont have spyware on your mac
Logged

EvilDave

  • Hero Member
  • *****
  • Karma: +341/-40
  • Offline Offline
  • Posts: 1789
    • View Profile
    • NXT Foundation
Re: NRS v1.6.2
« Reply #155 on: November 06, 2015, 11:14:11 pm »

@neofilis and @wiser: hope you guys are up and running or at least getting closer.....sometimes the blockchain can take way too long to d/l, there is a bootstrap blockchain available at: http://www.peerexplorer.com/
Check the version, though.


OK, moving on to the subject at hand,  the issues with NRS 1.6.2 API.

Myself, JL777, Damelon, Jean-Luc and Riker (formerly Lyaffe) have been in deep discussion for way too much of the last few hours, and while we don't yet have a complete solution for the medium and long-term issues that are involved here, we do have a reasonable interim solution for the short term ie the next few days.

I need to stress here that both versions of the NRS (1.6.2 and 1.5.15) are completely safe for routine use, these issues only arise when accessing API calls for the NRS, so this issue only affects API users. 'Normal' home users can run either version with no problems.

There have been a couple of changes made to the 1.6.2 API in order to optimise local database performance which were not completely documented in the change logs/release notes. (well, the direct changes were documented, but the consequences for the rest of the API chain were not)
This has resulted in some external projects and businesses experiencing serious issues with their functionality (chiefly SuperNET, Drachmae, 44Phones and Nxt2Pay so far, but one top-secret project with a demo tomorrow also got borked).

I'll let Riker explain the short term solutions to you, via Slack:
Quote
Exchanges and business affected by the API change should revert back to 1.5.15.
Supernet and Jay users and anyone who rely on public nodes, should select a subset of the nodes which they know and trust and keep these nodes on 1.5.15
Regular users can continue to use 1.6.2 on their local workstations to enjoy the account ledger and additional features.
Regarding the API changes, while the list of changes look intimidating the changes themselves are minimal. We can set a hot channel for anyone who has a problem or needs guidance with porting the API to 1.6 

TL:DR If you have an Nxt-based project, and you haven't reviewed the API changes and adjusted your code to match: use 1.5.15.
If you provide an open API node to the network, stay on 1.5.15 please, until further notice.
Everyone else: use whatever. I don't care and it doesn't matter.


That's the short term, we still have a lot of stuff on the table for the medium and long term to ensure that Nxt provides a stable environment for developers and external projects. I'll try to post a rough outline of the medium/long term proposals later on tonight, but can't guarantee that.
Anyhow, we'll be working on this over the weekend, so there will be updates.

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

EvilDave

  • Hero Member
  • *****
  • Karma: +341/-40
  • Offline Offline
  • Posts: 1789
    • View Profile
    • NXT Foundation
Re: NRS v1.6.2
« Reply #156 on: November 06, 2015, 11:17:33 pm »

Full repost of the changelogs and API info from J-L so far :
(non-techies start scrolling now)

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

Release 1.6.2

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

sha256:

954125b60578120dc32fac774eb923efe65ff046f31b1c8f29eab94349850ee3  nxt-client-1.6.2.zip

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

sha256:

6e7c77bd601783779aef72cd42ea04086698e7e921abf49aedb4ab9dab513427  nxt-client-1.6.2.jar

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

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


Change log:

The 1.6 series is no longer considered experimental. If upgrading from 1.5.15
or earlier, see the 1.6.0e and 1.6.1e changelogs for other important changes
in 1.6.

The account ledger now uses transaction id as event id for all events except
block generation. To apply this change, the account ledger table will be
automatically truncated on upgrade to this release. Users who desire to
restore the deleted past account ledger entries should run a full rescan from
the API test page. Note that account ledger records are only kept for 30000
blocks by default.

Added currency transfers history page to the Monetary System UI.

Added generate hallmark dialog to facilitate hallmarking your node. The host
field is pre-populated with the external node address as detected by UPnP.
Note that when using dynamic IP address you should set up and use a dynamic
DNS hostname instead of the numeric IP for the hallmark. And when using a
non-default port, the host field should be filled as host:port.

Added "clear results" link in the ShapeShift My Exchanges section, to allow
clearing past transaction history. As this history data is being retrieved
from the ShapeShift servers, it allows correlating Nxt accounts previously
used for exchange transactions with the current user IP address and with each
other, thus clearing history after no longer needed is important for the user
privacy.

Funding a new account using ShapeShift now relies on the ShapeShift sendamount
API which provides better conversion rate. The user first specifies the
amount of NXT to receive, the dialog then presents a deposit address for the
source currency which the user needs to fund with the exact amount within 10
minutes.

Added ledger tab to the account info dialog.

Added includeAssetInfo or includeCurrencyInfo parameters, default false, to
the getAccountAssets, getAccountCurrencies, getAccountExchangeRequests,
getExpectedAssetTransfers, and getExpectedCurrencyTransfers APIs.

Tabs are now sorted mostly alphabetically on the API test page.

Added nxt.hideErrorDetails property, default false, to allow suppressing node
specific configuration details in error messages returned to peers.

Increased default prunable lifetime setting to 90 days. Minimum enforced is
still 2 weeks.

The UPnP connection timeouts are now also configurable in nxt.properties.

Updated Bouncy Castle library to version 1.53, Jetty to version 9.3.5, IzPack
installer to 5.0.5, and weupnp to 0.1.4. Make sure to delete the old lib
folder if unpacking over a previous installation.


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

iQIcBAEBCgAGBQJWNQgzAAoJENqvaxkWiP4ZbrsP/i9jXuuaXoMx7+d6DOwPG9Z+
AUktpye5SXhbQvSDJQhQ2L4FSto1X6gbBuGGVaoHA5M+N5IN1GydTTYe9s2B9G8Q
wFZD5+WFzDM54ygv0JC2to8Ns8LU9/b9VIWqSczzdzYPQ+mbmMYXcglkgz70zgbM
yAwK5MbyO/sDiW8BE9QiyEgF6TvolbJT0GgdKb4wvOPuRJ9mx0zDVU0TA/W5zT5k
Xo1RxuDqqt97i0uaFVr29IGXnsJaxC5Pj1f7BjlHa9+cUmyBcIkbGMlA587grGzv
CV7gmG/tAh57wi6CY0yyQD23mzj54cS44Yi09Xz3kESkpIM5YkPiQ+D6/0uIU4Pb
PjKaNgCqv4CpjSC3iA7+qWENg8knZ0xdfTUgxIldOJHiZhhcq5qYRBpC/pKFIbpl
rsTceTZWUfITc1pCyh7QjlcrX1ZgzhpspvCFoTtJ3firESCcSZynp0W5IC0oaRxD
xvZSkso5b55y4iQT1TNMMESse8DVAqwBDDdsKhdX6OJCQohC5Tjw7xUamWzoXkZe
xWf1bMgYHPZKpViBWBc3UiN3Zj0T7jVwPkhWFK+QB9fj1QgdJDV2WOX+QwyiGZy4
WKKKI3TJ8FZzu1knJUECagffdfFt4P7tJK3XHtep7n0Df6UNX6XamWlJnnB3uiBb
1aSre/dZrGCWQNO06tuc
=6NJp
-----END PGP SIGNATURE-----
***************************************************************************
Posting publicly our detailed explanation of the reasons behind the 1.6 API changes, and the conclusions reached:

The reason we are bundling quite a few incompatible API changes in 1.6 is exactly because it is an optional update, not requiring a hard fork, and this was emphasized in the first 1.6.0e changelog. Some of our APIs, such as getAccount and getAsset, date back from before the switch to using a database, when we kept all objects in memory and were doing rescans. What was efficient and simple to do then is no longer true now. I wish we could have started with a perfectly designed APIs, but in a real world, APIs do need to change. Yes, I have heard the suggestion about versioned APIs, but we don't have the development resources to maintain such versioning, and it would be an overkill for a change like the include parameter defaults. Even if we did have versioned APIs, for how many versions back would you expect that they should be maintained? If for two versions, this is the same as what you get by allowing both 1.5 and 1.6 to coexist on the network until the next hard fork, if you need the old version stay with 1.5.

The database is our bottleneck now, and the motivation behind most API changes has been that the defaults should give you the best performance. An API user should be able to call getAccount, getAsset, and getAccountAssets, with just the corresponding object id's, without digging in the documentation or reading the code to figure out what extra options to add to avoid performance problems. In 1.5, by default getAccount also returns asset balances, currency balances, lessors, and effective balance. Those are expensive to get, and the API user certainly does not need all of them all the time. The getAsset call by default counts total number of trades, transfers, and shareholders for the asset. The includeCounts parameter was added a few releases back to allow optimizing the performance of getAsset, but at some point the default of true should be changed to false, because it makes the API difficult to learn and use if for every getAsset call you need to add includeCounts=false in order to get acceptable performance. It will still work without it, but performance will suffer, and the user will complain that everything is slow.

In 1.7, we are adding singleton assets, which are like regular assets in all respects but limited to quantity of 1, and at a much lower issuance fee, 1 NXT. This will have the side effect that the asset table can increase in size a lot, as users can start creating a lot of those singleton assets (intended to use as tradeable tokens representing a single object). Thinking about the performance consequences of this made me review the queries to the asset table, and is one of the reasons for the includeAssetInfo default value change.

There are such include parameters in very many API calls, and in most of them they have been added after the API was first published, to allow improving the performance. Until now, there defaults have been set to be consistent with the API behavior before they were added, because this was done at minor releases where we did not want to introduce incompatible changes. But this cruft all adds up, and this is why we looked at 1.6 as the best time to globally fix such defaults, improve consistency, optimize performance, and make the API easier to learn and use.

We had long internal discussions about the issue, also involving the SuperNet developers. We had a proposal for a workaround using a filter, supplying different default parameter values based on configuration in nxt.properties, but this was not considered useful by the SuperNet team so I am not going to implement it. There is no other feasible technical solution. All clients of the APIs that are affected by the changes must be updated, and we will document in details which APIs have been changed to make that easier. There will be no reversal in 1.6.3.

The 1.6.1e changelog did have an "incompatible changes" section, and the rest of the incompatible changes were also included in the 1.6.2 changelog, but now we realize that in practice this is not sufficient. To improve communication to potentially affected parties, we plan to setup mailing lists for such notifications, and make sure to announce important changes as early as pratically possible in the future.
******************************************************************************************************

This is a summary of the incompatible API changes from 1.5 to 1.6.

If you use any of the following APIs, and require the additional fields returned
when the corresponding includeX parameters are set to true, make sure these
parameters are explicitly added with a value of true to the API call. By default
their values are now false, which results in the corresponding additional fields
not being returned unless explicitly requested. If the additional fields are not
needed, do not request them as this will only hurt performance.

getAccount:
default values of includeAssets, includeCurrencies, includeEffectiveBalance,
includeLessors have been changed to false

getAccountAssets:
new includeAssetInfo parameter has been added, default false

getAccountCurrencies:
new includeCurrencyInfo parameter has been added, default false

getAccountExchangeRequests:
new includeCurrencyInfo parameter has been added, default false

getAccountTaggedData:
default value of includeData has been changed to false

getAllAssets:
default value of includeCounts has been changed to false

getAllCurrencies:
default value of includeCounts has been changed to false

getAllExchanges:
default value of includeCurrencyInfo has been changed to false

getAllTaggedData:
default value of includeData has been changed to false

getAllTrades:
default value of includeAssetInfo has been changed to false

getAsset:
default value of includeCounts has been changed to false

getAssets:
default value of includeCounts has been changed to false

getAssetsByIssuer:
default value of includeCounts has been changed to false

getAssetTransfers:
default value of includeAssetInfo has been changed to false

getBalance:
default value of includeEffectiveBalance has been changed to false

getChannelTaggedData:
default value of includeData has been changed to false

getCurrencies:
default value of includeCounts has been changed to false

getCurrenciesByIssuer:
default value of includeCounts has been changed to false

getCurrency:
default value of includeCounts has been changed to false

getCurrencyTransfers:
default value of includeCurrencyInfo has been changed to false

getDGSGood:
default value of includeCounts has been changed to false

getDGSGoods:
default value of includeCounts has been changed to false

getExchanges:
default value of includeCurrencyInfo has been changed to false

getExchangesByExchangeRequest:
default value of includeCurrencyInfo has been changed to false

getExchangesByOffer:
default value of includeCurrencyInfo has been changed to false

getExpectedAssetTransfers:
new includeAssetInfo parameter has been added, default false

getExpectedCurrencyTransfers:
new includeCurrencyInfo parameter has been added, default false

getState:
default value of includeCounts has been changed to false

getTrades:
default value of includeAssetInfo has been changed to false

searchAssets:
default value of includeCounts has been changed to false

searchCurrencies:
default value of includeCounts has been changed to false

searchTaggedData:
default value of includeData has been changed to false


The additional fields that the includeX parameters add when set to true are:

includeAssetInfo: asset name and decimals

includeCounts: for assets, number of trades, transfers, and shareholders;
for currencies, number of exchanges and number of transfers

includeCurrencyInfo: currency name, code, type, decimals, issuanceHeight,
issuerAccount

includeData: the actual data bytes of the tagged data

includeEffectiveBalance: the effective and guaranteed balances of the account

includeAssets, includeCurrencies, includeLessors: for the getAccount API,
respectively the asset balances, currency balances, and lessors to the account



The getAccountTransactions and getAccountTransactionIDs APIs, deprecated in 1.5
have been removed in 1.6. Use getBlockchainTransactions instead and make sure
to handle correctly the phased transactions.



Any APIs that accept an object id such as account, asset, or currency, but do
not need to retrieve the actual object, no longer check for its existence.
As a result, instead of returning an error when supplied with an unknown id,
they will return an empty result.
Logged
Nulli Dei, nulli Reges, solum NXT
NXT Donations: NXT-BNZB-9V8M-XRPW-3S3WD
We will ride eternal, shiny and chrome!

EvilDave

  • Hero Member
  • *****
  • Karma: +341/-40
  • Offline Offline
  • Posts: 1789
    • View Profile
    • NXT Foundation
Re: NRS v1.6.2
« Reply #157 on: November 07, 2015, 12:07:31 am »

I was going to post an outline of the medium and long term proposals to prevent this sort of issue occuring again, but I went to bed instead. 8)

I'll post in the morning, here's some music to get you thru the night :
https://www.youtube.com/watch?v=2IzR_ClTE8Y
Logged
Nulli Dei, nulli Reges, solum NXT
NXT Donations: NXT-BNZB-9V8M-XRPW-3S3WD
We will ride eternal, shiny and chrome!

wiser

  • Full Member
  • ***
  • Karma: +7/-1
  • Offline Offline
  • Posts: 129
    • View Profile
Re: NRS v1.6.2
« Reply #158 on: November 07, 2015, 12:34:33 am »

I got my wallets up and running, so I just needed to be patient. I'm transferring my NXT and assets to an online wallet on secureae.com so that I don't have to keep dealing with the wallet client. Hopefully I can just log in and do what I need to do.
Logged

Tosch110

  • Hero Member
  • *****
  • Karma: +211/-18
  • Offline Offline
  • Posts: 2365
    • View Profile
Re: NRS v1.6.2
« Reply #159 on: November 07, 2015, 12:43:31 am »

I got my wallets up and running, so I just needed to be patient. I'm transferring my NXT and assets to an online wallet on secureae.com so that I don't have to keep dealing with the wallet client. Hopefully I can just log in and do what I need to do.

The official wallet client has no problems
Pages: 1 ... 6 7 [8] 9 10 ... 18  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly