[TixFi] is a decentralized ticket store for the Ethereum blockchain.

• [TixFi] - Forked from Feamcor(Bileto)
  • Introduction
  • High-Level Solution
  • Try TixFi
  • Roles
  • States
    • Store
    • Event
    • Purchase
  • Events Emitted
    • Inherited
    • Internal
  • Best Practices
  • Smart Contract Installation
  • DApp Installation (development build)
  • DApp Installation (production build)
  • Future Enhancements

TixFi is a set of smart contracts, written in Solidity 0.5.6, which implement the business of a ticket store. It is accompanied by a decentralized web3-enabled application (DApp) where users, according to their roles, can manage the store, its events and perform ticket purchases, cancellations, refunds and event check-in.

TixFi can be deployed to an Ethereum blockchain, be it the public mainnet, a public testnet like Rinkeby, a private network, or on a local development blockchain like Ganache.

As currency for ticket purchases, so far, TixFi uses Ethereum's native Ether.

TBD

TixFi is deployed to Rinkeby testnet (see it on Etherscan). Its DApp is deployed to IPFS and can be accessed here.

Any account, at any time, can be associated to many roles. For instance, the store owner can purchase tickets to an event, turning the account also on a customer.

• Owner - at a first moment, the store's Owner corresponds to the account who deployed the smart contract into the blockchain. Later on, the Owner can transfer ownership to another account. There is only one Owner and its impact on the contract is none (unless it is a Pauser) but to hold or withdraw the funds that are reserved to the maintenance and future development of the store's smart contract and DApp.
• Pauser - corresponds to the accounts which are allowed to trigger the store's emergency stop mechanism. At a first moment, the store's Owner account is also the first Pauser account. A Pauser account can add another pausers (to share the burden), or it can renounce such role (with great power comes great responsibility).
• Organizer - corresponds to the accounts who created events on the store. Later on, such accounts can manage the event lifecycle: from starting to suspending or ending sales of tickets, plus completing or cancelling the event. Each event can only be managed by its Organizer account.
• Customer - corresponds to the accounts who purchased tickets on the store. Later on, such accounts can check-in or request purchase cancellation and refund (when such conditions are allowed). Each purchase can only be managed by the account who completed the purchase (i.e. the Customer). Customer accounts must be an EOA.

• Unpaused - initial state of the store, meaning that it is open for business.
• Paused - emergency stop state, where no actions can be run (that is, store is closed) until unpaused. It impacts all events managed by the store.

• Created - event is created, but not yet selling tickets.
• Sales Started - event is actively selling tickets (prior to event date).
• Sales Suspended - event is temporarily not selling tickets (emergency stop).
• Sales Finished - event is not selling tickets anymore (just before event date).
• Completed - event happened successfully and funds are ready to be settled between store and organizer.
• Cancelled - event is cancelled, allowing all purchases to be cancelled and/or refunded by customers.

• Completed
• Cancelled
• Refunded
• Checked-In

• OwnershipTransferred
• Paused
• Unpaused
• PauserAdded
• PauserRemoved

• EventCreated
• EventSalesStarted
• EventSalesSuspended
• EventSalesFinished
• EventCompleted
• EventSettled
• EventCancelled
• PurchaseCompleted
• PurchaseCancelled
• PurchaseRefunded
• CustomerCheckedIn

• Reentrancy - functions sensitive to reentrancy are guarded using OpenZeppelin ReentrancyGuard.
• Access Control - TBD
• Arithmetic Issues - arithmetic operations are checked against over or underflow using OpenZeppelin SafeMath.

TBD

TBD

TBD

Note: the following list doesn't imply on order of implementation.

• Replace Store emergency stop by OpenZeppelin Pausable.
• Introduce explicit roles by OpenZeppelin Roles.
• Use an Oracle to bring data from external sources.
• Turn TixFi into a DAO.
• Allow different kinds of tickets, with distinct prices.
• Allow assignment of seats.
• Allow to increase or decrease number of tickets available for sale.
• Allow multiple accounts to manage the store subject to multi-sig protocol.
• Allow multiple accounts to manage an event subject to multi-sig protocol.
• Allow store balance to be distributed to many accounts.
• Allow event balance to be distributed to many accounts.
• Split contract between store and events.
• Replace store currency from Ether to an ERC-20 utility token or to a stablecoin like DAI.
• Integrate customer identification with uPort or other identity provider.
• Turn tickets into ERC-721 NFT deeds.
• Could ticket validation during check-in benefit of ZK-proof like zkSNARKS or even zkSTARKS? etc.