You are viewing a single comment's thread from:
RE: Why does steem use this canonical thing instead of strict secp256k1?
To clarify why I mentioned "it" took me 2years to figure it out.
- I did not work full time on this project but in my spare time whenever I felt like dealing with crypto and not with my thesis.
- it actually is the whole python-library stack that not only does the signing but also the serialization. I wanted it to be as flexible as possible and that is why it took so long.
I fully comprehend the volume of work you had to do and that's entirely what I disagree with.
The ecosystem would be much larger if these things were less mysterious. Imagine that you'd been able to get it finished in a month-- imagine what you might've built then?
do you support return data as json format now in piston?