Instead of usernames and passwords, Magic uses blockchain-based public and private keys to authenticate users under the hood. A decentralized identifier is signed by the private key to generate a valid authentication token that can be used to verify user identity.
Traditionally, usernames are publicly recognizable identifiers that help pinpoint a user, whereas passwords are secrets that were created by the user and are supposed to be something only they know.
You can think of public and private keys as materially improved versions of usernames and passwords. The public key is the identifier and the private key is the secret. Instead of being created by users and prone to human error (e.g. weak/reused passwords), the key pair is generated via elliptic curve cryptography that has proven itself as the algorithm used to secure immense value sitting on mainstream blockchains like Bitcoin and Ethereum.
Using blockchain key pairs for authentication gives Magic native compatibility with blockchain, supporting over a dozen of blockchains. This enables blockchain developers to use Magic SDK to provide user-friendly onboarding experiences to mainstream users and tap into the potential of the rapidly expanding blockchain industry that is growing 56.1% year over year and projected to reach $69.04 billion by 2027.
The key pairs are also privacy-preserving (no personally identifiable information) and exportable. This allows user identity to be portable and owned by users themselves (self-sovereignty). The world is already moving towards this direction with novel solutions from companies like Workday and Microsoft.
As a first step, we are committed to enabling a passwordless future, by providing developers with the easiest way to integrate passwordless login methods into their apps, but having blockchain key-pairs actually connects us to other future-proof infrastructure such IPFS for decentralized user identity data storage, which will pave the way towards worldwide adoption of decentralized identity.
Pricing info is coming very soon! We'll be carrying over the pricing from our existing key management product (https://fortmatic.com/pricing) with some changes. Love to hear your feedback on the price range as we are trying to make this an optimal choice for new and growing startups.
It's actually possible to lock ourselves out as the root user and not be able to change the permissions!
Sean from Magic here! Pricing is coming very soon! We'll be carrying over the pricing from our existing key management product (https://fortmatic.com/pricing) and make slight adjustments. Love to hear your feedback on the price range as we are trying to make this an optimal choice for startups and growing companies too!
Founder of Magic here! Depends on the functionalities you are using with Auth0, as long as you can export user data including a unique email for each user into a user table, you will be able to map Magic user directly to that table, it should be relatively clean since there are no password credentials involved.
We'll work on a documentation on this and also feel free to reach out to us at hello@magic.link in the meanwhile. Would love to learn more about your use case and explore how we can help you migrate!
Sorry! Thanks for letting me know. I've updated the blog. Right now it's Mac only because Kitematic runs on Mac right now, but we are working hard on delivering a Windows version soon :)
No problem. This is still a great accomplishment. I understand that there's a lot to do to make all this happen. Although I'm actually hoping to see a Linux version :)
Hi tigeba, the current version of Kitematic is fully compatible with the latest boot2docker. Unless there are custom changes made to the boot2docker VM.
Being able to attach an existing Docker server is definitely something we are looking at :)
Hi kaylarose. Really sorry about the app being buggy and thank you for understanding that we're still very new. Previous versions of Kitematic relied on too many dependencies: VirtualBox, boot2docker, a DNS server inside the boot2docker VM and Unison for file syncing. The current version removed the need for the DNS server inside the VM and Unison, slimmed down the app and fixed a lot of the critical installer issues.
We're working hard to make the app reliable. In terms of UI, there are plans on making things more consistent and easier to understand as well.
Thank you again for trying out Kitematic! Definitely let us know if there are suggestions on things we can improve on :)
Hey, folders will be created under ~/Kitematic/app_name/volume_name, and the contents of the volume will be sync'ed across the folder and the container.
Instead of usernames and passwords, Magic uses blockchain-based public and private keys to authenticate users under the hood. A decentralized identifier is signed by the private key to generate a valid authentication token that can be used to verify user identity.
Traditionally, usernames are publicly recognizable identifiers that help pinpoint a user, whereas passwords are secrets that were created by the user and are supposed to be something only they know.
You can think of public and private keys as materially improved versions of usernames and passwords. The public key is the identifier and the private key is the secret. Instead of being created by users and prone to human error (e.g. weak/reused passwords), the key pair is generated via elliptic curve cryptography that has proven itself as the algorithm used to secure immense value sitting on mainstream blockchains like Bitcoin and Ethereum.
Using blockchain key pairs for authentication gives Magic native compatibility with blockchain, supporting over a dozen of blockchains. This enables blockchain developers to use Magic SDK to provide user-friendly onboarding experiences to mainstream users and tap into the potential of the rapidly expanding blockchain industry that is growing 56.1% year over year and projected to reach $69.04 billion by 2027.
The key pairs are also privacy-preserving (no personally identifiable information) and exportable. This allows user identity to be portable and owned by users themselves (self-sovereignty). The world is already moving towards this direction with novel solutions from companies like Workday and Microsoft.
As a first step, we are committed to enabling a passwordless future, by providing developers with the easiest way to integrate passwordless login methods into their apps, but having blockchain key-pairs actually connects us to other future-proof infrastructure such IPFS for decentralized user identity data storage, which will pave the way towards worldwide adoption of decentralized identity.