> For the complete documentation index, see [llms.txt](https://dmtp.gitbook.io/dmtp-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dmtp.gitbook.io/dmtp-sdk/11-web3-traffic-exchange-release-notes/11.2-web3-traffic-exchange-mvp2-release-notes.md).

# MVP2 Release Notes

## Introduction

We're pleased to announce the release of MVP2 for the Web3 Traffic Exchange SDK. This update brings significant improvements to our platform, including the launch of our production environment and several key enhancements to functionality and user experience.

## Key Updates

### Production Environment Launch

* Our production environment is now live. All users should transition to using this environment for their campaigns and inventories.

### Banner Format Change

* Banner size requirement has been updated to 64x64 pixels.
* Offer wall item rendering updated to match new design specifications.

### Offer Wall Enhancements

* Added support for offer wall ad inventory in addition to traditional banners.
* Publishers can now create and manage offer wall inventories.
* New JavaScript method provided for publishers to invoke the offer wall.

### Campaign and Inventory Management

* Added ability to delete ad campaigns.
* Added ability to delete ad inventories.

### User Experience Improvements

* Enhanced handling of banner click events in TMA mode.
* Updated navbar with new items including Home link, updated logo, and visible points balance.
* Points per click in campaign creation set to 1 by default and editing disabled.

### Developer Experience

* Created and published SDK user documentation.
* Updated handling of Telegram user ID for better tracking.

### Security Enhancement

* Implemented hashing of wallet addresses in the banner exchange code URL.

## Current Limitations

* One wallet address per user account.
* Limited to one active campaign per user.
* Maximum of two inventories per user (one banner and one offer wall).
* Basic reporting features showing only current point balance.
* Points system remains a virtual currency without blockchain integration.

## Upcoming Features

We're continually working to improve the SDK. Future updates will include tracking ad impressions, in-game bonuses API, "only unplayed" ad selection rules, and further UI improvements.

## Feedback

Your input is crucial for our ongoing development. Please report any issues or suggestions through our support system at <https://dmtp-tech.zendesk.com/hc/en-us/requests/new>.


---

# 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://dmtp.gitbook.io/dmtp-sdk/11-web3-traffic-exchange-release-notes/11.2-web3-traffic-exchange-mvp2-release-notes.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.
