BetDEX API FAQ

[druspencer]

The team over at BetDEX kindly exposed a simple API endpoint to allow developers to see their currently published mainnet markets. this endpoint groups all their markets by category (sport) and event (league) and provides additional information such as expected end date and team codes.

• https://prod.events.api.betdex.com/events

This lists all of their currently running markets that have been published with their authority J2LqciLvyxVHMjMcda73459zWfFxw7rveDb5YAhSdGTe.

Why does this exist?

BetDEX, as early consumers of the Monaco Protocol, have to work around some of the limitations in the protocol. They opened up the API in order to allow developers to work around these limitations whilst also reducing the amount of on-chain requests a consumer would have to make in order to get currently published markets by the operator.

What are the limitations?

• No events service
• Market PDA generation

What's the TLDR?

• eventAccount through the API is a top level unique identifier to group markets under the same context
• eventAccount on a market on-chain mean nothing right now and link to nothing
• Markets grouped under the same eventAccount through the API may have different eventAccounts on chain
• An events service is in-development to make the eventAccount mean something and provide on-chain context for a market
• Market PDA generation on the Monaco Protocol is being looked into in order to reduce limitations

What is the events service?

The events service is an in development on-chain program that will provide more context about the event a market is for. This is the eventAccount found on a marketAccount. Without an event account, you can't know the context around a market, so you may see a market that has a title Both Teams to Score with Yes | No as outcomes, but you wouldn't know what sporting event this relates to.

The events service will provide that information. By querying the associated eventAccount you'd be able to see that the Both Teams to Score market relates to Manchester City vs Arsenal in the EPL taking place on 18th May 2023.

Knowing this eventAccount you would then, in theory, be able to find all markets associated with that event. However, without an event service, this isn't possible right now. Additionally, there is the second limitation of market PDA generation.

What is the Market PDA Limitation?

Market PDAs are generated based on eventPk, mintToken, and marketType only one market can be created for each combination of these. However, there is currently only 4 supported marketTypes on the protocol. Meaning any one event can only have 4 markets associated with it:

• eventX-USDT-EventResultFullTime
• eventX-USDT-EventResultHalfTime
• eventX-USDT-EventResultBothSidesScore
• eventX-USDT-EventResultWinner

This of course does not scale for an operator such as BetDEX running multiple market types. As such, they group markets together on their API level rather than an on-chain level.

From the example below we can see that we have the event:

• EventAccountAcS38FQfKHbwoUWiKJFbcKVXj8TiSUnLg5kXaQYx2VZ1
• The participants, with team codes are Newcastle United and Brighton & Hove Albion
• Their top players for scoring markets are Almirón and Mac Allister
• Starting at 1684434600
• Estimated to finish as 1684441800
• The event is FOOTBALL in the EPL which translates to Football and English Premier League for display purposes

None of this information exists on-chain, but it is vital context for a market operator in order to group its markets not only for the user, but for internal operator functions such as settlement.

We can also see that this event has 3 markets:

• Full Time Result
• Both Teams to Score
• Over/Under 2.5

Each of these markets do exist on-chain, but they could theoretically have different eventAccounts. This is because of the PDA limitation. Essentially, right now - the on-chain eventAccount for a market means nothing for BetDEX. The top-level API eventAccount, is their unique identifier for market grouping. Eventually, with an events service and the PDA restrictions resolved, this top-level API eventAccount will also relate to an on-chain event providing all the context around a market required for any operator.

          "events": [
            {
              "eventAccount": "AcS38FQfKHbwoUWiKJFbcKVXj8TiSUnLg5kXaQYx2VZ1",
              "eventName": "",
              "participants": [
                {
                  "name": "Newcastle United",
                  "players": [
                    "Almirón"
                  ],
                  "id": "NEW"
                },
                {
                  "name": "Brighton & Hove Albion",
                  "players": [
                    "Mac Allister"
                  ],
                  "id": "BRH"
                }
              ],
              "eventStart": 1684434600,
              "estimatedEnd": 1684441800,
              "category": "FOOTBALL",
              "categoryTitle": "Football",
              "eventGroup": "EPL",
              "eventGroupTitle": "English Premier League",
              "markets": [
                {
                  "marketAccount": "6gTVRcfu7fda5qXLSvetHSuSn8SHxpUmh1Tf5GPdAA2t",
                  "marketLock": 1684434600,
                  "marketName": "Full Time Result",
                  "outcomes": [
                    "Newcastle United",
                    "Draw",
                    "Brighton & Hove Albion"
                  ],
                  "invalidOutcomes": [ ],
                  "displayPriority": 1,
                  "mint": "Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB"
                },
                {
                  "marketAccount": "4bfEM6JBL3ZSi5tdkye3QHUiQPnmTeyv2gbsYybfFqnm",
                  "marketLock": 1684434600,
                  "marketName": "Both Teams to Score",
                  "outcomes": [
                    "Yes",
                    "No"
                  ],
                  "invalidOutcomes": [ ],
                  "displayPriority": 4,
                  "mint": "Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB"
                },
                {
                  "marketAccount": "4pWFm451YAcPwmGW4dHmefzbXghQMyazt4qYdPfHSfoi",
                  "marketLock": 1684434600,
                  "marketName": "Over/Under 2.5",
                  "outcomes": [
                    "Over 2.5",
                    "Under 2.5"
                  ],
                  "invalidOutcomes": [ ],
                  "displayPriority": 7,
                  "mint": "Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB"
                }
              ]

[druspencer]

Answers in post