Stellar-Sentinel/sentinel-contracts

选用指南

AI 根据 README 整理 · 2026/10/17 03:46:12

使用方式

通过 Stellar CLI 部署和调用合约，使用 Rust 和 Soroban SDK 构建。

查看 README 依据

These commands create a **new** identity and contract instance; they do not redeploy or alter the contract above. Install the Stellar CLI, Rust, and the Wasm target first. Keep the generated identity in secure storage and never commit its seed phrase. ```bash stellar keys generate sentinel-admin --network testnet --fund --secure-store stellar contract build --locked stellar contract deploy \ --wasm target/wasm32v1-none/release/sentinel_contract.wasm \ --source-account sentinel-admin \ --network testnet \ --alias sentinel_contract stellar contract invoke \ --id sentinel_contract \

Requires stable Rust, the `wasm32-unknown-unknown` and `wasm32v1-none` targets, and Stellar CLI for optimized deployment builds. There are no contract-specific environment variables; network IDs and signing identities are supplied to deployment tooling outside this repository. ```bash rustup target add wasm32-unknown-unknown wasm32v1-none cargo build --target wasm32-unknown-unknown --release stellar contract build --locked cargo test cargo clippy --all-targets -- -D warnings ```

部署要求

需要 Rust 稳定版、wasm32-unknown-unknown 和 wasm32v1-none 目标，以及 Stellar CLI。

查看 README 依据

Requires stable Rust, the `wasm32-unknown-unknown` and `wasm32v1-none` targets, and Stellar CLI for optimized deployment builds. There are no contract-specific environment variables; network IDs and signing identities are supplied to deployment tooling outside this repository. ```bash rustup target add wasm32-unknown-unknown wasm32v1-none cargo build --target wasm32-unknown-unknown --release stellar contract build --locked cargo test cargo clippy --all-targets -- -D warnings ```

已知限制

合约不存储完整历史，需要事件索引；无法验证链下评分的准确性；管理事件索引当前不在仪表板显示。

查看 README 依据

# Stellar Sentinel Soroban Contract [](https://github.com/Stellar-Sentinel/sentinel-contracts/actions/workflows/ci.yml) [](LICENSE) Soroban contract for administrator-managed monitoring and response roles, a configurable 0–100 score threshold, and account flags. It publishes flag and administrative events and stores the latest flag for each subject. It does not store full history; event indexing is needed for that.

| `gpause` / `gunpause` | guardian or administrator address | `bool` | Guardian pause state changed. | The existing `flagged` event remains unchanged: its topics are `flagged`, agent address, and subject address, and its value is the `u32` score. The backend also decodes `flaggedv2` reports. Administrative event indexing is not currently shown in the dashboard. A failed or unauthorized call aborts before publishing an event. ## Testnet deployment

Successful initialization and state-changing administrative calls publish the corresponding events described above. Read methods do not extend the TTL of each grant; expired grants are removed from the active registry when agent counts or lists are refreshed. Only trusted addresses should receive agent authorization. The contract enforces the score range and threshold, but it cannot establish that an off-chain score is accurate. Storage follows Soroban TTL and archival rules. Deploy, initialize, and configure each network separately; never commit secrets.