> For the complete documentation index, see [llms.txt](https://docs.djib.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.djib.io/products/djib-sign/get-started-with-djib-sign.md).

# Get started with Djib Sign

To start working with the app, all you need is a crypto wallet on Solana, Ethereum or Binance blockchain. Djib Sign already supports Phantom and Solflare wallets for Solana and Metamask wallet for Ethereum and Binance blockchain.&#x20;

Log in to the [app](https://sign.djib.io/) by connecting to your wallet, and from there you will be able to upload files, share files and ask members to either sign (according to your defined order) or just view the document, finally you store the signed documents as NFT and all members will have a life-long access to it.&#x20;

No subscription or extra hassle for payment is required throughout the cycle and user pays the fee by DJIB token which directly buys with the crypto asset on their wallet, on Djib Sign dashboard.


---

# 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.djib.io/products/djib-sign/get-started-with-djib-sign.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.
