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

# FAQ

## FAQ

### What is SPLEN?

SPLEN is a platform for sending onchain assets through private claim links.

### Does SPLEN hold my assets?

No. Transfers are secured through the SPLEN escrow contract rather than being held by SPLEN as a custodian.

### Does the recipient need gas?

No. SPLEN covers the gas required for the claim through its relayer.

### Does the recipient need a wallet?

The recipient needs a wallet to receive the assets, but they do not need to have a wallet set up before receiving the claim link.

### Are claim links private?

Yes. Claim links contain the information required to access the associated claim. They should only be shared with the intended recipient.

### What happens if nobody claims the assets?

Unclaimed transfers can be refunded after the applicable claim period. The current period is 30 days.

### Can I share a claim link publicly?

You should not. Anyone who obtains access to a claim link may be able to claim the associated assets.

### Is SPLEN custodial?

No. SPLEN is designed around non-custodial escrow.

### Where can I use SPLEN?

Check the SPLEN application for currently supported networks and assets.


---

# 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.splen.site/splen/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.
