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

Add Providers

To add a Provider, call the addProvidersFor function on the Snowflake smart contract with the approvingAddress, Providers, v,r,s signatures from both Addresses, and the timestamp of the function call.

Triggers event: ProviderAdded

The addProvidersFor function should contain:

ARGUMENTS

Parameter

Type

Description

approvingAddress

address

A current Associated Address of the EIN.

providers

address[]

Array of addresses provided.

r, s, v signature

bytes32, bytes32, uint8

Signed message as required in the format below.

timestamp

uint

Timestamp of the function call to prevent replay attacks.

Signatures should follow the below pattern:

keccak256(
                    abi.encodePacked(
                        "I authorize that these Providers be added to my Identity", ein, providers, timestamp
                    )
                )
PreviousProvider ManagementNextUpgrade Providers

Last updated 6 years ago

Was this helpful?