1 of 82

Docs

Welcome to Six Sigma Sports

Six Sigma Sports is a next generation sports betting platform designed to democratize the sports betting industry. It’s deployed on the Sports, Gaming and Entertainment Network (The SGE Network); a Cosmos SDK-based layer-1 blockchain that uses its own native utility token (The SGE Token). It is a new approach to sports betting, re-imagined with the benefit of blockchain technology to bring a transparent, fast, and uniquely engaging experience.

At Six Sigma Sports, for the first time ever, you can truly step into the shoes of the operator behind a sports book.

CHANGE THE GAME | BE THE HOUSE

Overview

Quick Reads

Be the House - Explained

What is House Mode?

House mode allows the user to be “The House”. “The House” refers to the role of an operator of a casino establishment, of a sportsbook, or any "house" where gambling activities are hosted. Implicit in the definition of “the House”, is the operator’s role in setting the rules, providing the games, and holding a stake in the betting outcomes.

The term also reflects the casino's inherent advantage in almost all games, known as the "house edge". This advantage ensures that, over time, the casino will make a profit, as the odds are slightly tilted in its favor across various games.

How does the House Edge work?

Conceptually, the house edge represents the operator’s built-in advantage to secure its profits over time. The game is structured so that, even though players make their decisions and can employ strategies, the rules inherently favor the house. This slight advantage ensures that, while individual players might win in the short term, the casino will come out ahead in the long run. The house edge is designed in a way to maintain a balance between providing an entertaining experience, offering players a chance to win and ensuring the casino's profitability.

How does this apply to Six Sigma Sports?

Six Sigma Sports is excited to unveil a new innovative platform, providing users with a unique opportunity to engage in sports betting as "The House," taking advantage of the inherent "House's Edge". The Six Sigma Sports application affords users the flexibility to either place bets using a familiar sportsbook interface or to participate across betting markets in the capacity of "The House." This seamless transition between roles is facilitated by a user-friendly toggle switch within our application, ensuring a smooth and intuitive experience.

How does a user participate as “the House”?

In order to engage as the House, first a user must identify a specific market within a fixture they feel is attractive to participate in. Once identified, the user contributes liquidity and takes their place in a queue managed by the application. When the user selects to participate in a market, they accept all bets from bettors, up to the payout capacity contributed, at the prevailing market odds. Users should monitor odds and any other news developments that may happen leading up to a match, just as a sportsbook operator would. House users will have the option to withdraw unused liquidity at any time.

Example:

A user wants to participate as the House in the English Premier League Match - Fulham - Manchester United. In order to participate, the user selects “View Bets” to enter the House mode on this specific fixture.

Upon selecting “View Bets”, all bets that are available to participate as the House are listed. The user selects the individual market to participate.

In this particular scenario, the user has opted to engage in the "3 Way Result" market.

On the interface, three key pieces of information are displayed: "0 / 0 SGE / 154.9225 SGE."

The first value, "0," indicates the total number of bets that have been placed in this market.

The second value, "0 SGE," represents the cumulative value of all the bets that have been placed in this market.

The third value, "154.9225 SGE," signifies the amount of SGE (the platform's native currency) that all users have committed to the market in order to participate as the House.

To proceed, the user is required to deposit a sum of SGE into the market, with the minimum deposit currently set at 10 SGE. By selecting the “Be The House” option, the user will be directed to the House Slip, which summarizes the details of the transaction and prepares it to be signed and recorded on the blockchain.

The user must select “accept all odds and line changes” as a condition to participate as the House. Once selected, the user can deposit their SGE tokens into the market by selecting “Be The House”.

Upon selection, this will bring up the wallet transaction confirmation display. (This example displays a Keplr wallet). Once the user selects approve, the transaction will be processed via the SGE Network and the user will be placed into the order book for the house.

Now that the user is positioned in the order book, they will accept bets alongside other

participants as “the House”.

A Deeper Understanding of the Mechanics and Economics behind the House:

When a user participates as The House, the user is essentially an active liquidity provider. When they deposit SGE into a market, the user is committing to take the other side of all bets placed in the market at the prevailing odds. The allocation of bets, examined in more detail later, is dependent on the user’s position in the order book and any existing bets they have taken.

It is important to note that participating as the House does NOT guarantee a positive result nor does it guarantee offset risk. In reality, sportsbooks often do not see balanced flow and do experience the gain and loss volatility associated with any single or small group of events. The performance of a sportsbook should be measured over large number of bets and an extended period of time.

Maximum Loss = User Deposit

The deposited amount determines the user's maximum risk exposure (maximum loss) when participating as the House. To illustrate, if a user deposits 50 SGE into a market as The House, their potential loss is strictly limited to 50 SGE. This maximum risk exposure represents the potential payout, and therefore is likely to be reached while accepting bets that amount to less than 50 SGE.

Order Book Functionality

User deposits into a market as The House are organized in a sequential order, based on the time at which each deposit was made, adhering to a first-come, first-serve principle. When a user occupies the “top” position in the order book, they are allocated all incoming bets across the various outcomes within the market, until their capacity is used. After fulfilling this initial capacity, the user’s “re-usable” capacity is calculated, before moving them to the back of the queue. This systematic approach ensures a fair and orderly distribution of bets among users participating as The House.

How is the capacity calculated?

Odds Source: The application uses a data provider that supplies odds which we expect to be in-line with the broader market.

First let’s start with some relevant definitions:

Probability = 1/Odds

Break-Evens: A break-even percentage, also referred to as Implied Odds, is the percentage of time a bet must win for you to neither win nor lose money making the bet over time at the odds in question.

True-Odds: True Odds, in theory represents the actual probability of an event happening. In practice, bettors and sportsbooks utilize various proprietary methods to arrive at what they believe are the “True Odds” of an event. One can also estimate the True Odds implied in a set of published odds. The first version of the House functionality on Six Sigma Sports utilizes the equal margin method to do so, which simply applies the total margin equally to each betting outcome to arrive at the True Odds.

Summing the Break-Even (Implied Odds) percentages across outcomes on a market will typically add up to >100%. We know the probabilities of an event cannot be greater than 100%, and the difference between the observed implied probabilities of the odds offered by a sportsbook and True Odds represents the Vig (House Edge) of the Sportsbook.

Applying the above concepts to the Six Sigma Sports House:

At the time of contribution to the House, the user’s submitted amount is split and allocated across the potential market outcomes in what we refer to as a “True Odds Ratio”. Mathematically speaking, if the sportsbook were to accept bets at those odds and in the True Odds Ratio, it would yield a risk-free positive result; No matter the event outcome, the sportsbook would earn the Vig implied in those odds; the House, including a user’s house deposit, would be a winner in any scenario. It is important to note, odds change and betting flow is unlikely to be “perfectly” balanced. The chances of achieving offset risk is highly dependent on one’s position in the House order book, the amount of betting flow in the book, and the volatility of the odds.

The order book further optimizes the process for every participant by treating each “outcome vertical” independently, even when evaluating overall risk and capacity. Once House participants start engaging in bets, this benefits users by maintaining their position in the queue to accept offsetting risk.

Let’s look at an illustrated example:

· Here we have a hypothetical SouthHampton (H) v. Manchester United (A) football match. For the provided odds, we can calculate the break-evens and estimate the True Odds. As you see here the House Vig is approximately 7.6%.

· The first House User contributes 2,000 SGE into the order book, which net of a 50bps fee, creates a capacity of 1,990 SGE. Remember, this represents the user’s max loss and payout capacity.

· In order to ensure the supplied payout capacity cannot be exceeded, the capacity calculation is first “anchored” to the outcome with the longest odds. Here we see that the bet capacity implied by a max payout of 1,990 SGE, if fully engaged on a single outcome, would be most limited by the 4.2 odds for Southampton to win, allowing House User 1 to accept a maximum of 622 SGE in bets for Southampton. From there, the available capacity for each other “outcome vertical”, Draw and Away (ManUnited), is calculated based on the True Odds ratio previously discussed.

· As you can see in the box titled House User Exposure, the red line illustrates the max loss if a user took only single-direction bets in each outcome. The P&L line below illustrates how the House wins under any scenario (+199 SGE), if the sportsbook accepts bets in the True Odds Ratio with the odds unchanged.

· The last section titled House Order Book, illustrates what happens in an order book of 3 House Users that is engaged by 2 different bettors. In particular, note that when Bettor 1 takes all the capacity of House User 1 for the Home team, the order book is updated to reflect this reduced capacity, but maintains House User’s 1 position under the other outcome verticals (Draw & Away) in order to be prioritized to benefit from offset risk.

· The allocation of capital across outcomes is updated for both executed bets and changing odds.

· This positioning is maintained until the user’s remaining capacity in the other outcomes is engaged OR the odds change to such a degree that capacity is reduced to 0 because taking additional bets on those outcomes would no longer be risk-reducing. At the realization of either of those 2 outcomes, the user is recycled to the back of the order book with any remaining capacity they have, thus creating capital efficiency and the opportunity for the House user to engage additional bets. [Note this capacity calculation is equal to the user’s original contribution, less the max loss possible from the bets they have engaged. Hypothetically, if perfectly offset risk was achieved in a true odds ratio, the user would be able to re-use 100% of their original contribution).

· A few notes regarding withdrawals of House liquidity:

o A house user will be able to withdraw unused liquidity at any time.

o There are no partial withdrawals. Currently, if withdrawing, it must be for 100% of unused liquidity.

o Once a user’s capacity has been fully engaged, and is therefore “recycled” to the back of the queue, withdrawal is no longer possible.

To recap, the main principles and take aways of the House order book are the following:

Participating as the House is still betting; It is not guaranteed to be risk free, but you can never lose more money than your deposit.
First come, first serve. Those who deposit first receive the first bets.
Odds changes can limit or reduce the value of bets allocated. Odds changes are unpredictable. Our design ensures our first principle is always maintained, even if this reduces the maximum amount of risk allocatable to each user.
You can, and are likely, to end with some directional risk. Flow is rarely perfectly balanced, even if you are early to contribute liquidity to a market.
It is the user’s responsibility to monitor odds changes and market news just as a sportsbook operator would.

Pulling it all together

The more often and earlier a user engages as the House and the more bets are placed, the more profitable a house depositor can be over the long term. The key to success is to participate frequently and to encourage bettors to bet in markets where you provide liquidity.

Good luck !

Application Onboarding

Six Sigma Sports is a licensed sports betting application and takes its responsibilities seriously. In order to use the application you must register an account and successfully complete the KYC process. The KYC process includes:

Liveliness check
ID Verification
Proof of Address

Users must not be present or reside in certain countries, including The United States and The United Kingdom ("Excluded Locations"); Please reference the T&C's for full details and note this list may be updated from time to time.

Platform Economics & Incentives

SGE and the Six Sigma Sports application

The SGE Token, Incentive Structure, and Ecosystem.

The SGE token serves several purposes:

· It is the native token of the SGE Network that helps secure the PoS blockchain and facilitate on-chain governance.

· It is the initial denomination for all activity in the Six Sigma Sports application.

· It is the Key to access the House functionality of the Six Sigma Sports application.

Important Notes to the illustrations and figures

· It is important to observe that the following illustrations are not 100% fixed as there are dynamic inputs which could impact the figures and are unknown at this time.

· The lock (and corresponding unlock) figures represent the most accelerated path possible. Token locks may be extended in the future.

· Application Rewards are primarily reserved for user acquisition and will be offered to bettors in the Six Sigma Sports application.

· The Strategic Reserve (SR) is the Six Sigma Sports House actor. We will use the SR to be the first and last line of liquidity for the sportsbook. Once the sportsbook is live, the size of the SR will also be variable depending on results. Please see the Six Sigma Sports GitBook for further details (https://six-sigma-sports.gitbook.io/docs/)

· Other definitions as used in the illustrations:

o Total Supply = Tokens that have been minted by the blockchain.

o Inflation = Max Supply - Total Supply (& is automatically distributed to validators/delegators)

o “Circulating Supply” = Total Supply - Locked Tokens

o “Circulating Supply” includes the Strategic Reserve (100M) and Application Rewards (up to 511M) as they are not locked on chain. However, the initial distribution of Application Rewards (betting incentives) will be variable and correspond to the engagement and reward programs of the application. As the application scales, so will reward token distribution, but this is not on a fixed schedule.

The token distribution at genesis can be categorized as follows:

Technical Specifications

Key On-Chain Definitions

SGE blockchain application specification and main concepts explanation

Bet

In the SGE Network chain, a bet is an entity that represents the details of a wager being placed on the system by the bettor. A bet is placed when a user wager tokens on particular odds of an event.

A bet is defined by:

Bet Fee: If in force, tokens may be deducted from the total number of wagered tokens as a bet fee. The purpose of deducting the betting fee from the wagered amount is to facilitate the expenses of the background operations that take place to complete an entire bet life cycle.
Bet Amount: This is the remaining number of tokens after the deduction of the betting fee from the total wagered amount. This is the amount for which the wager is actually placed. $Bet Amount = Total Wagered Amount - Bet Fee$
Payout: This is the number of tokens to be given back to the bettor if he wins the bet. For detailed calculations, have a look at
Payout Profit: This is the pure winning amount of a bet that represents the profit portion of the payout only. $Payout Profit = Payout - Bet Amount$
Max Loss Multiplier: This is a coefficient that is being used while calculating the available liquidity to be assigned for a bet to be fulfilled. In other words, this is the worst-case multiplier for a house that all of the bets get winner and the house should pay for all of them. This is different for each odds of a market.

Market

A market is a registered sporting event that takes place in the real world and has been added to the blockchain from an authentic source.

Bet Odds

Every Market has multiple odds on which the user can bet. For example, in a match between two teams and a 3-way result bet, the odds can be for Team A to win, Team B to win, or a draw. These odds determine the value of the payout to the user if he wins the bet.

House

The house is a representation of a betting house that is responsible for paying out the winner's profit. this module takes care of guaranteeing the final payment of the odds and prevents the SR pool module account to be bankrupt. Users can participate in the market as a house and get rewards according to their deposit amounts.

Order Book

The order book is responsible for the management of the participation of depositors of a market and the payout of the bettor's winning amount from the participant's deposited amounts. All of the calculations regarding participation and payouts are taking place in this module.

OVM

The OVM module is responsible for the validation and unmarshalling of the JWT tickets used by the blockchain modules. The trusted public keys are stored in the OVM module parameters and can be replaced with a proposal and voting mechanism.

Ticket

A ticket or a JWT ticket is used as an origin verification mechanism for pushing data to the blockchain. It is used to verify that any transaction made to the blockchain, such as a market addition, bet placement, etc, contains data from an authentic source. A ticket has an issued timestamp and an expiry timestamp, between which the ticket will be valid and can be used to make the transactions in the system. For more details on the ticket, visit the Guide/JWT ticket.

Payload

In the SGE Network chain, a payload is JSON data that contains the details of an entity. A payload can be useful for making transactions. The transactions related to the market, bet, and, the house modules require a JWT ticket. The creation of a JWT ticket requires JSON data related to the transaction, which we call a payload. Apart from the data required for the transaction, every payload should have fields named, iatmeans issue timestamp, and, extmeans expiry timestamp. The payloads, if required, are stated in the CLI section of each module.

UID

It is the unique identifier of an entity in the blockchain. The entities which can be uniquely identified by a UID are:

Bet
Market
Odds
Order Books

The format of UUID (or unique universal identifier) accepted in the blockchain is the format of a UUID. UUIDs are a sequence of digits equal to 128 bits. It accepts hexadecimal digits, i.e., 0-9 and a-f. The hexadecimal digits are grouped as 32 hexadecimal characters with four hyphens:

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Six Sigma Modules

The modules section elaborates on the technical details of all the modules.

Modules are logically separated packages in the code under x directory, the main logic of the application resides in these modules.

Bet

SGE blockchain application bet module description

The Bet module receives and processes requests to accept wagers and settles bets. In the case of wagering, it validates the request and places the bet.

For the settlement, the blockchain automatically queries resolved markets and then for each of these markets, checks the result of the market, and determines the betting result, then the order book The module responsible for the participation and fund management distribution will transfer the calculated values to the participants and the bettor accounts according to the settlement status.

Params

Bet module parameter types and definition.

The Bet module has the following parameters:

Batch Settlement Count: this is the count of bets to be settled automatically in each block.
Max bet by UID query count: is the max count of bets to be returned in the bets by UID list query.
Constraints: contains the bet wagering constraints.

The proto for the params is as follows:

// Params defines the parameters for the module.
message Params {
  option (gogoproto.goproto_stringer) = false;

  // batch_settlement_count is the batch settlement bet count.
  uint32 batch_settlement_count = 1;

  // max_bet_by_uid_query_count is the maximum bet by uid query items count.
  uint32 max_bet_by_uid_query_count = 2;
}

Constraints

Constraints define the constraints that will apply while accepting bets. The following constraints can be applied to the bet acceptance criteria:

Min Amount: Blockchain should not accept bets with a bet amount (after the deduction of the bet fee) less than the value stored in this field.
Fee: Blockchain should set a fee for every bet it accepts.

The proto for the constraints are as follows:

// Constraints is the bet constrains type for the bets
message Constraints {
  // min_amount is the minimum allowed bet amount.
  string min_amount = 1 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Int",
    (gogoproto.nullable) = false
  ];

  // fee is the fee that the bettor needs to pay to bet.
  string fee = 2 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Int",
    (gogoproto.nullable) = false
  ];
}

Accounts

Bet module, module accounts definition.

There is one account in the Bet module.

Bet Fee Collector: This account holds the betting fee transferred from the bettor to the bet_fee_collector module account.
During bet wagering, the betting fee is transferred from the bettor's account to the bet module account of the Bet module.
- Name of the account: bet_fee_collector

Store

Defines the way in which the state of the Bet is being stored in the chain.

Bet

The Bet message is used to store the data of a particular bet placed in the blockchain. The bet entity consists of the following fields:

uid: It is the unique identifier of a bet.
market_uid: It is the unique identifier of a market.
odds_uid: It is the unique identifier of an odds.
odds_type: It denotes the type of odds.
odds_value: It is the value of odds
amount: It is the total wager amount for a bet.
bet_fee: It is the number of tokens deducted from the amount (or total wager amount) as the betting fee.
status: It denotes the status of the bet that whether the bet is placed or settled, etc.
result: It is the result of the bet after the bet settlement.
creator: It is the creator of the transaction, which means the Bettor.
created_at: It is the timestamp at which the bet was placed on the system.
settlement_height: is the height at that the bet will be settled.
max_loss_multiplier: is the multiplier coefficient of the maximum loss.
bet_fulfillment: is the fulfillment of the participation item and payout amount.

The proto for the Bet messages is as follows:

Enums

Bet Status

It states the various types of the state a bet can have throughout its lifetime.

Result

It states the various types of states the result of a bet can have after the bet settlement.

Odds Type

It states the various types of odds that the system supports.

UID2ID

The Bet message is used to store the map of UIDs and sequential numeric IDs generated by the blockchain:

PendingBet

The active bet holds the information required for the bets that are not settled yet.

SettledBet

The active bet holds the information required for the bets that are settled.

Betstats

The Bet message is used to store any statistics that need to be tracked by the blockchain, currently, it tracks the total count of bets only.

BetFulfillnent

The fulfillment data structure for the participation and payout amount.

Payout

Supported Odds Types

Note: Let bet_amount be 3564819

Decimal(European): Calculated as bet_amount * oddsValue ex. 3564819 * 1.29 = 4598616.51.
Fractional(British): Calculated as bet_amount + (bet_amount * fraction) ex. 3564819 + (3564819 * 2/7) = 4583338.71.
Moneyline(American): Calculated as:
- Positive odds value: bet_amount + (bet_amount * |oddsValue/100|) ex. 3564819 + 3564819 * |+350/100| = 16041685.50 the result will be rounded to floor.
- Negative odds value: bet_amount + (bet_amount * |100/oddsValue|) ex. 3564819 + 3564819 * |100/-350| = 4583338.71 the result will be rounded to floor.

Precision

Some of the Online Calculators round the division result to two-digit precision in Fractional and Moneyline calculations. In other words, these online calculators try to convert Moneyline and Fractional odds to Decimal odds and then calculate the payout according to the calculated rounded decimal value. This approach makes a big difference in the resulting payout. SGE-Network is accepting bets with usge that may have a high value in the market. For this kind of value, it is better to have a high-precision calculation in the blockchain code.

Note: The final calculated payout amounts are rounded to 2-digit float values, so we have a small portion of lost benefits/payouts.

Keeper

The main logic of the Bet module definitions and methods.

Wagering

There are several steps for an incoming bet to be placed:

Check for duplicate UID
Validate the Ticket and unmarshal it to the wager payload type types.WagerTicketPayload
KYC validation according to the creator address in the message and the KYC address of the ticket if required.
Get the corresponding market from the market module and validate the odds existence.
Validate the minimum bet amount according to the module parameters.
Calculate and set the betting fee.
Validate and calculate the payout profit according to the odds type, bet amount, and odds value.
Call ProcessWager method of the Order Book module. this method handles the lock/unlock of the payout, participations, and bet fulfillments and transfers the payout and fees to the corresponding module accounts.
Set the initial Status, Result,CreatedAt, and BetFulfillments attributes.
Calculate the sequential ID, Set bet statistics, and bet to the bet module state.

Settlement

There are several steps for an incoming bet to be settled:

Check UUID validity
Get the corresponding bet object
Validates the bet creator stored in the state with the incoming bettorAddress of the settlement message.
Check the bet status not to be canceled or settled before.
Get the corresponding market from the market store and check if it exists, and is not aborted or canceled. If it is, calculate the payout and refund the bettor using RefundBettor method of the Order Book module keeper then sets the bet status as settled and finalizes the method.
Sets the proper bet result according to the WinnerOddsUIDs.
According to the bet result determined in the previous step, call BettorWins or BettorLoses of the Order Book module keeper.
Set the settled bet in the bet module state.

Batch Settlement

This is being used in the bet module end blocker in order to settle the bets automatically in batch.

APIs

This section elaborates on the transaction message handler methods being exposed by the Bet module.

Wager

When a wager transaction is processed, the following things happen:

If KYC is not ignored, KYC validation of the user should be approved and KYC ID should be equal to the creator's address.
Then, invoke the OVM module to validate the ticket.
After the ticket validation, the Order Book module is invoked to manage the transfer of funds involved in the process and distribute the participation exposures.
Then, a new bet will be created with the given data and stored in the bet module's KVStore, in the following way:

RPC

The RPC for adding a market is as follows:

Request Message

The request message for Wager is MsgWager. The proto for the request message is as follows:

Response Message

The response message Wager is MsgWagerResponse. The proto for the request message is as follows:

CLI

Bet module CLI.

This section specifies the queries, transactions, and required payloads. By following this section, one can get a deep understanding of the functioning of the bet module in the SGE Network chain.

Queries

Bet module CLI queries.

Queries of this module can be used to get the data of bets placed in the blockchain and params. The following queries have been exposed by the Bet module:

Query the bet module Params

sged q bet params

Query the list of all the bets

sged q bet bets

Query the list of all the bets of a bettor

sged q bet bets-by-creator [creator]

The below table explains the details of the argument required for the above query:

Params

Description

Type

Validation

Example

creator

creator account address

string

Required
Valid Address

sge1059gavv45jdp0l7c4kkskr0jae02j9cxmjr3f3

Query the list of all active bets of a market

sged q bet pending-bets [market-uid]

The below table explains the details of the argument required for the above query:

Params

Description

Type

Validation

Example

uid

UID of market

string

Required
Valid UUID

0435e5b6-635f-11ed-90a6-bb470175dfce

Query get specific bet

sged q bet bet [creator] [uid]

The below table explains the details of the argument required for the above query:

Params

Description

Type

Validation

Example

creator

creator account address

string

Required
Valid Address

sge1059gavv45jdp0l7c4kkskr0jae02j9cxmjr3f3

UID

UUID of the bet

string

Required
Valid UUID

0435e5b6-635f-11ed-90a6-bb470175dfce

Query bets by bettor and UID pair list

sged q bet bets-by-uids [creator:uid]

The below table explains the details of the argument required for the above query:

The creator:uid pair is separated by a colon : and each pair is separated by a comma , from other pairs.

Params

Description

Type

Validation

Example

creator:uid

creator account address and UID pair list

string

Required
Valid Address

sge1059gavv45jdp0l7c4kkskr0jae02j9cxmjr3f3:0435e5b6-635f-11ed-90a6-bb470175dfce

Transactions & Payloads

The exposed transactions CLI commands and ticket payloads by the Bet module.

Place Bet

The below transaction can be used to place a bet on the blockchain.

Command

The below table specifies the details of the arguments used in the above transaction:

Argument

Description

Type

Validation

Example

Payload

The payload for the place-bet transaction is as follows:

The values in the payload should be changed according to the data.

The details of the payload parameters are stated in the below table:

House

Params

House module parameter types and definition.

The House module has the following parameters:

Min Deposit: minimum allowed amount of deposit.
House Participation Fee: the fee that the depositor needs to pay to become the house of a market

The proto for the params is as follows:

// Params define the parameters for the house module.
message Params {
  option (gogoproto.goproto_stringer) = false;

  // min_deposit is the minimum amount of acceptable deposit.
  string min_deposit = 1 [
    (gogoproto.moretags) = "yaml:\"min_deposit\"",
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Int",
    (gogoproto.nullable) = false
  ];

  // house_participation_fee is the % of the deposit to be paid for a house
  // participation by the user
  string house_participation_fee = 2 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Dec",
    (gogoproto.nullable) = false
  ];
}

Accounts

House module, module accounts definition.

There is one account in the Accounts module.

House Fee Collector: This account holds the participation fee of all participants.
- Name of the account: house_fee_collector

Store

Defines the way in which the state of the House is being stored in the chain.

Deposit

The Deposit message is used to store the data of a particular deposition in the blockchain. The deposit is allowed on the markets that are in Active status. The deposit entity consists of the following fields:

creator: The address of the deposit message creator account.
depositor_address: The address of the depositor.
market_uid: It is the unique identifier of a market.
participation_index: The index of the participation of the market.
amount: The amount of the deposit.
fee: The amount of paid fee for the deposition.
liquidity: The amount of available liquid amount for participation (amount - fee).
withdraw_count: The count of withdrawals on a deposit.
total_withdraw_amount: The total amount of withdrawal value till now.

The proto for the Deposit messages is as follows:

// Deposit represents the deposit against a market held by an account.
message Deposit {
  option (gogoproto.equal) = false;
  option (gogoproto.goproto_getters) = false;
  option (gogoproto.goproto_stringer) = false;

  // creator is the bech32-encoded address of the depositor.
  string creator = 1 [ (gogoproto.moretags) = "yaml:\"creator\"" ];

  // creator is the bech32-encoded address of the depositor.
  string depositor_address = 2
      [ (gogoproto.moretags) = "yaml:\"depositor_address\"" ];

  // market_uid is the uid of market/order book against which deposit is being
  // made.
  string market_uid = 3 [
    (gogoproto.customname) = "MarketUID",
    (gogoproto.jsontag) = "market_uid",
    json_name = "market_uid"
  ];

  // participation_index is the index corresponding to the order book
  // participation
  uint64 participation_index = 4
      [ (gogoproto.moretags) = "yaml:\"participation_index\"" ];

  // amount is the amount being deposited on an order book to be a house
  string amount = 5 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Int",
    (gogoproto.nullable) = false,
    (gogoproto.moretags) = "yaml:\"amount\""
  ];

  // withdrawal_count is the total count of the withdrawals from an order book
  uint64 withdrawal_count = 6 [ (gogoproto.moretags) = "yaml:\"withdrawals\"" ];

  // total_withdrawal_amount is the total amount withdrawn from the liquidity
  // provided
  string total_withdrawal_amount = 7 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Int",
    (gogoproto.nullable) = false,
    (gogoproto.moretags) = "yaml:\"total_withdrawal_amount\""
  ];
}

Withdraw

The Withdraw message is used to store the data of a particular withdrawal in the blockchain. The withdraw entity consists of the following fields:

creator: The withdrawal message creator address.
id: The sequential ID of withdrawal generated by the blockchain.
address: The address of the depositor account.
market_uid: It is the unique identifier of a market.
participation_index: The index of the participants created when deposited.
mode: The mode of withdrawal.
amount: The amount of withdrawal.

The proto for the withdrawal messages is as follows:

// Withdrawal represents the withdrawal against a deposit.
message Withdrawal {
  option (gogoproto.equal) = false;
  option (gogoproto.goproto_getters) = false;
  option (gogoproto.goproto_stringer) = false;

  // creator is the bech32-encoded address of the depositor.
  string creator = 1 [ (gogoproto.moretags) = "yaml:\"creator\"" ];

  // withdrawal is the withdrawal attempt id.
  uint64 id = 2 [
    (gogoproto.customname) = "ID",
    (gogoproto.jsontag) = "id",
    json_name = "id",
    (gogoproto.moretags) = "yaml:\"id\""
  ];

  // address is the bech32-encoded address of the depositor.
  string address = 3 [ (gogoproto.moretags) = "yaml:\"address\"" ];

  // market_uid is the uid of market against which the deposit is
  // being made.
  string market_uid = 4 [
    (gogoproto.customname) = "MarketUID",
    (gogoproto.jsontag) = "market_uid",
    json_name = "market_uid"
  ];

  // participation_index is the id corresponding to the book participation
  uint64 participation_index = 5
      [ (gogoproto.moretags) = "yaml:\"participation_index\"" ];

  // mode is the withdrawal mode enum value
  WithdrawalMode mode = 6 [ (gogoproto.moretags) = "yaml:\"mode\"" ];

  // amount is the amount being withdrawn.
  string amount = 7 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Int",
    (gogoproto.nullable) = false,
    (gogoproto.moretags) = "yaml:\"amount\""
  ];
}

Enums

// WithdrawalMode is the enum type for the withdrawal mode.
enum WithdrawalMode {
  // invalid
  WITHDRAWAL_MODE_UNSPECIFIED = 0;
  // full
  WITHDRAWAL_MODE_FULL = 1;
  // partial
  WITHDRAWAL_MODE_PARTIAL = 2;
}

Keeper

The main logic of the House module definitions and methods.

Deposit

There are several steps for a deposit to be made:

Set participation fee.
Initiate participation in the market by order book module.
Set the participation index generated by the order book module.
Check the authz grant to be available for the message creator and depositor address in the ticket.
Update authz spend limit or delete if is zero.
Set the deposit in the state of the blockchain.

// Deposit performs deposit operation to participate as a house in a specific market/order book
func (k msgServer) Deposit(goCtx context.Context,
	msg *types.MsgDeposit,
) (*types.MsgDepositResponse, error) {
	ctx := sdk.UnwrapSDKContext(goCtx)

	params := k.GetParams(ctx)
	if err := msg.ValidateSanity(ctx, &params); err != nil {
		return nil, sdkerrors.Wrap(err, "invalid deposit")
	}

	var payload types.DepositTicketPayload
	if err := k.ovmKeeper.VerifyTicketUnmarshal(goCtx, msg.Ticket, &payload); err != nil {
		return nil, sdkerrors.Wrapf(types.ErrInTicketVerification, "%s", err)
	}

	depositorAddr := msg.Creator
	if payload.DepositorAddress != "" &&
		payload.DepositorAddress != msg.Creator {
		if err := k.ValidateMsgAuthorization(ctx, msg.Creator, payload.DepositorAddress, msg); err != nil {
			return nil, err
		}
		depositorAddr = payload.DepositorAddress
	}

	if err := payload.Validate(depositorAddr); err != nil {
		return nil, sdkerrors.Wrapf(types.ErrInTicketPayloadValidation, "%s", err)
	}

	participationIndex, err := k.Keeper.Deposit(
		ctx,
		msg.Creator,
		depositorAddr,
		msg.MarketUID,
		msg.Amount,
	)
	if err != nil {
		return nil, sdkerrors.Wrap(err, "failed to deposit")
	}

	msg.EmitEvent(&ctx, depositorAddr, participationIndex)

	return &types.MsgDepositResponse{
		MarketUID:          msg.MarketUID,
		ParticipationIndex: participationIndex,
	}, nil
}

Withdraw

There are several steps for a withdrawal to be made:

Get the corresponding deposit.
Check the amount and validate if it is possible to pay.
Call the order bookkeeper to liquidate the participation.
Check the authz grant to be available for the message creator and depositor address in the ticket.
Update authz withdrawal limit or delete if is zero.
Set the withdrawal in the state.
Modify and set the deposit and put the withdrawal info.

// Withdraw performs withdrawal of unused tokens corresponding to a deposit.
func (k msgServer) Withdraw(goCtx context.Context,
	msg *types.MsgWithdraw,
) (*types.MsgWithdrawResponse, error) {
	ctx := sdk.UnwrapSDKContext(goCtx)

	var payload types.WithdrawTicketPayload
	if err := k.ovmKeeper.VerifyTicketUnmarshal(goCtx, msg.Ticket, &payload); err != nil {
		return nil, sdkerrors.Wrapf(types.ErrInTicketVerification, "%s", err)
	}

	isOnBehalf := false
	depositorAddr := msg.Creator
	if payload.DepositorAddress != "" {
		depositorAddr = payload.DepositorAddress
		isOnBehalf = true
	}

	if err := payload.Validate(depositorAddr); err != nil {
		return nil, sdkerrors.Wrapf(types.ErrInTicketPayloadValidation, "%s", err)
	}

	// Get the deposit object
	deposit, found := k.GetDeposit(ctx, depositorAddr, msg.MarketUID, msg.ParticipationIndex)
	if !found {
		return nil, sdkerrors.Wrapf(types.ErrDepositNotFound, ": %s, %d", msg.MarketUID, msg.ParticipationIndex)
	}

	var err error
	msg.Amount, err = k.orderbookKeeper.CalcWithdrawalAmount(ctx,
		depositorAddr,
		msg.MarketUID,
		msg.ParticipationIndex,
		msg.Mode,
		deposit.TotalWithdrawalAmount,
		msg.Amount,
	)
	if err != nil {
		return nil, sdkerrors.Wrapf(types.ErrInTicketVerification, "%s", err)
	}

	if isOnBehalf {
		if err := k.ValidateMsgAuthorization(ctx, msg.Creator, payload.DepositorAddress, msg); err != nil {
			return nil, err
		}
	}

	id, err := k.Keeper.Withdraw(ctx, deposit, msg.Creator, depositorAddr, msg.MarketUID,
		msg.ParticipationIndex, msg.Mode, msg.Amount)
	if err != nil {
		return nil, sdkerrors.Wrap(err, "process withdrawal")
	}

	msg.EmitEvent(&ctx, depositorAddr, id)

	return &types.MsgWithdrawResponse{
		ID:                 id,
		MarketUID:          msg.MarketUID,
		ParticipationIndex: msg.ParticipationIndex,
	}, nil
}

APIs

This section elaborates on the transaction message handler methods being exposed by the House module.

Deposit

When a deposit transaction is processed, the following things happen:

Validate the incoming deposit message.
Call the Deposit method of the keeper.

RPC

The RPC for adding a market is as follows:

// Deposit defines a method for performing a deposit of coins to become part
// of the house corresponding to a market.
rpc Deposit(MsgDeposit) returns (MsgDepositResponse);

Request Message

The request message for Deposit is MsgDeposit. The proto for the request message is as follows:

// MsgDeposit defines a SDK message for performing a deposit of coins to become
// part of the house corresponding to a market.
message MsgDeposit {
  option (gogoproto.equal) = false;
  option (gogoproto.goproto_getters) = false;

  // creator is the account who makes a deposit
  string creator = 1 [ (gogoproto.moretags) = "yaml:\"creator\"" ];
  // market_uid is the uid of market/order book against which deposit is being
  // made.
  string market_uid = 2 [
    (gogoproto.customname) = "MarketUID",
    (gogoproto.jsontag) = "market_uid",
    json_name = "market_uid"
  ];
  // amount is the amount being deposited on an order book to be a house
  string amount = 3 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Int",
    (gogoproto.nullable) = false
  ];
  // ticket is the jwt ticket data.
  string ticket = 4;
}

Response Message

The response message for Deposit is MsgDepositResponse. The proto for the request message is as follows:

// MsgDepositResponse defines the Msg/Deposit response type.
message MsgDepositResponse {
  string market_uid = 1 [
    (gogoproto.customname) = "MarketUID",
    (gogoproto.jsontag) = "market_uid",
    json_name = "market_uid"
  ];

  uint64 participation_index = 2
      [ (gogoproto.moretags) = "yaml:\"participation_index\"" ];
}

Withdraw

When a withdrawal transaction is processed, the following things happen:

Validate the incoming deposit message.
Call the Deposit method of the keeper.

RPC

The RPC for adding a market is as follows:

// Withdraw defines a method for performing a withdrawal of coins of unused
// amount corresponding to a deposit.
rpc Withdraw(MsgWithdraw) returns (MsgWithdrawResponse);

Request Message

The request message for Withdraw is MsgWithdraw. The proto for the request message is as follows:

// MsgWithdraw defines a SDK message for performing a withdrawal of coins of
// unused amount corresponding to a deposit.
message MsgWithdraw {
  option (gogoproto.equal) = false;
  option (gogoproto.goproto_getters) = false;

  string creator = 1 [ (gogoproto.moretags) = "yaml:\"creator\"" ];
  string market_uid = 2 [
    (gogoproto.customname) = "MarketUID",
    (gogoproto.jsontag) = "market_uid",
    json_name = "market_uid"
  ];
  // participation_index is the index corresponding to the order book
  // participation
  uint64 participation_index = 3
      [ (gogoproto.moretags) = "yaml:\"participation_index\"" ];
  // mode is the withdrawal mode. It can be full or partial withdraw
  WithdrawalMode mode = 4 [ (gogoproto.moretags) = "yaml:\"mode\"" ];
  // amount is the requested withdrawal amount
  string amount = 5 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Int",
    (gogoproto.nullable) = false
  ];
  // ticket is the jwt ticket data.
  string ticket = 6;
}

Response Message

The response message for Withdraw is MsgWithdrawResponse. The proto for the request message is as follows:

// MsgWithdrawResponse defines the Msg/Withdraw response type.
message MsgWithdrawResponse {
  uint64 id = 1 [
    (gogoproto.customname) = "ID",
    (gogoproto.jsontag) = "id",
    json_name = "id",
    (gogoproto.moretags) = "yaml:\"id\""
  ];

  string market_uid = 2 [
    (gogoproto.customname) = "MarketUID",
    (gogoproto.jsontag) = "market_uid",
    json_name = "market_uid"
  ];

  uint64 participation_index = 3
      [ (gogoproto.moretags) = "yaml:\"participation_index\"" ];
}

CLI

House module CLI.

This section specifies the queries, transactions, and required payloads. By following this section, one can get a deep understanding of the functioning of the house module in the SGE Network chain.

Queries

House module CLI queries.

Query the House Params

Query the Deposits

Query deposits of a depositor by address

The below table explains the details of the argument required for the above query:

Params

Description

Type

Validation

Example

Query withdrawals of a depositor by address

The below table explains the details of the argument required for the above query:

Params

Description

Type

Validation

Example

Query withdrawal by ID

The below table explains the details of the argument required for the above query:

Transactions

Deposit

The below transaction can be used to deposit on the blockchain.

Command

sged tx house deposit [market_uid] [amount] [ticket] --flags

The below table specifies the details of the arguments used in the above transaction:

Argument

Description

Type

Validation

Example

market_uid

Unique Identifier of a market

string

Required
Valid UUID

0435e5b6-635f-11ed-90a6-bb470175dfce

amount

is the deposit amount (contains bet fee also)

Integer

Positive
Should be greater than the minimum deposit amount of the module

100000000

ticket

ticket data of deposit

string

Required

Valid Ticket

Withdraw

The below transaction can be used to withdraw on the blockchain.

Command

sged tx house withdraw [market_uid] [participation_index] [ticket] [mode] [amount] --flags

The below table specifies the details of the arguments used in the above transaction:

Argument

Description

Type

Validation

Example

market_uid

Unique Identifier of a market

string

Required
Valid UUID

0435e5b6-635f-11ed-90a6-bb470175dfce

participation_index

The index of the participation when creating deposit

uint64

Required

ticket

Ticket data of the withdraw

string

Required

Valid UUID

mode

Mode of the withdrawal (full or partial)

uint32

Required

amount

is the deposit amount (contains bet fee also)

Integer

Positive
Should be greater than the minimum deposit amount of the module

100000000

Market

Overview and Concepts

Purpose

The Market module serves the following purposes in the SGE Network chain:

The market module pushes the verified data of the sports events onto the SGE Network chain from off-chain sources. This way the sport-event is added to the blockchain and becomes readily available for the bettors to wager on it.
It stores the markets pushed to the blockchain.
It also resolves the markets when the market is finished and the winner odds are passed to it, hence declaring the result of the market.
It can update the markets as and when the update request is made.
It can activate or deactivate the markets, thus making them available or unavailable, respectively, for placing bets.

Params

Market module parameter types and definition.

The Market module do not have any parameters.

Store

This section defines the way in which the state of the Market is being stored in the chain.

Market

A market is an entity being stored in the SGE Network chain to hold the data related to a market that has been verifiably pushed to the blockchain. It contains the following fields:

uid: It is the unique identifier of a market.
start_ts: It is the timestamp when a particular market will start.
end_ts: It is the timestamp when a particular market will end.
odds: It is a list of all the odds for a particular market. the meta is a human-readable description of the odds, it can be a JSON string to be used by oracle services. Ex: { "uid" :uid_win_event, "meta": "tam A wins" }, { "uid": uid_draw_event, "meta": "draw"}, { "uid": uid_loose_event, "meta": "team A loose"}
winner_odds_uids: It is a list of all the UIDs of odds that have won the market. This should necessarily be a subset of the above-provided odds_uids.
status: It defines the current state of the market.
resolution_ts: It is the timestamp when the market came to a resolution i.e. when the system received a resolution request for a market.
creator: It holds the account address responsible for the addition of the market to the blockchain.
meta: It is a human-readable description of the market, it can be a JSON string to be used by oracle services.
book_id is the ID of the order book created and assigned to the market, this is the same value as market UID.

The proto for the market is as follows:

Market Status

The status of a market in the chain can be defined in either of the five following ways:

API

This section elaborates on the transaction message handler methods being exposed by the Market module.

Add

When a transaction of adding a market is processed, the following actions take place:

The creator address and the ticket format are validated in the market module.
The OVM module is invoked to retrieve the ticket's contents and validate it.
If the ticket is valid, it is checked if the market already exists.
If the market does not already exist, a new market is created with the provided data and added to the market module's KVStore. The market is created as shown below:

RPC

The RPC for adding a market is as follows:

Request Message

The request message for Add is MsgAdd. The proto for the request message is as follows:

Add ticket payload

Response Message

The response message of the MsgAdd is MsgAddResponse. The proto for the response message is as follows:

Resolve

When a transaction of resolving a market is processed, the following actions take place:

The creator address and the ticket format are validated in the market module.
The OVM module is invoked to retrieve the ticket's contents and validate it.
If the ticket is valid, it is checked if the market already exists.
If the market already exists, the market status should,types.MarketStatus_STATUS_ACTIVEso that the market can be resolved now.
Then the market is resolved as per the provided odds value and status and stored in the KVStore of the market module.

RPC

The RPC for resolving a market is as follows:

Request Message

The request message for Resolve is MsgResolve. The proto for the request message is as follows:

Resolve ticket payload

The proto of the payload accepted for the resolution of the market is as follows:

Response Message

The response message of the MsgResolve is MsgResolveResponse. The proto for the response message is as follows:

Update

When a transaction of updating a market is processed, the following actions take place:

The creator address and the ticket format are validated in the market module.
The OVM module is invoked to retrieve the ticket's contents and validate it.
If the ticket is valid, it is checked if the market already exists.
If the market already exists, the market status should be types.MarketStatus_STATUS_Active or types.MarketStatus_STATUS_Inactive
Then the market is updated as per the provided data and stored in the KVStore of the market module again in the following way:

RPC

The RPC for updating a market is as follows:

Request Message

The request message for Update is MsgUpdate. The proto for the request message is as follows:

Update ticket payload

The proto of the payload accepted for updating the market is as follows:

Response Message

The response message of the Update is MsgUpdateResponse. The proto for the response message is as follows:

CLI

Market module CLI.

This section specifies the queries, transactions, and required payloads. By following this section, one can get a deep understanding of the functioning of the house module in the SGE Network chain.

Queries

Market module CLI queries

Queries of this module can be used to get the data of markets and params. The following queries have been exposed by the market module:

Query the Params

sged q market params

Query all the markets

sged q market markets

Query a market by uid

sged q market market [uid]

Gets a single UID and returns the corresponding market, the following table explains the details of the argument required for the above query:

Params

Description

Type

Validation

Example

uid

Unique Identifier of a market

string

Required
Valid UUID

0435e5b6-635f-11ed-90a6-bb470175dfce

Query specific markets by UID list

sged q market markets-by-uids [uid]

Gets a list of comma-separated UID and returns the list of markets. The below table explains the details of the argument required for the above query:

Params

Description

Type

Validation

Example

uid

A list of unique identifiers of markets separated by ,

string

Required
Valid UUID

0435e5b6-635f-11ed-90a6-bb470175dfce

Transactions & Payloads

The exposed transactions CLI commands and ticket payloads by the Market module.

Add Market Transaction

The below transaction can be used to add a market to the blockchain.

Command

Payload

The payload for the add-market transaction is as follows:

The values in the payload should be changed according to the data.

Update Market Transaction

The below transaction can be used to update a market stored in the blockchain.

Command

Payload

The payload for the update-market transaction is as follows:

The values in the payload should be changed according to the data.

Resolve Market Transaction

The below transaction can be used to resolve a market to the blockchain.

Command

Payload

The payload for the resolve-market transaction is as follows:

The values in the payload should be changed according to the data.

Update Market Transaction

The below transaction can be used to update a market to the blockchain.

Command

Payload

The payload for the update-market transaction is as follows:

The values in the payload should be changed according to the data.

Mint

The mint module is responsible for calculating and minting SGE tokens that will be distributed among validators as block rewards. The SGE mint module implements the concept of phases which defines the inflation curve of the SGE Network chain over its lifetime. Refer to the Token Economics section to know more about the inflation curve.

Overview & concepts

The Mint module is responsible for minting tokens to reward validators and delegators for helping secure the chain. The Mint module is responsible for the inflation in the chain.

The Minting Mechanism of the SGE Network chain

Unlike the default Mint Module of the Cosmos, which can vary the inflation rate dynamically based on the ratio of the bonded and the unbonded tokens at any point in time, the Mint module of the SGE Network chain follows a strict regime of inflation rates defined by the phases.

Phases

Phases are nothing but specific discreet time frames during which a certain inflation rate holds for the chain. Phases have two components:

duration: The duration is defined as the year_coefficient. It defines the time in years for which a phase will hold. For example, a year_coefficient of 0.75 means that the phase will last for 9 months, that is, 3/4th of a year.
inflation: This parameter defines the inflation rate of the chain for the phase in question. Inflation is defined as a decimal. That is inflation of 0.10000 means an inflation rate of 10%.

The duration and inflation rate of phases can be modified via governance. For more details about phases, visit phases.

If all the specified phases are over, the chain enters a special phase called the final_phase, where the phase duration is infinite and the phase inflation is zero. Note that the inflation rate does not depend on the number of bonded and unbonded tokens

Params

Bet module parameter types and definition.

The Mint module employs two types of parameters-

Genesis parameters
Minter parameters

Genesis Parameters

These parameters determine the inflation curve of the SGE Network chain over the lifetime of the chain. These parameters define the basic configuration of the chain. These parameters can be modified only via governance.

blocks_per_year: This parameter determines the average number of blocks that will be generated over a year. In the above example, every 51840 block will be considered as 1 year.
mint_denom: This value represents the coin denomination of the minted coins
phases: This is an array of phase durations and their corresponding inflation rates. A detailed explanation of the Phases can be found in the concepts section.
exclude_amount: By default, inflation is calculated over the total supply of coins. This parameter is used to exclude some amount of tokens before calculating the inflation amount. This is in accordance with Token Economics.

Minter Parameters

Minter is an entity that holds the fields required for the functioning of the minting mechanism. These parameters are used to store the current state of the minter. The minter parameters are automatically calculated during the operation of the chain. These can't be influenced directly via governance.

phase_provision: This value calculates how many tokens are to be minted in the current phase. The value is recalculated at the end of every phase.
inflation: This parameter defines the inflation rate for the current phase.
phase_step: This parameter determines which phase the minter is in currently.
truncated_tokens: The block provision equals the current annual provision divided by the number of blocks per year, the result needs to be converted to sdk.Int as it is used in the MintCoins method of the bank module of blockchain. So the decimal part of the value will be truncated from the actual value, so we store truncated values in the minter and add this value to the annual provision in the next block.

Store

Minter

The Minter message is used to store the data of the current inflation in the blockchain. The Minter entity consists of the following fields:

inflation: current inflation rate of the chain.
phase_step: Phase of inflation that the chain is working with.
phase_provisions: Expected provisions of the current phase.
truncated_tokens: Holds the truncated value of the mint calculations of the phases.

The proto for the Order Book messages is as follows:

// Minter represents the minting state.
message Minter {
  // inflation is the current annual inflation rate.
  string inflation = 1 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Dec",
    (gogoproto.nullable) = false
  ];
  // phase_step is the index of phases slice + 1.
  int32 phase_step = 2;
  // phase_provisions is the current phase expected provisions.
  string phase_provisions = 3 [
    (gogoproto.moretags) = "yaml:\"phase_provisions\"",
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Dec",
    (gogoproto.nullable) = false
  ];
  // truncated_tokens holds current truncated tokens because of Dec to Int
  // conversion in the minting.
  string truncated_tokens = 4 [
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Dec",
    (gogoproto.nullable) = false
  ];
}

Phase

The Phase message is used to store the data of a particular phase in the parameters in the blockchain. The Phase entity consists of the following fields:

inflation: The inflation rate of the phase.
year_ocefficient: The coefficient of a year (ex. 0.75 == 9 months).

// Phase defines the phase parameters for the module.
message Phase {
  option (gogoproto.goproto_stringer) = false;

  // inflation is the current phase inflation rate.
  string inflation = 1 [
    (gogoproto.moretags) = "yaml:\"inflation\"",
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Dec",
    (gogoproto.nullable) = false
  ];
  // year_coefficient is the proportion of a complete year.
  string year_coefficient = 2 [
    (gogoproto.moretags) = "yaml:\"year_coefficient\"",
    (gogoproto.customtype) = "github.com/cosmos/cosmos-sdk/types.Dec",
    (gogoproto.nullable) = false
  ];
}

Begin Block

Adding automatic execution of certain logic at the beginning of each block is being done in the Mint Module. The section elaborates on all the begin-blocker executions in the Mint module. Minting parameters are recalculated and inflation is paid at the beginning of each block.

Detect Current Phase

Checking if the chain has moved from one phase to another, including the final phase, and re-setting the minter in case the phase has changed, is a begin-blocker operation implemented in the Mint module. It is implemented as follows:

// CurrentPhase returns current phase of the inflation
func (m Minter) CurrentPhase(params Params, currentBlock int64) (Phase, int) {
	if currentBlock == 1 {
		return params.GetPhaseAtStep(1), 1
	}

	cumulativeBlock := sdk.NewDec(0)
	var currentStep int
	var found bool

	// add each phase blocks until reaching the range which the current block is in
	for i := 0; i < len(params.Phases); i++ {
		// add current phase blocks to cummulative blocks
		cumulativeBlock = cumulativeBlock.Add(params.getPhaseBlocks(i + 1))

		currentStep = i + 1

		// if the current block is less than or equal to cummulative blocks
		// this means that we are in the i+1 step which is set in above line
		if sdk.NewDec(currentBlock).LTE(cumulativeBlock) {
			found = true
			// it is the current phase
			// so there is no need for furthur phase blocks check
			break
		}
	}

	// if there is no detected phase,
	// this means that the rest of inflation is zero as end phase
	if !found {
		return EndPhase(), EndPhaseAlias
	}

	// the phase has found and we need to return the phase specifications
	return params.GetPhaseAtStep(currentStep), currentStep
}

If the phase has changed, set the minter with the changed parameters:

// set the new minter properties if the phase has changed or inflation has changed
if currentPhaseStep != cast.ToInt(minter.PhaseStep) || !minter.Inflation.Equal(currentPhase.Inflation) {
	// set new inflation rate
	newInflation := currentPhase.Inflation
	minter.Inflation = newInflation

	// set new phase step
	minter.PhaseStep = cast.ToInt32(currentPhaseStep)

	// set phase provisions of new phase step
	totalSupply := k.TokenSupply(ctx, params.MintDenom)
	minter.PhaseProvisions = minter.NextPhaseProvisions(totalSupply, params.ExcludeAmount, currentPhase)

	// store minter
	k.SetMinter(ctx, minter)
}

Next Phase Provision

Since the SGE Network chain is predominantly reliant on phases for its inflation model, the phase_provision keeps track of the total amount of tokens to be distributed in the current phase. This value is calculated every time there is a phase change.

// NextPhaseProvisions returns the phase provisions based on current total
// supply and inflation rate.
func (m Minter) NextPhaseProvisions(totalSupply sdk.Int, excludeAmount sdk.Int, phase Phase) sdk.Dec {
	// calculate annual provisions as normal
	annualProvisions := m.Inflation.MulInt(totalSupply.Sub(excludeAmount))

	// return this phase provisions according to the year coefficient
	// ex.
	//    year coefficient = 0.5
	//    blocks per year = 100
	// 	  this phase provisions is 100 * 0.5 => 50
	return annualProvisions.Mul(phase.YearCoefficient)
}

Block Provision

Calculate the provisions generated for each block based on the current phase provisions. The provisions are then minted by the mint module's ModuleMinterAccount and then transferred to the auth's FeeCollector ModuleAccount.

// BlockProvisions returns the provisions for a block based on the phase
// provisions rate.
func (m Minter) BlockProvisions(params Params, phaseStep int) (sdk.Coin, sdk.Dec) {
	// get total blocks in this phase
	blocksPerPhase := params.getPhaseBlocks(phaseStep).TruncateDec()

	// detect each block provisions then and the truncated value from previous block
	provisionAmt := m.PhaseProvisions.Quo(blocksPerPhase).Add(m.TruncatedTokens)

	// extract the integer and decimal part of provisions
	// the decimal part is the truncated value because of conversion to sdk.Int
	// so the decimal part is truncated and needs to be added in next block
	intPart := provisionAmt.TruncateDec()
	decPart := provisionAmt.Sub(intPart)

	return sdk.NewCoin(params.MintDenom, intPart.TruncateInt()), decPart
}

CLI

This section specifies the queries, transactions, and required payloads. By following this section, one can get a deep understanding of the functioning of the mint module in the SGE Network chain.

Queries

Query the Params

Query the current inflation rate

Query the current inflation phase step

Query the current phase provisions

Query if inflation is in the end_phase or not

Orderbook

The Order Book is a module for the order book and fund management over module accounts and actors.

Accounts

Order book module, module accounts definition.

The Order Book module has one module account which is as follows:

Book Liquidity Account
1. Name: orderbook_liquidity_pool
2. This account holds the liquidity of the books and bets amount and payout of all accounts.

Store

Defines the way in which the state of the Order book is being stored in the chain.

OrderBook

The OrderBook message is used to store the data of a particular order book in the blockchain. The OrderBook entity consists of the following fields:

uid: The UID of the order book.
participation_count: The count of participation in this book.
odds_count: Count of odds registered in the market related to this book.
status: the status of the book.

The proto for the Order Book messages is as follows:

Enums

OrderBookParticipation

The BookParticipation message is used to store the data of a particular participation in the OrderBook in the blockchain. The BookParticipation entity consists of the following fields:

index: The sequential index of participation in a book.
order_book_uid: The uinque identifier of the OrderBook.
participant_address: The account address of the participant.
liquidity: The amount of participation minus fees.
current_round_liquidity: Participations are calculated in multiple rounds depending on the payout amount.
exposures_not_filled: The count of exposures that are not filled till now.
total_bet_amount: Total value of bet amount that is calculated from the payout.
current_round_total_bet_amount: Total value of bet amount in the current round calculations.
max_loss: Maximum possible loss of participation.
current_round_max_loss_odds_uid: UID list of odds with maximum calculated loss.
actual_profit: The pure profit that goes to the participant account balance.
is_settled: Show whether the participation is settled or not.

The proto for the Order Book messages is as follows:

ParticipationBetPair

The ParticipationBetPair message is used to store the data of a particular participation and bet in the OrderBook in the blockchain. The ParticipationBetPair entity consists of the following fields:

order_book_uid: The uinque identifier of the OrderBook.
participant_index: The index of participation in a book.
bet_uid: True unique identifier of bet that payout was done from participation.

OrderBookOddsExposure

The BookOddsExposure message is used to store the data of a particular exposure of odds in the OrderBook in the blockchain. The BookOddsExposure entity consists of the following fields:

order_book_uid: The uinque identifier of the OrderBook.
odds_uid: The unique identifier of the odds.
fulfillment_queue: The queue of bet fulfillment for the odds exposure.

ParticipationExposure

The ParticipationExposure message is used to store the data of a particular exposure of participation in the OrderBook in the blockchain. The ParticipationExposure entity consists of the following fields:

order_book_uid: The uinque identifier of the OrderBook.
odds_uid: The unique identifier of the Odds.
participation_index: The index of participation in the Order book.
exposure: The exposure is the payout that should be done.
bet_amount: The calculated bet amount of the expected payout.
is_fulfilled: Fulfillment status of the exposure.
round: Current round of calculation of exposures.

OrderBookStats

The OrderBookStats message is used to store the statistics data of Order Books in the blockchain. The OrderBookStats entity consists of the following fields:

resolved_unsettled: The list of resolved markets that have unsettled bets.

Purpose

The purpose of this lock is to maintain idempotency in the system. The payout lock checks for idempotency whenever an exported keeper function of the module is invoked by any other module. It follows the following conditions:

While wagering
- If a payout lock (or bet UID) exists in the store, then the wager request is rejected, inferring that the bet has already been placed in the blockchain with the same bet UID.
- If the payout lock does not exist, then the wager request is accepted and a payout lock with the bet UID of the bet is stored in the blockchain.
While bet settlement
- If the payout lock does not exist in the store, then the bet settlement request is rejected.
- If the payout lock exists, then the bet settlement request is accepted, the settlement is processed, and the payout is deleted from the store.

Params

The Order Book module has the following parameters:

Max order book participation: maximum allowed participation count of an order book.
Batch Settlement Count: Automatic batch settlement count in each block.
Requeue Threshold: This is a defined value for resetting the fulfillment queue if liquidity is less than this value.

The proto for the params are as follows:

CLI

Order Book module CLI.

This section specifies the queries, transactions, and required payloads. By following this section, one can get a deep understanding of the functioning of the orderbook module in the SGE Network chain.

OVM

Origin Verification Module

The Origin Verification Mechanism (OVM) is used to verify the origin of any off-chain data when they are pushed into the chain. This module ensures that no corrupt or unauthenticated data can make its way into the chain.

Overview & concepts

The SGE Network chain relies on external off-chain data of matches and other markets. To push this data reliably to the chain, some kind of origin verification is required. The OVM module essentially fills this role in the SGE Network chain. The OVM Module verifies the following data:

Event data pushed by the House to the chain.
Validity of Odds data during bet placement by the bettor.

Concepts

To verify the origin of the data, a simple mechanism of signing and verification with a private key and the corresponding public key is performed.

The data that needs to be pushed into the blockchain is first signed by the private key of a trusted source. This process occurs off-chain. Essentially, we create an encrypted ticket with the trusted private key. The curve used for signing and verification of the ticket is the Edwards-curve Digital Signature Algorithm. This algorithm has been chosen for the following benefits:

Fast single-signature verification
Fast batch verification
Very fast signing Fast key generation
High-security level
Foolproof session keys
Collision resilience
No secret array indices
No secret branch conditions
Small signatures
Small keys

Details of the algorithm can be found here.

Working Principle

After generating the encrypted signed ticket, this signature data is included in the transactions. This includes transactions for adding/editing betting markets on the chain, as well as verifying odds when the user places on these markets. All tickets come with an expiry timestamp which invalidates the ticket after a certain duration. This facility prevents the use or abuse of old and expired tickets.

The OVM Module essentially stores a list of trusted public keys. These public keys are just the counterpart to the private keys that were used to sign and encrypt the tickets off-chain. When a transaction is made to the chain that necessitates verification of the origin of the data, the corresponding module invokes the OVM module for verification and decryption purpose. The OVM Module works as an interface, which can decode any signed data passed to it when supplied with the encryption algorithm and the decrypted type. This design completely nullifies the need to change the structure of the OVM if the ticket structure changes. This essentially enables the OVM to be a global verification module.

When the OVM is invoked, it first attempts to verify the signature of the data against the list of registered public keys. If the signature is verified successfully by the leader public key (the first element in the public keys slice in the key vault store), the OVM decrypts the data into the provided structure and returns it to the invoking module. In case the signature verification fails, or the ticket seems to have expired, or the decrypted structure does not match with the expected structure, the verification is considered to be a failure and a corresponding error is returned to the invoking module, which consequently results in failure of the transaction.

The OVM Leader is the public key that is being used for the verification of the tickets, The first element of the Key Vault public keys is the leader. If the private key of the leader's public key gets corrupt/hacked/leaked, The holders of the rest of the public keys can create a pub keys-change proposal to replace the leaked public key with a new one and choose the new leader key. Each proposal needs at least 3 "yes" or 2 "no" to make blockchain code to decide about the proposal's approval or rejection, the modification happens in the end blocker if the condition of votes is satisfied.

APIs

The OVM module has only one state table consisting of a list of strings that are the trusted public keys.

Key Vault

The Public Keys is an entity that stores the public keys of the registered oracles which can verifiably push data to the blockchain. It contains:

public_keys: A list of allowed public keys.

The proto for the PublicKeys is as follows:

// KeyVault is the information of important keys stored in ovm state.
message KeyVault {
  // public_keys contains allowed public keys.
  repeated string public_keys = 1 [ (gogoproto.nullable) = false ];
}

PublicKeysChangeProposal

The public keys change proposal is store in the state to be used to change the compromised public keys.

// PublicKeysChangeProposal is the type for the proposal for additions and
// removals of pub keys.
message PublicKeysChangeProposal {
  // id is the sequential id of the proposal generated by the blockchain.
  uint64 id = 1;
  // creator is the account address of the proposal creator.
  string creator = 2;
  // modifications contain the ticket payload of the proposal.
  PubkeysChangeProposalPayload modifications = 3
      [ (gogoproto.nullable) = false ];
  // votes contains the votes of the proposal.
  repeated Vote votes = 4;
  // start_ts is the block time that the proposal is set.
  int64 start_ts = 5 [
    (gogoproto.customname) = "StartTS",
    (gogoproto.jsontag) = "start_ts",
    json_name = "start_ts"
  ];
  // result is the result of the finished proposal.
  ProposalResult result = 6;
  // result_meta is the metadata related to the result of the finished proposal.
  string result_meta = 7;
  // finish_ts is the block time that the proposal is set as finished.
  int64 finish_ts = 8 [
    (gogoproto.customname) = "FinishTS",
    (gogoproto.jsontag) = "finish_ts",
    json_name = "finish_ts"
  ];
  // status is the status of a proposal.
  ProposalStatus status = 9;
}

// ProposalResult is the enum type for the proposal result.
enum ProposalResult {
  // unchosen value
  PROPOSAL_RESULT_UNSPECIFIED = 0;
  // approved
  PROPOSAL_RESULT_APPROVED = 1;
  // rejected
  PROPOSAL_RESULT_REJECTED = 2;
  // expired
  PROPOSAL_RESULT_EXPIRED = 3;
}

// ProposalStatus is the enum type for the proposal status.
enum ProposalStatus {
  // unchosen value
  PROPOSAL_STATUS_UNSPECIFIED = 0;
  // active
  PROPOSAL_STATUS_ACTIVE = 1;
  // finished
  PROPOSAL_STATUS_FINISHED = 2;
}

Vote

The vote tracks the votes for the proposals.

// Vote is the type for the proposal vote.
message Vote {
  // public_key is the public key of the voter.
  string public_key = 1;
  // vote is the vote enum value.
  ProposalVote vote = 2;
}

// ProposalVote is the enum type for the proposal vote.
enum ProposalVote {
  // unchosen value
  PROPOSAL_VOTE_UNSPECIFIED = 0;
  // no
  PROPOSAL_VOTE_NO = 1;
  // yes
  PROPOSAL_VOTE_YES = 2;
}

ProposalStats

The proposal statistics are stored to keep track of the count of proposals.

// ProposalStats is the type for the proposal statistics.
message ProposalStats {
  // pubkeys_change_count is the pubkeys change proposals count.
  uint64 pubkeys_change_count = 1;
}

CLI

OVM module CLI.

This section specifies the queries, transactions, and required payloads. By following this section, one can get a deep understanding of the functioning of the ovm module in the SGE Network chain.

Queries

OVM module CLI queries.

Queries

Queries of this module can be used to get the data of public keys of the oracles in the blockchain and the params. The following queries have been exposed by the OVM module:

Query the params

sged q ovm params

Query public keys

sged q ovm pubkeys

Query public keys change active proposals

sged q ovm pubkeys-change-proposals [status]

Params

Description

Type

Validation

Example

status

Active or finished proposals

uint32

Required
1 or 2

1: Active 2: Finished

Transactions & Payloads

The exposed transactions CLI commands and ticket payloads by the OVM module.

Proposal

The below transaction can be used to create a proposal for pubkey change on the blockchain.

Command

sged tx ovm pubkeys-change-proposal [ticket] --flags

The below table specifies the details of the arguments used in the above transaction:

Argument

Description

Type

Validation

Example

ticket

Used for proposal verification.

String (JWT token)

Cannot be empty
Cannot contain space (More validations will be added in the future)

1eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1aWQiOiI5OTkxYzYwZi0yMDI1LTQ4Y2UtYWU3OS0xZGMxMTBmMTY5OTkiLCJ4aWQiOiJCZXRPZGQiLCJuYW1lIjoiMSIsImJldF9ldmVudF91aWQiOiI1NTMxYzYwZi0y

MDI1

Payload

The payload for the proposal transaction is as follows:

{
 "public_keys": ["-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEAzoP3SVo1tUEhd+cF/zw+8XxtOScdJyD7T3QqKzpC9x0=\n-----END PUBLIC KEY-----"],
 "leader_index": 1,
 "exp": 1667863498866062000,
 "iat": 1667827498,
 "iss": "Oracle",
 "sub": "PubKeysChangeProposal"
}

Vote

The below transaction can be used to create a proposal for pubkey change on the blockchain.

Command

sged tx ovm vote-pubkeys-proposal [ticket ][pubkeyIndex] --flags

The below table specifies the details of the arguments used in the above transaction:

Argument

Description

Type

Validation

Example

ticket

Used for proposal verification.

String (JWT token)

Cannot be empty
Cannot contain space (More validations will be added in the future)

1eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1aWQiOiI5OTkxYzYwZi0yMDI1LTQ4Y2UtYWU3OS0xZGMxMTBmMTY5OTkiLCJ4aWQiOiJCZXRPZGQiLCJuYW1lIjoiMSIsImJldF9ldmVudF91aWQiOiI1NTMxYzYwZi0yMDI1

pubkeyIndex

The registered pubkey index that you are voting on behalf

uint32

Cannot be empty
The pubkey index should be available in current public keys list
The ticket should be signed with the private key corresponding to this pubkey at index

Payload

The payload for the vote transaction is as follows:

{
 "proposal_id": 1,
 "vote": 1,// 1: no, 2:yes
 "exp": 1667863498866062000,
 "iat": 1667827498,
 "iss": "Oracle",
 "sub": "PubKeysChangeProposalVote"
}

Subaccount

A subaccount is a unique account variant wherein the subaccount module regulates both its balance and permissions.

Overview and Concepts

The SGE-Network node application introduces a distinctive account type called subaccount and its balance is managed by this module. The subaccount balance is intended for use in betting and engaging in the "be the house" feature to participate in the markets as a house.

Concepts

The subaccount balance is established with an unlocking period, following which the balance can be withdrawn to the owner's main balance.

Owners have the option to create the Subaccount themselves, or it can be generated by the rewards module.

APIs

This section elaborates on the transaction message handler methods being exposed by the House module.

Create

When a create transaction is processed, the following things happen:

Validate the incoming create message.
Call the Create method of the keeper.

RPC

The RPC for creating a subaccount is as follows:

Request Message

The request message for Create is MsgCreate. The proto for the request message is as follows:

Response Message

The response message for Deposit is MsgDepositResponse. The proto for the request message is as follows:

Top-Up

When a top-up transaction is processed, the following things happen:

Validate the incoming create message.
Call the TopUp method of the keeper.

RPC

The RPC for a top-up of the subaccount is as follows:

Request Message

The request message for TopUp is MsgTopUp. The proto for the request message is as follows:

Response Message

The response message for TopUp is MsgTopUpResponse. The proto for the request message is as follows:

Withdraw Unlocked Balances

When a top-up transaction is processed, the following things happen:

Validate the incoming create message.
Call the WihtdrawUnlocked method of the keeper.

RPC

The RPC for a top-up of the subaccount is as follows:

Request Message

The request message for WihtdrawUnlockedBalances is MsgWihtdrawUnlockedBalances. The proto for the request message is as follows:

Response Message

The response message for WihtdrawUnlockedBalances is MsgWihtdrawUnlockedBalancesResponse. The proto for the request message is as follows:

Wager

When a wager transaction is processed, the following things happen:

Validate the incoming create message.
Call the Wager method of the keeper.

RPC

The RPC for a wager of the subaccount is as follows:

Request Message

The request message for Wager is MsgWager. The proto for the request message is as follows:

Response Message

The response message for Wager is MsgWagerResponse. The proto for the request message is as follows:

CLI

Subaccount module CLI.

This section specifies the queries, transactions, and required payloads. By following this section, one can get a deep understanding of the functioning of the subaccount module in the SGE Network chain.

Queries

House module CLI queries.

Query the Subaccount Params

Query deposits of a depositor by address

The below table explains the details of the argument required for the above query:

Params

Description

Type

Validation

Example

Transactions

Create

The below transaction can be used to create a subaccount on the blockchain.

Command

The below table specifies the details of the arguments used in the above transaction:

Argument

Description

Type

Validation

Example

Top-Up

The below transaction can be used to top up a subaccount on the blockchain.

Command

The below table specifies the details of the arguments used in the above transaction:

Argument

Description

Type

Validation

Example

Withdraw

The below transaction can be used to withdraw a subaccount unlocked balance.

Command

The below table specifies the details of the arguments used in the above transaction:

Wager

The below transaction can be used to wager using the subaccount and owner account balance.

Command

The below table specifies the details of the arguments used in the above transaction:

Reward

The responsibility for overseeing and validating campaigns and reward allocations lies with the reward module.

FAQ

Coming Soon

Privacy Policy

1. Introduction

The information in this Privacy Policy describes how we, SAAGE Labs Limited, a company registered in England (Company number 13783501) whose registered address is Cannon Place, 78 Cannon Place, London, United Kingdom, EC4N 6AF, use the personal data you provide us when you use the SIX SIGMA SPORTS application (“SIX SIGMA SPORTS”), any of the services provided by us which are accessible through SIX SIGMA SPORTS (“Services”), the website (https://sixsigmasports.io/#) or any other sites of ours (“Sites”) and through any communications with us in connection with SIX SIGMA SPORTS (“Communications”).

SIX SIGMA SPORTS, the Services and Sites are delivered to you in partnership with our online gaming licensor, SunSeven N.V. (a company incorporated under the laws of Curacao, company number 100554, and having its registered office at Heelsumstraat 51, E-Commerce Park, Curacao). When you engage with SunSeven N.V. in connection with the provision of SIX SIGMA SPORTS, the Services, and the Sites, SunSeven N.V. is acting as a processor on our behalf. When we refer to information collected by us throughout this policy, this includes information collected by SunSeven N.V. on our behalf and under our instructions.

We respect your privacy and protecting your information is paramount. We want you to be informed and empowered with respect to your privacy when you use SIX SIGMA SPORTS and the Services, Sites, and during any Communications with us, so please read this Privacy Policy carefully. This Privacy Policy sets out our practices regarding your personal data, how we collect, process, and treat it, and the rights you have in relation to the protection of your personal data.

2. Important information and who we are

SAAGE Labs Limited is the controller and is responsible for your personal data (collectively referred to as “we”, “us” or “our” in this policy).

We have appointed a data privacy manager. If you have any questions about this privacy policy, please contact them using the details set out below.

Contact details

Our full details are:

· Full name of legal entity: SAAGE Labs Limited

· Attention: Data Privacy Manager

· Email address: support@sixsigmasports.io

· Postal address: Cannon Place, 78 Cannon Place, London, United Kingdom, EC4N 6AF

3. Complaints

If you have a complaint relating to the processing of your personal data, please use the contact details above to contact us.

We would appreciate the opportunity to address any concerns or complaints you may have with respect to SIX SIGMA SPORTS, the Services, Sites and Communications and our data processing practices. However, you have the right to make a complaint at any time to the Supervisory Authority (that is, the regulator for data protection issues). In the UK, this is the Information Commissioner’s Office (ICO) (https://ico.org.uk/make-a-complaint/).

4. Your duty to inform us of changes

It is important that the personal data we hold about you is accurate and current. Please keep us informed if your personal data changes during our relationship with you.

5. The data we collect about you

We may collect, use, store and transfer different kinds of personal data about you as follows:

· Communications Data: details regarding the communications made between us.

· Identity Data: first name, last name, username, e-mail address or similar identifier, title, date of birth.

· Contact Data: address and email address.

· Financial Data: digital wallet address.

· Transaction Data: details about transactions to and from you.

· Device Data: IP Address.

· Usage Data: includes details of your use of SIX SIGMA SPORTS, the Services and Sites including, but not limited to, traffic data, and other communication data, whether this is required for our own purposes or otherwise and the resources that you access (including but not limited to the digital wallet(s) used).

· Marketing and Communications Data: includes your preferences in receiving marketing from us and your communication preferences.

· Location Data: Geo-Location IP.

We also collect, use and share Aggregated Data such as statistical or demographic data for any purpose. Aggregated Data could be derived from your personal data but is not considered personal data in law as this data will not directly or indirectly reveal your identity. However, if we combine or connect Aggregated Data with your personal data so that it can directly or indirectly identify you, we treat the combined data as personal data which will be used in accordance with this privacy policy.

We do not collect any Special Categories of Personal Data about you (this includes details about your race or ethnicity, religious or philosophical beliefs, sex life, sexual orientation, political opinions, trade union membership, information about your health, and genetic and biometric data). Nor do we collect any information about criminal convictions and offences.

6. How is your personal data collected?

We will collect and process the following data about you:

· Information you give us. This is information (including Identity, Contact and Marketing and Communications Data) you consent to giving us about you by filling in forms on SIX SIGMA SPORTS or on our Sites, or through Communications with us (for example, by email or chat). It includes information you provide when you register to use SIX SIGMA SPORTS or subscribe to any of our Services and when you report a problem with SIX SIGMA SPORTS or our Services or our Sites. If you contact us, we will keep a record of that correspondence.

· Information we collect about you and your device. Each time you visit one of our Sites or use SIX SIGMA SPORTS we will automatically collect personal data including device and usage Data. We collect this data using cookies and other similar technologies.

· Location Data. We also use geo-location IP to determine your current location. It is necessary for us to determine your location to provide you with access to and use of SIX SIGMA SPORTS and the Services in compliance with our legal and regulatory obligations. If you wish to register to use SIX SIGMA SPORTS and the Services, you will be asked to consent to your data being used for this purpose. You can withdraw your consent to your data being used for this purpose at any time by requesting the deletion of your SIX SIGMA SPORTS account.

· Information we receive from other sources including third parties and publicly available sources. We will receive personal data about you from various third parties and public sources as set out below:

o Device Data from the following parties:

§ analytics providers including but not limited to Meta, Google Analytics and other third party affiliate networks;

§ advertising networks including but not limited to Meta and Google; and

§ search information providers including but not limited to Google Index, Bing and Yahoo.

o Identity and Contact Data from data brokers, data aggregators or third party service providers.

7. How we use your personal data

We will only use your personal data when the law allows us to do so. Most commonly we will use your personal data in the following circumstances:

· Where you have consented before the processing.

· Where we need to perform a contract, we are about to enter or have entered with you.

· Where it is necessary for our legitimate interests (or those of a third party) and your interests and fundamental rights do not override those interests. When we rely on our legitimate interests, you have the right to object at any time. For example, we may process your personal data to:

o Keep our records up to date.

o Provide you with our Services, including for the purpose of quality control and analysis.

o Develop and improve our Services.

o Communicate and manage our relationship with you.

· Where we need to comply with a legal or regulatory obligation.

We will only send you direct marketing communications by email, Progressive Web App (PWA) notification or native in-app notification if we have your consent. You have the right to withdraw that consent at any time by contacting us.

We will get your express opt-in consent before we share your personal data with any third party for marketing purposes. We will never sell your personal data.

Purposes for which we will use your personal data

Purpose/activity

Type of data

Lawful basis for processing

To register you as a new SIX SIGMA SPORTS user

Identity

Contact

Location

Your consent

Necessary to comply with legal obligations

To manage our relationship with you including notifying you of changes to SIX SIGMA SPORTS or any of the Services and managing any requests or complaints received from you

Identity

Contact

Profile

Marketing and Communications

Performance of a contract with you

Necessary for our legitimate interests (to keep records updated and to analyse how customers use our products/ Services)

Necessary to comply with legal obligations (to inform you of any changes to our terms and conditions)

To administer and protect our business and SIX SIGMA SPORTS including troubleshooting, data analysis and system testing

Identity

Contact

Device

Usage

Location

Necessary for our legitimate interests (for running our business, provision of administration and IT services, network security)

To deliver content and advertisements to you

To make recommendations to you about goods or services which may interest you

To monitor trends so we can improve SIX SIGMA SPORTS

Identity

Contact

Device

Content

Profile

Usage

Marketing and Communications

Location

Consent

Necessary for our legitimate interests (to develop our products/Services and grow our business)

8. Disclosures of your personal data

We may need to disclose your personal data to others to facilitate the provision to you of SIX SIGMA SPORTS. Disclosure of your personal information to a third party will only be made where they agree to keep your information confidential and will only be used for the specific purpose for which we provide it to them. Your data may be disclosed to the other persons or entities as described below.

· Third parties who supply services to us, such as our online gaming licensor (SunSeven N.V., as referred to above) and our KYC service provider.

· Our professional advisors, such as our legal advisors where they require information in order to provide advice to us in relation to SIX SIGMA SPORTS, our Services, Sites or Communications.

· Any regulatory authority we may be subject to for the purpose of demonstrating compliance with applicable laws and regulations.

· Third parties to whom we may choose to sell, transfer or merge parts of our business or our assets. Alternatively, we may seek to acquire other businesses or merge with them. If a change happens to our business, then the new owners may use your personal data in the same way as set out in this privacy policy.

· Such third parties as we reasonably consider necessary in order to prevent crime, e.g., the police.

9. International transfers

Your personal data may be stored and processed outside the UK in countries that may have different data protection rules than our own. Whenever we transfer your personal data out of the UK, we ensure a similar degree of protection is afforded to it by ensuring appropriate safeguards have been put in place.

Please contact us if you want further information on the specific mechanism used by us when transferring your personal data out of the UK.

10. Data security

All information you provide to us is stored on our secure servers. Information we pass to third parties will be stored on their secure servers.

Once we have received your information, we will use strict procedures and security features to try to prevent your personal data from being accidentally lost, used, or accessed in an unauthorised way.

We have put in place procedures to deal with any suspected personal data breach and will notify you and any applicable regulator when we are legally required to do so.

11. Use of Cookies

SIX SIGMA SPORTS, the Services and our Sites use “cookies” and similar technologies to collect and store certain information. These typically involve pieces of information or code that a website transfers to or accesses from your computer hard drive or mobile device to store and sometimes track information about you. Depending on their purpose, the cookies may last only the length of a single browsing session, but in some cases, may last longer to ensure their purpose is fulfilled. Cookies help us recognise you as a unique visitor when you return to SIX SIGMA SPORTS and our Sites and help us to better understand how visitors use SIX SIGMA SPORTS and our Sites. This helps us to provide you with a good experience when you use SIX SIGMA SPORTS and our Sites and also allows us to improve SIX SIGMA SPORTS, our Sites and the Services. We will ask for your consent to place cookies or other similar technologies on your device, except where they are essential for us to provide you with a service that you have requested.

Broadly, SIX SIGMA SPORTS and our Sites use cookies and similar technologies for the following purposes:

· Strictly necessary cookies. These are cookies that are required for the operation of SIX SIGMA SPORTS, the Services and our Sites. They include, for example, cookies that enable you to log into secure areas of SIX SIGMA SPORTS and our Sites.

· Analytical cookies. These allow us to recognise and count the number of visitors and to see how visitors move around SIX SIGMA SPORTS and our Sites when they are using them. This helps us to improve the way SIX SIGMA SPORTS and our Sites work, for example, by ensuring that users are finding what they are looking for easily.

· Tracking cookies. These cookies record your visit to SIX SIGMA SPORTS and our Sites, the pages you have visited and the links you have followed. We will use this information to make SIX SIGMA SPORTS and our Sites, and the advertising displayed on them more relevant to your interests.

You can find more information about the individual cookies we use and the purposes for which we use them in the table below:

Cookie Title

Cookie Type

Cookie Name

Purpose

Expiry

Name: App Session Cookie

Category: Strictly Necessary

Type: Persistent Cookies

Application feature in use

Application state

Time Zone

Device type

Expires 7 days from visit

Name: User Session Cookie

Category: Strictly Necessary

Type: Session Cookies

Wallet Address

Wallet Balance

Wallet Type

Track Login/Logout of SIX SIGMA SPORTS and our Sites

End of session / Expires on Logout of our Site

Please note that the following third parties may also use cookies when you access SIX SIGMA SPORTS, our Services or our Sites, over which we have no control. These named third parties may include, for example, advertising networks and providers of external services like web traffic analysis services. These third party cookies are likely to be analytical cookies or performance cookies or targeting cookies:

· Google Analytics

· Facebook Pixel

· Instagram Pixel

· Elfsight

· Youtube

You can choose whether to allow analytical and tracking cookies by clicking on the button(s):

· Analytical or Tracking cookies ON/OFF

However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of SIX SIGMA SPORTS, our Sites or our Services.

12. Data retention

We will only keep your personal data for as long as necessary to carry out the relevant purposes set out in this Privacy Policy and in order to comply with our legal and regulatory obligations, following which we will securely destroy your personal information. We will provide you with more detail regarding the storage periods for the different types of personal data as and when you request.

In some circumstances you can ask us to delete your data: see Your legal rights below for further information.

In some circumstances we will anonymise your personal data (so that it can no longer be associated with you) for research or statistical purposes, in which case we may use this information indefinitely without further notice to you.

13. Your legal rights

We are committed to delivering the rights that data protection law provides. Please be aware that these rights are often not absolute, and exemptions may apply.

You have the right to:

· Be informed: and to be provided with clear, transparent and easily understandable information about how we use your information and your rights. This is why we are providing you with the information in this Privacy Policy.

· Request access to your personal data (commonly known as a “data subject access request”). This enables you to receive a copy of the personal data we hold about you and to check that we are lawfully processing it.

· Request correction of the personal data that we hold about you. This enables you to have any incomplete or inaccurate data we hold about you corrected, though we may need to verify the accuracy of the new data you provide to us.

· Request erasure of your personal data. This enables you to ask us to delete or remove personal data where there is no good reason for us continuing to process it. You also have the right to ask us to delete or remove your personal data where you have successfully exercised your right to object to processing (see below), where we may have processed your information unlawfully or where we are required to erase your personal data to comply with local law. Note, however, that we may not always be able to comply with your request of erasure for specific legal reasons which will be notified to you, if applicable, at the time of your request.

· Object to processing of your personal data where we are relying on a legitimate interest (or those of a third party) and there is something about your particular situation which makes you want to object to processing on this ground as you feel it impacts on your fundamental rights and freedoms. You also have the right to object where we are processing your personal data for direct marketing purposes. In some cases, we may demonstrate that we have compelling legitimate grounds to process your information which override your rights and freedoms.

· Request restriction of processing of your personal data. This enables you to ask us to suspend the processing of your personal data in the following scenarios:

o if you want us to establish the data’s accuracy;

o where our use of the data is unlawful, but you do not want us to erase it;

o where you need us to hold the data even if we no longer require it as you need it to establish, exercise or defend legal claims; or

o you have objected to our use of your data, but we need to verify whether we have overriding legitimate grounds to use it.

· Request the transfer of your personal data to you or to a third party. We will provide to you, or a third party you have chosen, your personal data in a structured, commonly used, machine-readable format. Note that this right only applies to automated information which you initially provided consent for us to use or where we used the information to perform a contract with you.

· Withdraw consent at any time where we are relying on consent to process your personal data. However, this will not affect the lawfulness of any processing carried out before you withdraw your consent. If you withdraw your consent, we may not be able to provide certain products or Services to you. We will advise you if this is the case at the time you withdraw your consent.

You can exercise any of these rights at any time by contacting us using the contact details set out at the top of this Privacy Policy.

14. How we Protect Your Information

We do our best to protect your personal data, but we cannot guarantee the security of your data transmitted; any transmission is at your own risk. Once we have received your information, we will use strict procedures and security features to try to prevent unauthorised access, loss, or damage.

15. Links to Third Party Websites

SIX SIGMA SPORTS may, from time to time, contain links to and from the websites of our partner networks, advertisers, and affiliates. If you follow a link to any of these websites, please note that these websites have their own privacy policies and that we do not accept any responsibility or liability for these policies.

16. Changes

We keep our privacy policy under regular review. This version was last updated on 1 December 2023.

We may make changes to this Privacy Policy in future to reflect changes in the functionality of SIX SIGMA SPORTS or otherwise changes in the way that we process your personal information. Any changes we may make to our SIX SIGMA SPORTS Privacy Policy will be posted [https://six-sigma-sports.gitbook.io/docs/privacy-policy] and, where the changes are material or we decide it is appropriate, notified to you in any manner we deem appropriate. Please check back frequently to see any updates or changes. Please note that from time to time, we may require you to read and acknowledge such updates or changes.

Terms & Conditions

Last updated: 8-July-2024

1. Introduction

These terms and conditions and the documents referred to below (the "Terms") apply to the use of the current website (the "Website") and its related or connected services (collectively, the "Service").

You should carefully review these Terms as they contain important information concerning your rights and obligations concerning the use of the Website and form a binding legal agreement between you - our customer (the "Customer"), and us. By using this Website and/or accessing the Service, you, whether you are a guest or a registered user with an account (“Account”), agree to be bound by these Terms, together with any amendments, which may be published from time to time. If you do not accept these Terms, you should refrain from accessing the Service and using the Website.

The Service is licensed and managed by CRGC MANAGEMENT LTD, a limited liability company registered in Costa Rica (“Company”), licensed in the State of Anjouan under the Computer Gaming Licensing Act 007 of 2005..

The Terms are comprised of and include:

these general terms and conditions (“Ts&Cs”);
additional specific rules that apply to specific products and services (e.g. game sports betting rules etc), as updated from time to time and available here (https://six-sigma-sports.gitbook.io/betting-rules); and
the rules for any promotion that we offer from time to time (“Promotion Terms”).

2. General Terms

We reserve the right to revise and amend the Terms (including any documents referred to and linked to below) at any time. You should visit this page periodically to review the Terms and Conditions. Amendments will be binding and effective immediately upon publication on this Website. If you object to any such changes, you must immediately stop using the Service. Your continued use of the Website following such publication will indicate your agreement to be bound by the Terms as amended. Any bets not settled prior to the changed Terms taking effect will be subject to the pre-existing Terms.

3. Your Obligations

You acknowledge that at all times when accessing the Website and using the Service (application):

3.1. You are is over 18, or the legal age at which gambling, or gaming activities are allowed under the law or jurisdiction that applies to you. We reserve the right to request proof of age documents from you at any time.

3.2. You are not self-excluded from gambling or otherwise prohibited for any reason from gambling with us or from using the Services.

3.3. You are of legal capacity and can enter into a binding legal agreement with us. You must not access the Website or utilize the Service if you are not of legal capacity.

3.4. You are a resident in a jurisdiction that allows gambling. You are not a resident of any country in which access to online gambling to its residents or to any person within such country is prohibited. It is your sole responsibility to ensure that your use of the service is legal. We do not accept liability if your use of our Services is in contravention of the laws of the country where you are resident or located (as applicable).

3.5. You may not use a VPN, proxy or similar services or devices that mask or manipulate the identification of your real location.

3.6. You are the authorized user of the payment method you use.

3.7. You must make all payments to us in good faith.

3.8. When placing bets you may lose some or all of your money deposited to the Service in accordance with these Terms and you will be fully responsible for that loss.

3.9. When placing bets you must not use any information obtained in breach of any legislation in force in the country in which you were when the bet was placed.

3.10. You are not acting on behalf of another party or for any commercial purposes, but solely on your own behalf as a private individual in a personal capacity.

3.11. You must not either attempt to manipulate any market or element within the Service in bad faith nor in a manner that adversely affects the integrity of the Service or us.

3.12. You must act in good faith in relation to use of the Service at all times and for all bets made using the Service.

3.13. You, or, if applicable, your employees, employers, agents, or family members, are not registered as an Affiliate in our Affiliate program.

4. Restricted use

You must not use the Service:

4.1. If you are under the age of 18 years (or below the age of majority as stipulated in the laws of the jurisdiction applicable to you) or if you are not legally able to enter into a binding legal agreement with us or you acting as an agent for, or otherwise on behalf, of a person under 18 years (or below the age of majority as stipulated in the laws of the jurisdiction applicable to you);

4.2. If you reside in a country in which access to online gambling to its residents or to any person within such country is prohibited.

4.3. If you are a resident of one of the following countries, or accessing the Website from one of the following Restricted Countries:

· Austria

· France and its territories

· Germany

· Netherlands and it’s territories

· Spain

· Union of Comoros

· United Kingdom

· USA and it’s territories

· All FATF Blacklisted countries, any other jurisdictions deemed prohibited by Anjouan Offshore Financial Authority.

4.4. To collect nicknames, e-mail addresses and/or other information of other Customers by any means (for example, by sending spam, other types of unsolicited emails or the unauthorised framing of, or linking to, the Service);

4.5. to disrupt or unduly affect or influence the activities of other Customers or the operation of the Service generally;

4.6. to promote unsolicited commercial advertisements, affiliate links, and other forms of solicitation which may be removed from the Service without notice;

4.7. in any way which, in our reasonable opinion, could be considered as an attempt to: (i) cheat the Service or another Customer using the Service; or (ii) collude with any other Customer using the Service in order to obtain a dishonest advantage;

4.8. to scrape our odds or violate any of our Intellectual Property Rights; or

4.9. for any unlawful activity whatsoever.

4.10. You cannot sell or transfer your account to third parties, nor can you acquire a player account from a third party

4.11. You must not attempt to gain unauthorised access to our websites and mobile applications or any server computer or database connected to our websites or mobile applications;

4.12. You may not in any way interfere, interrupt, attempt to interrupt, or attempt to manipulate the operation of our Services or the normal play of any of our products. You agree to play personally via the interfaces made available by us only.

4.13. We may immediately terminate your Account upon written notice to you if you use the Service for unauthorised purposes. We may also take legal action against you for doing so in certain circumstances.

4.14. Employees of Company, its licensees, distributors, wholesalers, subsidiaries, advertising, promotional or other agencies, media partners, contractors, retailers and members of the immediate families of each are NOT allowed to use the Service for real money without prior consent from the Company Director or CEO. Should such activity be discovered, the account(s) will be immediately terminated and all bonuses/winnings will be forfeited.

5. Registration

5.1. You agree that at all times when using the Service:

5.2. We reserve the right to refuse to accept a registration application from any applicant at our sole discretion and without any obligation to communicate a specific reason.

5.3. Before using the Service, you must personally complete the registration form and read and accept these Terms. In order to start betting on the Service, we may require you to become a verified Customer which includes passing certain checks. You may be required to provide a valid proof of identification and any other document as it may be deemed necessary. This includes but is not limited to, a picture ID (copy of passport, driver's licence or national ID card) and a recent utility bill listing your name and address as proof of residence. We reserve the right to suspend wagering or restrict Account options on any Account until the required information is received. This procedure is done in accordance with the applicable gaming regulation and anti-money laundering legal requirements.

5.4. You have to provide accurate contact information, inclusive of a valid email address (“Registered Email Address”), and update such information in the future to keep it accurate. It is your responsibility to keep your contact details up to date on your Account. Failure to do so may result in you failing to receive important Account related notifications and information from us, including changes we make to these Terms. We identify and communicate with our Customers via their Registered Email Address. It is the responsibility of the Customer to maintain an active and unique email account, to provide us with the correct email address and to advise Company of any changes in their email address. Each Customer is wholly responsible for maintaining the security of his Registered Email Address to prevent the use of his Registered Email Address by any third party. Company shall not be responsible for any damages or losses deemed or alleged to have resulted from communications between Company and the Customer using the Registered Email Address. Any Customer not having an email address reachable by the Company will have his Account suspended until such an address is provided to us. We will immediately suspend your Account upon written notice to you to this effect if you intentionally provide false or inaccurate personal information. We may also take legal action against you for doing so in certain circumstances and/or contact

5.5. You are only allowed to register one Account with the Service. Accounts are subject to immediate closure if it is found that you have multiple Accounts registered with us. This includes the use of representatives, relatives, associates, affiliates, related parties, connected persons and/or third parties operating on your behalf.

5.6. In order to ensure your financial worthiness and to confirm your identity, we may ask you to provide us with additional personal information, such as your name and surname, or use any third-party information providers we consider necessary. Should any additional personal information be obtained via third-party sources, we will inform you about the data obtained.

5.7. You must keep your password for the Service confidential. In the case of a digital wallet holding crypto assets, you must have a safeguarded private key for your wallet address (being “Your Wallet”) that only you can access and control to sign transactions and prove your ownership of your Account and its assets.

5.8. You acknowledge and agree that we do not store, hold, or manage your private key, and that we have no access to or control over your private key. You also acknowledge and agree that we cannot recover, restore, or reset your private key if you forget, lose, or disclose it, or if it is damaged, corrupted, or hacked. If you lose access to your private key, you may lose access to Your Wallet and its assets permanently, and we will not be liable for any loss or damage resulting from your failure to safeguard your private key

5.9. When you register with us, you will choose a unique user ID and password for your Account which will be linked to Your Wallet. You must not under any circumstances share your user ID, password or private key or allow any other person to use your Account (and/or Your Wallet). It is your responsibility to maintain the confidentiality and security of your user ID, password and/or private key and to ensure that you do not reveal your user ID, password and/or private key to anyone else.

5.10. Provided that the Account information requested has been correctly supplied, we are entitled to assume that bets, deposits, withdrawals and all other in-application actions have been made by you. We advise you to change your password on a regular basis and never disclose it to any third party. It is your responsibility to protect your password and any failure to do so shall be at your sole risk and expense. You may log out of the Service at the end of each session. If you believe any of your Account information is being misused by a third party, or your Account has been hacked into, or your password has been discovered by a third party, you must notify us immediately. You must notify us if your Registered Email Address has been hacked into, we may, however, require you to provide additional information/ documentation so that we can verify your identity. We will immediately suspend your Account once we are aware of such an incident. In the meantime you are responsible for all activity on your Account including third party access, regardless of whether or not their access was authorised by you.

5.11. You must not at any time transmit any content or other information on the Service to another Customer or any other party by way of a screen capture (or other similar method), nor display any such information or content in a frame or in any other manner that is different from how it would appear if such Customer or third party had typed the URL for the Service into the browser line.

5.12. We are under no obligation to open an Account for you and our website sign-up page is merely an invitation to treat. It is entirely within our sole discretion whether or not to proceed with the opening of an Account for you and, should we refuse to open an Account for you, we are under no obligation to provide you with a reason for the refusal.

5.13. Upon receipt of your application, we may be in touch to request further information and/ or documentation from you in order for us to comply with our regulatory and legal obligations.5.11 By registering, you confirm to us that you meet the eligibility criteria in Section 4 of these Terms and that all information you provide when opening an account and subsequently is and will be kept complete and accurate.

6. Your Account

6.1. Accounts could use several currencies, including digital assets (tokens).

6.2. To bet/wager or play games on SIX SIGMA SPORTS, you will need to hold SGE tokens (which are tokens that are native to the sports, gaming and entertainment network built using the Cosmos SDK) or any other token approved by us as a betting token in Your Wallet so that those tokens are viewable in your Account.

6.3. You may be required to pay a blockchain transaction fee, over which we have no control, for making a deposit or withdrawal and you should check with any service provider you may use in connection with the purpose if they will apply any charges. We do not accept any responsibility for fees or charges applied by third parties.

6.4. We do not give credit for the use of the Service.

6.5. We may close or suspend an Account if you are not or we reasonably believe that you are not complying with these Terms, or to ensure the integrity or fairness of the Service or if we have other reasonable grounds to do so. We may not always be able to give you prior notice. If we close or suspend your Account due to you not complying with these Terms, we reserve the right to pursue any available remedies, which could include cancelling and/or voiding any of your bets and withholding any money or crypto assets to the extent applicable

6.6. We reserve the right to close or suspend any Account without prior notice and return all unsettled funds. Contractual obligations already matured will however be honoured.

6.7. We reserve the right to refuse, restrict, cancel or limit any wager at any time for whatever reason, including any bet perceived to be placed in a fraudulent manner in order to circumvent our betting limits and/ or our system regulations.

6.8. You must inform us as soon as you become aware of any errors with respect to your Account.

6.9. Please remember that betting is purely for entertainment and pleasure and you should stop as soon as it stops being fun. Absolutely do not bet anything you can’t afford to lose. If you feel that you may have lost control of your gambling, we offer a self-exclusion option. This is available directly in the application by navigating to Responsible Gambling and selecting Deactivate Account. We are committed to safer gambling and have a number of self-help tools to help you manage your gambling. These tools provide you with the ability to:

· control and limit your spending;

· receive notifications about your session of play;

· temporarily “cool off” from using the Services; and

· self-exclude and close your Account.

6.10. Please refer to [https://six-sigma-sports.gitbook.io/docs/responsible-gambling-resources] for more information about our safer gambling tools, including how to access advice and support on how to gamble responsibly.

6.11. You cannot transfer, sell, or pledge Your Account to another person. This prohibition includes the transfer of any assets of value of any kind, including but not limited to ownership of accounts, winnings, deposits, bets, rights and/or claims in connection with these assets, legal, commercial or otherwise. The prohibition on said transfers also includes however is not limited to the encumbrance, pledging, assigning, usufruct, trading, brokering, hypothecation and/or gifting in cooperation with a fiduciary or any other third party, company, natural or legal individual, foundation and/or association in any way shape or form

6.12. Should you wish to close your account with us, please send an email from your Registered Email Address to our Customer Support Department via the links on the Website.

6.13. You are responsible for reporting or declaring any funds withdrawn, including winnings, if such reporting is required by local law, tax or other authorities.

7. Placing Bets and Using the Services

7.1. We only accept bets made online (including via our mobile applications). Bets are not accepted in other ways, including by telephone, email, post or fax, and will not be valid if received in such a way.

7.2. It is important that you ensure that all details of any bet are correct. Once we have accepted a bet, you cannot change or cancel it. We may refuse the whole or part of a bet for any reason.

7.3. A bet is not accepted by us until we have confirmed it to you.

7.4. You may only place bets using the SGE tokens or any other token approved by us as a betting token in Your Wallet.

7.5. You may implement certain limits on your Account using our safer gambling tools. Please see [https://six-sigma-sports.gitbook.io/docs/responsible-gambling-resources] for more information. We may also implement certain limits on your Account in accordance with our legal and regulatory obligations and commitment to safer gambling.

7.6. We may place maximum limits on the amount of each bet you may place using the Services. We may also impose limits on the maximum amount of winnings, which apply regardless of the amount you have bet or staked, and/or maximum amount of bets that you may place. Please see our Betting Rules for more information (https://six-sigma-sports.gitbook.io/betting-rules).

7.7. You are fully aware that there is a risk of losing money, SGE tokens and/or any other tokens when gambling, including when participating as the House, and you are responsible for any such loss.

7.8. Information shown on the Services for the purpose of gambling is for illustration purposes only and does not constitute any advice, endorsement or recommendation by us and we do not accept responsibility for bets that are placed on the basis of such display information. This information may be provided by third parties and may not be up to date (for example, live video coverage may be subject to a delay of a few seconds) or may be affected by an Error (please see Section Errors below).

7.9. All transactions made on our site might be checked to prevent money laundering or terrorism financing activity. Suspicious transactions will be reported to the relevant authority

7.10. You agree that, save in the case of manifest error or our negligence, we and our transaction data and records shall be the final authority in determining the terms and settlement of any bets you place.

8. Errors

8.1. In the event of an error or malfunction of our system or processes, all bets are rendered void. You are under an obligation to inform us immediately as soon as you become aware of any error with the Service. In the event of communication or system errors or bugs or viruses occurring in connection with the Service and/or payments made to you as a result of a defect or error in the Service, we will not be liable to you or to any third party for any direct or indirect costs, expenses, losses or claims arising or resulting from such errors, and we reserve the right to void all games/bets in question and take any other action to correct such errors.

8.2. We make every effort to ensure that we do not make errors in posting bookmaker lines. However, if as a result of human error or system problems a bet is accepted at an odd that is: materially different from those available in the general market at the time the bet was made; or clearly incorrect given the chance of the event occurring at the time the bet was made then we reserve the right to cancel or void that wager, or to cancel or void a wager made after an event has started.

8.3. We have the right to recover from you any amount overpaid. An example of such a mistake might be where a price is incorrect or where we enter a result of an event incorrectly. If the error cannot be rectified until after settlement, we may demand that you pay us the relevant outstanding amount relating to any erroneous bets or wagers. Accordingly, we reserve the right to cancel, reduce or delete any pending plays, whether placed with funds resulting from the error or not.

9. Rules of Play, refunds and cancellations

9.1. If a result cannot be validated by us, for instance if the feed broadcasting the event is interrupted (and cannot be verified by another source) then at our election, the wagers on that event will be deemed invalid and wagers refunded.

9.2. Customers are solely responsible for their own Account transactions. Once a transaction is complete, it cannot be changed. We do not take responsibility for missing or duplicate wagers made by the Customer and will not entertain discrepancy requests because a play is missing or duplicated. Customers may review their transactions in the My Bets section of the site after each session to ensure all requested wagers were accepted.

9.3. If an event is posted by us with an incorrect date, all wagers have action based on the date announced by the governing body.

9.4. Company reserves the right to remove events, markets and any other products from the Website.

9.5. In-depth explanation of our sports betting rules is on the separate page: Betting Rules by Sport (https://six-sigma-sports.gitbook.io/betting-rules)

10. Communications and Notices

10.1. All communications and notices to be given under these Terms by you to us shall be sent using a Customer Support form on the Website.

10.2. All communications and notices to be given under these Terms by us to you shall, unless otherwise specified in these Terms, be either posted on the Website and/or sent to the Registered Email Address we hold on our system for the relevant Customer. The method of such communication shall be in our sole and exclusive discretion.

10.3. All communications and notices to be given under these Terms by either you or us shall be in writing in the English language and must be given to and from the Registered Email Address in your Account.

10.4. From time to time, we may contact you by email for the purpose of offering you information about betting, unique promotional offerings, and other information from SixSigmaSports.io. You agree to receive such emails when you agree to these Terms when registering at the Website. You can choose to opt out of receiving such promotional offerings from us at any time by selecting the Opt-Out option in any such email or by submitting a request using the Contact Us form.

11. Matters Beyond Our Control

11.1. We cannot be held liable for any failure or delay in providing the Service due to an event of Force Majeure which could reasonably be considered to be outside our control despite our execution of reasonable preventative measures such as: an act of God; trade or labour dispute; power cut; act, failure or omission of any government or authority; obstruction or failure of telecommunication services; or any other delay or failure caused by a third party, and we will not be liable for any resulting loss or damage that you may suffer. In such an event, we reserve the right to cancel or suspend the Service without incurring any liability.

12. Liability

12.1. TO THE EXTENT PERMITTED BY APPLICABLE LAW, WE WILL NOT COMPENSATE YOU FOR ANY REASONABLY FORESEEABLE LOSS OR DAMAGE (EITHER DIRECT OR INDIRECT) YOU MAY SUFFER IF WE FAIL TO CARRY OUT OUR OBLIGATIONS UNDER THESE TERMS UNLESS WE BREACH ANY DUTIES IMPOSED ON US BY LAW (INCLUDING IF WE CAUSE DEATH OR PERSONAL INJURY BY OUR NEGLIGENCE) IN WHICH CASE WE SHALL NOT BE LIABLE TO YOU IF THAT FAILURE IS ATTRIBUTED TO: (I) YOUR OWN FAULT; (II) A THIRD PARTY UNCONNECTED WITH OUR PERFORMANCE OF THESE TERMS (FOR INSTANCE PROBLEMS DUE TO COMMUNICATIONS NETWORK PERFORMANCE, CONGESTION, AND CONNECTIVITY OR THE PERFORMANCE OF YOUR COMPUTER EQUIPMENT); OR (III) ANY OTHER EVENTS WHICH NEITHER WE NOR OUR SUPPLIERS COULD HAVE FORESEEN OR FORESTALLED EVEN IF WE OR THEY HAD TAKEN REASONABLE CARE. AS THIS SERVICE IS FOR CONSUMER USE ONLY WE WILL NOT BE LIABLE FOR ANY BUSINESS LOSSES OF ANY KIND.

12.2. IN THE EVENT THAT WE ARE HELD LIABLE FOR ANY EVENT UNDER THESE TERMS, OUR TOTAL AGGREGATE LIABILITY TO YOU UNDER OR IN CONNECTION WITH THESE TERMS SHALL NOT EXCEED (A) THE VALUE OF THE BETS AND OR WAGERS YOU PLACED VIA YOUR ACCOUNT IN RESPECT OF THE RELEVANT BET/WAGER OR PRODUCT THAT GAVE RISE TO THE RELEVANT LIABILITY, OR (B) EUR €500 IN AGGREGATE, WHICHEVER IS LOWER.

12.3. WE STRONGLY RECOMMEND THAT YOU (I) TAKE CARE TO VERIFY THE SUITABILITY AND COMPATIBILITY OF THE SERVICE WITH YOUR OWN COMPUTER EQUIPMENT PRIOR TO USE; AND (II) TAKE REASONABLE PRECAUTIONS TO PROTECT YOURSELF AGAINST HARMFUL PROGRAMS OR DEVICES INCLUDING THROUGH INSTALLATION OF ANTI-VIRUS SOFTWARE.

13. Gambling By Those Under Age

13.1. If we suspect that you are or receive notification that you are currently under 18 years or were under 18 years (or below the age of majority as stipulated in the laws of the jurisdiction applicable to you) when you placed any bets through the Service your Account will be suspended (locked) to prevent you placing any further bets. We will then investigate the matter, including whether you have been betting as an agent for, or otherwise on behalf, of a person under 18 years (or below the age of majority as stipulated in the laws of the jurisdiction applicable to you). If having found that you: (a) are currently; (b) were under 18 years or below the majority age which applies to you at the relevant time; or (c) have been betting as an agent for or at the behest of a person under 18 years or below the majority age which applies:

13.2. all winnings currently or due to be credited to your Wallet will be retained;

13.3. all winnings gained from betting through the Service whilst under age must be paid to us on demand (if you fail to comply with this provision we will seek to recover all costs associated with recovery of such sums); and/or

13.4. This condition also applies to you if you are over the age of 18 years but you are placing your bets within a jurisdiction which specifies a higher age than 18 years for legal betting and you are below that legal minimum age in that jurisdiction.

13.5. In the event we suspect you are in breach of the provisions of this Clause or are attempting to rely on them for a fraudulent purpose, we reserve the right to take any action necessary in order to investigate the matter, including informing the relevant law enforcement agencies.

14. Fraud

14.1. Fraudulent activity or cheating constitutes a serious breach of the Agreement. We will seek criminal and contractual sanctions against any Customer involved in fraud, dishonesty or criminal acts. We will withhold payment where applicable to any Customer where any of these are suspected. The Customer shall indemnify and shall be liable to pay to us on demand all costs, charges or losses sustained or incurred by us (including any direct, indirect or consequential losses, loss of profit, loss of business and loss of reputation) arising directly or indirectly from the Customer’s fraud, dishonesty or criminal act.

14.2. We consider fraudulent activity or cheating to include, but not be limited to:

· identity fraud;

· payment fraud;

· money laundering;

· third-party funding;

· forgery;

· using payment details or a wallet that does not belong to you (including stolen or fraudulent payment details/wallets);

· collusion with other individuals;

· utilisation of software to gain an unfair advantage;

· circumventing any of our registration and/or bet placement processes in order to register an account and/or place a bet (including by circumventing our front-end software or our onboarding process in order to submit a bet directly on the blockchain);

· exploitation of Errors, malfunctions or Interruptions;

· betting on fixed sporting events; and/or

· misuse of non-public or inside information.

15. Intellectual Property

15.1. Any unauthorised use of our name and logo may result in legal action being taken against you.

15.2. As between us and you, we are the sole owners of the rights in and to the Service, our technology, software and business systems (the "Systems") as well as our odds. you must not use your personal profile for your own commercial gain (such as selling your status update to an advertiser); and when selecting a nickname for your Account we reserve the right to remove or reclaim it if we believe it appropriate.

15.3. You may not use our URL, trademarks, trade names and/or trade dress, logos ("Marks") and/or our odds in connection with any product or service that is not ours, that in any manner is likely to cause confusion among Customers or in the public or that in any manner disparages us.

15.4. Except as expressly provided in these Terms, we and our licensors do not grant you any express or implied rights, license, title or interest in or to the Systems or the Marks and all such rights, license, title and interest specifically retained by us and our licensors. You agree not to use any automatic or manual device to monitor or copy web pages or content within the Service. Any unauthorized use or reproduction may result in legal action being taken against you.

16. Your License

16.1. Subject to these Terms and your compliance with them, we grant to you a non-exclusive, limited, non transferable and non sub-licensable license to access and use the Service for your personal non-commercial purposes only. Our license to you terminates if our agreement with you under these Terms ends.

16.2. Save in respect of your own content, you may not under any circumstances modify, publish, transmit, transfer, sell, reproduce, upload, post, distribute, perform, display, create derivative works from, or in any other manner exploit, the Service and/or any of the content thereon or the software contained therein, except as we expressly permit in these Terms or otherwise on the Website. No information or content on the Service or made available to you in connection with the Service may be modified or altered, merged with other data or published in any form including for example screen or database scraping and any other activity intended to collect, store, reorganise or manipulate such information or content.

16.3. Any non-compliance by you with this Clause may also be a violation of our or third parties' intellectual property and other proprietary rights which may subject you to civil liability and/or criminal prosecution.

17. Your Conduct and Safety

17.1. For your protection and protection of all our Customers, the posting of any content on the Service, as well as conduct in connection therewith and/or the Service, which is in any way unlawful, inappropriate or undesirable is strictly prohibited (“Prohibited Behaviour”).

17.2. If you engage in Prohibited Behaviour, or we determine in our sole discretion that you are engaging in Prohibited Behaviour, your Account and/or your access to or use of the Service may be terminated immediately without notice to you. Legal action may be taken against you by another Customer, other third party, enforcement authorities and/or us with respect to you having engaged in Prohibited Behaviour.

17.3. Prohibited Behaviour includes, but is not limited to, accessing or using the Service to: promote or share information that you know is false, misleading or unlawful; conduct any unlawful or illegal activity, such as, but not limited to, any activity that furthers or promotes any criminal activity or enterprise, violates another Customer's or any other third party’s privacy or other rights or that creates or spreads computer viruses; harm minors in any way; transmit or make available any content that is unlawful, harmful, threatening, abusive, tortuous, defamatory, vulgar, obscene, lewd, violent, hateful, or racially or ethnically or otherwise objectionable; transmit or make available any content that the user does not have a right to make available under any law or contractual or fiduciary relationship, including without limitation, any content that infringes a third party’s copyright, trademark or other intellectual property and proprietary rights; transmit or make available any content or material that contains any software virus or other computer or programming code (including HTML) designed to interrupt, destroy or alter the functionality of the Service, its presentation or any other website, computer software or hardware; interfere with, disrupt or reverse engineer the Service in any manner, including, without limitation, intercepting, emulating or redirecting the communication protocols used by us, creating or using cheats, mods or hacks or any other software designed to modify the Service, or using any software that intercepts or collects information from or through the Service; retrieve or index any information from the Service using any robot, spider or other automated mechanism; participate in any activity or action that, in the sole and entire unfettered discretion of us results or may result in another Customer being defrauded or scammed; transmit or make available any unsolicited or unauthorised advertising or mass mailing such as, but not limited to, junk mail, instant messaging, "spim", "spam", chain letters, pyramid schemes or other forms of solicitations; create Accounts on the Website by automated means or under false or fraudulent pretences; impersonate another Customer or any other third party, or any other act or thing done that we reasonably consider to be contrary to our business principles. The above list of Prohibited Behaviour is not exhaustive and may be modified by us at any time or from time to time. We reserve the right to investigate and to take all such actions as we in our sole discretion deem appropriate or necessary under the circumstances, including without limitation deleting the Customer’s posting(s) from the Service and/or terminating their Account, and take any action against any Customer or third party who directly or indirectly in, or knowingly permits any third party to directly or indirectly engage in Prohibited Behaviour, with or without notice to such Customer or third party.

18. Links to Other Websites

18.1. The Service may contain links to third party websites that are not maintained by, or related to, us, and over which we have no control. Links to such websites are provided solely as a convenience to Customers, and are in no way investigated, monitored or checked for accuracy or completeness by us. Links to such websites do not imply any endorsement by us of, and/or any affiliation with, the linked websites or their content or their owner(s). We have no control over or responsibility for the availability nor their accuracy, completeness, accessibility and usefulness. Accordingly when accessing such websites we recommend that you should take the usual precautions when visiting a new website including reviewing their privacy policy and terms of use.

19. Complaints

19.1. If you have any concerns or questions regarding these Terms you should contact our Customer Service Department via the links on the Website and use your Registered Email Address in all communication with us.

19.2. NOTWITHSTANDING THE FOREGOING, WE TAKE NO LIABILITY WHATSOEVER TO YOU OR TO ANY THIRD PARTY WHEN RESPONDING TO ANY COMPLAINT THAT WE RECEIVED OR TOOK ACTION IN CONNECTION THEREWITH.

19.3. If a Customer is not satisfied with how a bet has been settled then the Customer should provide details of their grievance to our Customer Service Department. We shall use our reasonable endeavours to respond to queries of this nature within a few days (and in any event we intend to respond to all such queries within 28 days of receipt).

19.4. Disputes must be lodged within three (3) days from the date the wager in question has been decided. No claims will be honoured after this period. The Customer is solely responsible for their Account transactions.

19.5. In the event of a dispute arising between you and us our Customer Service Department will attempt to reach an agreed solution. Should our Customer Service Department be unable to reach an agreed solution with you, the matter will be escalated to our management.

19.6. Should all efforts to resolve a dispute to the Customer's satisfaction have failed, the Customer has the right to have the dispute settled via arbitration.

20. Assignment

20.1. Neither these Terms nor any of the rights or obligations hereunder may be assigned by you without the prior written consent of us, which consent will not be unreasonably withheld. We may, without your consent, assign all or any portion of our rights and obligations hereunder to any third party provided such third party is able to provide a service of substantially similar quality to the Service by posting written notice to this effect on the Service.

21. Severability

21.1. In the event that any provision of these Terms is deemed by any competent authority to be unenforceable or invalid, the relevant provision shall be modified to allow it to be enforced in line with the intention of the original text to the fullest extent permitted by applicable law. The validity and enforceability of the remaining provisions of these Terms shall not be affected.

22. Breach of These Terms

22.1. Without limiting our other remedies, we may suspend or terminate your Account and refuse to continue to provide you with the Service, in either case without giving you prior notice, if, in our reasonable opinion, you breach any material term of these Terms. Notice of any such action taken will, however, be promptly provided to you.

23. General Provisions

23.1. Term of agreement. These Terms shall remain in full force and effect while you access or use the Service or are a Customer or visitor of the Website. These Terms will survive the termination of your Account for any reason.

23.2. Gender. Words importing the singular number shall include the plural and vice versa, words importing the masculine gender shall include the feminine and neuter genders and vice versa and words importing persons shall include individuals, partnerships, associations, trusts, unincorporated organisations and corporations.

23.3. Waiver. No waiver by us, whether by conduct or otherwise, of a breach or threatened breach by you of any term or condition of these Terms shall be effective against, or binding upon, us unless made in writing and duly signed by us, and, unless otherwise provided in the written waiver, shall be limited to the specific breach waived. The failure of us to enforce at any time any term or condition of these Terms shall not be construed to be a waiver of such provision or of the right of us to enforce such provision at any other time.

23.4. Acknowledgement. By hereafter accessing or using the Service, you acknowledge having read, understood and agreed to each and every paragraph of these Terms. As a result, you hereby irrevocably waive any future argument, claim, demand or proceeding to the contrary of anything contained in these Terms.

23.5. Language. In the event of there being a discrepancy between the English language version of these rules and any other language version, the English language version will be deemed to be correct.

23.6. Governing Law. These Terms are governed excsluively by the law in force in the state of Anjouan in the Union of Comoros.

23.7. Entire agreement. These Terms constitute the entire agreement between you and us with respect to your access to and use of the Service, and supersedes all other prior agreements and communications, whether oral or written with respect to the subject matter hereof.