> For the complete documentation index, see [llms.txt](https://docs.arweavekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arweavekit.com/data-upload-service.md). # Data Upload Service This service is used with Arweave Data Storage SDK to upload data to Arweave and pay for the storage using other chain's stablecoin tokens. ***Supported chains and stablecoins*** *Ethereum and EVM:* USDC and USDT *Solana:* USDC and USDT *Cosmos:* Noble *If you would like to request support for a stablecoin payment on a different chain, please open an issue in the github repo* [*here*](/data-upload-service.md) ### Prerequisites * Docker * Node.js (>= v20.18.3) * pnpm (>= v9.14.2) ### Installation ``` pnpm install ``` ### Running the service ``` pnpm start:dev ``` ### Running the service in production mode ``` pnpm start:prod ``` ### Prisma migrations ``` pnpm db:migrate:dev ``` ``` pnpm db:migrate:prod ``` ### Prisma Studio ``` pnpm db:studio ``` --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.arweavekit.com/data-upload-service.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.