Skip to main content

Sending Assets to Connected Wallets

Layer4 allows you to send blockchain assets to connected wallets using email addresses instead of complex blockchain addresses. This guide explains how to do this through both the web app and API.

Using the Web App

The process of sending assets is integrated into the token creation flow. When creating a token, you can now specify either:

  • An email address (for connected wallets)
  • A public blockchain address

Steps to Send Assets

  1. Follow the standard token creation process
  2. When you reach the "To Address" field, you can:
    • Enter an email address of a connected wallet
    • Enter a public blockchain address
    • Leave it empty to use the workspace wallet

Using email addresses eliminates the risk of sending assets to incorrect blockchain addresses!

Verifying Connected Users

Before sending assets to an email:

  1. Ensure the recipient has an active wallet connection
  2. Check the connection status in the Wallet Management page
  3. If needed, send a connection request first

Using the Public API

You can programmatically send assets using the Layer4 API. The API accepts both email addresses and blockchain addresses as recipients.

API Endpoint

POST/api/v1/buckets/{bucketId}/tokens

Authentication

  • Requires an API key with appropriate permissions
  • Include the API key in request headers

Request Format

The token creation payload accepts either an email address or a public blockchain address in the toAddress field.

For detailed API examples and request/response formats, please refer to our API documentation.

Best Practices

  • Verify wallet connections before sending assets
  • Double-check email addresses before sending
  • Use descriptive token names and metadata
  • Keep records of asset distributions
  • Test with small amounts first when using new connections