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

Removing Resolvers

Remove Resolvers

For end users to remove a Resolver directly from their EINs, they should call the removeResolver function on the Snowflake smart contract with the approving address, the resolver address, a bool indicating whether or not the Resolver uses Snowflake-specific functionality, and a bytes parameter with any extra data as needed, such as a function call to be executed on signup. Allowances open payments gateways between an EIN and a smart contract.

ARGUMENTS

Parameter

Type

Description

resolver

address

Ethereum Address of the Resolver to be removed in the function call.

isSnowflake

bool

Boolean indicating whether the Resolver uses

extraData

bytes

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

See below for an example of using extraData to execute functionality on removal of a Resolver.

PreviousAdding Resolvers (delegated)NextAllowances in Snowflake

Last updated 6 years ago

Was this helpful?