Our smart contract is live on polygon mumbai testnet
Flex node allows users to write graphql query commands or our template command to query on-chain activities such as borrows events in compounds on Polygon mainnet or nft holding in opensea on Ethereum mainnet and store those file as json file into ipfs via web3.storage.
When smart contract want to calculate those file, we also provide chainink external adapter to get those file and compute on chainlink node and send result back into smart contract.
We implement 2 layers, storage layer and execution layer.
- Storage layer, We use IPFS to store query commands data and on-chain data.
- Execution layer, Our stack separates into 3 parts, Chainlink node, Chainlink external adapter, flex-contract and flex-frontend.
-
Chainlink node
We create our own spec and job to parse data from our external adapter on polygon mumbai testnet.
-
Chainlink external adapter
We have 2 external adapters that do different tasks.
Get on-chain data using graphql command and return cid from ipfs. Get specific data that is stored on cid.
-
Flex contracts
Sample contract that gets on-chain data and how to build requests from our flex-node.
- The query creator has incentive from everyone using their query command.
- Dynamic query variable.
- Support Non-evm chain.
- Support more third party on-chain query data.