Switch to ArdorForum

I like this. 0.1% to a maximum of 1 NXT for regular transactions. Would make micro tx viable.

Quote from: abctc on November 17, 2015, 07:16:57 am

cheap blockchain DDoS-ing.

Such low fees are indeed dangerous. 0.1 NXT is worth 0.006 USD atm.

For just 600 dollars one could spam the blockchain with 100k transactions. This would cause a serious unconfirmed tx queue and bloat. It's not acceptable imo.
I don't see the problem with 1 Nxt or 2 Nxt fees, it's just 6 cents and 12 cents respectively.

Quote from: achim on November 17, 2015, 07:44:53 am

Quote from: abctc on November 17, 2015, 07:16:57 am

cheap blockchain DDoS-ing.

Such low fees are indeed dangerous. 0.1 NXT is worth 0.006 USD atm.

For just 600 dollars one could spam the blockchain with 100k transactions. This would cause a serious unconfirmed tx queue and bloat. It's not acceptable imo.
I don't see the problem with 1 Nxt or 2 Nxt fees, it's just 6 cents and 12 cents respectively.

I can do a tx in bitcoin with zero fees (I do this regularly) if my coins are old enough or the tx amount is big enough. There is no point for higher tx fees in Nxt, other that there must be some to prevent spam, but I don't see much difference between 1 NXT or 0.5 NXT as base fee.

You are calculating your example with 0.1 NXT but this amount is beyond dispute.

I think the account leasing time is too short. It makes it a hassle to re-lease it repeatedly (while for many people barely even the transaction fee will be made up with the rewards).
Not sure why the limit exists anyways - since one can always stop the leasing by transacting the coins to a new address. I think the allowed maximum lease period should be 6 months.

In case anyone did not pay attention:

1. There will be changes in fees and permanent message size limit in 1.7. They will take effect in the 1.7 hard fork, in very early January 2016.

2. These changes will break any application that has hardcoded fees of 1 NXT, or uses permanent messages exceeding 160 bytes.

3. THESE CHANGES HAVE BEEN ANNOUNCED ALREADY, AND ALL API USERS CAN, AND ABSOLUTELY MUST START UPDATING THEIR CODE NOW. DO NOT WAIT UNTIL 1.7 STABLE IS RELEASED, AND THEN COMPLAIN THAT YOU HAVE NOT BEEN GIVEN ENOUGH NOTICE. START UPDATING TO 1.6.2, USE SERVER-SIDE FEE CALCULATION, AND EITHER SWITCH TO PRUNABLE MESSAGES, OR MAKE SURE PERMANENT MESSAGE SIZE DOES NOT EXCEED 160 BYTES.

4. To repeat. Do not wait until 1.7.1 stable, and then blame the developers for not giving sufficient advance notice once it is suddenly released and the hard fork is right around the corner. THIS IS THE ADVANCE NOTICE.

Technical questions about the transition should be discussed here: https://nxtforum.org/core-development-discussion/adapting-client-side-code-to-the-fee-changes-planned-for-1-7/

In the past it wasnt clear what the exact limits are. Until the exact parameters are known, it is not easy for someone like me to make changes to meet such unknown parameters.

My limited intellect cannot fathom a reason why it makes sense to reject a 161 byte permanent message and an extra base fee. Since some of the MGW messages exceeds 160 bytes (not many), this means it will need to be changed to make sure it never exceeds 160 bytes, instead of just paying the extra fee for the rare cases over 160 bytes

James

I think the account leasing time is too short. It makes it a hassle to re-lease it repeatedly (while for many people barely even the transaction fee will be made up with the rewards).
Not sure why the limit exists anyways - since one can always stop the leasing by transacting the coins to a new address. I think the allowed maximum lease period should be 6 months.