elective-stereophonic
elective-stereophonic
NRS v1.5.0e singapore
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 25359 times)

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

elective-stereophonic
elective-stereophonic
assembly
assembly