> 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/getting-started/42-points/42-points.md).

# 42 Points

You earn points by trading on 42. Every week, a set amount of points is shared among users based on their activity.

## Weekly issuance

42 issues points on a weekly cycle, running Thursday 00:00 UTC to Wednesday 23:59 UTC.

* Busier weeks issue more. The amount moves within that range with trading activity on 42 and never falls below the minimum.
* Each week's points are shared among users based on what they did on 42 that week.

## How you earn

Each week's points are shared among all wallets based on their trading volume and the positions they hold through settlement. Boosts, including boosts for community contributions such as mindshare and referrals, multiply that.

### Trading volume

Trading volume carries the most weight. It is the value of every buy and every sell you make in the week, across all 42 markets, whether a trade wins or loses.

### Settlement

Positions you hold until their market settles add further to your share, on top of their trading volume. What counts is what you paid for them: the more you paid for positions held through settlement, the more they add, whichever way the market resolves.

* They count in the week the market settles, not the week you bought.
* A position sold before settlement keeps its trading volume but adds nothing for settlement.

### Boosts

A boost raises your share of the week's points, applied on top of your trading volume and settlement. Boost types include, but are not limited to:

* Your total mindshare score for the week
* Activity of the wallets you referred
* Holding special entitlement credentials
* Wallets designated for a boost

Different types of boosts can stack. Your final points for the week combine your trading volume, settlement and boosts, measured against the total across the network.

## Weekly updates

Points are updated once a week, after each week closes on Wednesday (UTC). You can see your points and the week's total on \[Points page — link to add].

Points earned in a week appear in the following update.

## Disclaimers

* 42 may exclude any wallet or activity that undermines the fairness of the program, and remove points earned from it.
* System wallets operated by 42 do not earn points.
* 42 may update these rules and will announce changes before they take effect.
* Participation may be restricted in some jurisdictions. You are responsible for complying with the laws that apply to you.
* Nothing here is financial, investment or legal advice.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.42.space/getting-started/42-points/42-points.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
