Hydro
  • Getting Started
  • Raindrop
    • Raindrop Overview
    • Client Side Raindrop
      • Client-Side Raindrop Overview
      • Handling User Signatures
      • Recognizing Users
      • User Account Management
        • Check if Username is Taken
        • Creating HydroIDs
        • Creating HydroIDs (delegated)
        • Deleting Users
      • Verifying signatures
    • Server Side Raindrop
  • Snowflake
    • Snowflake Overview
      • Setting Up Snowflake
      • Naming Conventions
      • Handling User Signatures
    • Address Management
      • Adding Addresses
      • Removing Addresses
    • Provider Management
      • Add Providers
      • Upgrade Providers
    • Resolver Management
      • Adding Resolvers
      • Adding Resolvers (delegated)
      • Removing Resolvers
    • Allowances in Snowflake
      • User Hydro Balances and the Allowance Structure
      • Allowance management logic
      • Setting Initial DApp Allowances
      • Changing DApp Allowances
      • Change DApp Allowances (Delegated)
    • Payments in Snowflake
      • Self-Initiated Payments
      • Resolver-Initiated Payments
        • EIN - EIN Transfer
        • EIN - Address Withdrawal
      • Resolver-Initiated Via Payments
        • EIN - Via - EIN Transfer
        • EIN - Via - Address Withdrawals
      • Resolver-As-Escrow Payments
        • Resolver - EIN Transfer
        • Resolver - Address Withdrawal
      • Resolver-As-Escrow Via Payments
        • Resolver - Via - EIN Transfer
        • Resolver - Via - Address Withdrawal
    • Building a Resolver
      • Smart Contract
      • React Front-End
    • Building a Via Contract
  • Ice
    • Untitled
  • Tide
    • Untitled
Powered by GitBook
On this page

Was this helpful?

  1. Snowflake
  2. Snowflake Overview

Naming Conventions

Naming Conventions

Snowflake function and argument naming conventions are consistent with ERC 1484 naming conventions. Many functions in Snowflake offer the ability for direct calls from end-users as well as meta-transactions that require signatures from end-users to allow service providers to pay gas costs.

Prefixes transfer: denotes an end-destination of a payment as an EIN withdraw: denotes an end-destination of a payment as an address.

Suffixes For: Indicates a change to an EIN's metadata. To: denotes a target recipient of a transfer. Delegated: Indicates a meta transaction and requires a signature from an end-user. (For is implied along with a Delegated suffix). Via: Indicates a HYDRO token transfer through a smart contract which executes arbitrary functions before passing an output to a destination EIN or address.

PreviousSetting Up SnowflakeNextHandling User Signatures

Last updated 6 years ago

Was this helpful?