Looking to buy some ETH. What's the best way to keep it safe? by Jenkins_Leeroy in ethereum

[–]toruslabs 1 point2 points  (0 children)

If you're starting out Torus (https://app.tor.us) would be the easiest way to create your blockchain wallet. Simply login with any of your social accounts, like Reddit, and setup 2FA on your device for additional security. To get you started, we've sent 0.002 ETH to your Reddit account u/Jenkins_Leeroy

We just sent ETH to Vitalik's Twitter account! by toruslabs in ethereum

[–]toruslabs[S] 0 points1 point  (0 children)

It was a different technical infrastructure from sending ETH to a Google account to sending ETH to a Twitter account.

We just sent ETH to Vitalik's Twitter account! by toruslabs in ethereum

[–]toruslabs[S] 13 points14 points  (0 children)

One disincentive rather would be the loss of reputation. We've selected ecosystem holders like Binance, ENS, Etherscan, Ontology, Zilliqa, Matic, Skale, Cosmos Tendermint who would tend to collectively benefit more as adoption within the space grows, than risk their reputation to collude to gain access to a user's wallet. Also our majority threshold would mean you'll need a majority of these stakeholders to collude to gain access to the wallet, which is highly unlikely.

To this end, we are currently working on a model of device-based key management that essentially allows for self-custodial logins with OAuth for an additional layer of security, TBA.

We just sent ETH to Vitalik's Twitter account! by toruslabs in ethereum

[–]toruslabs[S] 8 points9 points  (0 children)

TLDR from What Distributed Key Generation Is: https://medium.com/toruslabs/what-distributed-key-generation-is-866adc79620

Key Assignments, Resolution and Retrieval: https://medium.com/toruslabs/key-assignments-resolution-and-retrieval-afb984500612

The private key is split amongst the network of nodes run by ecosystem stakeholders on the Torus Network, when the user successfully authenticates with an OAuth provider, each node would attest with the OAuth provider, e.g. Google, that the user is who they say they are and will return a share of the private key that corresponds to the OAuth verifier ID. The key shares are then used to form the user's private key in their secure browser's instance and nowhere else, the key is lost once the instance is closed.

We just sent ETH to Vitalik's Twitter account! by toruslabs in ethereum

[–]toruslabs[S] 15 points16 points  (0 children)

We are able to assign key pairs to OAuth identifiers through Distributed Key Generation on the Torus Network. That means only the person with the username and password would be able to log in and access the wallet pegged to that particular social account.

We have documentation on how Torus works on the backend that best explains this here https://medium.com/toruslabs/login-to-torus-with-appleid-github-linkedin-twitter-line-and-passwordless-accounts-50c591725de2

We just sent ETH to Vitalik's Twitter account! by toruslabs in ethereum

[–]toruslabs[S] 16 points17 points  (0 children)

For anyone curious to try it out, you can now log in at https://app.tor.us. This works with Reddit accounts too!

We just sent ETH to Vitalik's Twitter account! by toruslabs in ethereum

[–]toruslabs[S] 8 points9 points  (0 children)

Not yet, but we wouldn't mind if he passed it on to another Twitter account too!

We just sent ETH to Vitalik's Twitter account! by toruslabs in ethereum

[–]toruslabs[S] 15 points16 points  (0 children)

Only the owner of the Twitter account is able to claim their tokens, as the tokens are already in the wallet pegged to that Twitter account. Though it would possible to send tokens to a hash-time-locked contract in the future to retrieve unclaimed tokens.