FAQs
Can Openfort support my ecosystem's login system?#
Yes, Openfort's architecture is built to allow thousands of new gaming ecosystems flourish. You ecosystem can be added as an OAuth provider allowing your community to be recognized.
What if I can't find my authentication provider in the documentation?#
No problem, let us know which provider you want to use and we'll get right into it.
Can players use their existing wallets alongside Openfort Auth?#
Users can link existing wallets to their account. This allows you to store and share these wallet addresses with games via the SDK for read-only use.
What level of support and Service Level Agreements (SLAs) are provided?#
At Openfort, we understand the significance of maintaining a high standard of service. Our Service Level Agreements (SLAs) reflect our commitment to providing a reliable, efficient, and safe environment for your operations.
Security and Contingency Planning#
If Openfort were to shut down with a one-month notice, would there be scope to change the signer on the Smart Contract Wallet and use it in connection with a different provider that manages the private keys differently?#
TLDR: With enough time, transitioning is fairly simple. You’d need to invoke the transferOwnership
function for users to accept the new signer.
Detailed Answer: Yes, if Openfort shuts down with a one-month notice, it's possible to change the signer. Since Openfort wallets are non-custodial, users have control over their private keys. The key migration process would involve using the "recovery share" and "device share" from Shamir's Secret Sharing (SSS) to reconstruct the private key, allowing users to accept a new signer through the transferOwnership
function. The new provider would need to support compatible key management systems.
If Openfort were shut down with zero notice, would there be any scope to do a migration? Would that rely on a self-hosted Shield for the recovery share and the device share being intact?#
TLDR: If there is no self-hosted option, users should rely on on-chain social recovery.
Detailed Answer: Migration is still possible, but it depends on the self-hosted Shield for the recovery share and the availability of the device share. If a self-hosted Shield is not in place, users can utilize on-chain social recovery. As long as the device share and recovery share are intact, users can reconstruct their private key and migrate to a new provider. On-chain social recovery can also help recover the wallet if the device share is lost.
If Openfort's API were compromised, what is the risk there? Can that risk be mitigated? What’s the risk of the auth share on the private key being exposed?#
TLDR: Both Openfort's server and Shield are encrypted. Even if an attacker obtains the auth share, they would need a secret to decrypt it.
Detailed Answer: If Openfort's API were compromised, the risk is limited because both the auth share and Shield service are encrypted. Even if an attacker gains access to the auth share, they would still need to decrypt it using a secret. Furthermore, since the private key is split using Shamir's Secret Sharing, the auth share alone is insufficient to reconstruct the full key without the device or recovery share.