Scribd
Upload
23 views4 pages

Project Schematic

Uploaded by

Soham Mukherjee
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views4 pages

Project Schematic

Uploaded by

Soham Mukherjee
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Project Schematic: CryptoGuard

1. Frontend (User Interface)

o Login & OTP Verification:

 Handles user authentication with email, password, and


CG PInverification.

 Directs users to secure pages based on CG Pin input.

o Transaction Security Analysis:

 Accepts user input for Bitcoin transactions and displays


a risk score.

 Shows a list of common wallets flagged for fraudulent


activity.

o Fraud Assessment & Reporting:

 Allows users to review transaction patterns and detect


potential fraud.

 Enables crowdsourced reporting of suspicious


transactions, contributing to a community-based fraud
prevention system.

o Encryption Services & Expert Consultation:

 Provides secure messaging for users to communicate


with cybersecurity experts.

o AI Chatbot:

 Provides a chat interface for users to ask security-


related questions.

2. Backend (Server & API Integrations)

o User Authentication System:

 Verifies user credentials, CG Pin, and manages secure


access.

o Transaction History & Fraud Detection:

 Processes user-submitted Bitcoin transaction IDs.


 Communicates with Etherscan API to retrieve
transaction history and generate a risk score based on
CryptoGuard’s algorithms.

o Common Wallet Database:

 Maintains a database of wallets commonly flagged for


fraud.

 Updates this list based on crowdsourced reports.

o Security Audit API (Etherscan):

 Uses Etherscan API to fetch security audit data for


Ethereum wallets and displays it on CryptoGuard.

o AI Chatbot API (Cx Genie):

 Handles chatbot interactions for user inquiries.

 Responds based on user queries and provides relevant


security advice.

o Encryption Service:

 Provides a secure channel for communication between


users and security experts.

o Crowdsourced Spam/Fraud Report Storage:

 Stores user reports of fraudulent wallets and


transactions.

3. Database

o User Data:

 Stores user credentials, OTP codes, preferences, and


alert configurations.

o Transaction Data:

 Stores transaction histories, fraud assessment data, and


risk scores.

o Audit & Fraud Detection Data:

 Maintains records of audited wallets, flagged


transactions, and commonly reported fraudulent wallets.

o Crowdsourced Reports:
 Stores user-submitted reports for suspicious wallets and
transactions.

Workflow Summary

1. Login and OTP Verification:

o User logs in using email and password, then enters OTP for
secure access. Verified users proceed to the main dashboard.

2. Transaction Analysis:

o User submits a Bitcoin transaction ID. The backend retrieves


transaction history via the Etherscan API, assesses the risk
score, and checks if the transaction involves any commonly
flagged wallets.

3. Fraud Detection & Reporting:

o Users can view patterns in the transaction history that may


indicate fraud. Users can also report suspicious wallets, which
are stored and updated in the common wallet database.

4. Expert Consultation:

o Users access encryption services and send messages to


cybersecurity experts through a secure channel.

5. AI Chatbot:

o The chatbot provides real-time responses to user queries


using Cx Genie offering security advice based on the
platform’s expertise.

Technologies & Tools Used

 Frontend: HTML, CSS (UI components and interactions)

 Backend: JavaScript(API handling, data processing)

 APIs:

o Etherscan API: For transaction history and security audit.

 Database: (MongoDB) Stores user data, transaction details, fraud


reports, and audit logs.

 Deployment: Netlify (for static frontend hosting), optional backend


deployment on a cloud platform.

You might also like