elective-stereophonic
elective-stereophonic
NRS v1.5.0e
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 ... 5 [All]

Author Topic: NRS v1.5.0e  (Read 25371 times)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
NRS v1.5.0e
« on: April 06, 2015, 07:47:59 pm »

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

Release 1.5.0e

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

sha256:

da89d5d7641b9dcfba725ad618fd5b98da39254d7bcdad129c2affcc9a3826e8  nxt-client-1.5.0e.zip


This is a development release for testing only. Source code is not provided.


Change log:

This is an experimental release for the Voting System and Phasing. It enables
these features on testnet, and is a required update for all testnet nodes.

It is also possible to run this version on main net, but the block at which the
new features will be enabled has not been set yet.


New features:


Voting System.

Voting System API calls:

CreatePoll, CastVote, GetPoll, GetPolls, GetPollResult, GetPollVote,
GetPollVotes, SearchPolls.

Polls processing is optional. If nxt.processPolls=false (default is true), vote
counting is not done and no poll results are stored. This can be used to reduce
the load on lower performance nodes. It is still possible to get the results of
a poll using getPollResult, as long as the required vote and balances data
hasn't been trimmed yet.

Regardless of the nxt.processPolls setting, votes for polls that finished
before the last trim height (1441 blocks by default) are deleted and only
aggregate results, if processing is enabled, are kept.

Votes are weighted based on the voting model selected, which can be by account,
by balance, by asset balance or by currency balance, and a minimum balance
cutoff can also be specified. The voting model is defined when the poll is
created, however a different voting model can be specified when calling the
getPollResult API, to calculate on the fly an alternative vote counting, as
long as vote data is still available.

Voting multiple times, changing, or deleting votes is not allowed.

The fee to create a poll is 10 NXT for a poll with up to 20 options, with 1 NXT
additional fee for any additional option (max 100 options are possible).


Phasing.

Phasing API calls:

ApproveTransaction, GetAccountPhasedTransactions,
GetAccountPhasedTransactionCount, GetAssetPhasedTransactions,
GetCurrencyPhasedTransactions, GetPhasingPoll, GetPhasingPolls,
GetPhasingPollVote, GetPhasingPollVotes, GetVoterPhasedTransactions.

A transaction of any type can be phased by adding a phased=true parameter and
an appropriate set of phasing parameters. Phased transactions are accepted in
the blockchain immediately (subject to all usual validations), but are executed
only at finish height, if still valid and if the required quorum has been met.
If not approved, or not valid at finish height, they remain in the blockchain
but are never executed, and any changes they caused to the sender unconfirmed
balance are reversed, except that the fee is not refunded.

In addition to the voting models available in polls, phased transactions can
use a whitelist of accounts (max 10) allowed to vote for the transaction.

It is possible to vote for (approve) up to 10 phased transactions with a single
approval transaction. This transaction will be accepted in the blockchain only
if all phased transactions it is voting for are already in it.

Voting multiple times is allowed but has no effect on vote counting, votes
after the first vote from each account are ignored.

It is also possible to make any transaction phased without needing voting for
approval. This can be used to create transactions with deferred execution.

Pay on reveal secret is supported as a voting model for phased transactions.
When this voting model is used, the phased transaction must include the
hash of a secret chosen by the sender (up to 100 bytes long), and an approval
transaction for it is only accepted if it includes the secret that results in
this hash. It does not matter who the sender of the approval transaction is,
unless a whitelist is also defined. Supported hash functions currently are
sha256, ripemd160, and sha256 followed by ripemd160. The codes to specify them
as parameters are available from the getConstants API.

Finally, it is possible to make a phased transaction that is released or
rejected not on the basis of voting, but based on the presence of other
transactions (linked transactions) in the blockchain at its finish height.
To do that, up to 10 phasingLinkedFullHash transaction hashes can be defined
when creating the phased transaction. Note that this does not create a
dependency between the linked transactions themselves. This feature can be
used to implement atomic execution of transactions of any type, provided the
phased transaction is phasing safe. Transactions already in the blockchain
before the acceptance of the phased transaction can also be linked, as long
as they are not more than 60 days old, or themselves phased transactions.

The deferred execution with no approval needed, pay on reveal secret, and
linked transactions features are currently accessible using the API only, the
UI for them will be completed in a later release.

Similar to voting, the phasing data for phased transaction that finished before
the last trim height is also deleted and only the aggregate approval results
are kept.

The fee for making a transaction phased depends on the voting model selected.
For by-account voting with no minimum balance, or no voting needed, it is 1 NXT
in addition to the regular fee for that particular transaction type. For voting
that depends on voter balances, the additional phasing fee is 20 NXT.

The fee for approving a phased transaction is 1 NXT for each phased
transaction included in the vote.


Variable size messages, encrypted messages, digital goods deliveries. After VS
block, messages and encrypted messages will be allowed to be up to 40 kbytes
long instead of 1000 bytes, with 1 NXT fee for each 1024 bytes. Digital goods
deliveries can also be up to 40 kbytes, with 1 NXT fee for each 1024 bytes
after the first 10k. A single transaction is always limited not to exceed the
maximum block payload length, currently 255 * 176 bytes.


Other new APIs:

GetOrderTrades - given an askOrder, bidOrder, or both, returns all trades that
were executed as a result of this order.

GetDGSExpiredPurchases - returns the purchases for a given seller which have
expired without being delivered.

GetDGSTagsLike - returns all Digital Goods Store tags starting with a given
(at least 2 characters long) prefix.

GetAliasesLike - returns all Aliases starting with a given (at least 2
characters long) prefix.

SearchAccounts - full text search on account info (name and description).

GetPlugins - returns a list of all installed plugins.

DumpPeers - returns all active peers of a certain version.

Shutdown - shuts down the server. Takes an optional scan parameter, if true
the derived tables are truncated and a full rescan with validation is scheduled
on next start. The resulting nxt_db folder is smaller, and a node bootstrapped
with this database is going to verify the blockchain and rebuild all derived
tables on start. While this ensures validity of the blockchain and all tables,
it cannot verify that this is the current consensus blockchain and not a fork,
therefore providing such a database for download is still not trustless.

GetLog - returns the most recent log messages, kept in a memory buffer.

GetStackTraces - returns the stack traces of the currently running threads.

Shutdown, getLog and getStackTraces require the admin password.


Changed APIs:

CreateTransaction - to facilitate debugging and to allow preparing transaction
bytes and json even for transactions that are currently invalid, if broadcast
parameter is false, all relevant transaction fields (json, bytes, hash, etc)
are still included in the result even in the case of invalid transaction.
If broadcast=true, those fields are returned only in case of successful
transaction broadcast, otherwise only the error messages are returned.
This change affects all APIs that end up creating a new transaction.

GetConstants - in addition to adding the new transaction types and subtypes,
and the voting models, the format of the resulting json has been changed.

Added optional timestamp parameter to getExchanges and getTrades.

Added optional account parameter and pagination support to getCurrencyFounders.

Always include errorCode and errorDescription in some API results that only had
an error field in case of an error.

Limit number of records returned by all APIs that support pagination to
nxt.maxAPIRecords at a time (default 100), unless the admin password is
provided or is not needed.

AddPeer adds an isNewlyAdded boolean to the returned peer json, indicating
whether the peer was not already known.


Client changes:

Extended UI in the "advanced" transaction modal dialog for every transaction
type for invoking the different variants of phased transactions (to be approved
by a certain number of accounts or balance/asset/currency holders).

New main sidebar item for the Voting System, modal to create the various types
of polls, pages to find active polls and follow polls over time, list with own
polls and votes casted.

Generic notification system for incoming transactions showing the number
of transaction types and total new transactions.

Unconfirmed transactions are only displayed in the "Dashboard" and "My Transactions"
pages and no longer appear in other tables.

Transaction info dialog for AE Bid and Ask orders now displays a table containing
the actual trades mathcing the specific order.

New account login feature for faster login just by Nxt account.

User specific client DB with new logout option to clear user data.

Streamlined sidebar/navigation structure.

Send Currency button added to the toolbar which invokes the transfer currency dialog

Environment information, client settings and various diagnostic information is logged
to the browser's JavaScript console during startup and login.

Phasing tab was added to the transaction info dialog of phased transactions.

Various bug fixes.


Client Plugin System:

Functionality - The NRS client comes with a new plugin system, enabling third
party developers to provide additional functionality for the client. Plugins
can be activated/deactivated on startup, the status of installed plugins can be
seen on a separate settings page. Plugins can hook into the new "Plugins"
sidebar navigation item or provide their own navigation structure.

Security - Plugins are not sandboxed or restricted in any way and have full
access to client functionality including the passphrase. It is essential to only
install plugins from trusted sources and in doubt don't use plugins together
with accounts storing larger amounts of NXT. There are prominent security
warnings both on the login page and within the plugins folder.

Installation - A Plugin is provided as an archived file containing the necessary
HTML/JS/CSS files and can be installed by extracting the file in the plugins/
client directory.

Developer - For a plugin to be valid is has to follow a certain minimal file
structure and be shipped with a manifest.json file with some meta information.
Detailed information can be found in the DEVELOPERS.md file in the plugins/
directory. There is also a "hello_world" example plugin to get an idea how
things work.


Other important changes:

Fixed transaction ordering in AE order matching to always be by transaction
index instead of by id, to take effect after Voting System Block.

Enforce nxt.adminPassword if set, even if the APIServer is listening on
localhost only.

Added nxt.ignorePeerAnnouncedAddress and nxt.cjdnsOnly properties, relevant
only for cjdns users or multihomed nodes.

Default initial peers are now stored in nxt.defaultPeers and
nxt.testnetDefaultPeers instead of being populated by NxtDbVersion on database
creation.

Allow the API server to handle both http and https requests on different ports,
if nxt.apiServerSSLPort is set to a port different from nxt.apiServerPort and
nxt.apiSSL=true. If the SSL and non-SSL ports are configured to be the same,
the nxt.apiSSL property determines whether SSL is used or not. On testnet,
non-SSL port is hardcoded to 6876 and SSL, if enabled, to 6877.

Reduced the default nxt.maxRollback to 800. Also added a nxt.trimFrequency
setting to control how often the trim is run, default 1000.

This release requires Java 8 and will not run or compile with Java 7.

run.bat has been updated to search for a Java 8 installation using the Windows
registry.

Updated Jetty to version 9.2.10 and Bouncy Castle to version 1.52. If unpacking
on top of a previous installation, delete the old lib folder first.

This release will perform a database upgrade with a full rescan on first start.

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

iQIcBAEBAgAGBQJVItxeAAoJEFOhyXc7+e2AGksQAJT0SolvRBp8bUPllvz4MivZ
4JirVpWQbVXaE7u3PKte3qA+UFgcaincMU1YM9YCPsHsbX9K24+fIRhblHHBoG7p
zVrqYNcE/1+uJMS0I1UFV2GDx3aFY+2lM/m4rVp8BXNGuUdNFdvAO6vW8i0bj+Ba
Rbe6Xds58YzGXZbkIuxNDnJHqlL/gBAF1q3yPuvftBx6m8nnGoOdjsVh6UDcrHTh
eeqK2hI4ZGNilwE0Coc99qIzSJi85ReE3/LANlQVac532ggVg4dK21HuB2joVtFo
wvBEcFpoeW4VdFSWWla3DRdxOOMo13OnIpIi07cWgrHH/eIG2VtZxoG3rFSyYe9s
NsVCwuV3iQxcvlU6yd4DzWprauyOKjJy0WQC0500whgJfKEZUVZeFVxlh3vLJVKN
4Jmc0cR2/hfqnpIQ6I13w8s6+UeeLnkQxmFRN9DKRICkX6PSqjejfDNjNEutCqAu
9edJ8QmVlJIUygeOjoMRZLVx4fDuxXG9UZOxu4r8DT9IfvkjX0pt5huI8uHSHIpB
tOKKV3aaELfhh2ybF7n86D+i50UAZsRUz/jSLEYfAawS6Em25hpmxk3SdRtz7Uxs
rhvD8qCyVTWeSbqtztZoUmcgWvPqDvcMqi9DTZjn2WgsoFaIBtBHzRyNjW568NYJ
9KMLLhaV6bZ6eMK3mGle
=rWe6
-----END PGP SIGNATURE-----
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: NRS v1.5.0e
« Reply #1 on: April 06, 2015, 08:08:49 pm »

+1440 to Nxt team.
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

crimi

  • Hero Member
  • *****
  • Karma: +122/-11
  • Offline Offline
  • Posts: 863
    • View Profile
Re: NRS v1.5.0e
« Reply #2 on: April 06, 2015, 08:10:23 pm »

Awesome.
Logged

msin

  • Hero Member
  • *****
  • Karma: +138/-18
  • Offline Offline
  • Posts: 1288
    • View Profile
Re: NRS v1.5.0e
« Reply #3 on: April 06, 2015, 08:12:32 pm »

Need to get my reading glasses out for this one!
Logged

dude

  • Full Member
  • ***
  • Karma: +44/-5
  • Offline Offline
  • Posts: 207
    • View Profile
Re: NRS v1.5.0e
« Reply #4 on: April 06, 2015, 08:15:58 pm »

That's one crazy changelog, GJ!  ;)
Logged

ThomasVeil

  • Hero Member
  • *****
  • Karma: +183/-11
  • Offline Offline
  • Posts: 1400
    • View Profile
Re: NRS v1.5.0e
« Reply #5 on: April 06, 2015, 08:25:03 pm »

That's one crazy changelog, GJ!  ;)

Thought the same! Wow. Good stuff.
Cheers to all contributors!
Logged
ARDOR-BPV3-837M-QZTQ-9DQ69  oxpal.com

EvilDave

  • Hero Member
  • *****
  • Karma: +341/-40
  • Offline Offline
  • Posts: 1789
    • View Profile
    • NXT Foundation
Re: NRS v1.5.0e
« Reply #6 on: April 06, 2015, 08:34:15 pm »

This is brilliant. Going to be getting 1.5 nodes up very soon. Good work, guys !

Anyone else note the change in message payloads (among the 20 other good things)....40kB is now possible per message.
Thats quite a lot and will allow all sorts of interesting things to be directly hosted on the blockchain.
Logged
Nulli Dei, nulli Reges, solum NXT
NXT Donations: NXT-BNZB-9V8M-XRPW-3S3WD
We will ride eternal, shiny and chrome!

yassin54

  • Hero Member
  • *****
  • Karma: +240/-14
  • Offline Offline
  • Posts: 2503
  • I am Homer, Sorry my english is Bad!!
    • View Profile
Re: NRS v1.5.0e
« Reply #7 on: April 06, 2015, 08:36:13 pm »

Great work!  ;D ;D

Come-from-Beyond

  • Hero Member
  • *****
  • Karma: +794/-671
  • Offline Offline
  • Posts: 4013
    • View Profile
Re: NRS v1.5.0e
« Reply #8 on: April 06, 2015, 08:46:19 pm »

Is it possible to switch an account into "all transactions must be phased" mode? This would allow to split control on the account between several entities. Without this one entity could empty the account by omitting "phased" parameter.
Logged

abuelau

  • Sr. Member
  • ****
  • Karma: +74/-1
  • Offline Offline
  • Posts: 461
    • View Profile
    • mynxt.info
Re: NRS v1.5.0e
« Reply #9 on: April 06, 2015, 08:58:56 pm »

Is it possible to switch an account into "all transactions must be phased" mode? This would allow to split control on the account between several entities. Without this one entity could empty the account by omitting "phased" parameter.

I believe this will only be possible with account control

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #10 on: April 06, 2015, 08:59:27 pm »

Yes, this is part of account control and is planned for 1.6, Petko is working on it.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

xchrix

  • Guest
Re: NRS v1.5.0e
« Reply #11 on: April 06, 2015, 09:01:11 pm »

mind blowing! i imagine several hundred hours of developing  :o
Logged

abuelau

  • Sr. Member
  • ****
  • Karma: +74/-1
  • Offline Offline
  • Posts: 461
    • View Profile
    • mynxt.info
Re: NRS v1.5.0e
« Reply #12 on: April 06, 2015, 09:01:33 pm »

Is it possible to switch an account into "all transactions must be phased" mode? This would allow to split control on the account between several entities. Without this one entity could empty the account by omitting "phased" parameter.

I believe this will only be possible with account control

That will be a game changer for NXT. Really looking forward to it.

jones

  • Hero Member
  • *****
  • Karma: +310/-8
  • Offline Offline
  • Posts: 1043
  • write code not war
    • View Profile
    • jNxt
Re: NRS v1.5.0e
« Reply #13 on: April 06, 2015, 09:03:59 pm »

40kb message attachments + partial alias search make a project I'm thinking of much easier to accomplish :) very cool.

atomic within nxt transactions and atomic cross chain transactions open up many more doors also.
Logged
-- Jones NXT-RJU8-JSNR-H9J4-2KWKY

Come-from-Beyond

  • Hero Member
  • *****
  • Karma: +794/-671
  • Offline Offline
  • Posts: 4013
    • View Profile
Re: NRS v1.5.0e
« Reply #14 on: April 06, 2015, 09:20:18 pm »

atomic within nxt transactions and atomic cross chain transactions open up many more doors also.

Atomic within Nxt - easy.
Atomic cross-chain - I doubt.
Logged

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.0e
« Reply #15 on: April 06, 2015, 09:33:30 pm »

Congrats on the release! Always nice to see something new.

40kb message attachments + partial alias search make a project I'm thinking of much easier to accomplish :) very cool.

atomic within nxt transactions and atomic cross chain transactions open up many more doors also.

NXT+ has had partial alias search if you need it over a websocket connection. see it live

Hopefully I'll get to update it soon so all the 1.5 goodies will also be available over websockets.   ;D
Logged
HEAT: DEX | SDK | HOME

lopalcar

  • Hero Member
  • *****
  • Karma: +99/-15
  • Offline Offline
  • Posts: 561
    • View Profile
Re: NRS v1.5.0e
« Reply #16 on: April 06, 2015, 09:46:46 pm »

Finally, it is possible to make a phased transaction that is released or
rejected not on the basis of voting, but based on the presence of other
transactions (linked transactions) in the blockchain at its finish height.
To do that, up to 10 phasingLinkedFullHash transaction hashes can be defined
when creating the phased transaction. Note that this does not create a
dependency between the linked transactions themselves. This feature can be
used to implement atomic execution of transactions of any type, provided the
phased transaction is phasing safe. Transactions already in the blockchain
before the acceptance of the phased transaction can also be linked, as long
as they are not more than 60 days old, or themselves phased transactions.
This seems very interesting, but I don't know if I understanding it  :-[

I know I'm asking something "trivial" and maybe this isn't the correct place to ask... But can someone explain a little bit here how the transactions are generated? When I choose to not broadcast the transaction I get the Unsigned bytes and the signed bytes "Where does the full transaction hash and signature hash come from?, I mean, how are they derived from the transaction bytes?"
If the full transaction hash is derived from the signed transaction bytes, doesn't this hash changes when the timestamp changes? And can I broadcast a transaction once the defined deadline has elapsed, or the deadline start counting once the transaction is broadcasted and not included in the transaction bytes? :\ If so, this only gives margin for 24h for the transactions to be made?
Can this be used for cross chain transaction including for example a bitcoin transaction hash? "I have the same doubt for bitcoin: how long can a transaction stay "in paper" before it becomes outdated and not accepted by the network? I don't know either how bitcoin transactions are generated at this levels..." If so this is quite awesome  :o

Hope someone find a few minutes to answer, anyways, great work dev team!!

Logged

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.0e
« Reply #17 on: April 06, 2015, 09:53:06 pm »

nxt.cjdnsOnly

Nnever heard of hyperboria before, cool stuff, seems it's already used
Logged
HEAT: DEX | SDK | HOME

toenu

  • Full Member
  • ***
  • Karma: +52/-1
  • Offline Offline
  • Posts: 231
    • View Profile
Re: NRS v1.5.0e
« Reply #18 on: April 06, 2015, 10:09:52 pm »

Many, many excellent changes, thank you.

One issue: when trying to send a phased transaction I got the error "Transaction is not signed yet". (When accessing the node over its IP).
The same thing on localhost worked without problem.
Logged

apenzl

  • Hero Member
  • *****
  • Karma: +247/-10
  • Offline Offline
  • Posts: 2497
    • View Profile
    • Nxter.org
Re: NRS v1.5.0e
« Reply #19 on: April 06, 2015, 10:25:47 pm »

Hail to the Nxt core kings, baby. Thanks.  8)

HCLivess

  • Hero Member
  • *****
  • Karma: +121/-47
  • Offline Offline
  • Posts: 521
  • Hardcore Gaming CEO
    • View Profile
Re: NRS v1.5.0e
« Reply #20 on: April 06, 2015, 10:47:11 pm »

In NXT we trust
Logged
Producing, Lending, Mining, Trading, Forging, Staking

superresistant

  • Sr. Member
  • ****
  • Karma: +29/-3
  • Offline Offline
  • Posts: 327
    • View Profile
Re: NRS v1.5.0e
« Reply #21 on: April 07, 2015, 06:28:08 am »

neoranga

  • Jr. Member
  • **
  • Karma: +5/-0
  • Offline Offline
  • Posts: 34
    • View Profile
Re: NRS v1.5.0e
« Reply #22 on: April 07, 2015, 06:48:21 am »

Amazing release! Congratulations to all the devs involved.
Logged

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.5.0e
« Reply #23 on: April 07, 2015, 08:46:06 am »

Now we can vote! ;D i pick the Vote by NXT Balance in the create poll form, when i click on the transaction - voting_model:   Vote by Account  ::)

what does it mean Transaction is not signed yet, i try to send a transaction approved by a certain number of accounts and enter my second account in the Accounts (Whitelist) form as an approver but i am unable to send this transaction.
« Last Edit: April 07, 2015, 09:12:16 am by lurker10 »
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #24 on: April 07, 2015, 09:26:12 am »

Now we can vote! ;D i pick the Vote by NXT Balance in the create poll form, when i click on the transaction - voting_model:   Vote by Account  ::)
This is a UI bug in the transaction info. The poll is actually created correctly, with voting model 1 (by NXT balance).

Quote
what does it mean Transaction is not signed yet, i try to send a transaction approved by a certain number of accounts and enter my second account in the Accounts (Whitelist) form as an approver but i am unable to send this transaction.
I suspect this is again a UI bug, when running on a remote node and signing transactions locally (in javascript), somebody already reported the same problem. Must be because I changed the phasing and approving transactions byte format to add the by-transaction and by-hash options.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #25 on: April 07, 2015, 09:39:54 am »

Finally, it is possible to make a phased transaction that is released or
rejected not on the basis of voting, but based on the presence of other
transactions (linked transactions) in the blockchain at its finish height.
To do that, up to 10 phasingLinkedFullHash transaction hashes can be defined
when creating the phased transaction. Note that this does not create a
dependency between the linked transactions themselves. This feature can be
used to implement atomic execution of transactions of any type, provided the
phased transaction is phasing safe. Transactions already in the blockchain
before the acceptance of the phased transaction can also be linked, as long
as they are not more than 60 days old, or themselves phased transactions.
This seems very interesting, but I don't know if I understanding it  :-[

I know I'm asking something "trivial" and maybe this isn't the correct place to ask... But can someone explain a little bit here how the transactions are generated? When I choose to not broadcast the transaction I get the Unsigned bytes and the signed bytes "Where does the full transaction hash and signature hash come from?, I mean, how are they derived from the transaction bytes?"
The full hash is derived from all transaction bytes, but with signature bytes removed, and signature hash added instead. This way anyone can verify that the full transaction hash indeed matches this transaction, yet they cannot broadcast it without having the actual signature.
Quote
If the full transaction hash is derived from the signed transaction bytes, doesn't this hash changes when the timestamp changes? And can I broadcast a transaction once the defined deadline has elapsed, or the deadline start counting once the transaction is broadcasted and not included in the transaction bytes? :\ If so, this only gives margin for 24h for the transactions to be made?
You cannot change the timestamp after creating and signing the transaction, because indeed it would change the full hash and require the transaction to be signed again.
The deadline is included in the transaction bytes and is relative to the timestamp, not to the actual broadcasting time. Yes, it currently gives you only a margin of 24 hours, but I will change that in the next 1.5 version and remove the limitation on max deadline (32767 minutes instead of 1440).
Quote
Can this be used for cross chain transaction including for example a bitcoin transaction hash? "I have the same doubt for bitcoin: how long can a transaction stay "in paper" before it becomes outdated and not accepted by the network? I don't know either how bitcoin transactions are generated at this levels..." If so this is quite awesome  :o

Hope someone find a few minutes to answer, anyways, great work dev team!!
No, not for cross chain, those transaction hashes make sense on our blockchain only. I don't actually know how bitcoin handles timestamp and deadlines of transactions either.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

shmoula

  • Full Member
  • ***
  • Karma: +18/-4
  • Offline Offline
  • Posts: 136
    • View Profile
    • Homepage
Re: NRS v1.5.0e
« Reply #26 on: April 07, 2015, 09:40:38 am »

Java 8? Are you joking? What is the reason for this unwise step?
Logged
NXT-EZHL-B8FR-PZHS-DZZBR | Habbeat | NAWA (NXT Asset Watcher for Android) | NXTwalch (NXT Wallet balance watch)

bitcoinpaul

  • Hero Member
  • *****
  • Karma: +590/-590
  • Offline Offline
  • Posts: 3097
  • Karmageddon
    • View Profile
Re: NRS v1.5.0e
« Reply #27 on: April 07, 2015, 09:48:58 am »

Java 8? Are you joking? What is the reason for this unwise step?

What r u suggesting?
Logged
Like my Avatar? Reply now! NXT-M5JR-2L5Z-CFBP-8X7P3

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #28 on: April 07, 2015, 09:55:00 am »

40kB is now possible per message. Thats quite a lot and will allow all sorts of interesting things to be directly hosted on the blockchain.
The reason for that change was not to allow hosting more things on the blockchain, but to avoid forcing users to split their data (usually json formatted machine readable messages) across multiple AMs, connected using referenced transactions, which ultimately wastes more space and creates more processing load. If they are going to do it anyway, let them fit it in a single message, but pay the same total fee. However, I still see the problem that this makes it easier for anyone to upload things to the blockchain (you wouldn't bother to split a jpeg file into multiple messages, but with a single one it is easy), and this can create blockchain bloat. If this indeed starts happening, we may have to increase fees or think of some other solution.

I was thinking about only having the transaction signature be on a hash of the message bytes, not the actual bytes, this way if we later decide to prune those messages the transaction signatures would still verify. But this turned out to not be a simple change, and will not be done for 1.5.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #29 on: April 07, 2015, 09:57:29 am »

Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

starik69

  • Sr. Member
  • ****
  • Karma: +11/-17
  • Offline Offline
  • Posts: 301
    • View Profile
Re: NRS v1.5.0e
« Reply #30 on: April 07, 2015, 10:05:01 am »

Oh, by default it runs on mainnet ::)
Logged
NXT-R2U6-22MC-LQL2-22222 (648774468) - NXT | All versions of NXT client and more - https://mega.co.nz/#F!J1xmgAyC!cnaqdxHALLMGiS0hTPrhAg

Jimmy2011

  • Sr. Member
  • ****
  • Karma: +24/-19
  • Offline Offline
  • Posts: 329
    • View Profile
Re: NRS v1.5.0e
« Reply #31 on: April 07, 2015, 10:22:35 am »


Awsome!
Logged
NXT-LX5G-L63N-ST8S-9LVZY

shmoula

  • Full Member
  • ***
  • Karma: +18/-4
  • Offline Offline
  • Posts: 136
    • View Profile
    • Homepage
Re: NRS v1.5.0e
« Reply #32 on: April 07, 2015, 10:39:55 am »

Java 8? Are you joking? What is the reason for this unwise step?
http://www.oracle.com/technetwork/java/javase/eol-135779.html

Oh, that sounds reasonable. I heard somewhere reason like "our programmers want to try out new stuff", which drove me crazy! :)
Logged
NXT-EZHL-B8FR-PZHS-DZZBR | Habbeat | NAWA (NXT Asset Watcher for Android) | NXTwalch (NXT Wallet balance watch)

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: NRS v1.5.0e
« Reply #33 on: April 07, 2015, 11:13:41 am »

Great,can't wait to test voting.
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

capodieci

  • Hero Member
  • *****
  • Karma: +256/-19
  • Offline Offline
  • Posts: 1356
  • BlockchainZoo.com
    • View Profile
    • ZooBC - Advancing Blockchain Technology
Re: NRS v1.5.0e
« Reply #34 on: April 07, 2015, 11:27:28 am »

+32767
Logged
- Decentralised Business Network: DeBuNe -
Will be implemented on
ZooBC.com - Join the forum ZooBC.org - By Blockchain Zoo

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: NRS v1.5.0e
« Reply #35 on: April 07, 2015, 04:50:23 pm »

Logged

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.5.0e
« Reply #36 on: April 07, 2015, 06:44:16 pm »

success_poll_followed error_polls_save_db after clicking on Log out and clear user data, cannot save and follow polls no more :'(
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.5.0e
« Reply #37 on: April 07, 2015, 07:34:35 pm »

CRDTS owners poll: MIN VOTING BALANCE was set to 10 in the form. Weights show 0 even the poll creator who owns 181 currency units and should be able to cast a vote.
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

Daedelus

  • Hero Member
  • *****
  • Karma: +230/-12
  • Offline Offline
  • Posts: 3280
    • View Profile
Re: NRS v1.5.0e
« Reply #38 on: April 07, 2015, 08:44:45 pm »

Great work  ;D

You mentioned trimming a few times (every 1441 blocks by default). Is this a rolling trimming; we accept a new block, we drop an old block?

What stage is it at? Seems quite advanced.
Logged
NXT: NXT-4CS7-S4N5-PTH5-A8R2Q

Eadeqa

  • Hero Member
  • *****
  • Karma: +83/-68
  • Offline Offline
  • Posts: 1888
    • View Profile
Re: NRS v1.5.0e
« Reply #39 on: April 08, 2015, 02:30:07 am »

40kB is now possible per message. Thats quite a lot and will allow all sorts of interesting things to be directly hosted on the blockchain.
The reason for that change was not to allow hosting more things on the blockchain, but to avoid forcing users to split their data (usually json formatted machine readable messages) across multiple AMs, connected using referenced transactions, which ultimately wastes more space and creates more processing load. If they are going to do it anyway, let them fit it in a single message, but pay the same total fee. However, I still see the problem that this makes it easier for anyone to upload things to the blockchain (you wouldn't bother to split a jpeg file into multiple messages, but with a single one it is easy), and this can create blockchain bloat. If this indeed starts happening, we may have to increase fees or think of some other solution.

Yes, this will bloat the blockchain. Please fix this before official release.

Is it possible to delete old messages?
Logged
NXT-GZYP-FMRT-FQ9K-3YQGS

capodieci

  • Hero Member
  • *****
  • Karma: +256/-19
  • Offline Offline
  • Posts: 1356
  • BlockchainZoo.com
    • View Profile
    • ZooBC - Advancing Blockchain Technology
Re: NRS v1.5.0e
« Reply #40 on: April 08, 2015, 04:10:22 am »

Please fix this before official release.

Is it possible to delete old messages?

It would be cool if users could flag old data for deletion and get a credit worth 50% of the fee paid when storing the data. Data flagged for deletion gets purged from the blockchain and the account has a free transaction each 2 deleted ones.

Well it would require radical changes, but still is an idea.

R
Logged
- Decentralised Business Network: DeBuNe -
Will be implemented on
ZooBC.com - Join the forum ZooBC.org - By Blockchain Zoo

mystcoin

  • Full Member
  • ***
  • Karma: +50/-0
  • Offline Offline
  • Posts: 188
    • View Profile
Re: NRS v1.5.0e
« Reply #41 on: April 08, 2015, 05:36:10 am »

Some observations of the Voting System:

1. The Followed Polls list is lower case. I'd prefer the original case.

2. The API and the NRS Client behave differently when registering votes. The API accepts minRange value votes, but the Client treats the minRange value as no vote.

3. I was able to double vote, once in the NRS Client and immediately after in the API, but only the first transaction was confirmed, so the vote results were accurate.

4. I am allowed to vote even when I don't have the minimum balance. I am charged the transaction fee and the vote is recorded, but it is given zero weight, so the final results are correct. It would be better if I was prevented from voting and no transaction was created.

Logged

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: NRS v1.5.0e
« Reply #42 on: April 08, 2015, 05:46:04 am »

Please fix this before official release.

Is it possible to delete old messages?

It would be cool if users could flag old data for deletion and get a credit worth 50% of the fee paid when storing the data. Data flagged for deletion gets purged from the blockchain and the account has a free transaction each 2 deleted ones.

Well it would require radical changes, but still is an idea.

R
en,good idea.
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.5.0e
« Reply #43 on: April 08, 2015, 06:34:46 am »

Please fix this before official release.

Is it possible to delete old messages?

It would be cool if users could flag old data for deletion and get a credit worth 50% of the fee paid when storing the data. Data flagged for deletion gets purged from the blockchain and the account has a free transaction each 2 deleted ones.

Well it would require radical changes, but still is an idea.

R
en,good idea.
But we all know that it is impossible.
Logged

mystcoin

  • Full Member
  • ***
  • Karma: +50/-0
  • Offline Offline
  • Posts: 188
    • View Profile
Re: NRS v1.5.0e
« Reply #44 on: April 08, 2015, 07:20:05 am »

Some more observations about the Voting System:

1. The getPoll and getPolls API calls don't return minRangeValue and  maxRangeValue. These might be useful.

2. It appears that the poll creation form adds 8 decimal places to the minimum balance entered to convert NXT to NQT, which is correct, but it seems to be doing the same for assets and currencies even when there are no decimal places. Not fully confirmed.
Logged

HolgerD77

  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: NRS v1.5.0e
« Reply #45 on: April 08, 2015, 07:23:07 am »

40kB is now possible per message. Thats quite a lot and will allow all sorts of interesting things to be directly hosted on the blockchain.
The reason for that change was not to allow hosting more things on the blockchain, but to avoid forcing users to split their data (usually json formatted machine readable messages) across multiple AMs, connected using referenced transactions, which ultimately wastes more space and creates more processing load. If they are going to do it anyway, let them fit it in a single message, but pay the same total fee. However, I still see the problem that this makes it easier for anyone to upload things to the blockchain (you wouldn't bother to split a jpeg file into multiple messages, but with a single one it is easy), and this can create blockchain bloat. If this indeed starts happening, we may have to increase fees or think of some other solution.

Yes, this will bloat the blockchain. Please fix this before official release.

Is it possible to delete old messages?

Yes, I think this will definitely happen and people will find (and use) very creative ways, to store all kinds of things in the blockchain if they have the possibility to do so, see e.g.:
https://nxtforum.org/general-discussion/nice-1-5e-testing-i-just-decentralized-satoshi's-whitepaper-on-blockchain/

:-)
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.5.0e
« Reply #46 on: April 08, 2015, 08:49:59 am »

2. It appears that the poll creation form adds 8 decimal places to the minimum balance entered to convert NXT to NQT, which is correct, but it seems to be doing the same for assets and currencies even when there are no decimal places. Not fully confirmed.

Confirmed, this is a bug.
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

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.0e
« Reply #47 on: April 08, 2015, 09:08:36 am »

Great work  ;D
You mentioned trimming a few times (every 1441 blocks by default). Is this a rolling trimming; we accept a new block, we drop an old block?
What stage is it at? Seems quite advanced.

Trimming means to trim the "derived" tables. These derived tables basically hold "parsed" transactions in memory.
These tables are versioned since the same "derived" object (like an alias for instance) can have different values at different heights.
So it does not have anything to do with blockchain trimming, it's how things work internally.
Logged
HEAT: DEX | SDK | HOME

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #48 on: April 08, 2015, 09:45:07 am »

Yes, this will bloat the blockchain. Please fix this before official release.

Is it possible to delete old messages?
I agree. I am working on prunable messages now. If I can't finish it for 1.5 stable, we will have to stay with the old message size limits.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.0e
« Reply #49 on: April 08, 2015, 09:46:38 am »

I agree. I am working on prunable messages now. If I can't finish it for 1.5 stable, we will have to stay with the old message size limits.

Prunable as in blockchain pruning?
Logged
HEAT: DEX | SDK | HOME

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #50 on: April 08, 2015, 10:08:36 am »

The idea is to use a hash of the message instead of the message itself when constructing and signing the transaction bytes, then at a later point the message can be deleted but the transaction signature can still be verified.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.0e
« Reply #51 on: April 08, 2015, 10:58:37 am »

The idea is to use a hash of the message instead of the message itself when constructing and signing the transaction bytes, then at a later point the message can be deleted but the transaction signature can still be verified.

Wow wow wow.
I bow down before you.
That is so smart!

Will this be applied to all message attachments not exclusively AM?
« Last Edit: April 08, 2015, 11:12:31 am by verymuchso »
Logged
HEAT: DEX | SDK | HOME

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.0e
« Reply #52 on: April 08, 2015, 11:06:30 am »

I have been working towards integrating end-users own dropbox, box, drive etc.. accounts as a means of backend storage for on-chain messages while using the hash of that content on the chain.
But this adds a whole new set of possibilities, now you could rent out blockchain/db space for a limited set of blocks and not require any form of other external storage.

Might it be an idea to start working towards supporting other database engines like mysql for instance that can handle much larger datasets?
Logged
HEAT: DEX | SDK | HOME

Daedelus

  • Hero Member
  • *****
  • Karma: +230/-12
  • Offline Offline
  • Posts: 3280
    • View Profile
Re: NRS v1.5.0e
« Reply #53 on: April 08, 2015, 11:17:14 am »

Great work  ;D
You mentioned trimming a few times (every 1441 blocks by default). Is this a rolling trimming; we accept a new block, we drop an old block?
What stage is it at? Seems quite advanced.

Trimming means to trim the "derived" tables. These derived tables basically hold "parsed" transactions in memory.
These tables are versioned since the same "derived" object (like an alias for instance) can have different values at different heights.
So it does not have anything to do with blockchain trimming, it's how things work internally.

Gotcha  ;D
Logged
NXT: NXT-4CS7-S4N5-PTH5-A8R2Q

Come-from-Beyond

  • Hero Member
  • *****
  • Karma: +794/-671
  • Offline Offline
  • Posts: 4013
    • View Profile
Re: NRS v1.5.0e
« Reply #54 on: April 08, 2015, 11:43:12 am »

Wow wow wow.
I bow down before you.
That is so smart!

Will this be applied to all message attachments not exclusively AM?

There is no benefit to hash transactions that affect effective balance for an obvious reason.
Logged

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: NRS v1.5.0e
« Reply #55 on: April 08, 2015, 01:56:21 pm »

Yes, this will bloat the blockchain. Please fix this before official release.

Is it possible to delete old messages?
I agree. I am working on prunable messages now. If I can't finish it for 1.5 stable, we will have to stay with the old message size limits.

via Imgflip Meme Maker
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

shmoula

  • Full Member
  • ***
  • Karma: +18/-4
  • Offline Offline
  • Posts: 136
    • View Profile
    • Homepage
Re: NRS v1.5.0e
« Reply #56 on: April 08, 2015, 02:17:26 pm »

Logged
NXT-EZHL-B8FR-PZHS-DZZBR | Habbeat | NAWA (NXT Asset Watcher for Android) | NXTwalch (NXT Wallet balance watch)

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.0e
« Reply #57 on: April 08, 2015, 03:08:44 pm »

Wow wow wow.
I bow down before you.
That is so smart!

Will this be applied to all message attachments not exclusively AM?

There is no benefit to hash transactions that affect effective balance for an obvious reason.

Depends on your definition of "hash transactions".
If you replace the message appendage bytes with the hash of those bytes and sign the transaction after that, it would be as if the message contents have always been that hash.
So that brings you back at how things are right now.

Messages that are shorter than their hash output should of course not be put through this.

What is the obvious reason you are refering to?

Edit: Ahhhh i get your obvious reason. You assume I'm talking about also pruning the amount, fee, sender and recipient fields.
No that obviously cannot happen, just talking about bringing back 1000+ byte appendages to 64 bytes.
« Last Edit: April 08, 2015, 03:21:28 pm by verymuchso »
Logged
HEAT: DEX | SDK | HOME

galeki

  • Full Member
  • ***
  • Karma: +16/-2
  • Offline Offline
  • Posts: 228
    • View Profile
Re: NRS v1.5.0e
« Reply #58 on: April 08, 2015, 09:05:20 pm »

About the files storage, how about we just store magnet link in blockchain and assign it to alias.

And a separate background daemon monitoring new alias with magnet link and download them into nxt/cache/files/.

User can set the max single file size and the whole cache size, and the 'download window' (like back 260000 blocks), so no worry of disk full, and for a public node just set them all 0.

Users can use something like <img src="alias:my_good_pics"/> to show pics, and even the file is too big or too early, users can easily download them with one click on the magnet link.

Of course we can replace magnet link with something else, maybe something more sophisticated.
« Last Edit: April 08, 2015, 09:11:11 pm by galeki »
Logged

allwelder

  • Hero Member
  • *****
  • Karma: +196/-13
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
Re: NRS v1.5.0e
« Reply #59 on: April 08, 2015, 11:21:28 pm »

Start run.bat,it disappeared instantly ???
Need I pr-set something,such as testnet?
Logged
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

coretechs

  • Sr. Member
  • ****
  • Karma: +161/-1
  • Offline Offline
  • Posts: 436
    • View Profile
Re: NRS v1.5.0e
« Reply #60 on: April 09, 2015, 12:26:15 am »

I put up an instance of nxtportal on testnet.

http://test.nxtportal.org
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

longzai1988

  • Sr. Member
  • ****
  • Karma: +44/-1
  • Offline Offline
  • Posts: 268
    • View Profile
Re: NRS v1.5.0e
« Reply #61 on: April 09, 2015, 04:34:41 am »

Start run.bat,it disappeared instantly ???
Need I pr-set something,such as testnet?

You need java 8
Logged
10533725144527397164 NXT-HSBE-8PWL-CUCD-BHUD6
NXT Multigateway - http://multigateway.com/

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: NRS v1.5.0e
« Reply #62 on: April 09, 2015, 06:31:36 am »

Great work,my confidence increase more,just buy more NXT.
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.0e
« Reply #63 on: April 09, 2015, 07:21:09 am »

About the files storage, how about we just store magnet link in blockchain and assign it to alias.
And a separate background daemon monitoring new alias with magnet link and download them into nxt/cache/files/.
User can set the max single file size and the whole cache size, and the 'download window' (like back 260000 blocks), so no worry of disk full, and for a public node just set them all 0.
Users can use something like <img src="alias:my_good_pics"/> to show pics, and even the file is too big or too early, users can easily download them with one click on the magnet link.
Of course we can replace magnet link with something else, maybe something more sophisticated.

Sounds like a great idea, if it's possible, not very much familiar with the bittorrent protocol.
When using torrent desktop client I remember there being a maximum to the number of active torrents, if this mechanism where to be used then it must be able to handle the possibly ten/hundreds of  thousands of individual active torrents.
Perhaps hadoop would be a good fit for this scenario.
Logged
HEAT: DEX | SDK | HOME

mystcoin

  • Full Member
  • ***
  • Karma: +50/-0
  • Offline Offline
  • Posts: 188
    • View Profile
Re: NRS v1.5.0e
« Reply #64 on: April 09, 2015, 09:15:16 am »

Some more observations about the Voting System getPollResult API call:

1. The call returns an integer when weight is 0. It probably should be an empty string for consistency.

2. My understanding is that if I don't specify the parameters holding, votingModel, minBalance and minBalanceModel then the returned results are based on the original values specified when the poll was created.  It might be better if the call returns votingModel, minBalance and minBalanceModel (holding is already returned) so I could see what the results are based on without making a separate call to getPoll.

Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #65 on: April 09, 2015, 02:38:44 pm »

The idea is to use a hash of the message instead of the message itself when constructing and signing the transaction bytes, then at a later point the message can be deleted but the transaction signature can still be verified.
Done,. seems to work, for both plain and encrypted messages. Need to test more, and decide what the limits and fees should be.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #66 on: April 09, 2015, 05:32:07 pm »

Some more observations about the Voting System getPollResult API call:

1. The call returns an integer when weight is 0. It probably should be an empty string for consistency.
For the "result", empty string is different from 0. Empty string means no one selected a value for that option, while 0 means the sum of all values selected for it is 0.
For weight, the meaning is the number of the votes (weighted) cast for that option, there is no need for a special null value (empty string) here.

Quote
2. My understanding is that if I don't specify the parameters holding, votingModel, minBalance and minBalanceModel then the returned results are based on the original values specified when the poll was created.  It might be better if the call returns votingModel, minBalance and minBalanceModel (holding is already returned) so I could see what the results are based on without making a separate call to getPoll.
Will add in the next release.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

mystcoin

  • Full Member
  • ***
  • Karma: +50/-0
  • Offline Offline
  • Posts: 188
    • View Profile
Re: NRS v1.5.0e
« Reply #67 on: April 09, 2015, 06:43:09 pm »

Some more observations about the Voting System getPollResult API call:

1. The call returns an integer when weight is 0. It probably should be an empty string for consistency.
For the "result", empty string is different from 0. Empty string means no one selected a value for that option, while 0 means the sum of all values selected for it is 0.
For weight, the meaning is the number of the votes (weighted) cast for that option, there is no need for a special null value (empty string) here.
Okay, then it would still be more consistent to return string "0" rather than integer 0, since non-zero weights are returned as strings.
Logged

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: NRS v1.5.0e
« Reply #68 on: April 09, 2015, 09:46:56 pm »

Some more observations about the Voting System getPollResult API call:

1. The call returns an integer when weight is 0. It probably should be an empty string for consistency.
For the "result", empty string is different from 0. Empty string means no one selected a value for that option, while 0 means the sum of all values selected for it is 0.
For weight, the meaning is the number of the votes (weighted) cast for that option, there is no need for a special null value (empty string) here.
Okay, then it would still be more consistent to return string "0" rather than integer 0, since non-zero weights are returned as strings.

Wouldn't it make more sense to return those as numbers?
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #69 on: April 09, 2015, 10:13:02 pm »

They are longs and can cause overflow in javascript, this is why they are returned as strings.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

grewalsatinder

  • Hero Member
  • *****
  • Karma: +89/-3
  • Offline Offline
  • Posts: 527
    • View Profile
Re: NRS v1.5.0e
« Reply #70 on: April 10, 2015, 04:14:52 am »

So, MultiSig is available in this NRS release or still in testnet?

if availble in this NRS release, how do we use it?
Anyway, if it's still in testnet, I'd still like to know how to use it in testnet? Any wiki, article, guide etc. if MultiSig is available at any network (main or testnet)?
Logged
NXT-QK5L-7YM9-YPVF-55GL5 - Twitter: https://twitter.com/satindergrewal

mystcoin

  • Full Member
  • ***
  • Karma: +50/-0
  • Offline Offline
  • Posts: 188
    • View Profile
Re: NRS v1.5.0e
« Reply #71 on: April 10, 2015, 05:50:21 am »

So, MultiSig is available in this NRS release or still in testnet?

if availble in this NRS release, how do we use it?
Anyway, if it's still in testnet, I'd still like to know how to use it in testnet? Any wiki, article, guide etc. if MultiSig is available at any network (main or testnet)?

NRS v1.5.0e is an experimental release for testing on the Testnet. There is a wiki page with instructions for using the Testnet: https://wiki.nxtcrypto.org/wiki/Testnet

There is no wiki page yet for phasing. It is discussed in the first post of this thread and here: https://nxtforum.org/general/2-phased-transactions-post-implementation-specification/
Logged

lucky88888

  • Hero Member
  • *****
  • Karma: +42/-14
  • Offline Offline
  • Posts: 694
  • NXT-E328-UJDF-KTGH-9C6YQ
    • View Profile
Re: NRS v1.5.0e
« Reply #72 on: April 10, 2015, 10:01:41 am »

where is start forging button for this release?
Logged
NXT-E328-UJDF-KTGH-9C6YQ
8897013707391239174

HolgerD77

  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: NRS v1.5.0e
« Reply #73 on: April 10, 2015, 11:40:16 am »

where is start forging button for this release?

Only displayed when logged in with passphrase, ask @MrV for further information, has to do with account login changes.
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

toenu

  • Full Member
  • ***
  • Karma: +52/-1
  • Offline Offline
  • Posts: 231
    • View Profile
Re: NRS v1.5.0e
« Reply #74 on: April 10, 2015, 05:44:28 pm »

The hello world plugin has a file html/modals/hello_world.html with some info. Where is this being displayed in the client, if at all? Wasn't able to find it.
Logged

toenu

  • Full Member
  • ***
  • Karma: +52/-1
  • Offline Offline
  • Posts: 231
    • View Profile
Re: NRS v1.5.0e
« Reply #75 on: April 10, 2015, 06:59:02 pm »

One issue: when trying to send a phased transaction I got the error "Transaction is not signed yet". (When accessing the node over its IP).
The same thing on localhost worked without problem.

Maybe related: Generating tokens also doesn't work when accessing remotely. Error: Secret phrase not specified.
Logged

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: NRS v1.5.0e
« Reply #76 on: April 10, 2015, 07:48:30 pm »

They are longs and can cause overflow in javascript, this is why they are returned as strings.

Didn't we restrict them to between -100 and 100 (even less but I forget the exact number)?
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #77 on: April 10, 2015, 07:59:06 pm »

They are longs and can cause overflow in javascript, this is why they are returned as strings.

Didn't we restrict them to between -100 and 100 (even less but I forget the exact number)?
The result is the total sum of them, each multiplied by the vote weight for each (number of nqt/assets/currency), so it can become quite large.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

LiQio

  • Hero Member
  • *****
  • Karma: +50/-5
  • Offline Offline
  • Posts: 672
    • View Profile
    • NxtLoader for Windows
Re: NRS v1.5.0e
« Reply #78 on: April 10, 2015, 08:52:57 pm »

I don't know if this has been asked/tested before:

Assuming that the typical home user runs an always-on anti virus scanner without excluding database files (specifically nxt.h2.db), and further assuming that the new possibility of storing a lot of data leads to bad guys deliberately storing malware (or malware patterns) on the bockchain -> could this be used to trigger alarms? Or is the data somehow packaged or encoded (or whatever) and should therefore not raise virus alerts?

HolgerD77

  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: NRS v1.5.0e
« Reply #79 on: April 11, 2015, 08:22:14 am »

The hello world plugin has a file html/modals/hello_world.html with some info. Where is this being displayed in the client, if at all? Wasn't able to find it.

Can't remember if I just forgot to add a button for this or if I just filled this a bit as a stub to demonstrate how a modal file for a plugin look like.
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: NRS v1.5.0e
« Reply #80 on: April 11, 2015, 08:51:36 am »

They are longs and can cause overflow in javascript, this is why they are returned as strings.

Didn't we restrict them to between -100 and 100 (even less but I forget the exact number)?
The result is the total sum of them, each multiplied by the vote weight for each (number of nqt/assets/currency), so it can become quite large.

I remember now. Thanks.
Logged

mikesbmw

  • Hero Member
  • *****
  • Karma: +41/-6
  • Offline Offline
  • Posts: 590
    • View Profile
Re: NRS v1.5.0e
« Reply #81 on: April 11, 2015, 01:42:53 pm »

My NRS won't start and shows these messages:

2015-04-11 15:35:25 FINE: Database connection pool current size: 2
2015-04-11 15:35:25 FINE: Will apply sql:
DROP TABLE IF EXISTS poll
2015-04-11 15:35:25 FINE: Will apply sql:
DROP TABLE IF EXISTS vote
2015-04-11 15:35:25 FINE: Will apply sql:
CREATE TABLE IF NOT EXISTS vote (db_id IDENTITY, id BIGINT NOT NULL, poll_id BIG
INT NOT NULL, voter_id BIGINT NOT NULL, vote_bytes VARBINARY NOT NULL, height IN
T NOT NULL)
2015-04-11 15:35:25 FINE: Will apply sql:
CREATE UNIQUE INDEX IF NOT EXISTS vote_id_idx ON vote (id)
2015-04-11 15:35:25 FINE: Will apply sql:
CREATE UNIQUE INDEX IF NOT EXISTS vote_poll_id_idx ON vote (poll_id, voter_id)
2015-04-11 15:35:25 FINE: Will apply sql:
CREATE TABLE IF NOT EXISTS poll (db_id IDENTITY, id BIGINT NOT NULL, account_id
BIGINT NOT NULL, name VARCHAR NOT NULL, description VARCHAR, options ARRAY NOT N
ULL, min_num_options TINYINT, max_num_options TINYINT, min_range_value TINYINT,
max_range_value TINYINT, finish_height INT NOT NULL, voting_model TINYINT NOT NU
LL, min_balance BIGINT, min_balance_model TINYINT, holding_id BIGINT, height INT
 NOT NULL)
2015-04-11 15:35:25 FINE: Will apply sql:
CREATE TABLE IF NOT EXISTS poll_result (db_id IDENTITY, poll_id BIGINT NOT NULL,
 result BIGINT, weight BIGINT NOT NULL, height INT NOT NULL)
2015-04-11 15:35:25 FINE: Will apply sql:
ALTER TABLE transaction ADD COLUMN IF NOT EXISTS phased BOOLEAN NOT NULL DEFAULT
 FALSE
Logged
Number one Nxt nerd with fancy fantasies!
NXT: NXT-5MMT-RUYC-NCC9-AU8BL

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.5.0e
« Reply #82 on: April 11, 2015, 02:37:26 pm »

Just wait, this step takes some time.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: NRS v1.5.0e
« Reply #83 on: April 11, 2015, 05:16:09 pm »

Quote
This release will perform a database upgrade with a full rescan on first start.
Is there a reason for not starting the API server until this is complete? I believe the server can run before the full block-chain is downloaded, in which case it can't do much but at least the HTML user interface gets shown.
Logged

rubenbc

  • Hero Member
  • *****
  • Karma: +187/-3
  • Offline Offline
  • Posts: 1304
  • I'm here and you?
    • View Profile
Re: NRS v1.5.0e
« Reply #84 on: April 13, 2015, 08:41:32 am »

I like so much.
this is a turning point . excellent work team ;)
Pages: 1 2 3 ... 5 [All]
 

elective-stereophonic
elective-stereophonic
assembly
assembly