> For the complete documentation index, see [llms.txt](https://slippay.gitbook.io/slippay-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://slippay.gitbook.io/slippay-docs/smart-contract-and-open-source/open_source.md).

# Open-source declaration

The Open Track requires an explicit open-source plan for any smart contract. This is that declaration.

## Smart contract

* **What:** SlipPay subscription contract (Soroban), `slippay-subscription`.
* **Source:** `contracts/subscription/src/lib.rs` in the public repo `github.com/Galmanus/slippay`.
* **License:** **Apache-2.0** — declared in `contracts/subscription/Cargo.toml` and in the repository-root `LICENSE` file. The contract source is public and Apache-2.0 from inception (not a future relicensing promise).
* **Deployed (mainnet):** `CBJMQ6ZYQJ2OMM46FGXPEIKKZDRHHERBXUVE54ZN64FDPKN5DJKSEVQN` · Wasm hash `1dbda19a2c9962cf798b62557f7c6388a3ea3c7c506ddb7aafbd549843510c6b`.
* **Deployed (testnet):** `CBN3M7IAKNSCSDQIUUGDBHSFUQDOFAQQQK6UXJZYGGIWERQGT24VBTFQ` (same Wasm hash — identical bytecode promoted after the F5 real-wallet end-to-end charge gate closed).
* **Reproducible build:** Soroban SDK 26 · Stellar protocol 26 · `cargo test --release` (5/5 passing). The mainnet Wasm hash matches the source in-repo, so any third party can rebuild and verify byte-for-byte.

## Open-source roadmap for future deployments

* All future contract versions (v0.3+, e.g. the pre-auth allowance primitive noted in `DEPLOYED.md` F4) ship Apache-2.0 in the same public repo before mainnet deploy.
* Each deploy records upload tx, deploy tx, deployer, and Wasm hash in `contracts/subscription/DEPLOYED.md` so the on-chain bytecode is always traceable to a public, licensed source commit.

## What is NOT open-source (and why)

* The off-chain API (`supabase/functions/api`), web app, and platform-fee billing logic are proprietary — they are the commercial layer, not the on-chain primitive. The grant-relevant artifact (the contract) is fully open.


---

# 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://slippay.gitbook.io/slippay-docs/smart-contract-and-open-source/open_source.md?ask=<question>&goal=<user_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.