Hamster is an all-in-one toolkit and middleware service platform for Web3.0 developers. We are committed to helping more developers enter the Web3.0 field, quickly master this rapidly changing technical field, adapt to its high-speed development and ultimately achieve success. In March this year, Chainlink released an important new product Functions that allows everyone to safely and quickly obtain any off-chain API data they want. Although the use of Chainlink Functions is relatively simple, it still requires 6 steps and writing code to implement, which leads to high learning and usage costs for users. We believe there should be a more friendly way to use Chainlink Functions. Therefore, Hamslink came into being. It provides a visualized, 0-code, easy way to use Chainlink Functions.

What it does

  1. Visualized operation The functional modules of Hamlink's visualized interface are clear and appropriately prioritized. Users can not only quickly find the functions they want, such as creating subscriptions and requests, but also view important but less frequently used details, such as subscription request records, recharge records, and added consumer contract records.
  2. Subscription management Subscriptions are the basis for requesting data using Chainlink Functions. In Hamlink, users can quickly create subscriptions and quickly add consumer contracts and recharges to subscriptions. At the same time, users can easily view all these operations at any time.
  3. Create request In Hamlink, the request templates provided by Chainlink community members are integrated. Users can quickly complete request creation through templates. Users can also edit and download integration requests at any time. In addition, users can directly complete request testing in Hanslink to verify the effect. All of these, users only need simple operations on the visualized interface.

How we built it

First, analyze and sort out the process and functions of using Chainlink Functions. Then classify them according to indicators such as frequency of use, importance, and necessity. Finally, rearrange and visualize the functions and usage methods of Chainlink Functions to get the current Hamslink. Project technical stack:golang、vue.js、solidity、javascript、mysql、ethers.js

Challenges we ran into

1.How to think about problems from the perspective of junior developers or web2 developers

2.How to minimize the learning cost for users and improve ease of use as much as possible

Accomplishments that we're proud of

Using Chainlink Functions through the Hamlink tool can greatly reduce learning costs and greatly improve efficiency. This not only brings great convenience to web3 developers, but also greatly lowers the threshold for web2 developers to enter web3.

What we learned

  1. Chainlink Functions promotes the introduction of web2 data into web3, greatly enriching the application scenarios of web3.
  2. There are significant differences between web2 and web3 development. Lowering the threshold for web2 developers to enter web3 will help the prosperity of the web3 ecosystem.

What's next for Hamslink

Pay close attention to and study Chainlink and Chainlink Functions so as to make corresponding adjustments and follow-ups at any time. The specific contents are roughly as follows:

1) Support Avalanche Fuji Testnet network

2) Chainlink Functions request template market

3) Necessity study of visualizing other Chainlink products

Built With

Share this project: