# An introduction to GET Protocol ## What is GET Protocol? GET Protocol is a digital ticketing infrastructure provider that has built state of the art ticketing infrastructure battle tested around the world by non-tech savvy attendees. Since inception in 2016, our ethos is to create products that put end users first, ensuring event organizers, artists and fans can benefit from the benefits of blockchain and NFT technology whilst keeping complexity to a minimum. GET Protocol offers two products, a White-Label full suite ticketing solution & a Digital Twin NFT layer for existing ticketing companies to tap into. All tickets that are processed through GET Protocol are registered on-chain the moment a ticket is sold and viewable in real-time through our [NFT Ticket Explorer.](https://explorer.get-protocol.io) ## Where has GET Protocol been used? **Globally.** GET Protocol's White-Label alone has served: ### 121 countries ### 217 **events in a single month.** ### 423 unique artists and organisers. ## How many Tickets have processed through GET Protocol? There has been over **3,000,000 tickets** processed on-chain through GET Protocol since 2016. [Check this for yourself here via our NFT Ticket Explorer](https://explorer.get-protocol.io/). ## What are NFT Tickets? All tickets processed through GET Protocol are registered on-chain as NFT tickets. NFT Tickets unlock: * Immutable, transparent ownership history tracking ticket lifecycles on-chain * Web3 fan engagement channels for event organisers, artists and ticketeers. * Pre, during and post-event collectibles that can provide gating of digital content. * In the future, the ability to tap into decentralised event financing. {% embed url="" %} ## How big is the GET Protocol team? We currently have 50+ people working full time in Amsterdam and remote. We're constantly looking for great talent in a range of positions, [Take a look for yourself on our hiring page!](https://guts.recruitee.com/) ![Say Cheese!](/files/-MWdFkmrkEUbgnVQJUsY) ## What are the benefits of GET Protocol for ticketing companies? GET Protocol offers products that cover the entire spectrum of ticketing. Any ticketing company no matter size or location can integrate one of our products to benefit from blockchain and NFTs. Ticketing companies looking for a complete infrastructure that eradicates ticket scalping and unlocks new engagement avenues, would be interested in our white-label which you can learn more about here: {% content-ref url="/pages/1q4xwkJnArGVnn1WihXj" %} [GET Protocol White-Label](/get-protocol-products/get-protocol-white-label) {% endcontent-ref %} Alternatively, our Digital Twin solution allows existing ticketing companies to tap into Blockchain and NFTs without any risk to existing ticketing operations, find out more here: {% content-ref url="/pages/aPZJ6lbtDqme7ZyV0aZm" %} [GET Protocol Digital Twin](/get-protocol-products/get-protocol-digital-twin) {% endcontent-ref %} ## What are the benefits of GET Protocol for event goers? One of the more immediate benefits to an event goer purchasing a ticket through a ticketing company using the GET Protocol white-label, is the ability to buy a ticket from the primary market and secondary market at a fair value which has been dictated by the event organiser and artist. The white-label solution completely eradicates ticket scalping at a commercial scale, by including a set of technologies that ensure only an authentic in-app ticket can be validated. **The Benefits of NFT Tickets** We see NFT Tickets as a way of expanding the lifecycle of a ticket through pre-event, during event and post-event innovations that were previously not possible. **Pre-Event** Prior to an event's ticket sale, GET Protocol has a 'Decentralised Event Financing' product, in which artists & event organisers can raise funding for their event through DeFi. NFT Tickets can be bundled and assessed by liquidity providers for a loan, which is then enforced through GET Protocol's smart contracts. ![](/files/7RyaeUhie2fKKVTe13xa) This product is being rolled out through a waiting list, which can be accessed here: **During The Event** During an event's ticket cycle, all purchased tickets are transparently viewable in real-time on the GET Protocol [NFT Ticket Explorer](https://explorer.get-protocol.io), providing clear ownership history for each and every ticket. ![](/files/gURBT0RW78hEoAfXou0J) **Post-Event** When a ticket is scanned at an event and provides entry access, it no longer needs to go straight in the trash, instead each NFT ticket is claimable as a Collectible which can then be used by creators to provide access into their digital experiences. ![](/files/2FJB7A3X9AsXCjCaH3gU) Every NFT is sent to the user's wallet address over the Polygon network. As GET Protocol's collectibles are still in a fledgling stage, we're constantly looking to expand the possibilities and creative process around this exciting new avenue. Read more about this here: {% content-ref url="/pages/Mw6kjBkCHBlj8XkrCS6X" %} [Post-Event NFT Collectibles](/get-protocol-products/post-event-nft-collectibles) {% endcontent-ref %} ## What are the benefits of GET Protocol for artists and event organisers? **Strengthening the event connection** A fully digital ticketing approach ensures the strongest connection between event organisers, artists and their fans from ticket sale to post event. Once a ticket is checked in it can be claimed as a digital collectible. This provides a completely new method for storytelling and connecting with fans. In the future these collectibles will offer perpetual revenue from secondary market sales whilst incentivising repeat event attendance. **Clearer insights** Event organisers get a deeper insight into who owns tickets for an event at every point in the event life cycle whilst being able to keep track of how many tickets have been sold, re-sold and checked in. **Direct communication** Artists can directly communicate with fans through SMS whilst having peace of mind that every fan is able to acquire a ticket at a fair price both on the primary and secondary ticket markets. **Scalper free ticketing** Selling tickets to an event using the GET Protocol white-label ensures a scalp free ticketing process. You can read about Dutch comedian, Jochem Myjer's experience here: {% embed url="" %} # GET Protocol White-Label ## What is GET Protocol's White-Label? GET Protocol's white-label system is a state of the art turn-key ticketing infrastructure that provides full control over event ticketing including the elimination of ticket scalping, control over primary and secondary market revenue and data, verified customer data & the ability to connect with fans through future proofed Web2 and Web3 channels. The white-label has been battle tested since 2016 and utilized at events across the globe by several white-label clients along with our own ticketing company - GUTS Tickets. You can view the white-label product further on the GET Protocol website: {% embed url="" %}
## # GET Protocol Digital Twin ## What is the GET Protocol Digital Twin? GET Protocol's Digital Twin product allows enterprise ticketing companies to twin their existing ticket inventory as NFTs which can then be distributed to attendees as Collectibles. Integrating with the Digital Twin comes with zero operation risk and low effort integration allowing for a hassle free way for ticketing companies to tap into the benefits of NFT & Web3 technology. Each Collectible can not only be fully customised with event artwork and metadata but can also act as a digital pass into experiences that can be gated exclusively for collectible holders. You can read more about the Digital Twin on our product page: {% embed url="" %} ## How does the Digital Twin work technically? From a technical perspective, ticketing integrators pass ticket data through an API which mints and distributes an NFT copy to an attendee. Tickets are currently twinned on the Polygon blockchain and processed through GET Protocol ensuring they are real-time viewable on-chain through our [NFT Ticket Explorer.](https://explorer.get-protocol.io/) # GET Protocol NFT Ticket Explorer ![](/files/D80P0ZHj7FYEEN2rrsO3) ## What is the NFT Ticket Explorer? The NFT Ticket Explorer gives a look under the hood at all ticketing activity happening through GET Protocol. This importantly provides a transparent view of ticketing operations occurring whilst also showcasing the magnitude of tickets being processed through the protocol. > GET Protocol has processed millions of on-chain smart tickets since 2016, all for real-world events and bought by non-crypto savvy users. ## Why Is The Explorer Needed? In an industry notoriously opaque, GET Protocol goes in the other direction. You could see the NFT ticket explorer as a streamlined block explorer that clearly presents easy-to-digest ticket information in a manner that requires minimal technical knowledge. If a user wishes to delve further into a ticket’s complexity like its transaction hashes, this information can be found via the links to the underlying blockchain explorer. This marks an important step towards presenting a clear look under the hood of all ticketing operations occurring through the protocol and in fact it’s a major achievement for ticketing in general. ### What Is The Explorer URL? > ### [You can access the explorer here](https://explorer.get-protocol.io/): {% embed url="" %} ## What Pages Are There? Let’s go over the features — both current and coming up — of our newborn. ### **Homepage** **The homepage** provides a statistics hub for real time ticketing data. These metrics can be broken down over various time periods to highlight ticketing activity across a range of dates. The search functionality allows the user to look up each individual ticket using an NFT Index or other unique criteria — of course there’s also the random button for anyone without a ticket that wants the full experience. ![](https://cdn-images-1.medium.com/max/800/1*EoO8mTn9hOrtUgp6kjOPdg.png) ***Recent ticket sales and state changes*** update in real time to give a concrete picture of current ticketing operations occurring through GET Protocol around the world. By clicking on a specific index across both sets of metrics, the user is taken to that specific ticket’s lifecycle page. ![](https://cdn-images-1.medium.com/max/800/1*-UYOlpvEdCK2bwDICy7y5Q.png) ### ***Lifecycle Page*** To get a clearer look at the status of an individual ticket flowing through GET Protocol, **the life cycle page** breaks down a ticket’s journey into specific state changes. It’s important to note that not all state changes may occur to one ticket, for example not every ticket will become “invalidated” and later on some tickets may not be ***“claimed” — which is a feature coming in the next update that will incorporate the ability to claim a ticket as a digital collectible. Something we’re very excited about.*** ![](https://cdn-images-1.medium.com/max/800/1*Kq22fIDpgKIqG0BNeGzKXQ.png) # Post-Event NFT Collectibles ## What is a GET Protocol NFT Collectible? The days of tickets going straight into the trash after providing entry access are soon to be over. Using GET Protocol's white-label, each NFT ticket is claimable as a digital collectible. Collectibles offer new avenues for connection, storytelling and revenue and can be displayed and exchanged on decentralised marketplaces such as [OpenSea](https://opensea.io/collection/get-protocol). When a ticket is scanned at an event, the collectible is automatically sent to the user's wallet address over the Polygon network. As GET Protocol's collectibles are still in a fledgling stage, we're constantly looking to expand the possibilities and creative process around this exciting new avenue. ## How does an attendee claim their NFT? You can read more about the 3 step claim process on our website here: {% embed url="" %} ## Is there a showcase of GET Protocol NFT Tickets? Our showcase site is available here: # The $GET Token - Fundamentals ## What is the $GET token? $GET is an ERC-20 token on the Ethereum and Polygon blockchains that fuels all tickets processed through GET Protocol. * Coin Gecko: * CoinMarketCap: {% embed url="" %} ## What is the circulating and total supply of $GET? The total and circulating supply of GET is as follows: | **Supply** | **Amount** | | --------------------------- | ---------- | | Circulating Supply | 17,414,673 | | Total Supply (Fixed supply) | 23,368,773 | Total Supply distribution:
Amount
Circulating Supply17,414,673
GET Protocol DAO Treasury2,600,000
User Growth Fund3,354,100~
## How can I acquire $GET tokens? Please visit: {% content-ref url="/pages/ILCCIZaeIXTp9LZs2gHT" %} [How & Where To Acquire $GET](/get-protocol-tokenomics/how-to-buy-get) {% endcontent-ref %} ## What are the contract addresses for $GET? **The $GET token address on Ethereum is:** [0x8a854288a5976036a725879164ca3e91d30c6a1b](https://etherscan.io/address/0x8a854288a5976036a725879164ca3e91d30c6a1b) **The $GET token address on Polygon is:** [0xdb725f82818De83e99F1dAc22A9b5B51d3d04DD4](https://polygonscan.com/address/0xdb725f82818de83e99f1dac22a9b5b51d3d04dd4) ## **Will more $GET tokens be created?** $GET has a fixed supply meaning that no more tokens can be created. This can be verified via the token smart contract: {% embed url="" %} ## Was there an ICO for $GET? GET Protocol was funded by ICO which finalized on the 13th of December 2017. The average ICO rate for $GET was 0.00102483 *ETH / GET* with the total amount of ETH raised being: 10,935 *ETH.* **For more information:** {% embed url="" %} The ICO included a security audit which was conducted by Matthew Di Ferrante, founder of ZK Labs. They are a leading smart contract development & auditing firm that have conducted audits for many crypto projects including the likes of Polkadot and Enjin.[ More information on the audit available in this PDF.](https://github.com/mattdf/audits/blob/master/guts/guts-audit.pdf) ## What is the regulatory status of the *$*GET token? From GET Protocol's inception onwards, we've made it a priority to ensure that the project is compliant to regulatory and legal rules. In order to ensure that these checks were carried out as fairly and unbiased as possible, we hired the services of an independant Dutch law firm, [De Roos Advocaten](https://deroosadvocaten.nl) to conduct a [Howey Test](https://www.findlaw.com/consumer/securities-law/what-is-the-howey-test.html). The Howey Test was created by the US Supreme Court in order to determine whether certain transactions qualify as "investment contracts", a.k.a "securities". De Roos Advocaten concluded, that **if** the SEC would make the case that $GET is a security, they would have a difficult time making a legal argument for this claim. The Roos argues that $GET has the attributes of a utility and was marketed as such. **The $GET token passed the Howey Test conducted by De Roos Advocaten and therefore the token will likely be considered a utility and NOT a security.** This conclusion is based upon the tokens functionalities and role of the token within GET Protocol. In case the asset would be evaluated by the US supreme court (i.e. challenged by the SEC) the law firm states it would be highly unlikely that the offering would be considered an offering of a security. If you would like to read the official report conducted by De Roos Advocaten [then you can click this link.](https://drive.google.com/file/d/19UwaQxUbhsqa5QiZ2MciDCe66eiraAgH/view) If you instead would like to read the original blog post created by us after the Howey Test was conducted [then you can click this link.](https://blog.guts.tickets/results-of-the-howey-test-on-get-by-independent-law-firm-5f1a65cee4e4) As for other countries and unions, [GET is considered a utility token in Europe](https://get-protocol.io/files/GET_Analysis_Security_EU_Law.pdf), [Singapore](https://get-protocol.io/files/Legal_Status_GET_Token_Singpore_Assement.pdf) and the US as mentioned above. # The $GET Token - Usage ## What is the role of $GET within the protocol? $GET is the fuel for each and every ticket processed through GET Protocol. The economics of $GET have been designed to ensure that there is on-chain transparency of value flows and activity whilst providing a clear and simple pricing model for ticketing integrators of GET Protocol. The rate of $GET required per ticket varies based on a number of factors, the main three being: * The price of the ticket * The ticket issuer * Complexity of ticket needs You can see this on-chain value flow by querying the GET Protocol [SubGraph](https://thegraph.com/hosted-service/subgraph/getprotocol/get-protocol-subgraph) and can read more about the queries in our [Mainnet blog post.](https://www.get-protocol.io/content/mainnet) For further technicalities, you can read our developer documentation: {% embed url="" %} ## How do ticketeers topup their $GET? Ticketeers topup their GET using their account on our integrator dashboard. GET needs to be topped up before integrator partners sell their tickets. Ticketeers can topup their GET within the dashboard either using the built in FIAT onramp with circle or alternatively be sending GET to their integrator account wallet via their own self custody wallet. ## Do attendees need to acquire $GET to buy tickets? No, attendees do not know about GET when experiencing the ticket purchase flow. They pay for their ticket using local FIAT currency. Our system is built to hide as much technical complexity as possible to ensure a smooth ticketing experience. ## If the price of $GET rises, won't tickets become too expensive? The amount of $GET that is needed to fuel each ticket, is denominated by a USD value which we refer to as the **basePrice**. This ensures that on-chain accounting is standardised to a single currency - USD. This **basePrice** along with the factors above, determine the amount of $GET necessary for each ticket - we call this variable amount of $GET needed per ticket the **mintRate.** In order to understand why the price of $GET rising does not effect the cost of processing a ticket through GET Protocol, it is important to know that all ERC-20 tokens are divisible to **18 decimal places**. This means that one $GET can be broken into: **0.000,000,000,000,000,001 parts.** Since we denominate the cost of a ticket in USD, this means that if the price of a single $GET increases, then the amount of $GET needed for a ticket can be less than a whole number, ensuring price fluctuations of $GET will not make the cost of ticketing infeasible. Here is a table example - note that **these are example figures and not indicative of actual pricing figures.** | USD Value - basePrice | Price of $GET on the market | $GET needed - mintRate | | --------------------- | --------------------------- | ---------------------- | | $0.3 | $0.5 | 0.6 | | $0.3 | $1.5 | 0.2 | | $0.3 | $4 | 0.075 | # The $GET Token - Staking token.get-protocol.io *PSA: Please verify that you are on* [***token.get-protocol.io***](https://token.get-protocol.io) *when using the GET Staking platform.* During February 2023, the GET Protocol staking platform was launched. This staking platform allows GET token holders to stake their GET in order to receive rewards from ticketing activity occurring through the protocol. The goal of the staking platform is to align all protocol participants around the long term vision of the protocol and as such receive rewards from its usage.
### Depositing GET into the Staking system When a user deposits GET into the staking system, they will receive a new token in the form of the xGET token. The xGET token is an ERC-20 token which represents a claim to your underlying GET within the staking system. xGET is transferable allowing for trading & other DeFi utility. xGET follows the [xToken model](https://github.com/fei-protocol/ERC4626#xerc4626) and can only accrue value against the underlying asset, in this case GET. This is known as a [yield-bearing asset](https://academy.stakedao.org/what-are-yield-bearing-tokens/). Or in more plain terms; xGET will always be redeemable for the same amount or more GET than deposited, never less, because xGET would be equal to `assetsDeposited + assetsRewarded`. Therefore xGET is a share token that represents the underlying assets in the vault where there are only two ways for GET to enter; deposited by a staker, or transferred to the vault as rewards. ### Reward Sources The staking system currently aggregates four sources of rewards that are regularly distributed: * A percentage of Ticketing Fees from fuel usage is redeemable as staking rewards upon each ticket check-in or invalidation. This can create streaming rewards to stakers driven by real-world ticketing usage. 100% of UGF funded top-ups made for GUTS Netherlands B.V. will go to stakers. * A percentage of **Trading Fees** collected by protocol-owned-liquidity will be available as staking rewards. The GET collected fees will be transferred to the staking contract and the ETH/USDC collected fees will compound the position. * **Instant Withdrawal Fees** are triggered when a staker withdraws their assets prior to the unlock time. This fee will remain on the contract and be distributed to remaining stakers. * When a staker wishes to withdraw via a standard withdrawal their shares will be locked within the vault. The staker does not earn rewards during this withdrawal period but the underlying shares still acrrue this value, which is then redistributed to remaining stakers upon cancellation or withdrawal execution. These are known as **Redistributed Rewards**. ### Withdrawing GET from the Staking system There are two ways to withdraw GET from the staking system. A normal withdrawal which comes with a 6 month unstake period or an instant withdrawal which has a % penalty that linearly reduces based on the time left on the unstaking period for a GET withdrawal. #### Normal Withdrawal By submitting a normal withdrawal request, the amount of GET selected for withdrawal will go through a 6 month unstaking period. Once the 6 month period completes, the user must execute the withdrawal in order to receive their GET. This execution period lasts for a 1 month time period. If the GET is not withdrawn during this 1 month period then the GET will return to being staked for the user. #### Instant Withdrawal If the user wishes to instantly withdrawal at the beginning of the unstake period, this comes at a 15% penalty that is deducted from the total amount of GET being unstaked. This penalty linearly decreases over time based on the time left of the unstaking GET. Examples of this are: Withdrawal at 6 Months Unstaking Left - 15% Penalty Withdrawal at 3 Months Unstaking Left - 7.5 Penalty Withdrawal at 1.5 Months Unstaking Left - 3.75% Penalty For technical specifics and links to the staking system's contracts & audits, please visit our technical docs & refer to the 'Contracts' section: {% embed url="" %} # How & Where To Acquire $GET If you're looking to acquire $GET but don't know where to start, this resource is for you. If you're curious to learn more about the $GET token, particularly what role it performs with GET Protocol then visit: {% content-ref url="/pages/3WHQIMszoGaVssV6Yd91" %} [The $GET Token - Usage](/get-protocol-tokenomics/the-usdget-token-usage) {% endcontent-ref %} If you'd like to learn more about the $GET token fundamentals, like circulating supply, regulatory stance and history please visit: {% content-ref url="/pages/xcXL3qRuEsjbsHgbtNMz" %} [The $GET Token - Fundamentals](/get-protocol-tokenomics/the-usdget-token-fundamentals) {% endcontent-ref %} For $GET staking queries, please visit: {% content-ref url="/pages/BLPO0oUdGZxYhQkj4XdE" %} [The $GET Token - Staking](/get-protocol-tokenomics/get-staking) {% endcontent-ref %} ## How To Acquire $GET The first question to ask yourself when looking to acquire $GET is which platforms you are most familiar with: * Decentralised exchanges - Uniswap (Ethereum & Polygon networks) **\[Recommended]** For those looking to acquire $GET on a decentralised exchange, $GET is tradable on Uniswap, this avenue has higher liquidity and is therefore recommended. {% content-ref url="/pages/HrRRISxUtQ6PfZVeDetO" %} [Acquiring $GET On Uniswap](/get-protocol-tokenomics/how-to-buy-get/how-to-buy-get-sushiswap) {% endcontent-ref %} # Acquiring $GET On Uniswap ## What is Uniswap? Uniswap is a decentralised exchange that supports multiple networks, including Ethereum and Polygon. This allows swaps to occur for GET pools on both network. ## What are the GET pools on Uniswap? The pair on Polygon is GET/USDC: {% embed url="" %} The pair on Uniswap is GET/ETH: {% embed url="" %} # Bridging Your GET: Why you’d want to and how to do it GET is a cross-chain token, meaning that it exists on multiple blockchains, sidechains, and rollups across the ecosystem of Ethereum. Specifically, much of GET’s functionality exists between Ethereum’s Mainnet and the Polygon sidechain. Ethereum offers ease of trade and access while Polygon provides minimal fees (a big reason why we use this chain for issuing tickets). Polygon is also a much more environmentally friendly blockchain technology which may align with for your personal goals in token ownership. You may find that one of these chains is preferable to the other depending on your specific needs, and we find that if you’re active trader or you use your GET tokens regularly, then Polygon may be preferable. Before you can take advantage of this, however, you must bridge your tokens. Bridging is a term that just means to move your tokens to a different chain. Generally speaking, this can become quite convoluted, but with SushiSwap’s latest version, the process is greatly simplified. For the purposes of this tutorial, we assume you already have a non-custodial, web3 capable Ethereum wallet setup and ready to go. If not, we recommend [Rainbow](https://rainbow.me/). It’s super easy and makes the process of buying your first ETH a breeze. You can even use Apple Pay and Google Pay! Once you have a little ETH in your wallet, it’s time to get $GET. We start by visiting the [new SushiSwap app](https://sushi.com/swap) that enables bridging. Make sure the top dropdown box is set to “Ethereum Mainnet” with ETH selected as your token. On the lower box, select “Polygon Mainnet” as your chain.
Select the token dropdown and input the $GET Polygon token address: 0xdb725f82818De83e99F1dAc22A9b5B51d3d04DD4. Import this token and set it as your custom token. Be careful to import the correct token. Only ever import by this contract address and never search for the token ticker directly.
Now, enter in how much you’d like to swap. Your final setup should look something like this:
The fees are automatically calculated by SushiSwap for the most optimal route and probably shouldn’t be adjusted unless you feel confident in your skills with setting custom gas. Once you’re happy with everything, hit the Swap button and follow the prompts from your wallet: You should receive an approval request and a signing request for the transaction.
After you confirm everything, SushiSwap will automatically bridge and swap your token over the most optimal route available, all without you having to do anything (you can see the example route it selected for our example below). This is by far the simplest and safest method available for bridging GET onto Polygon.
# Viewing $GET On-Chain ## Viewing $GET fuel per ticket & event through the Community Dashboard The GET Protocol community have created a dashboard for viewing the $GET usage of tickets as they flow through the protocol: Brom's Community Dashboard: {% embed url="" %} 0xMartijn's Dashboard: {% embed url="" %} ## Viewing $GET on-chain via GET Protocol's SubGraph Using our subgraph anyone can get a clear picture of [$GET](https://twitter.com/search?q=%24GET\&src=cashtag_click) flowing through the protocol, fuelling event tickets globally. The queries allow for a breakdown across event metadata and usage data, aggregated by all-time & per-day. **You can access the subgraph below:** {% embed url="" %} You can also read more about the functionalities available with GET Protocol's SubGraph in our 'Mainnet' story hub article: {% embed url="" %}