Stellar-Kolo/kolo-contracts

选用指南

AI 根据 README 整理 · 2026/10/14 15:30:34

使用方式

通过 Rust 和 Soroban SDK 构建为 Wasm 合约，部署到 Stellar 网络，由后端应用调用合约接口。

查看 README 依据

## Build and test Requires Rust and the Wasm target: ```bash rustup target add wasm32v1-none ``` From the `contracts/` directory: ```bash cargo test cargo build --target wasm32v1-none --release ``` The release Wasm artifact is written to `contracts/target/wasm32v1-none/release/`. This target is required by Soroban SDK 27 with current Rust toolchains; `wasm32-unknown-unknown` is rejected by the SDK on newer Rust versions. ## Integration with Kolo

The [Kolo backend](https://github.com/Stellar-Kolo/kolo-backend) is responsible for loading the compiled Wasm, deploying contract instances, constructing and simulating Soroban transactions, obtaining authorization, submitting through Soroban RPC, and waiting for confirmation. It also needs to keep contract state and PostgreSQL records reconcilable. The [Kolo frontend](https://github.com/Stellar-Kolo/kolo-frontend) is the web companion; the planned primary member experience is WhatsApp-first.

部署要求

需要 Rust 和 Wasm 目标（wasm32v1-none），使用 Soroban SDK 27。

查看 README 依据

## Build and test Requires Rust and the Wasm target: ```bash rustup target add wasm32v1-none ``` From the `contracts/` directory: ```bash cargo test cargo build --target wasm32v1-none --release ``` The release Wasm artifact is written to `contracts/target/wasm32v1-none/release/`. This target is required by Soroban SDK 27 with current Rust toolchains; `wasm32-unknown-unknown` is rejected by the SDK on newer Rust versions. ## Integration with Kolo

已知限制

合约不自动触发操作，需应用协调；当前仅部署到测试网，未初始化实例，不适用于生产资金。

查看 README 依据

**Status:** a version of the contract code is deployed to Stellar Testnet for review. No savings-group instance has been initialized, and no token has been deposited. The backend integration is still being aligned with the current contract interface. This is not a production-ready custody system; do not use real funds. ### Testnet deployment - **Network:** Stellar Testnet - **Contract ID:** [`CBQCB6KIXAPDPKGNZFR3KSBBJNEJRFN3MAQL7S46JGFA5I22AUL4OPYL`](https://stellar.expert/explorer/testnet/contract/CBQCB6KIXAPDPKGNZFR3KSBBJNEJRFN3MAQL7S46JGFA5I22AUL4OPYL)

The contract enforces rules on an invocation; it does not run on a wall-clock schedule. `expected_cycle_days` informs the stored cycle-length setting used for TTL calculations, but the contract does not automatically trigger contributions, payouts, or resets. The application coordinates those actions. ## Interface Primary exported operations: ```text initialize( admin: Address, token: Address, name: String, contribution_amount: i128, group_type: GroupType, target_amount: Option<i128>, lock_until_target: bool, expected_cycle_days: Option<u32> )