Stellar Plus
  • Welcome
  • Quick Start
  • Welcome
  • Quick Start
  • 🎓Tutorials
    • Issuing your first asset
    • Bulk Payments
    • E2E Certificate of Deposit demo
    • Creating a new contract client
  • 📄Reference
    • Account
      • Base
      • Default Account Handler
      • Freighter Account Handler
    • Asset
      • Classic Asset Handler
      • Stellar Asset Contract Handler
      • Soroban Token Handler
    • Network
    • Contract Clients
      • Certificate of Deposit Client
    • Core
      • Contract Engine
      • Pipelines
        • Build Transaction
        • Classic Signing Requirements
        • Fee Bump
        • Sign Transaction
        • Soroban Auth
        • Simulate Transaction
        • Soroban Get Transaction
        • Submit Transaction
        • Soroban Transaction
        • Classic Transaction
    • Utils
      • Plugins
        • Fee Bump Plugin
        • Channel Accounts Plugin
        • Auto Restore Plugin
        • Profiler Plugin
      • Pipeline
        • Conveyor Belt
        • Multi-belt Pipeline
    • RPC
      • Default RPC Handler
      • Validation Cloud RPC Handler
    • Horizon Handler
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Reference
  2. Core
  3. Pipelines

Sign Transaction

PreviousFee BumpNextSoroban Auth

Last updated 11 months ago

Given a transaction or fee bump transaction, this pipeline will verify the list of provided requirements and sign the envelope accordingly. The 'signers' array is used for the signing process, throwing an error in case a signer is missing for a given requirement.

Soroban authorization entries are not handled by this pipeline. A dedicated Soroban authorization pipeline handles this scenario.

Input

type SignTransactionPipelineInput = {
  transaction: Transaction | FeeBumpTransaction
  signatureRequirements: SignatureRequirement[]
  signers: AccountHandler[]
}

  • transaction: The transaction or fee bump transaction object to be signed.

  • signatureRequirements: An array of signature requirements to be applied when signing the transaction. Refer to Classic Signing Requirements for details on how to generate the requirements.

  • signers: Array of AccountHandlers for the necessary accounts to sign the transaction.

Output

type SignTransactionPipelineOutput = Transaction | FeeBumpTransaction

This pipeline directly outputs the signed transaction or fee bump transaction.

📄
  • Input
  • Output