# Case Study: Gravita

Drawing on the successful integration by Gravita Protocol, one of Zyfi's early adopters, we've distilled valuable insights into effective UI practices. User demand for Paymaster is [constantly increasing as it can be seen from this Dune Dashboard.](https://dune.com/zyfi/zyfi-usage-overview)

<figure><img src="/files/FU1xx9GF5cAWKJxUIt2g" alt=""><figcaption></figcaption></figure>

## **Advantages**

* **Wide Token Acceptance**: Supports more than 80 ERC-20 tokens.
* **Transparent Fees**: Users see and approve only the exact amount needed, which is available upfront, optimizing costs and security.
* **Gas Refunds**: Unspent gas is refunded in the fee token it was paid in.
* **Instant Quotes**: The API delivers real-time fee quotes and discounts, improving user experience.

## **UI and UX implementation - Overview of Best Practices**

Unlock the full potential of your platform with simply crafted UI enhancements and additions:

1. **Add a tooltip with a Gas Icon and Display the Wallet Balance of the user**:
   * Ensure the user's wallet and token balances are easily visible near this icon.
2. **Spotlight on Paymaster Service - Clear Indicators for Paymaster Availability**:
   * Utilize eye-catching elements like colour contrasts or animations shining a spotlight on the revolutionary and cutting-edge paymaster service availability.
3. **Highlighting Savings: Unveil Discounts with Clarity**

   * Clearly display any discounts on gas fees available through the paymaster service.
   * Use visual cues like percentage-off tags or highlighted text to indicate savings.

   This approach not only highlights a key advantage your protocol offers compared to competitors, but also gives users a solid reason to return and transact more, driving even more engagement with your protocol.

<div align="center" data-full-width="false"><figure><img src="/files/nWoVkRmpe6vAEk0AAMnh" alt=""><figcaption><p>Zyfi and it's partners are happy to sponsor a discount on transaction fees for the first users</p></figcaption></figure></div>

## **Additional Considerations - Optional**

* **Zyfi Airdrop Participation:** users executing transactions through Zyfi will receive an airdrop from the protocol. A dashboard will soon be available with more information about this program.&#x20;
* **Remember User Preferences with Cookies**: Utilize cookies to save user preferences for future visits - consider not displaying the "Attention-Getter" or popup again or for a certain amount of time if the user closed it previously. When a user selects a token for gas payment, store this choice so that it's pre-selected upon their return, streamlining their experience.
* **Feedback Mechanisms**: Implement real-time feedback on gas fee calculations, discount and sponsoring as users select different tokens, or after they complete a transaction.
* **Documentation:**  you can also write your own documentation, [feel free to get inspired by Gravita's one linked here.](https://docs.gravitaprotocol.com/gravita-docs/how-does-gravita-work/paymaster-on-zksync)
* **Mobile**: Ensure that all elements are accessible and usable, without forgetting mobile users.

<figure><img src="/files/DfoWVNVUb2f20lm6XJa2" alt=""><figcaption><p>Do not forget mobile users!</p></figcaption></figure>

## **Conclusion**

In conclusion, embracing these best practices guarantees a seamless and efficient experience for users paying gas on your protocol with any ERC-20 token, including your token!&#x20;

[Check out our Dune Dashboard](https://dune.com/zyfi/zyfi-usage-overview) to see how much utilisation of Paymaster Services has increased over time.\
\
Consider extending the use of your token as a gas payment option to your partners and across zkSync: ZyFi works with DEXes, lending platforms, NFT marketplaces, gaming ecosystems and more.&#x20;


---

# 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.zyfi.org/integration-guide/case-studies/case-study-gravita.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.