Backend Overview
The Backend Service enables multi-signature transaction coordination for Stablecoin Studio. When a Hedera account requires multiple keys to sign a transaction, this service collects and manages the signatures.
How It Works
- The first signer creates a transaction proposal via the API.
- The backend stores it temporarily (3-minute validity window).
- Other key holders retrieve and sign the transaction.
- Once the signature threshold is met, the backend submits the fully signed transaction to Hedera.
Single-level keys only: Key lists or threshold keys cannot contain nested key lists or threshold keys.
Core Technologies
| Technology | Purpose |
|---|---|
| Node.js | Runtime |
| NestJS | Framework |
| PostgreSQL + TypeORM | Database |
| Swagger | API documentation |
| @hashgraph/sdk | Hedera integration |
| Winston | Logging |
| Jest | Testing |
When You Need It
The backend is optional. You only need it when operating stablecoins with multi-key accounts (keyList or thresholdKey). Single-key accounts can use the SDK, CLI, or Web DApp directly.