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. Resolver Management

Adding Resolvers

Add Resolvers

For end users to add a Resolver directly to their EINs through Snowflake, they should call the addResolver function with the following:

ARGUMENTS

Parameter

Type

Description

resolver

address

Ethereum Address of each Resolver to be set in the function call.

isSnowflake

bool[]

Boolean indicating whether the Resolver calls onSignup functions through Snowflake.

withdrawAllowance

uint[]

An array of uints corresponding with user-set allowances for each Resolver being added. See Allowances section for more detail.

extraData

bytes

Arbitrary data to trigger function calls when the Resolver is set for an EIN.

extraData should be used when executing specific functionality on addition of your resolver, such as building a user profile. The following example demonstrates a use of extraData being used in the addResolver function.

PreviousResolver ManagementNextAdding Resolvers (delegated)

Last updated 6 years ago

Was this helpful?