ProxyAI

A decentralized middleware that allows users to securely share, access, and pay for AI services like GPT, using tokenized credits across multiple blockchain network.

Summary

Included in this repository is:

• Solidity Contracts

• Forge local testing

• Testnet Testing Scripts

• Live Frontend Proxy_ai

Testing locally

Clone down the repo, cd into it, then build and run unit tests:

git clone https://github.com/acgodson/proxy.git
cd forge-contracts
npm run build
forge test

Expected output

Deploying to Testnet and Testing

You will need a wallet with at least 0.5 Testnet AVAX and 0.1 Testnet CELO.

• sourceChain: Obtain testnet AVAX here
• targetChain: Obtain testnet CELO here

create and update .env file

PRIVATE_KEY=your_wallet_private_key

npm run main

Expected output

---

ProxyAI Service

Process	Description
Authorization Key Generation	- The user calls the generateKey function on the ProxyAIRouter, initiating a cross-chain request to the Controller on the target chain.
	- The Controller on the target chain stores the idempotency key and relevant metadata, ensuring consistency across networks.
Idempotency Key Retrieval and AI Requests	- The user retrieves the Idempotency Key from the Controller using the original request hash.
	- The retrieved key is added to the authorization header in the prompt sent to the offchain AI endpoint.
Backend Verification, Token Transfer, and Receipt Submission	- After backend verification and processing, a receipt (proof of usage) is submitted via the submitReceipt function on the ProxyAIRouter.
	- Equivalent costs of operation in tokens are transferred to the ControllerVault on the target chain.
	- The ControllerVault receives the tokens and receipt payload, updates its records, and interacts with the Controller to finalize the receipt processing.
Receipt Processing	- The ControllerVault verifies the token transfer and receipt submission, ensuring that the idempotency key is marked as processed.
	- The Controller updates the idempotency data as processed, finalizing the cycle.

Smart Contracts

Smart Contract	Description
Controller Contract	- Manages idempotency key generation and token usage.
	- Only authorized ProxyAIRouter contracts can interact with it.
	- Handles the registration of routers and cross-chain message receipt.
	- Coordinates with the ControllerVault for after-request processing, including token transfers and receipt submissions.
ProxyAIRouter Contract	- Entry point for cross-chain operations on each source chain.
	- Interacts with the Controller to generate idempotency keys for AI authorization requests and submits receipts for AI service usage.
	- Manages gas fees and token transfers on behalf of users.
CustomRouter Contract	- A customizable contract that users can deploy to add their own logic and extends the ProxyAIRouter interface.
	- Allows developers to register as admins, deposit funds into a router's fee tanks, and initiate cross-chain requests for AI services.
ControllerVault Contract	- Acts as the receiving endpoint for receipt payloads and tokens from the router via the Wormhole Token Bridge.
	- Interacts with the Controller to process incoming receipts.