proposed NFT features via Django Application

Summary:

The Application is to built primarily using the on-chain NFT features (ERC1155 & not ERC721 on the @peerplays blockchain.). With HIVE and BTC decentralized Oracles are to be fully functional before the completion this project, purchase of NFTs with 3 coins will be possible (BTC, HIVE & PPY). Tokens of @threespeak can also be considered.

---

---

note: [Screen shot of the current marketplace: extended Opensource Expresscart to support NFTs]
.

Features:

---

• There should be a user management system capable of creating various user types - superadmin and staff
• The super admin should be able to create a group called organization (say, Tokyo Olympics New Hamphsire Marine Corps)
• Each organization will have a profile page aka landing page
• the organization landing page will show a description about the organization, reason for running either NFT marketplace or NFT-lottery aka 5050
• Each organization can have multiple 5050's
• There can be only one NFT-marketplace & it must support bids in FIAT and PPY (later BTC, HIVE etc)
• Each organization can have users and they can signup via organization page
• The organization users should be able to sign up with Facebook, Google, email etc and thus PeerID should be used
• Superadmin > creates organization > creates org users aka org-admins
• Org-admin users should be the ones creating various 5050s (progressive, normal, time bound, limited by number etc)
• org-admin must choose options like multiple beneficiaries, NFTs as tickets, non-NFT lottery tickets etc
• Users must be allowed to purchase lotteries without extensive signup - it must be a single page checkout where only the emails should be collected as a mandatory item.
• POS-Mode: The user emails are to be collected even if the NFTs are sold by volunteers walking around in a mall or during an event. ie, we must provide a "POS" aka point of sales mode where a volunteer of the charity organisation can sell the tickets and collect the bare minimum detail, ie, the email address of the person purchasing the ticket. The POS operator should be allowed to collect cash (FIAT) physically or by any other means he deems fit and sell the tickets. the POS user should then settle the collected cash to the org-admin or org-staff users.
• In the case of a scenario where and end user not providing email address to POS-mode user, then an email address provided by the system POS-username+mobile-number-of-buyer@organisation.com must be used as the unique email address. {Assuming that the end user will have an email/SMTP server like Qmail which supports unique email ids using the + symbol in them but all emails goes to the single email address ie POS-username@organisation.com}
• REPORTING: The org-admin user should be able to see the number of buyers, tickets sold, ticket type sold, total revenue generated, POS-user who sold the tickets, beneficiary rewards, on going lotteries as easy to understand reports.
• Upon completion of a draw an email should be send to superadmin and org-admins
• The reports should show the winner of each lottery & his details so that the org-admins can email / snail mail / telecall the winners
• The winner details, price money distributed & the amounts donated to benefeciaries must be published via organization profile. The report should include the details of the lottery, precise details of the events (purchase, draw) etc on the blockchain. The page must give emphasis to the provably fair nature of the blockchain based 5050 & highlight the unique RNG feature being employed (Provided by @peerplays blockchain). The winner profile can be included and in the winner's profile the NFTs involved if any can be listed as well. A basic profile can be created for the end user (buyer) & can be extended in later phases.
• Legal: The application must provide a page builder which will allow users to edit organisation page, terms and conditions etc. By default in addition to the home page (orgnisation landing page/profile), a description of the 5050, terms of the lottery, terms and conditions of the portal (software) etc can also be given. Lorem-Ipusum content can be provided. This will help org-admins to easily edit the content and adhere to various legal requirements.
• Age-Gate: The application needs a feature to implement and age-gate. This can be a dialogue box asking the end-user to agree whether the user is above certain age limit to participate in the charity raffle.
• Geo-Fencing : A feature to provide geo fence using Google APIs should be provided per organization

Code base: https://gitlab.com/PBSA/dapps/django-nft