> For the complete documentation index, see [llms.txt](https://docs.42.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.42.space/changelog/readme.md).

# Changelog

{% updates format="full" %}
{% update date="2026-06-16" %}

## Prouct update

#### Introducing a Tickets Reward System

We're launching a new rewards mechanic — **Tickets**. When you trade on designated markets, you automatically earn Tickets based on your activity: trading volume, streaks, daily participation, referrals, and more.  

Markets with special Ticket multipliers are now highlighted with a **Boosted** tag, making it easier to spot higher-reward opportunities

<div><figure><img src="/files/wpY6HZwfgsMvbqAbJy7w" alt=""><figcaption></figcaption></figure> <figure><img src="/files/bI1EPxHHQAp0Bk7i00Kx" alt=""><figcaption></figcaption></figure></div>

#### Clearer timeline and phase for soccer scoregrid markets

We've added a visual timeline to Soccer Scoregrid markets, giving you a clearer picture of exactly where you are in the market lifecycle at any point. The timeline shows when the market opens, when the spread surges as the match approaches, when the game kicks off and ends, and when the market resolves in one glance.

<figure><img src="/files/w0840z20jwbG9veVcVfA" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/g3SFwipcHnwfVzXnoLF3" alt=""><figcaption></figcaption></figure>

#### High exit spread warning

We added a visual aid for when there's a high exit spread

<figure><img src="/files/5S4ASKeYOoOjyAK0vaHr" alt=""><figcaption></figcaption></figure>

#### Bug Fixes

* Fixed a misleading display issue on Soccer Scoregrid markets where the trade summary displayed '0' in the sell state when no positions were selected
* Refined divider line colours for a cleaner, more polished look
* Prevent negative numbers from being entered in trade inputs
  {% endupdate %}
  {% endupdates %}

{% updates format="short" %}
{% update date="2026-06-11" tags="feature,improvement,fix" %}

## Product update

### Improved trading page layout

* The chart lives on the left so you always have context. Outcomes are listed beside it. And the trading window sits on the right. Everything where you need it
* **See what traders are actually doing.** The activity tabs got a refresh. Cleaner and easier to scan. Spot what other traders are buying across all outcomes at a glance
* New "Related Markets" section at the bottom of every page helps you find connected markets, and stay in the flow

<div align="center"><figure><img src="/files/zyja9KS2Pw0MvHRtzFZz" alt=""><figcaption></figcaption></figure></div>

### **Trade in your language**

We added language support so more people can trade with confidence

<figure><img src="/files/nSLoNVNkAY1wrXUUmpN9" alt=""><figcaption></figcaption></figure>

### New to 42?

We added a mechanics explainer so anyone can understand how it all works

<figure><img src="/files/zGFIi6syBt4DtDp63D9P" alt=""><figcaption></figcaption></figure>

### **Know before you buy**

A confirmation step before every purchase so you can stay in control

<figure><img src="/files/4UXEwDNe69doO40WDjsk" alt=""><figcaption></figcaption></figure>

<a href="/pages/NS8K2uanRK2FKhpTBlsl" class="button primary">Read full update</a><a href="https://gitbook.com/" class="button secondary">Documentation</a>
{% endupdate %}
{% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.42.space/changelog/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.