# Source Code Drop

A source code drop delivers the full source code of a project to the buyer. This is the most transparent product type — the buyer gets everything.

## When to Use

Use this type for:

* Full project repositories (trading bots, DeFi scripts, smart contracts)
* Boilerplates or starter kits
* Audited or documented codebases being sold outright
* Scripts or automation tools where the buyer will read, modify, and run the code themselves

## How Delivery Works

After payment confirms on-chain:

1. The order is marked **Completed**
2. The buyer can download the attached source archive (zip, tar, etc.) from their order page
3. No license key is generated by default — the buyer receives the files directly

## What to Upload

Attach your source code as a compressed archive (.zip or .tar.gz). Include:

* All source files
* A README with setup and usage instructions
* Any configuration examples or `.env.example` files
* Dependencies list (package.json, requirements.txt, etc.)

Do not include secrets, private keys, or credentials in your upload.

## Licensing

When you sell source code, clarify the license terms in your product description. Common approaches:

* **Personal use only** — buyer cannot resell or redistribute
* **Commercial use** — buyer can use in their own products
* **Full ownership** — buyer acquires all rights

The platform does not enforce software licenses — that is between you and the buyer.

## Tips

* Be explicit about what the code does, what dependencies it requires, and what the buyer needs to run it
* Test your archive before uploading to make sure the buyer receives a working project
* Consider including a short demo video or screenshots to show the code in action


---

# 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.blocksmiths.tech/vendors/source-code-drop.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.