# Why SwarmPad

SwarmPad emerges as a solution to several pressing issues currently plaguing the market, especially in the context of zkSync and IDO participation:

1. **Complicated bridging process:** Users are often deterred from participating in zkSync-based projects due to the complex bridging process, which involves switching networks, finding the appropriate bridge, setting up RPC, and more. SwarmPad simplifies this process by allowing users to join IDOs from various chains without needing to bridge assets or navigate cumbersome steps.
2. **High bridging & gas fees:** Bridging & gas fees can be prohibitively high for users trying to participate in zkSync-based projects, discouraging them from engaging with the ecosystem. SwarmPad's no-bridging design helps reduce these fees, making it more appealing for users to join IDOs.
3. **Lower Total Value Bridged compared to other L2 solutions:** At the time of writing, zkSync's Total Value Bridged in ETH is approximately 2x less than Optimism and 9x less than Arbitrum. This disparity affects the total fundraising potential for IDOs on zkSync. SwarmPad aims to bridge this gap by enabling seamless cross-chain participation, increasing the potential for funds to be raised on zkSync-based projects.
4. **Centralized decision-making for IDOs:** Most launchpad IDOs are determined by project teams, not the community, which goes against the principles of decentralization. SwarmPad addresses this issue by being community-driven and DAO-governed, ensuring that the community has a say in the IDOs hosted on the platform and promoting a more decentralized decision-making process.
5. **Limited asset support:** Many launchpads only support single assets, which can be less user-friendly and hinder participation. SwarmPad, on the other hand, supports multiple assets, making it easier for users to contribute to IDOs using various tokens and cryptocurrencies. This inclusive approach encourages broader participation and fosters a more vibrant and diverse ecosystem.


---

# 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://swarmpad.gitbook.io/swarmpad-docs/why-swarmpad.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.