What Is the Contracts Directory in AiToEarn? Repository Structure Analysis

The AiToEarn repository does not contain a contracts directory in its current main branch.

AiToEarn is built as a modern full-stack application using Next.js for the front-end, NestJS for the back-end, and Electron for desktop packaging. Despite expectations that blockchain smart contracts might reside in a dedicated folder, a comprehensive review of the codebase reveals no such directory exists, nor are there any Solidity (.sol) files present.

Repository Structure Overview

The project follows a monorepo pattern managed by Nx, organizing code into distinct applications and libraries. The primary directories include:

• project/aitoearn-web/ — Next.js front-end application
• project/aitoearn-electron/ — Electron wrapper for desktop deployment
• project/aitoearn-server/ — NestJS back-end API (implied by standard Nx structure)

Within these directories, you will find typical TypeScript/React source files, configuration files, and asset folders, but no contracts subdirectory appears anywhere in the tree.

Where "Contract" References Appear in the Codebase

While the physical contracts directory is absent, the term "contract" appears exactly twice in the source code, both instances occurring within user-facing legal pages in the front-end:

Terms of Service Page

The file project/aitoearn-web/src/app/[lng]/websit/terms-of-service/page.tsx contains UI text referring to a "binding contract between you and Aitoearn." This is strictly legal language presented to the user, not a reference to code files.

Data Protection Agreement

Similarly, project/aitoearn-web/src/app/[lng]/websit/data-protection-agreement/DataProtectionContent.tsx mentions "contractual obligations" and "contractual agreements." These strings are part of the privacy policy interface and do not indicate the presence of smart contract code.

Why Developers Might Expect a Contracts Directory

Many Web3 or blockchain-integrated applications store Solidity smart contracts in a root-level contracts/ folder. If you are searching for blockchain integration code in AiToEarn, consider the following:

• No Solidity compilation pipelines are configured in the build files
• No Web3 provider initialization appears in the server or web app entry points
• No ABI (Application Binary Interface) files are imported or referenced in the TypeScript source

The current architecture suggests AiToEarn operates as a traditional Web2 application without on-chain components.

Verifying Directory Absence

To confirm the directory does not exist locally, you can run a recursive search from the repository root:

find . -type d -name "contracts" 2>/dev/null

This command returns no results. Similarly, searching for Solidity files yields nothing:

find . -name "*.sol" 2>/dev/null

Summary

• No contracts directory exists in the AiToEarn main branch
• The repository uses Next.js, NestJS, and Electron, not blockchain infrastructure
• The only mentions of "contract" appear in legal UI text at terms-of-service/page.tsx and DataProtectionContent.tsx
• No Solidity files (.sol) are present in the codebase
• Blockchain functionality has not been added to the current repository state

Frequently Asked Questions

Is AiToEarn a blockchain or Web3 application?

Based on the source code analysis, AiToEarn is not currently a blockchain application. The repository contains no smart contracts, Web3 libraries, or blockchain node configurations. It is built as a standard full-stack web application using Next.js and NestJS.

Where are the smart contracts for AiToEarn stored?

There are no smart contracts stored in the AiToEarn repository. If the project plans to integrate blockchain features in the future, those contracts would likely be added to a contracts/ directory at the root or within a dedicated blockchain package, but such code is not present in the current main branch.

Why do I see the word "contract" in the codebase if there is no contracts directory?

The word "contract" appears only in user-facing legal documents. Specifically, the terms-of-service page and data-protection agreement component use contract terminology to describe legal agreements between the user and the platform, not software or blockchain contracts.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}