---
# System prepended metadata

title: Eve NFT Thingy

---

# Eve NFT Thingy


- Possibility for multiple wallet integration
- Login via torus/eve and then supercede that wallet with your beacon wallet (if available):
    1. Login with eve, check if the character has a wallet associated in the DB
    2. if no wallet is set in database for the character ask if they want to connect beacon wallet (user can say no or connect)
    3. Connect beacon wallet will be available always in the flyout
    4. If user ever connects beacon wallet then ask them if they want to make it their primary wallet to receive in-game NFTs if yes then store that in DB
    5. (Not sure) User can make eve address again primary -- JSN: don't think so.

- Nfts are generated and assigned to character_id and then transferred (with funds to transfer again?) when wallet is associated, or immediately transferred if there is an associated address
    - This transfer action is handled in backend

- Add reveal eve private key button to the flyout that shows user's private key in a modal (maybe with a copy icon?) --- Security issues?? Maybe don't show, shroud, and only permit copy--like a password manager. or 26 words??
- If the user is logged-in and has NFTs then show a transfer button that allows them to transfer the NFT to another address. This transfer will be triggered by the FE and will not go via backend system. The two cases (?):
    - 1: user is logged in and has nfts associated with account (not in personal wallet): no action button
    - 2: user is logged in and has already claimed nfts: transfer nfts button`contract.method.transfer`