Inspiration/Statement
API Problems of real world data transferring. Inspired from chainlink functions and graph protocol.
What it does?
# CrackedDev's job API now taps into decentralized nodes, ensuring reliable and efficient data retrieval for seamless job searching.
How I built it?
- first step is setup of graphql into locally
- create foundry project for smart contract for storing api data
- create subgraph to interact with UI with api data.
- graphql is more helpful in terms of getting data from onchain instead of calling smart contract functions.
- index with graph and contract event
- create next.js application to interact with jobs.
Challenges I ran into
- local set-up is always unhealthy
- graphql errors with connecting of smart contract
- next.js running errors
- smart contract compilation errors like "stack out of memory" in event handling
What I learned
- I am not so aware with graphql before this hackathone. Now, I can build API with using contract and graphql. Other stuff is Next.js. more familiar with components. upgrade my smart contract creating skills.
Feature Of this Decentralize API
- smart contract is immutable so, there is privacy thing with this API
- anyTime we update smart contract it can directly fetch data from graphql (add some code into graph folder.)
- indexing with smart Contract to subgraph to UI UI <-- Subgraph <-- Smart contract
Built With
- blockchain
- css
- ether
- foundry
- graphql
- html5
- javascript
- json
- next.js
- react
- solidity
- subgraph
- thirdweb
- web3
Log in or sign up for Devpost to join the conversation.