Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D DLT Middleware
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • FAITH
  • DLT Middleware
  • Issues
  • #1

Closed
Open
Created Apr 29, 2022 by João Gião@jgsOwner

Wait or not wait for transaction receipt, that is the question

When a transaction is submitted into the blockchain, the async response is not taken into account here and here. Several scenarios can occur:

  1. Fast response if occurs an error
  2. Slow response if the transaction is pending and a block is not mined.

Moreover, it is necessary to verify if this function can block/memory leak in any situation. This concern is due to when a pending transaction is officially submitted into the blockchain, a log appears in the console.

Edited Apr 29, 2022 by João Gião
Assignee
Assign to
Time tracking