zeemscript / TrustMint

Real assets. Clear rules. Stellar Soroban. 
 Open-source building blocks for tokenized invoices, property shares, and carbon credits—with eligibility and transfer rules checked by smart contracts. 
 Open the live preview 
 · Get started 
 · Report an issue 
## The idea
Tokenizing an asset is only one part of the work. Applications may also need holder eligibility, transfer policies, and rules tied to an asset's lifecycle. TrustMint brings those examples together in one inspectable Stellar Soroban repository, so builders can explore the pieces and adapt them for their own testnet prototypes.
TrustMint does not verify identities or provide legal compliance. A trusted verifier records an approval decision on-chain; identity documents and the process behind that decision remain off-chain and under the deploying project's control.
## Explore the building blocks
| Building block | What it demonstrates |
| --- | --- |
| **KYC Registry** | Authorized verifiers record approval, tier, jurisdiction, and optional expiry for a Stellar address. |
| **Compliance Engine** | Transfer policy examples such as pause controls, address and jurisdiction blocklists, transfer limits, holding periods, and holder caps. |
| **Invoice Token** | Invoice metadata with issuance, transfer, settlement, and redemption examples. |
| **Property Token** | Fractional property shares with cumulative per-share dividend accounting. |
| **Carbon Credit Token** | Credit issuance, transfer, and retirement records with beneficiary metadata. |
| **RWA Reference Token** | A separate SEP-41-style token example with KYC and compliance hooks and asset metadata. |
The repository also contains a React + Vite dashboard, a TypeScript SDK, deployment helpers, Rust contract tests, and local Stellar integration tests.
## How a policy check flows
 [code] 
Asset contracts invoke the registry and compliance engine during relevant operations. The exact checks depend on the contract and method. An on-chain approval is a record of a verifier's decision, not proof that an off-chain identity or compliance process is adequate.
## Get started
### Requirements
- Rust toolchain and the `wasm32-unknown-unknown` target
- Stellar CLI
- Node.js 20 or newer
- Docker, if you want to run the local integration suite
### Build and test the contracts
From the repository root:
 [code] 
### Run the dashboard
 [code] 
The interface can load without contract IDs. Network-backed workflows need the relevant `VITE_*_ID` values in `frontend/.env`. Start from `frontend/.env.example`. Vite variables are bundled into the browser app, so never put private keys, secrets, or identity documents in them.
### Deploy the example suite to Stellar testnet
The helper deploys the KYC registry, compliance engine, invoice token, property token, and carbon-credit token. It writes those IDs to `frontend/.env`. The separate RWA reference token is not included. The asset metadata in the script is placeholder data; review and replace it before every dep