Increasing the size of the value field
Posted: Thu May 31, 2012 10:06 pm
The issue 3 will need an update of all namecoin clients to be fixed.
Due to this bug, a name_update will fail if previous name_update or name_firstupdate used a value with more than 520 characters. Yes, you read it right...
So, I think we should "benefit" from this forced upgrade to increase the maximum number of characters for the value field, because we already need a general upgrade.
Why ?
Some possible namecoin usages are already limited by this, like GPG. See https://dot-bit.org/Personal_Namespace#Notes.
Other
Is it dangerous for the network ?
Each transaction above 1K will always have fee, for each 1K of data. If fees are set to the right value, they will do their job.
Each transaction above 10K will be rejected (another network rules).
How many characters ?
I propose to set it to 9000 characters max to allow 8k gpg keys with some other data.
What do you think ?
Should we adjust default fees ?
Defaults fees are now at 0.005NMC. Are they still right with merged mining and name costing 0.01NMC ?
Due to this bug, a name_update will fail if previous name_update or name_firstupdate used a value with more than 520 characters. Yes, you read it right...
So, I think we should "benefit" from this forced upgrade to increase the maximum number of characters for the value field, because we already need a general upgrade.
Why ?
Some possible namecoin usages are already limited by this, like GPG. See https://dot-bit.org/Personal_Namespace#Notes.
Other
Is it dangerous for the network ?
Each transaction above 1K will always have fee, for each 1K of data. If fees are set to the right value, they will do their job.
Each transaction above 10K will be rejected (another network rules).
How many characters ?
I propose to set it to 9000 characters max to allow 8k gpg keys with some other data.
What do you think ?
Should we adjust default fees ?
Defaults fees are now at 0.005NMC. Are they still right with merged mining and name costing 0.01NMC ?