docs.wundaflow.com
  • Overview
  • Roadmap
  • Typical use-cases
  • Glossary
  • Core concepts
    • Workflows
    • Tasks
    • Workers
    • Triggers
    • Signals
    • Webhooks
    • Retry policies
    • Wallets
    • KV Store
  • API
    • API Methods
      • Execute a workflow
      • Pause a workflow
      • Resume a workflow
      • Cancel a workflow
      • Check workflow status
      • Poll for notifications
      • Generate a wallet address
      • Read from KV Store
      • Write to KV Store
    • Authentication
    • Connectors
    • Secrets
    • Errors
  • Token
    • Tokenomics
    • Reward pools
  • Wundaverse
    • Intro
    • Randomness
      • Verifiable Delay Function (VDF)
    • Blobbs NFT
    • WundaGames
      • Wundaflip
  • DISCLAIMER
Powered by GitBook
On this page
  1. Core concepts

Wallets

For use-cases that involve blockchain interaction, either within a single chain or on multi-chain workflows, hot wallets will need to be generated to receive/send transactions.

Each wallet is created with it's own private key, which is stored securely within our secrets vault.

While wallets can be persistent and used repeatedly, we recommend that you adhere to a single-use principal and ensure that no funds are left in the wallet by the end of your workflow runs.

For multi-tenant systems - such as a CEX that needs to receive user deposits - creating a new deposit address for every transaction may not be desirable, however you can still maintain the 'zero funds' method by automatically sweeping remainders to a central custodial address at the end of every workflow.

PreviousRetry policiesNextKV Store

Last updated 1 year ago