Authentication
There are two options available to users to login and use the platform:
Traditional Sui Wallet
Oauth Wallet Login
Traditional Sui Wallet
The platform should enable all, or most, traditional wallets available for download on Chrome and other browsers.
Some examples include:
Sui Wallet
Suiet
Nightly
Stashed
but are not limited by just these options.
Leveraging a third party library (e.g. https://docs.sui.io/standards/wallet-standard) for wallet integration is essential for capturing as many wallets as possible, while allowing us to move faster and have greater security in the implementation of the wallet integration.
Oauth Wallet Login
The greatest value to the long-term growth of the Sage platform is to allow users to login with traditional oauth flows that they're already used to in web2 focused apps.
Leveraging the Enoki Flow Provider (https://docs.enoki.mystenlabs.com/ts-sdk/advanced/flow) provided by mysten makes this integration point very simple.
Sage SDK
The Sage SDK is responsible for implementing the integration to the Sage contracts, listening for events on chain, and reading data on chain.
UX / UI Design
Any application using the Sage SDK will have the ability to completely control all user flows and design aspects to match the design language appropriate for their platform.
Last updated