How to make real-time ⚡️, multiplayer 🧑‍🤝‍🧑, cross-device compatible 💻📱🥽 WebXR experiences. A thread based on a 3-part blog post I've written: https://t.co/ASxm8OH85k 🧵👇

The first section in the video is the @threejs editor 🤩

How to set up Auth with Metamask using Amazon Cognito (part 2) -

Great photo book made by my friend @andybillman1 👇

If you enjoyed this thread, you may enjoy the other topics I write about on my blog. Here is the link if you want to check it out :D https://t.co/j77qXRwUGY

Step 8: Your user has completed Auth!! Yay you've done it :D The user can now access your dApp and can now interact with your AWS Back End APIs / Smart Contracts!!

Step 7: Generate Cognito Identity credentials Using that Amazon Cognito Identity, we will now using AWS Security Token Service (STS) to generate a temporary set of Identity Access Management (IAM) credentials and then return these to the Front End.

Step 6: Generate / retrieve Cognito Identity Since we have validated a genuine user, we now want to generate access credentials for that user. We do this by retrieving that public address’s Amazon Cognito Identity, if one does not exist then we will generate one for them.

Step 5: Validate signature Once the Back End receives your signature, nonce and address – it can then start the process of validating the signature.

Step 4: Log in with signature & public address Now you have a valid signature, you pass this to the Back End, along with the nonce and your public address via a POST method.

Step 3: Sign message with nonce & private key Back on the Front End, we call a function called web3.eth.person.sign() – and pass the nonce and the users address into it, this will trigger a Metamask pop up to appear with these parameters encrypted.

Step 2: Get / create nonce Once the users account address has been retrieved, we then need to get a nonce (random string of characters) that we can then use for the user to sign and prove they are the owner of the account that created the signature.

Step 1: Get account address A user clicks the log in button on your website, this triggers a call to MetaMask to get your account address.

Web3 Auth allows users to self custody their log in details and remove the need for passwords. We can extend this capability with Web2 platforms, by providing these Web3 users with access credentials based on their account's address. I'll summarise how to do this in 8 steps 👇

Steps to implement Web3 Auth with Ethereum, Metamask and AWS 🧵 Full details on: https://t.co/6Bf8bhcK91 #ethereum #eth #crypto #blockchain #serverless #aws #javascript #MetaMask

Gotta buy that sweet sweet dip!!! 😋

Met a great Guy at @coinbureau live! 😀 #Bitcoin

At Coin Bureau Live!!! :D @coinbureau

Web3 Eth Auth ⛓️ with MetaMask 🦊 and AWS 💭 Oversimplified 🙂 vs Overdetailed 🙃 #ethereum #blockchain #crypto #eth #metamask #aws #amazonwebservices #amazoncognito #dynamodb #serverless #terraform #serverlessframework

New Wrapper.js template 🍫: Web3 login with MetaMask 🦊 and Amazon Cognito 🔐 https://t.co/LA1xLndyIf #web3 #eth #solidity #crypto #blockchain #aws

A coffee table with printed cast-in hexagon panels that can be individually illuminated [read more: https://t.co/k8iCaZqA34] [video: https://t.co/IbcKjVhIG8] https://t.co/W9QHRYUjdC