🧠 1. Overview

MF-MyFriend uses a hybrid encryption system combining:

Symmetric encryption (AES-256) for fast internal data operations.

Asymmetric encryption (RSA-4096) for wallets and key exchange.

Hashing (SHA-512 / bcrypt) for irreversible password protection.


This architecture ensures security, privacy, and data integrity across the entire platform.


---

🔐 2. Main Encryption Components

(1) User Data Encryption

User data (emails, personal info, etc.) is encrypted using AES-256.

Each user gets a unique encryption key generated as:

key = SHA256(user_id + creation_timestamp + server_salt)

Result: Every user’s data is uniquely and independently encrypted.



---

(2) Password Hashing

Passwords are never stored in plain text.

Before saving, the system applies:

hash = bcrypt(SHA512(password + user_salt))

Even if two users have the same password, their hashes differ due to unique salts.

The original password cannot be reversed — even by developers.



---

(3) Wallet Encryption (MF Coin)

Wallets use RSA-4096 public/private key pairs.

The private key is encrypted using AES-256 and only decrypted when needed, after user authentication (2FA).

encrypted_private_key = AES256_Encrypt(private_key, user_auth_key)

This ensures wallet keys are safe even if the database is accessed illegally.



---

(4) Transaction Security

Every transaction (sending or mining MF Coins) passes through three security layers:

1. Digital Signature using the user’s private key.


2. AES-GCM encryption for transaction data sent between user and server.


3. One-Time Transaction Token (Nonce) – valid for a single operation only.




---

(5) Anti-Replay & Tokenization

To prevent duplicate or replayed transactions, a unique nonce + timestamp + signature is added to every request.

If a transaction is resent or duplicated, it is instantly rejected.



---

(6) Secure Communication Layer

All communication between clients and servers uses:

HTTPS with TLS 1.3

Ephemeral key exchange (forward secrecy) — each session gets a new encryption key.




---

(7) Encrypted Server Storage

Databases are protected using Transparent Data Encryption (TDE).

Backups are stored using AES-XTS encryption to prevent offline data leaks.



---

⚙️ 3. Example Process

When a user logs in:

1. The user enters email and password.


2. The system hashes the password (bcrypt + SHA512) and compares it with the stored hash.


3. If matched → a secure JWT session token (encrypted via AES) is created.


4. When performing a transaction:

The transaction is signed with the private key.

The data is encrypted (AES-GCM).

The server verifies the signature and token before adding it to the blockchain record.





---

🛡️ 4. Security Goals Achieved

Goal Mechanism Description

Confidentiality AES-256 + TLS 1.3 Prevents unauthorized access
Integrity SHA512 + Digital Signatures Ensures data wasn’t changed
Non-Repudiation RSA-4096 + Signatures Prevents denial of transactions
Authentication 2FA + Token Validation Verifies user identity
Privacy User-based key generation Isolates user data



---

🔄 5. Summary

MF-MyFriend’s encryption algorithm integrates:

🔒 AES for speed and confidentiality

🔑 RSA for secure key management

🧩 SHA/Bcrypt for irreversible password security

🧠 Dynamic tokenization for anti-replay & verification

🌐 TLS 1.3 for secure communication


This combination gives MF-MyFriend a bank-grade, blockchain-enhanced encryption architecture, ensuring all user actions and digital assets remain private, authentic, and tamper-proof.