elective-stereophonic
elective-stereophonic
New fees and size limits in 1.7  
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.1 Upgrade before block 2870000 is mandatory!

Pages: 1 ... 4 5 [6]  All

Author Topic: New fees and size limits in 1.7  (Read 21439 times)

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: New fees and size limits in 1.7
« Reply #100 on: November 21, 2015, 09:02:13 pm »

Unless there are always a number of nodes running with a lifetime of -1 then there is a finite risk prunable data disappears forever..
I think the intention is that there will always be some archival nodes. You can help ensure that by running archival nodes yourself. Each of your server operators can run one, so you have redundancy even within the SuperNet group.

Quote
Hopefully there will be a good number of archive nodes etc.. but at the moment the health of an archive copy of NXT is unclear and at the moment no way I know to determine it
It's available for a given node with getState. I have asked for this information to be included in the client GUI peer list, and hopefully other peer explorers will start including it too. I know I run an archival node, and the devs said they did, and EvilDave said he was going to. I don't see a problem with having semi-official ones with hallmarks from community funds.

Quote
If I have to ship data copies separately and then verify it with custom software against the blockchain hashes, typically the answer to this would be to find some software that does it for me, in this case it would look a lot like a different blockchain.
I'm sorry that I was pointing out the obvious earlier; but then you say things like this, which I'm struggling to understand. Why would you need to ship data separately? If you run a node, and make sure your other nodes can see it, the NRS itself will fetch the data from it and verify the hashes. The "software that does it for you" is NRS.
Logged

xiahui135

  • Full Member
  • ***
  • Karma: +15/-11
  • Offline Offline
  • Posts: 150
    • View Profile
Re: New fees and size limits in 1.7
« Reply #101 on: November 22, 2015, 09:35:40 am »

It has been said several times that if the price goes significantly higher, we will do another poll and change the fee, just like we are doing now. Price was already 10x higher once, with the same fee, and it was not a problem. We do hard forks about every 6 months, if the price starts going solidly up we do have time to react, and in the worst case of very sudden price increase we will do another hard fork just to adjust the fees sooner.
Historically, NXT has been less volatile than other cryptocurrencies.
We just do not want another fork. It hurts.
Logged

sadface

  • Sr. Member
  • ****
  • Karma: +16/-2
  • Offline Offline
  • Posts: 273
    • View Profile
Re: New fees and size limits in 1.7
« Reply #102 on: November 22, 2015, 10:29:56 am »

regarding the post above me: has there been a discussion about what a fee could be or look like in the possibly distant future? sometimes things go very quickly in the crypto world and saying we're going to do another fork when the time comes isn't really a good answer. looking at the controversy regarding fees right now we might have a hard time rushing a hard fork to adjust the fees and depending on the price development another and then another etc
Logged

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: New fees and size limits in 1.7
« Reply #103 on: November 22, 2015, 03:01:23 pm »

The recent controversy hasn't been over fees levels as such. It's been over forcing app developers to switch to pruneable data, with the qualitative change in fee architecture one tool to encourage that. Lower size limits being another.

If everyone is following best practice, that is, using prunable data and setting the fees to 0 so the NRS calculates them, then future fee changes shouldn't cause app developers any coding work. Especially if the change is to reduce the fees rather than raise them.
Logged

chanc3r

  • Hero Member
  • *****
  • Karma: +124/-50
  • Offline Offline
  • Posts: 1019
  • NXTInspect
    • View Profile
Re: New fees and size limits in 1.7
« Reply #104 on: November 22, 2015, 10:17:18 pm »

@J-L - another one if I may...
Some characters in a JSON string need to be escaped,...
well " specifically.
so if I use a " in an AM - this will get encoded as \" in the output but I assume its 1 byte in the blockchain.

the question is - does this count as 1 character or two within the 160 limit?

and when does fee=0 take effect to mean 'use minimum fee' - is this already in place or only with 1.7?
« Last Edit: November 22, 2015, 10:55:51 pm by chanc3r »
Logged
NXT: 29996814460165 (NXT-JTA7-B2QR-8BFC-2V222)
@imrimr @NXTinspect

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: New fees and size limits in 1.7
« Reply #105 on: November 23, 2015, 09:38:12 am »

@J-L - another one if I may...
Some characters in a JSON string need to be escaped,...
well " specifically.
so if I use a " in an AM - this will get encoded as \" in the output but I assume its 1 byte in the blockchain.

the question is - does this count as 1 character or two within the 160 limit?
What matters is how it is stored in the blockchain, the escaping is in the output only. A " will take 1 byte, i.e. a message consisting of 32 " characters will fit exactly in the free limit. For permanent messages, which can be either text or binary, the size limits are currently based on their length in bytes; for other attachments such as aliases, that are text only, the limits are currently based on their character count. I see now that for aliases, texts in languages using double-byte characters will take more space than what they are being charged for, but I don't think it matters that much, those should really be a minority.

Quote
and when does fee=0 take effect to mean 'use minimum fee' - is this already in place or only with 1.7?
This has been in place since 1.5, maybe even 1.4. And this is why I keep saying that all changes needed to prepare for 1.7 can be done now, there is no need to wait for 1.7 stable.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

MrCluster87

  • Hero Member
  • *****
  • Karma: +81/-3
  • Offline Offline
  • Posts: 855
    • View Profile
    • youtube
Re: New fees and size limits in 1.7
« Reply #106 on: January 09, 2016, 05:54:13 pm »

Nxt Arbitrary Messages use case: Certified e-mails: https://www.youtube.com/watch?v=ycPv0eFJw-k

yassin54

  • Hero Member
  • *****
  • Karma: +240/-14
  • Offline Offline
  • Posts: 2503
  • I am Homer, Sorry my english is Bad!!
    • View Profile
Pages: 1 ... 4 5 [6]  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly