Skip to main content

Timeline for EOS authentication

Current License: CC BY-SA 4.0

10 events
when toggle format what by license comment
May 16, 2018 at 0:36 comment added Leo Ribeiro awwww man... You are absolutely right. I finally understood how eosjs-keygen works and yes, it's definitely a matter of policy and communication! Thank you for bring it up to my sight!
May 15, 2018 at 12:28 comment added Ariel Scarpinelli Yeah. But that is a matter of trust and proper policy and communication. The private key must never travel the internet. For the case you also trust Scatter devs not to do whatever they want with your key. In any case I say that you should support it or any other competitors, just not lock in to it if you want to reduce friction
May 14, 2018 at 18:58 comment added Leo Ribeiro That I understand, but are you going to give your PK to the application when you need to sign a transaction? Let's say a simple one like comment or vote. When you have scatter you have a popup to confirm the transaction you are signing and the app never sees your PK.
May 14, 2018 at 18:55 comment added Ariel Scarpinelli @LeoRibeiro you can do all that from JS. In the end your app is always calling http methods
May 14, 2018 at 18:54 comment added Ariel Scarpinelli @altShiftDev, edited to add a comment regarding clearing cache.
May 14, 2018 at 18:53 history edited Ariel Scarpinelli CC BY-SA 4.0
Added explanation about browser cache clear
May 14, 2018 at 18:48 comment added altShiftDev localstorage is not a permanent solution, if the browsers cache is cleared this will go too. This is why most methods involve some sort of browser extension. Either you'll have to ask them to back it up properly, which creates friction or rely on a more robust method.
May 14, 2018 at 12:55 comment added Leo Ribeiro but how are you going to sign transactions and interact with the application?
May 14, 2018 at 12:55 comment added Alex Gonzalez That's an interesting workaround, although it would be bad to tell users that they are screwed if they ever clear the browser cache.
May 14, 2018 at 11:34 history answered Ariel Scarpinelli CC BY-SA 4.0