This is the monorepo for the Teesa aApp, an autonomous agent built with the aApp Toolkit.

Teesa plays a word guessing game with users and rewards the winners with unique NFTs that it autonomously generates and issues. The core of Teesa operates within a Trusted Execution Environment (TEE), a security feature enabled by the aApp Toolkit. This TEE setup provides several key benefits:

• Confidentiality: It guarantees that the secret word chosen for the game remains confidential and cannot be leaked, even to the infrastructure administrators.
• Autonomous Wallet: Teesa manages its own blockchain wallet, created autonomously within the TEE. No one, including the development team, has access to the private keys, ensuring secure control over the NFT rewards.
• Enhanced Security: To further prevent potential leaks, Teesa utilizes a local LLM instance running directly inside the TEE when it infers a prompt that includes the secret word.
• User-Friendly Attestation: The aApp Toolkit out of the box provides a user-friendly interface to verify the TEE's cryptographic attestation, and the end user can ensure that the agent is genuinely running secure code inside a TEE.
• Seamless Upgradability: The toolkit facilitates secure upgrades. When a new version of Teesa is deployed, TEE attestation between the old and new instances ensures the secure transfer of sensitive state, like the agent's private keys.

The project is organized into two packages:

• packages/agent - The main package for the Teesa agent. Contain the main agent code.
• packages/nft - The package for the Teesa NFT. Contains the NFT contract and methods for interacting with it.
• packages/twitter-client - The package for the Teesa Twitter client.
• packages/web-app - The package for the Teesa web app. Contains the NextJS app.

To start the app in development mode follow these steps.

Follow the instructions in the Development Environment Setup guide to setup your development environment.

The .env file is used to configure the environment variables for the project. We have separated the file into two parts - one for each of the two packages:

cp .env.example .env

• OLLAMA_MODEL - the Ollama model to use (defaults to "qwen2.5:7b-instruct-q4_K_M")
• OpenRouter Configuration:
  • OPENROUTER_API_KEY - your API key for accessing the OpenRouter API
  • OPENROUTER_MODEL - the OpenRouter model to use (defaults to "x-ai/grok-3-beta")
• Langsmith Configuration (used only in development) - you can get the values from the Langsmith dashboard (https://smith.langchain.com/):
  • LANGCHAIN_TRACING_V2 - defaults to false
  • LANGCHAIN_ENDPOINT
  • LANGCHAIN_API_KEY
  • LANGCHAIN_PROJECT

• ENV_MODE- set to either dev for development or prod for production (defaults to prod)
• PrivyIO Configuration - you can get the values from the PrivyIO dashboard (https://dashboard.privy.io/):
  • NEXT_PUBLIC_PRIVYIO_APP_ID: Your PrivyIO app ID
  • PRIVYIO_APP_SECRET: Your PrivyIO app secret
• NEXT_PUBLIC_ATTESTATION_URL - URL for serving attestation verification by aApp Toolkit

• Twitter credentials:
  • TWITTER_USERNAME - the username of the Twitter account to use
  • TWITTER_PASSWORD - the password of the Twitter account to use
  • TWITTER_EMAIL - the email of the Twitter account to use
  • TWITTER_2FA_SECRET - the 2FA secret of the Twitter account to use
• Intervals:
  • TWITTER_INTERACTION_MONITORING_INTERVAL_SECONDS - the interval in seconds to monitor the Twitter interactions
  • TWITTER_POSTING_INTERVAL_MIN_MINUTES - the minimum interval in minutes to post to Twitter
  • TWITTER_POSTING_INTERVAL_MAX_MINUTES - the maximum interval in minutes to post to Twitter

• WALLET_PRIVATE_KEY - the private key of the wallet you will use to deploy the NFT contract
• CONTRACT_NETWORK - the blockchain network for the contract - mainnet, sepolia, base or baseSepolia
• RPC URLs for the networks:
  • RPC_URL_MAINNET - RPC URL for Ethereum Mainnet (we are using Alchemy, but you can use any other RPC provider)
  • RPC_URL_SEPOLIA - RPC URL for Ethereum Sepolia (we are using Alchemy, but you can use any other RPC provider)
  • RPC_URL_BASE - RPC URL for Base (we are using Alchemy, but you can use any other RPC provider)
  • RPC_URL_BASE_SEPOLIA - RPC URL for Base Sepolia (we are using Alchemy, but you can use any other RPC provider)
• Etherscan and Basescan API keys:
  • ETHERSCAN_API_KEY - Etherscan API key
  • BASESCAN_API_KEY - Basescan API key
• TEAM_ADDRESS - the address of the team wallet. We set it as the receiver for the NFT royalties.
• Pinata Configuration - you can get the values from the Pinata dashboard (http://pinata.cloud):
  • PINATA_API_KEY - your API key for accessing the Pinata API
  • PINATA_API_SECRET - your API secret for accessing the Pinata API
• FALAI_API_KEY - your API key for the Fal.AI API
• NFT_CONTRACT_ADDRESS - the address of the NFT contract. We set it automatically when deploying the contract

1. Install dependencies

   pnpm install

2. Build the project

   pnpm build

Refer to the Agent README for details on how to build the agent.

To use the app you need to deploy the NFT contract. Refer to the NFT README for more details.

Refer to the Web app README for details on how to start the web app.

Refer to the Twitter client README for details on how to start the Twitter client.

To deploy the app to production follow the steps described in the Deployment README.

This project is licensed under the MIT License. Feel free to use, modify, and distribute this project as per the license terms.