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. Utils
  3. Plugins

Fee Bump Plugin

PreviousPluginsNextChannel Accounts Plugin

Last updated 1 year ago

Was this helpful?

The Fee Bump plugin can be used to wrap any given transaction into a Fee Bump transaction before moving forward to submit the transaction for processing.

  • Pipeline Type: Submit Transaction

  • Supported Pipelines:

    • Submit Transaction

    • Soroban Transaction - Targets its inner pipeline.

    • Classic Transaction- Targets its inner pipeline.

preProcess

During the preProcess step of Submit Transaction pipelines, the Fee Bump plugin takes the original transaction and executes internal pipelines for it using the original header provided when instantiating the plugin according to the following steps.

  1. Wrap transaction into Fee Bump

  2. Calculate the signing requirements

  3. Sign the fee bump transaction

  4. Substitute the transaction object with the fee bump transaction object

Once the transaction is successfully wrapped into a fee bump and signed, the preProcess step proceeds with the Fee Bump transaction instead of the original transaction.

📄