Nxt Forum

Nxt Discussion => Nxt General Discussion => Topic started by: Damelon on March 16, 2016, 09:32:35 am

Title: Upcoming features in 1.8 release
Post by: Damelon on March 16, 2016, 09:32:35 am
I have requested and received the following list of features that will be implemented in the upcoming 1.8 release:

Desktop Wallet
Run the client wallet as a desktop application, see: https://bitbucket.org/JeanLucPicard/nxt/issues/338/desktop-wallet

Account Monitor
Server side component which automatically funds specific accounts based on various criteria to make sure the account owners always poses enough NXT to transact.

Wallet home customisation
Open the wallet on a specific page or modal, see: https://bitbucket.org/JeanLucPicard/nxt/issues/320/start-the-client-on-a-specific-page-or

Add-Ons
Simple server side plugin framework

Let's start sharing on our channels :)
Title: Re: Upcoming features in 1.8 release
Post by: martismartis on March 16, 2016, 09:41:39 am
ETA?
Title: Re: Upcoming features in 1.8 release
Post by: Damelon on March 16, 2016, 09:47:18 am
Not clear, but somewhere in the first weeks of April AFAIK
Title: Re: Upcoming features in 1.8 release
Post by: lurker10 on March 16, 2016, 09:53:27 am
Since this release is about improving user experience, is it reasonable to assume that the cause of decentralization is not put under threat by adding a second official package, this one with a bundled blockchain up to the 1.7 hard fork block?
Title: Re: Upcoming features in 1.8 release
Post by: Cassius on March 16, 2016, 10:17:57 am
This sounds cool but I have questions:

Desktop Wallet
Run the client wallet as a desktop application, see: https://bitbucket.org/JeanLucPicard/nxt/issues/338/desktop-wallet
What is it now?

Quote
Account Monitor
Server side component which automatically funds specific accounts based on various criteria to make sure the account owners always poses enough NXT to transact.
How complex will this be? For example, can you sell assets to fund a different account? This would be good for paying MS currency transactions in native tokens, but starts to sound a bit smart contracty.

Quote
Wallet home customisation
Open the wallet on a specific page or modal, see: https://bitbucket.org/JeanLucPicard/nxt/issues/320/start-the-client-on-a-specific-page-or

Add-Ons
Simple server side plugin framework

Let's start sharing on our channels :)
Title: Re: Upcoming features in 1.8 release
Post by: abctc on March 16, 2016, 10:23:37 am
I have requested and received the following list of features that will be implemented in the upcoming 1.8 release:
....
Let's start sharing on our channels :)
- Thank you!  Shared here: https://bitcointalk.org/index.php?topic=345882.msg14214165#msg14214165
Title: Re: Upcoming features in 1.8 release
Post by: durerus on March 16, 2016, 10:29:23 am
Is 2FA still planned for 1.8?
Title: Re: Upcoming features in 1.8 release
Post by: Jean-Luc on March 16, 2016, 10:41:38 am
No.
Title: Re: Upcoming features in 1.8 release
Post by: Tosch110 on March 16, 2016, 10:54:21 am
Thanks for the updates, shared here: https://twitter.com/ToschDev/status/710052406671888384
Title: Re: Upcoming features in 1.8 release
Post by: xcn on March 16, 2016, 10:59:45 am
Add-Ons
Simple server side plugin framework

is it nxtplugins related?
Title: Re: Upcoming features in 1.8 release
Post by: farl4bit on March 16, 2016, 12:31:18 pm
Shared!! Looking forward for the desktop wallet!  :) :)
Title: Re: Upcoming features in 1.8 release
Post by: websioux on March 16, 2016, 02:39:39 pm
I'm looking forward for the other 3 !  :P
And like to see the word framework.

This will help to build great apps and position NXT as the crypto network + framework that support traditional web/app developers.

Title: Re: Upcoming features in 1.8 release
Post by: NxtSwe on March 16, 2016, 03:49:53 pm
Account Monitor
Server side component which automatically funds specific accounts based on various criteria to make sure the account owners always poses enough NXT to transact.

How is this supposed to work?
Title: Re: Upcoming features in 1.8 release
Post by: PoofKnuckle on March 16, 2016, 04:09:22 pm

Add-Ons
Simple server side plugin framework


(https://catmacros.files.wordpress.com/2009/06/lol_copy9.jpg?w=720)
Title: Re: Upcoming features in 1.8 release
Post by: ScripterRon on March 16, 2016, 04:22:05 pm
Account Monitor
Server side component which automatically funds specific accounts based on various criteria to make sure the account owners always poses enough NXT to transact.

How is this supposed to work?
The account monitor has a funding account and one or more monitored accounts.  You can monitor Nxt, Asset or Currency.  When a monitored account balance becomes less than the threshold amount, a transfer transaction is initiated to transfer Nxt/Asset/Currency from the funding account to the monitored account.

Multiple account monitors can be active.  Monitored accounts are identified by an account property.  The account property must be set by the funding account owner.
Title: Re: Upcoming features in 1.8 release
Post by: Sebastien256 on March 16, 2016, 04:45:30 pm
Thanks, this look like interesting features!
Title: Re: Upcoming features in 1.8 release
Post by: Brangdon on March 16, 2016, 08:03:04 pm
The account monitor has a funding account and one or more monitored accounts.  You can monitor Nxt, Asset or Currency.  When a monitored account balance becomes less than the threshold amount, a transfer transaction is initiated to transfer Nxt/Asset/Currency from the funding account to the monitored account.
Are there safeguards to prevent abuse, or do you assume the monitored account is owned by the same person as the funding account?
Title: Re: Upcoming features in 1.8 release
Post by: ScripterRon on March 17, 2016, 03:34:32 am
The account monitor has a funding account and one or more monitored accounts.  You can monitor Nxt, Asset or Currency.  When a monitored account balance becomes less than the threshold amount, a transfer transaction is initiated to transfer Nxt/Asset/Currency from the funding account to the monitored account.
Are there safeguards to prevent abuse, or do you assume the monitored account is owned by the same person as the funding account?
You provide your secret phrase when starting an account monitor (same as when you start forging).  The API are StartAccountMonitor, StopAccountMonitor and GetAccountMonitor.
Title: Re: Upcoming features in 1.8 release
Post by: allwelder on March 17, 2016, 08:58:10 am
Great.
Shared on nxtchina.org (http://nxtchina.org/portal.php?mod=view&aid=66)
Title: Re: Upcoming features in 1.8 release
Post by: yassin54 on March 17, 2016, 09:04:48 am
Great.
Shared on nxtchina.org (http://nxtchina.org/portal.php?mod=view&aid=66)
man, you are a best Translator chinise
i love you so much for great work!!  :-* :-* :-*

Ps: Great work Dev and Foundation NXT!!!  8)
Title: Re: Upcoming features in 1.8 release
Post by: abctc on March 17, 2016, 09:49:52 am
The account monitor has a funding account and one or more monitored accounts.  You can monitor Nxt, Asset or Currency.  When a monitored account balance becomes less than the threshold amount, a transfer transaction is initiated to transfer Nxt/Asset/Currency from the funding account to the monitored account.

Multiple account monitors can be active.  Monitored accounts are identified by an account property.  The account property must be set by the funding account owner.
- amazing!  Translated and shared here: https://bitcointalk.org/index.php?topic=345882.msg14225089#msg14225089
Title: Re: Upcoming features in 1.8 release
Post by: HCLivess on March 17, 2016, 10:13:32 am
I suggest we make forging operations simpler
for example, when I start forging on my nxt node using a browser from another pc, it stops working the moment i close the browser... yet it is possible to do, although it serves no purpose
Title: Re: Upcoming features in 1.8 release
Post by: Riker on March 17, 2016, 10:25:36 am
The account monitor has a funding account and one or more monitored accounts.  You can monitor Nxt, Asset or Currency.  When a monitored account balance becomes less than the threshold amount, a transfer transaction is initiated to transfer Nxt/Asset/Currency from the funding account to the monitored account.
Are there safeguards to prevent abuse, or do you assume the monitored account is owned by the same person as the funding account?
You provide your secret phrase when starting an account monitor (same as when you start forging).  The API are StartAccountMonitor, StopAccountMonitor and GetAccountMonitor.

The idea behind this feature is to allow one account to automatically make sure that other accounts used by his application always poses small amount of NXT so that they can send transactions.
This can be used by businesses to mask the fact that they are using NXT under the hoods from their users.

The business owner specifies:
Funding account
Account property to identify other accounts to be funded
Amount to fund each time
Threshold under which the account has to be funded
Interval between funding transactions

Keeping the interval large enough and the amount to fund small enough should prevent abuse.
However, if there is a persistent problem the funding account can remove the funding property from the abusing funded account and thus stop the funding.
Title: Re: Upcoming features in 1.8 release
Post by: HCLivess on March 17, 2016, 10:26:31 am
Also, this is rather big. Together with the upcoming 2.0 features and very active development, NXT is the biggest thing under the radar.
Title: Re: Upcoming features in 1.8 release
Post by: durerus on March 17, 2016, 01:55:47 pm
The account monitor has a funding account and one or more monitored accounts.  You can monitor Nxt, Asset or Currency.  When a monitored account balance becomes less than the threshold amount, a transfer transaction is initiated to transfer Nxt/Asset/Currency from the funding account to the monitored account.
Are there safeguards to prevent abuse, or do you assume the monitored account is owned by the same person as the funding account?
You provide your secret phrase when starting an account monitor (same as when you start forging).  The API are StartAccountMonitor, StopAccountMonitor and GetAccountMonitor.

The idea behind this feature is to allow one account to automatically make sure that other accounts used by his application always poses small amount of NXT so that they can send transactions.
This can be used by businesses to mask the fact that they are using NXT under the hoods from their users.

The business owner specifies:
Funding account
Account property to identify other accounts to be funded
Amount to fund each time
Threshold under which the account has to be funded
Interval between funding transactions

Keeping the interval large enough and the amount to fund small enough should prevent abuse.
However, if there is a persistent problem the funding account can remove the funding property from the abusing funded account and thus stop the funding.

Got it! So using the Monetary System for concert cards (as you mentioned that as an example in the video with Marc) without the visitor of the concert having to consciously deal with NXT will be possible. So making this possible should no longer be mentioned as a reason for 2.0, no?
Title: Re: Upcoming features in 1.8 release
Post by: Riker on March 17, 2016, 02:23:19 pm
The account monitor has a funding account and one or more monitored accounts.  You can monitor Nxt, Asset or Currency.  When a monitored account balance becomes less than the threshold amount, a transfer transaction is initiated to transfer Nxt/Asset/Currency from the funding account to the monitored account.
Are there safeguards to prevent abuse, or do you assume the monitored account is owned by the same person as the funding account?
You provide your secret phrase when starting an account monitor (same as when you start forging).  The API are StartAccountMonitor, StopAccountMonitor and GetAccountMonitor.

The idea behind this feature is to allow one account to automatically make sure that other accounts used by his application always poses small amount of NXT so that they can send transactions.
This can be used by businesses to mask the fact that they are using NXT under the hoods from their users.

The business owner specifies:
Funding account
Account property to identify other accounts to be funded
Amount to fund each time
Threshold under which the account has to be funded
Interval between funding transactions

Keeping the interval large enough and the amount to fund small enough should prevent abuse.
However, if there is a persistent problem the funding account can remove the funding property from the abusing funded account and thus stop the funding.

Got it! So using the Monetary System for concert cards (as you mentioned that as an example in the video with Marc) without the visitor of the concert having to consciously deal with NXT will be possible. So making this possible should no longer be mentioned as a reason for 2.0, no?

It's an intermediate solution not suitable for mass usage since you'll need to pay a lot of fees but if you have few dozens accounts that you like to mask from NXT you can use the "Funding Monitor" this way.
Title: Re: Upcoming features in 1.8 release
Post by: testdruif on March 21, 2016, 09:06:05 pm
Is the plugin/addon feature already implemented or is it still in it's inital phase?
Title: Re: Upcoming features in 1.8 release
Post by: Riker on March 21, 2016, 09:16:06 pm
Add-ons are already implemented in package nxt.addons and documented in "nxt-client-1.8.0e.changelog.txt", look for "Server-side addOns"
We can use your feedback, if you like to implement the first ever add on.
Title: Re: Upcoming features in 1.8 release
Post by: testdruif on March 21, 2016, 09:21:07 pm
Already on it (if I can get intellij to work with 1.8e) :(
I'm going to bring email notification to the masses! ;)
Title: Re: Upcoming features in 1.8 release
Post by: testdruif on March 21, 2016, 10:01:14 pm
Already on it (if I can get intellij to work with 1.8e) :(
I'm going to bring email notification to the masses! ;)

Any idea why I'm running into problems when compiling?
I have to comment out

// load non-default properties files from the user folder
                    if (!dirProvider.isLoadPropertyFileFromUserDir()) {
                        return properties;
                    }

In order for the code to run.
Error:

Exception in thread "main" java.lang.ExceptionInInitializerError
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:264)
   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:122)
Caused by: java.lang.RuntimeException: Using an nxt-default.properties file from a version other than 1.8.0e is not supported!!!
   at nxt.Nxt.<clinit>(Nxt.java:77)
   ... 3 more
Title: Re: Upcoming features in 1.8 release
Post by: Riker on March 21, 2016, 10:13:00 pm
Already on it (if I can get intellij to work with 1.8e) :(
I'm going to bring email notification to the masses! ;)

Any idea why I'm running into problems when compiling?
I have to comment out

// load non-default properties files from the user folder
                    if (!dirProvider.isLoadPropertyFileFromUserDir()) {
                        return properties;
                    }

In order for the code to run.
Error:

Exception in thread "main" java.lang.ExceptionInInitializerError
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:264)
   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:122)
Caused by: java.lang.RuntimeException: Using an nxt-default.properties file from a version other than 1.8.0e is not supported!!!
   at nxt.Nxt.<clinit>(Nxt.java:77)
   ... 3 more

Depending on how you launch the server it is loading nxt-default.properties from a previous version, perhaps from "c:\program file\nxt"
You can tell which properties file is loaded from the nxt.log and/or the IntelliJ console window.
Title: Re: Upcoming features in 1.8 release
Post by: testdruif on March 21, 2016, 10:21:34 pm
Already on it (if I can get intellij to work with 1.8e) :(
I'm going to bring email notification to the masses! ;)

Any idea why I'm running into problems when compiling?
I have to comment out

// load non-default properties files from the user folder
                    if (!dirProvider.isLoadPropertyFileFromUserDir()) {
                        return properties;
                    }

In order for the code to run.
Error:

Exception in thread "main" java.lang.ExceptionInInitializerError
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:264)
   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:122)
Caused by: java.lang.RuntimeException: Using an nxt-default.properties file from a version other than 1.8.0e is not supported!!!
   at nxt.Nxt.<clinit>(Nxt.java:77)
   ... 3 more

Depending on how you launch the server it is loading nxt-default.properties from a previous version, perhaps from "c:\program file\nxt"
You can tell which properties file is loaded from the nxt.log and/or the IntelliJ console window.

I'm running it straight from intelliJ,

Only output I have is

"C:\Program Files\Java\jdk1.8.0_74\bin\java" -Didea.launcher.port=7536 "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community Edition 2016.1\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program Files\Java\jdk1.8.0_74\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\deploy.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\access-bridge-64.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\cldrdata.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\dnsns.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\jaccess.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\jfxrt.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\localedata.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\nashorn.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\sunec.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\sunjce_provider.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\sunmscapi.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\sunpkcs11.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\ext\zipfs.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\javaws.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\jfxswt.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\management-agent.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\plugin.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_74\jre\lib\rt.jar;C:\Users\testd\Downloads\nxt-private-1.8\out\production\nxt-private-1.8;C:\Users\testd\Downloads\nxt-private-1.8\lib\core-3.2.1.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\h2-1.4.191.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\javase-3.2.1.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\weupnp-0.1.4.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\tika-core-1.12.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\slf4j-api-1.7.18.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\json-simple-1.1.1.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\lucene-core-5.3.2.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\tika-parsers-1.12.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\bcprov-jdk15on-154.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\slf4j-jdk14-1.7.18.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\lucene-queries-5.3.2.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\javax.servlet-api-3.1.0.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\jetty-io-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\lucene-queryparser-5.3.2.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\jetty-http-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\jetty-util-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\jetty-server-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\jetty-servlet-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\lucene-analyzers-common-5.3.2.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\websocket-api-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\jetty-security-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\jetty-servlets-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\websocket-client-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\websocket-common-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\websocket-server-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\websocket-servlet-9.3.8.v20160314.jar;C:\Users\testd\Downloads\nxt-private-1.8\lib\jetty-continuation-9.3.8.v20160314.jar;C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community Edition 2016.1\lib\idea_rt.jar" com.intellij.rt.execution.application.AppMain nxt.Nxt
Initializing Nxt server version 1.8.0e
Command line arguments
-Didea.launcher.port=7536
-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community Edition 2016.1\bin
-Dfile.encoding=UTF-8
isHeadless=false
Exception in thread "main" java.lang.ExceptionInInitializerError
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:264)
   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:122)
Caused by: java.lang.RuntimeException: Using an nxt-default.properties file from a version other than 1.8.0e is not supported!!!
   at nxt.Nxt.<clinit>(Nxt.java:77)
   ... 3 more
Runtime mode nxt.env.CommandLineMode
User home folder C:\Users\testd\Downloads\nxt-private-1.8

Process finished with exit code 1
Title: Re: Upcoming features in 1.8 release
Post by: Riker on March 21, 2016, 10:26:22 pm
Try Placing a breakpoint in Nxt.java above line 77 and see exactly which nxt-default.properties file is loaded.
Title: Re: Upcoming features in 1.8 release
Post by: testdruif on March 21, 2016, 10:32:02 pm
Try Placing a breakpoint in Nxt.java above line 77 and see exactly which nxt-default.properties file is loaded.

fixed it by adding the conf folder to the sources in project structure
elective-stereophonic
elective-stereophonic
assembly
assembly