> For the complete documentation index, see [llms.txt](https://docs.rairprotocol.org/rairprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rairprotocol.org/rairprotocol/codebase/rairdapp/rairfrontend/proxy-settings-for-default-frontend.md).

# Proxy Settings for Default Frontend

**Create custom component `SimpleDApp.tsx`**

 This component uses these components:

* Connect button
* Social logins
* Main banner
* TitleCollection (replaced mint button to Main banner)

1. Remove Connect button from Header
2. Changed logic in `useConnectUser` hook and `TitleCollection` component
3. Improving styles
4. Adding specific conditions to display the Connect Button or Main banner
5. In `App.tsx` component I changed main url `'/'` . In RairDapp it uses `SimpleDApp.tsx` now. And because of this we see another main component
6. In order for authorization using social logins to work, you need to add the following variables to the env file:

* `VITE_BASE_MAINNET_ALCHEMY_KEY`
*  `VITE_BASE_MAINNET_GAS_POLICY`

In our case, this is the Base blockchain:\
 `VITE_BASE_MAINNET_ALCHEMY_KEY=xxx`\
 `VITE_BASE_MAINNET_GAS_POLICY=xxx`


---

# 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.rairprotocol.org/rairprotocol/codebase/rairdapp/rairfrontend/proxy-settings-for-default-frontend.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.