@williambanks has taken on the challenge. He estimates 5 days of work for him alone. Anyone interested is invited to work with him and share the bounty.
You are viewing a single comment's thread from:
@williambanks has taken on the challenge. He estimates 5 days of work for him alone. Anyone interested is invited to work with him and share the bounty.
Yep! I'm breaking the work down into a project. Opening issues on github as we speak.
https://github.com/steembots/steemsign/issues
Feel free to hop in and claim some, you get up to a 12 hour lock on any issue you want to tackle.
Pay will be proportional to the number of issues you tackle and complete over the next 5 days. So no worries and a lot of this can be done in parallel.
@trogdor has been rocking this hard and completing tasks so much faster than I can code review. I just wanted to invite everyone to congratulate him.
@pharesim This is very nearly code complete. Would you please check https://github.com/steembots/steemsign and let us know if that part is working correctly for your use case?
The only remaining issues are ECC and serializing. They will very likely be closed in the original time frame. I'm going to hold off on isolating the signing process into a webworker and using crypto.subtle for key protection because those really are implementation specific details that will just over complicate things at this point. Also chrome doesn't support passing a typed array to a webworker for some stupid reason.