Re: [ANN][XCP] Counterparty Protocol, Client and Coin (built on Bitcoin) - Official
Sorry guys, looks I broke something again .... 
Apparently 100,000,000,000 is too big of a number for coins.
"I was just trying to recreate DOGE .... *slinks away*"
(Wow, how many bugfixes did I cause in github today? lol)
Apparently 100,000,000,000 is too big of a number for coins.
"I was just trying to recreate DOGE .... *slinks away*"
(Wow, how many bugfixes did I cause in github today? lol)
Still .. better that these things happen now than in the future, where things will seriously break.
Note: I would suggest a max cap, because no matter what datatype you use, someone could simply issue 999999999999999999999999999.... coins as an attack.
I haven't tested non-alphanumeric characters in the asset name yet -- is there support for that or will I crash something again?
Note: I would suggest a max cap, because no matter what datatype you use, someone could simply issue 999999999999999999999999999.... coins as an attack.
I haven't tested non-alphanumeric characters in the asset name yet -- is there support for that or will I crash something again?
Absolutely. Keep 'em comin'.
I fixed the code so that it will run, but this same problem may exist elsewhere, so hold off on re-creating the problem for another twenty-four hours, maybe.
Asset names should only be upper-case alphabetic, but the code should catch all violations of that rule.
I ran into: raise exceptions.AssetError('Bad asset name.')
Besides the uppercase is there a minimum amount/limit on characters or certain asset names that are not valid like BTC, EUR, XAU,...