Architecture and assurance
Share the system responsibilities and the evidence behind a deployment review.
Download PDF · Editable Markdown
Thesauros separates the customer experience, integration services and vault execution so teams can review each responsibility directly.
Customer and partner layer
The partner owns the app experience, identity system and support relationship. A server-side Partner API credential links customers and reads scoped reporting. TypeScript and Python SDKs provide typed methods, response metadata, error handling and signature helpers. Wallet transaction authorization is a separate part of the flow.
Vault and market layer
Vault shares represent a position in the underlying asset. Provider adapters connect the vault to lending markets. The rebalancer changes allocation under its configured roles and controls. Integrations must use the ABI, assets and configuration of the confirmed deployment rather than treating every public repository version as equivalent.
Data and operating layer
The Partner API persists attribution and reporting records in PostgreSQL. Observed APY snapshots feed rate history and analytics; the configured monitoring service supplies observations used in protocol-wide reconciliation. Customer-facing views need timestamps, empty states and an explicit policy for delayed reporting.
Assurance evidence
The October 2025 Hexens report covers specific revisions in Thesauros/contracts. The original PDF and its finding dispositions remain authoritative. It does not automatically cover the newer optimized rebalancer, backend, SDKs or partner application.
Source review shows that the optimized rebalancer's admin can pause deposit and withdrawal actions, while provider-set changes use the configured timelock. Confirm role holders, fees, upgrade authority where applicable and action availability in the deployment pack.
Review package
Use the contract registry, source revision, audit/remediation mapping, role inventory, integration acceptance results and incident runbook together. The documentation provides the framework; onboarding establishes the configuration and operating commitments for the actual integration.