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 4 5  All

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

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: 1360
  • 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
Pages: 1 [2] 3 4 5  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly