Introduction

The following chapters describe common workflows that use a combination of Taurus-PROTECT API endpoints to accomplish specific operational objectives.
For a complete list of available endpoints and a description of the parameters please refer to our API reference.

Authentication

All workflow examples assume that you have a good understanding of the authentication and authorization mechanisms covered in the Authentication chapter. To keep the code examples concise, they build on a proxy server introduced in the HMAC authentication proxy section.

Creating Signatures for Approvals

Many actions in Taurus-PROTECT—such as creating a transaction request, or initiating staking—are subject to governance rules that require digital signatures from designated operators in groups. The Signing for approval section provides detailed guidance on generating ECDSA-SHA256 signatures to approve such requests across the Taurus-PROTECT system.

Whitelisting Contracts and Addresses

To interact with external addresses or contracts on the blockchain they must first be Whitelisted within the system. Only after a whitelisting request has been approved can funds be sent to an external address or calls made to a smart contract.

📘

Note

This section requires both authentication and creating signatures!

Creating Transactions

Taurus-PROTECT provides a variety of ways to create transactions safely. The transactions section of this documentation section provides a step-by-step guide to a simple, versatile workflow that covers a wide range of use cases.

📘

Note

This section requires both authentication and creating signatures!