> For the complete documentation index, see [llms.txt](https://docs.wizz.cash/wizz-wallet/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wizz.cash/wizz-wallet/bihelix-and-rgb/faq.md).

# FAQ

1. What addresses can receive $jerry and $RNA? \
   Answer: Currently, only the m/84'/0'/0'/9/0 and m/86/1/0/9/0/0 address paths support receiving RGB assets. The standard path m/84'/0'/0'/9/0 is recommended by default. If you're importing from a TokenPocket wallet, select m/86/1/0/9/0/0.&#x20;
2. Do I need to transfer BTC to my wallet before receiving the airdrop? \
   Answer: Yes, you do. Please refer to the "[Receiving RGB Assets](/wizz-wallet/bihelix-and-rgb/receive-rgb-assets.md#er-transfer-btc)" guide for detailed steps.&#x20;
3. Why do I need to transfer BTC before receiving the airdrop? \
   Answer: This is related to the design of the RGB protocol, where BTC is required for the "coloring" process to represent RGB-related assets.
4. When can I transfer $jerry? \
   Answer: Currently, Wizz Wallet supports the display of RGB assets. A new version supporting RGB asset transfers will be released soon. Please stay tuned for official announcements for the latest updates.
5. I used a bc1p address to receive $jerry. What should I do? \
   Answer: If RGB assets were mistakenly sent to an address with a different path, you can currently only view them but not transfer them. However, transferring non-RGB protocol assets from that wallet address will not result in the loss of RGB assets, so there’s no need to worry.
6. What are the $jerry airdrop rules? \
   Answer: Please check the official Jerry website: <https://jerrysbox.xyz/>.


---

# 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.wizz.cash/wizz-wallet/bihelix-and-rgb/faq.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.
