JOOPS NFT represents a physical electric scooter, your NFT is no longer a fun character, it’s a programmable smart contract. When you sign the contract by minting your NFT the decentralized protocol will start renting out your physical electric scooter and earning you a passive income directly through our decentralized App.

JOOPS P2P electric scooter hire & sharing company allows users to instantly rent and unlock electric scooters directly from their phone with a tap of a button. JOOPS utility token is designed to be the standardized currency in which its main purpose will be to facilitate transactions and payments directly through the JOOPS network allowing for a seamless reliable rental experience.

THE PROJECT

JOOPS interface will be the gateway to our decentralized applications on the blockchain. It will allow users to securely interact on the platform, as well as write, deploy and use smart contracts autonomously through our NFT initiative.

• A front-end interface for users to create bookings and return scooters.

• A wallet to manage accounts, funds, and smart contracts

• Smart contracts for booking and returning scooters

• Transactions enabling the interaction between users and smart contracts

• Messages enabling the interaction between smart contracts

• Events (log entries) triggered by transactions

• An app watching for events and sending requests to the scooter

​Smart contracts are programs written in the Solidity programming language, each user has to register before renting a scooter to make sure that only authorized users have access to the scooters. The smart contract makes this registering possible. For this, it provides functions to register a user, remove a user from the register and check if a user is registered.

Each scooter is represented by its own smart contract deployed to its own address, the interface of the contract enables the booking and returning of the scooter by a user. Only the owner of the contract can assign a registry to a scooter. Only a user registered in the assigned registry can book a scooter, and these actions can only be completed if the scooter is not already booked and enough funds are transferred prior to the booking.

Transactions are signed data packages that store a message to be sent from an externally owned account (representing a human user, or external actor) to another account on the blockchain (human user or smart contract).

The contract owner (administrator) triggers transactions with a client. These transactions are calls to set the registry and register authorized users.

​

The user triggers transactions with the user interface. These transactions are calls to book and return a scooter.

Smart contracts are able to send “messages” to other contracts. They can be conceived of as function calls. Essentially, a message is like a transaction, except it is produced by a contract and not an external actor. The scooter contract sends a message call to the registry contract to check if a user requesting to book a scooter is registered. The registry returns true if the user is registered, false otherwise. Only if the user is registered a booking is possible.

If a user sends a transaction to book or return a scooter corresponding events are generated. Events are log entries generated by message calls (transactions) in the blockchain. Events are written as logs to the blockchain and are accessible to external services, but not too smart contracts.

Watching for booking (“Booking”) or trip ending (“Return”) events. This is written in node.js and uses the web3.js JavaScript API to access the blockchain. Each scooter is represented by mapping a QNR to the address of the smart contract belonging to the scooter. The QNR is an internal unique identifier for a vehicle the application is watching for events containing the topics “Booking” and “Return”.

The DApp provides an endpoint for unlocking and locking the scooter. A scooter is identified uniquely by a QNR. When the user finishes the trip, he uses the ÐApp to return the scooter and end the rental. This calls a function of the scooter contract and creates an event that triggers a lock request.

Security considerations

The contracts are deployed to the public blockchain offering access to all smart contracts, transactions, and events stored in this public blockchain. While there is no risk of theft of funds,  it has to be prevented that unauthorized users obtain access to scooters and steal them.

General security provided by the blockchain protocol:

• Smart contract owners and users are identified by addresses

• No actions by adversaries are possible using these addresses without knowing the associated private key, which has to be kept secret

• All events contain secure information about the source of the event to prevent the generation of fake events by adversaries to get access to a scooter

Therefore, the following security measures are implemented:

• access to sensible smart contract functions is restricted to the contract owner

• Addresses for authorized users can be registered

• Only transactions for registered addresses are accepted by the smart contract for renting a scooter

• A whitelist containing the QNRs restricts access to scooters

• The DApp only accepts events generated by a smart contract belonging to a scooter.

• JOOPS blockchain technology will contribute to making these services more accessible, attractive, and economical for both users and operators globally. By now, it is indisputable that shared mobility services are the future, In particular electric scooter sharing. We believe that JOOPS blockchain technology will create a far superior P2P sharing platform as it makes the transactions between many parties more secure and efficient.