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
  • Snowflake Smart Contract Overview

Was this helpful?

  1. Snowflake

Snowflake Overview

PreviousServer Side RaindropNextSetting Up Snowflake

Last updated 6 years ago

Was this helpful?

Snowflake is currently in a beta phase

Snowflake Smart Contract Overview

The Snowflake smart contract is a compliant Provider under .

Under traditional smart contract infrastructure, dApps interact with users recognized by an Ethereum address. This creates complex user experiences in which a user must create a wallet, generally acquire Ethereum in their wallet and often additional tokens unique to the dApp experience. Snowflake operates as a base class that creates an underlying ecosystem of dApps that enable developers out-of-the-box to:

  • Leverage a broad range of digital identity standards through ERC 1484.

  • Allow users to access their dApps from an Identity associated with multiple addresses, and accordingly multiple devices without insecurely transferring private keys from one device to another.

  • Charge users directly in the HYDRO token for services provided by the dApp.

  • Charge users indirectly through a smart contract for services provided by the dApp.

    -- This transfer can occur through a DEX, enabling dApps to maintain complex token ecosystems and receive payments in any token without their end-users needing to manage multiple tokens in their wallets.

    -- This transfer can occur through arbitrarily sophisticated smart contracts with sophisticated payment structures such as interest rates, late fees, subscription fees, escrows, and other functions important to dApp development.

  • Pay gas costs for user transactions occurring within their dApps through meta-transactions, removing the requirement for their end users to pay gas costs. This significantly simplifies the user onboarding flow, removing the requirement for dApp end-users to hold Eth in their wallets.

ERC 1484