The problem TomaaS solves

Own or Stake shared mobility asset in TomaaS

1. The Problems :

• Capital issue : Starting a shared mobility business is often associated with significant financial barriers, making it challenging for new players to enter the market.
• Lack of consumer loyalty: Shared mobility services struggle to retain loyal customers due to various factors, such as the availability of alternative options and a lack of incentives for long-term usage.

2. The Solutions :
   TomaaS addresses these challenges by leveraging Web3 NFTs and introducing two innovative solutions:

• Real World Asset NFT: Users can purchase these NFTs, which represent ownership of physical assets like vehicles within the shared mobility ecosystem. NFT holders become the owners and earn rewards from the vehicle's operating profits. This ownership model encourages long-term engagement and provides individuals with a comparatively high Annual Percentage Rate (APR).
• Liquidity NFT: By acquiring Liquidity NFTs, users can provide liquidity to the shared mobility platform, staking pool makes for swaping cash into tangible asset or vice versa. Liquidity NFT holders receive a fixed 18% APR, enabling them to earn passive income from their investment.

3. How TomaaS Works :
   TomaaS offers individuals the opportunity to participate in the shared mobility ecosystem:

• Users can purchase Real World Asset NFTs, becoming owners of vehicles within the platform. They earn rewards based on the vehicle's operating profits, incentivizing ownership and active participation.
• Alternatively, users can acquire Liquidity NFTs and contribute liquidity to the shared mobility platform. By staking these NFTs in the TomaaS Staking Pool, they earn a fixed interest rate on their investment.
• Service users Locked-In can be seen by offering voucher without additional charge from service provider nor users.

Challenges I ran into

There are some challenges for me.
I designed the smart contract, redesigned the contract code while writing the test code, and redesigned it again while connecting to the frontend. Also, the data to be received through the indexer or rpc provider and the data to be brought directly from the test network had to be separated.
There were a lot of small movements in the smart contract, so there was a gasp problem, so I had to split buy and minting into appropriate sizes.
As the test net slowed down and responses were delayed, various problems occurred, and the problems were solved by using rpcprovider.
Due to repeated tests, the faucet was not enough, so the team members were busy taking care of the faucet as well.