🏢Architecture

A detailed explanation of the architecture of I On You Review dApp

Internal Application Farcaster Interaction:

User to Frontend: The user initiates the process by submitting a query that requires external AI processing via the frontend application.

API Gateway to Smart Contract on Avalanche: QuickNode interacts with the smart contract deployed on the Avalanche network. This is where the business logic resides to handle the requests.

Smart Contract to Chainlink Oracle: The smart contract requests external data processing through a Chainlink oracle that is configured to work with Avalanche, which allows the contract to interact with off-chain data securely.

Chainlink Oracle to External AI API: The Chainlink oracle makes an HTTP call to an external AI service, like ChatGPT, to process the data as needed.

External AI API to Chainlink Oracle: After processing the data, the AI service sends the result back to the Chainlink oracle.

Chainlink Oracle to Smart Contract on Avalanche: The Chainlink oracle updates the smart contract with the processed data.

Smart Contract to API Gateway: The smart contract sends the processed data back through the API Gateway.

API Gateway to Frontend: QuickNode delivers the AI-enhanced information to the frontend.

Frontend to User: The frontend displays the results to the user.

External Application Interaction:

External Application to API Gateway: Shows how an external application can make API calls through QuickNode to interact with your smart contracts on the Avalanche network.

Smart Contract to External Application: The requested data or transaction results are returned to the external application, demonstrating how your dApp can serve as a backend service for other applications.

By getting a clear and concise understanding of the architecture of the dApp, we can more easily investigate potential problem areas. 🧪

Last updated