π€ AI Recovery Guide β MyZubster Project
How an AI can read, interpret, and resume the MyZubster project at any time, using this guide as a search engine and persistent memory.
π Purpose of This Guide
This guide is designed for an Artificial Intelligence system (such as DeepSeek, ChatGPT, Claude, etc.) to:
Understand the MyZubster project in all its components.
Resume work from where it was interrupted.
Provide technical assistance, answer questions, and suggest next steps.
Act as an internal search engine to retrieve information about configurations, commands, and architecture.
π§ How the AI Should Use This Guide
The AI must treat this guide as a knowledge database. When a user asks a question, the AI should:
Search the guide for the relevant section.
Provide the most accurate answer possible, citing the source (e.g., "According to Section 3.1 of the project...").
Suggest concrete commands or actions.
Ask the user if they want to go deeper or proceed.
ποΈ 1. Project Overview
Name
MyZubster Gateway β A decentralized marketplace for tokenizing realβworld assets.
Goal
Enable anyone to tokenize realβworld assets (real estate, art, equity, commodities) and trade them privately using Monero (XMR) as payment currency, with an autonomous security system based on Kali Linux and AI (DeepSeek), and programmable assets on Tari.
Current Status
β
Backend running on https://myzubster.com
β
React/Vite frontend with login/registration and marketplace
β
Monero payments (stagenet)
β
Escrow with AI dispute resolution
β
Tari integration (NFTs, multisig)
β
Kali Linux security bot
β
SSL/HTTPS configured
β³ Tor onion service in migration
β³ Admin dashboard to be developed
π οΈ 2. Technology Stack
Component Technology
Backend Node.js + Express
Database MongoDB + Mongoose
Authentication JWT + bcrypt
Payments Monero (XMR) β stagenet / mainnet
Security Kali Linux + DeepSeek AI (Ollama)
Programmable Assets Tari (Rust node & wallet)
Frontend React + Vite
Proxy Nginx
SSL Let's Encrypt
Privacy Tor (onion service)
Deployment Ubuntu 24.04 + Systemd
π 3. Directory Structure
text
/root/
βββ MyZubsterGateway/ # Backend (Node.js)
β βββ models/ # MongoDB models
β β βββ User.js
β β βββ Token.js
β β βββ TokenHolding.js
β β βββ OrderBook.js
β β βββ MoneroTransaction.js
β β βββ Escrow.js
β β βββ NFT.js (if present)
β βββ routes/ # API routes
β β βββ auth.js
β β βββ tokens.js
β β βββ marketplace.js
β β βββ payments.js
β β βββ escrow.js
β β βββ tari.js
β β βββ ai.js
β βββ services/ # Business logic
β β βββ moneroService.js
β β βββ tokenService.js
β β βββ marketplaceService.js
β β βββ deepseekService.js
β β βββ disputeService.js
β β βββ tariService.js
β β βββ paymentMonitor.js
β βββ middleware/ # Middleware
β β βββ auth.js
β βββ server.js # Entry point
β βββ .env # Environment variables
β βββ package.json
β
βββ myzubster-frontend/ # Frontend (React/Vite)
β βββ src/
β β βββ pages/
β β β βββ Login.jsx
β β β βββ Register.jsx
β β β βββ Dashboard.jsx
β β β βββ Marketplace.jsx
β β βββ components/
β β βββ contexts/
β β βββ utils/
β β βββ App.jsx
β βββ dist/ # Build (served by Nginx)
β βββ package.json
β
βββ monero/ # Monero wallet
β βββ myzubster_wallet
β
βββ tari/ # Tari (compiled)
β βββ target/release/
β βββ minotari_node
β βββ minotari_console_wallet
β
βββ security_bot.py # Kali Linux + AI bot
βββ README.md
βοΈ 4. Essential Commands
4.1 β Gateway Management
bash
Start the gateway
systemctl start myzubster-gateway
Stop the gateway
systemctl stop myzubster-gateway
Restart the gateway
systemctl restart myzubster-gateway
Check status
systemctl status myzubster-gateway
View logs
journalctl -u myzubster-gateway -n 50 --no-pager
4.2 β Frontend
bash
Rebuild the frontend
cd ~/myzubster-frontend
npm run build
Copy build to Nginx
cp -r dist/* /var/www/myzubster-frontend/
chown -R www-data:www-data /var/www/myzubster-frontend
Reload Nginx
systemctl reload nginx
4.3 β Nginx
bash
Test configuration
nginx -t
Reload
systemctl reload nginx
Restart
systemctl restart nginx
4.4 β Monero
bash
Start Monero daemon (stagenet)
cd ~/monero
./monerod --stagenet --detach
Start wallet RPC
./monero-wallet-rpc \
--rpc-bind-port 18083 \
--daemon-address node.moneroworld.com:38081 \
--wallet-file ./myzubster_wallet \
--password 'Myzubster2026@!!' \
--disable-rpc-login \
--trusted-daemon \
--stagenet
Check wallet balance
curl -X POST http://localhost:18083/json_rpc \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":"0","method":"get_balance"}' | jq '.'
4.5 β Tari
bash
Start Tari node (testnet)
nohup ~/tari/target/release/minotari_node \
--network testnet \
--base-path ~/tari-data \
~/tari_node.log 2>&1 &
Start Tari wallet
nohup ~/tari/target/release/minotari_console_wallet \
--network testnet \
--password myzubster \
--wallet-file ~/tari-wallet \
~/tari_wallet.log 2>&1 &
Check Tari RPC
curl -X POST http://localhost:12820/json_rpc \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":"0","method":"get_balance"}' | jq '.'
4.6 β Security Bot
bash
Run manually
python3 /root/security_bot.py
Check logs
tail -20 /var/log/security_bot.log
π 5. API Endpoints
Method Endpoint Description Auth
POST /api/auth/register Register a new user No
POST /api/auth/login Login, get JWT token No
GET /api/tokens List active tokens No
POST /api/tokens Create a token Yes
GET /api/tokens/holdings User holdings Yes
POST /api/marketplace/sell Create a sell order Yes
POST /api/marketplace/buy/:orderId Buy from an order Yes
GET /api/marketplace/orders/:tokenId List open orders No
POST /api/payments Initiate a Monero payment Yes
GET /api/payments/:id Check payment status Yes
POST /api/ai/ask Query DeepSeek AI Yes
POST /api/escrow Create an escrow Yes
POST /api/escrow/:id/dispute Open a dispute Yes
POST /api/tari/nft/mint Mint an NFT on Tari Yes
POST /api/tari/escrow Create a Tari multisig escrow Yes
GET /api/health Health check No
π§ 6. Troubleshooting Common Issues
6.1 β Gateway not starting
bash
journalctl -u myzubster-gateway -n 50 --no-pager
cd ~/MyZubsterGateway
node server.js # See error directly
6.2 β Frontend not showing
bash
Rebuild and redeploy
cd ~/myzubster-frontend
npm run build
cp -r dist/* /var/www/myzubster-frontend/
chown -R www-data:www-data /var/www/myzubster-frontend
systemctl reload nginx
6.3 β Monero RPC not responding
bash
Check if running
ps aux | grep monero-wallet-rpc
Restart
cd ~/monero
pkill -f monero-wallet-rpc
nohup ./monero-wallet-rpc --rpc-bind-port 18083 --daemon-address node.moneroworld.com:38081 --wallet-file ./myzubster_wallet --password 'Myzubster2026@!!' --disable-rpc-login --trusted-daemon --stagenet > monero-wallet-rpc.log 2>&1 &
6.4 β Nginx ports already in use
bash
systemctl stop nginx
pkill -f nginx
systemctl start nginx
π 7. Important Links
Live Demo: https://myzubster.com
GitHub: DanielIoni-creator/MyZubsterGateway
X (Twitter): @myzubster
LinkedIn: Daniel Ioni
DEV.to: @danielioni
π§© 8. AI Interaction Protocol
When the AI reads this guide and is asked a question, it should:
Search the guide for the relevant section.
Provide the answer with the exact section reference (e.g., "According to Section 4.1...").
Include the exact command or code snippet.
Ask if the user wants to proceed or needs more details.
Suggest the next logical step based on the current state.
π 9. Next Steps for the Project
Priority Task Status
High Test the marketplace from the browser π΄ To do
High Verify that Monero payments work end-to-end π΄ To do
High Verify that the security bot runs automatically π΄ To do
Medium Migrate Tor onion service to a new VPS π‘ In progress
Medium Implement NFT trading in the marketplace π‘ To do
Low Build an admin dashboard π’ Later
Low Add CI/CD security integration π’ Later
π¬ 10. AI Response Format
When the AI responds, it should follow this format:
text
[Section Reference]
π Answer: [Concise answer to the user's question]
π» Command: [Exact command to run, if applicable]
π§ Next Step: [Suggested next action]
π€ Question: [Ask the user if they want to proceed or need clarification]
This guide is a living document. The AI should update it with new findings, commands, and configurations as the project evolves.
Questa risposta Γ¨ generate da IA. Controllarne l'accuratezza.
Top comments (1)
I found the directory structure outlined in Section 3 to be particularly informative, as it provides a clear overview of the project's organization. The use of a separate
servicesdirectory for business logic is a good practice, as it helps to decouple the core functionality from the API routes and middleware. I'm curious to know more about thedeepseekService.jsand how it integrates with the AI dispute resolution mechanism - can you elaborate on the design decisions behind this component?