# Free to Use Decentralised Tinder.

Users will create a profile that will be stored on Swarm and accessed via a digital wallet.

### Web3 Users

Simply use their existing wallet to interact with Swarm to create and access their profile.

### Web2 Users

A web3 wallet needs to be created for this user group so they can interact with Swarm, to create and access their profile.

***Temporary Wallets - There are solutions available, where a temporary wallet is created within a mobile browser. This wallet stays active until the browser tab is closed. ***

#### Wallet saved locally to Device/App

This solution works on the premise that the user will only have access to their profile (that is stored on Swarm), while they have access to their device. It is also based on the assumption that a temporary wallet designed for a web browser, can be enhanced so can be saved more locally and permanently, on a device.

#### Possible Solutions to Profile recovery?

- Currently users will access their profiles, because Swarm will recognise the wallet interacting with the protocol. If a user loses access to their wallet they lose access to their profile. Could a temporary/local wallet be created where the private key could be set to mobile # or email and 2fa. This way a web2 user could acccess their wallet

-Issue - storage of data like emails and mobiles. Centralisied etc.

- Alternatively an RPC**/portal on Swarm that would allow users to access their profile with an email/mobile & 2fa, which then links to their new temporary wallet.

## Profile Creation on Swarm.

Users will create a profile containing images and text, which will be stored on Swarm. When a profile is being constructed, it will be stored locally on the device (either via the app or dapp window/tab). At the point of profile generation, BZZ will need to be purchased/provided to facilitate the upload to the network.

## Accessing Profiles on Swarm.

An RPC**/portral will need to be built so user profiles stored on swarm, can only be accessed by the wallet that created it (also, to point above about web2 credentials access/recovery!?)

** is this the right terminology?