# REDX's Solution Strategy

REDX is addressing these challenges through the following approaches:

## **1. Expansion of Real Business Centered Around RED° TOKYO TOWER**

REDX is being developed around RED° TOKYO TOWER, Japan’s largest digital amusement facility, which opened in April 2024.

Located within Tokyo Tower, which attracts over 3 million visitors annually, this facility serves as a hub where all key stakeholders of the REDX project—including fans, creators, investors, and business partners—converge.

From this starting point, we will collaborate with partners to expand both online and offline experiences globally.

<div align="left"><figure><img src="/files/niGJIY1u0Uc4YdaNSHUK" alt="" width="375"><figcaption><p>Logo of RED° TOKYO TOWER</p></figcaption></figure></div>

<div align="left"><figure><img src="/files/TdRqT0LQKoiKoQuhf5lu" alt=""><figcaption><p>Image of RED° TOKYO TOWER</p></figcaption></figure></div>

RED° TOKYO TOWER official Web site: <https://tokyotower.red-brand.jp/>

## **2.** Bridging Web2 and Web3

REDX prioritizes ease of use for Web2 users, ensuring a familiar and seamless experience. For example:

* Tickets are automatically converted into NFTs.
* Users can earn REDX like loyalty points through various activities.
* Everyday purchases allow users to accumulate REDX tokens.
* Special NFTs can be obtained as part of the experience.

This design enables users to naturally experience the value of Web3 without needing prior blockchain knowledge.

## **3.** Global Expansion & Accessibility

By using RED° TOKYO TOWER as a launching point and ensuring Web2-level usability, REDX eliminates regional restrictions, making it accessible to users worldwide.

Additionally, by integrating with TON (The Open Network), which has over 300 million global users, REDX is accelerating the mainstream adoption of Web3.

**High-Level Structure of the REDX Solution**

<figure><img src="/files/BcuCaH0r7YWVWNGFaYHU" alt=""><figcaption><p><strong>High-Level Structure of the REDX Solution 1</strong></p></figcaption></figure>

<figure><img src="/files/6kMci61lpcsgibGG4yq4" alt=""><figcaption><p><strong>High-Level Structure of the REDX Solution 2</strong></p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.redx-project.com/introductions/redxs-solution-strategy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.