:droplet::snowflake: Front-end Hydro Snowflake Dashboard for the Coupon Marketplace described in the the following bounty: https://github.com/HydroBlockchain/hcdp/issues/255. Currently a work-in-progress!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Luiserebii 3c8fa7847d
Cleaning project up
1 year ago
docs Added ID of item to set of itemListings retrieved 1 year ago
public Initial commit 2 years ago
src Cleaning project up 1 year ago
.gitignore Finally, a working example! 2 years ago
README.md Initial commit 2 years ago
buildResolverList.js Initial commit 2 years ago
package-lock.json Modifiying CouponMarketplace component 1 year ago
package.json Modified package.json 2 years ago


Snowflake Dashboard

Build Status

This is a demo frontend for the Snowflake identity protocol written in React. It utilizes the web3-react library. For more information on Snowflake, please refer to the white paper.

Visit the live dashboard.

Adding Your Resolver To the Dashboard

  1. Create a smart contract on Rinkeby that appropriately inherits from the canonical SnowflakeResolver contract. For examples, see here. In order to be accepted to the dashboard, your smart contract source code must be verified on Etherscan.
  2. Note the checksummed address of your smart contract and make a folder with this name in src/components/resolvers/Rinkeby.
  3. Create an index.js file in the folder.
  4. This file should export the following exports:
    • default: A React Component wrapped in React.lazy. This component will receive a user’s EIN in the props as ein.
      • export default lazy(() => import('./ResolverComponent')).
    • extraDataComponent: An optional React Component wrapped in React.lazy. This component will receive a user’s EIN in the props as ein and a function sendExtraData. This function should be called with the bytes argument to be passed to your resolver on sign-up.
      • export default lazy(() => import('./ExtraDataComponent')).
    • ABI: The ABI of your contract.
    • logo: A 256x256 png logo for your resolver.
    • requiredAllowance: An optional HYDRO amount a user must set as their initial allowance for your resolver on sign-up.