Context switching kills momentum. When an AI assistant drops mid-project, the next session starts cold. No memory of the repository structure. No recall of which ports are live. No awareness that the Monero RPC was acting up yesterday. Daniel Ioni built something blunt and useful: a technical guide written specifically for AI systems so they can resume work on the MyZubster Gateway without hand-holding. It functions as persistent synthetic memory. Instead of dumping raw source code, it teaches the machine how to operate the system, troubleshoot failures, and respect the operator's authority before making destructive changes.

What MyZubster Actually Builds

MyZubster Gateway is a decentralized marketplace built around real-world asset tokenization. In plain terms, it is infrastructure that lets physical or traditional assets move on-chain with defined metadata and ownership rules. The platform handles fungible asset tokenization, meaning assets can be divided, traded, and tracked with standardized metadata attached to each unit.

Privacy sits at the center of the design. Transactions settle in Monero. Programmable assets and NFTs run on Tari. The entire operation shields itself behind a Tor Onion Service, making the gateway resistant to censorship and geographic blocking. A security layer runs on Kali Linux and uses DeepSeek AI security bots, suggesting automated intrusion detection or anomaly scanning rather than simple log rotation. Escrow and dispute resolution are not manual back-office tasks. They are automated, with AI mediating when trade conditions trigger a conflict.

That is the surface. Underneath, the system is a web of RPC endpoints, local databases, and Node.js processes that must stay synchronized or the marketplace stops clearing trades.

The Technical Stack and Why It Matters

The gateway listens on port 3002. That is the front door. Monero's wallet RPC sits at localhost:18083, handling private wallet operations, balance queries, and outgoing transfers without exposing user data to public chain analytics. Tari's RPC responds at localhost:12820, managing the programmable asset layer. If any of these endpoints drift or die, the marketplace grinds to a halt.

MongoDB sits in the background as the operational data store. Node.js powers the gateway service itself. The frontend code lives in a dedicated directory at ~/myzubster-frontend. This is a classic decentralized stack: blockchain nodes for settlement, a local database for state, and a thin web layer for interaction, all wrapped in privacy tooling. Nothing here is decorative. Every port and path was chosen to keep the system self-contained and defensible.

Running the System

Starting the gateway is a single systemd command: systemctl start myzubster-gateway. That sounds trivial until the service fails silently after an unattended reboot. Then you need journalctl -u myzubster-gateway -n 50 --no-pager to pull the last fifty log lines without paging noise. Those fifty lines usually hold the answer. Maybe the Monero RPC refused the connection. Maybe MongoDB never came back online after a system update.

The security bot lives at /root/security_bot.py and launches with python3 /root/security_bot.py. Running a security script as root is not something you do on a general-purpose server. Inside a hardened Kali environment dedicated to monitoring and automated response, it fits the operational model. The DeepSeek AI integration implies the bot is doing more than scanning logs; it is likely evaluating network behavior or transaction patterns for signs of compromise.

For frontend work, the guide removes guesswork entirely. The AI knows the exact landing spot: cd ~/myzubster-frontend. No searching through /var/www, /opt, or scattered home directories. The guide enforces consistency by pinning these paths exactly, which matters when multiple sessions or different AI instances touch the same server over weeks.

When Things Break

When the gateway goes dark, the first move is process reconnaissance. Run ps aux | grep node to see if the Node.js process is still breathing. If it vanished, check the logs. If logs show a database connection error, MongoDB is the culprit. Bring it up with systemctl start mongod. Many decentralized applications treat blockchain nodes as the fragile component, but in practice, the local MongoDB instance is often what flakes first after an unclean shutdown or a routine package update.

Matatizo ya Monero RPC yanafuata mfumo tofauti. Ikiwa salio litaacha kusasishwa au miamala ya malipo itakwama katika hali ya kusubiri (pending), mwongozo unaelekeza kukagua hali ya monero-wallet-rpc. Hiyo kwa kawaida inamaanisha kuhakiki ikiwa mchakato wa wallet RPC unaendelea, kuthibitisha kuwa umeunganishwa (synced) na daemon sahihi, na kuhakikisha kuwa bendera za uthibitishaji (authentication flags) zinaendana na kile ambacho gateway inatarajia. Upangaji wa matatizo (triage) hapa ni rahisi: tabaka la utatuzi wa blockchain (blockchain settlement layer) kwanza, kanzi data (database) pili, na programu (application) tatu. Ikiwa utapuuza mpangilio huo, utatafuta vitu visivyokuwepo kwenye log za Node.js wakati hitilafu halisi ni port ya RPC iliyokufa.

Jinsi AI Inavyopaswa Kutumia Mwongozo Huu

Mwongozo huu unaweka sheria nne za kitabia kwa AI, na sheria hizo zinaonyesha uelewa wa jinsi wasaidizi wa kiotomatiki wanavyofeli katika mazingira ya uzalishaji (production environments).

Kwanza, rejea sehemu mahususi. Ikiwa mtumiaji anatafuta suluhu ya hitilafu ya malipo, AI inapaswa kutaja Monero RPC au mfumo mdogo wa escrow (escrow subsystem) waziwazi ili mtumiaji ajue hasa ni sehemu gani inayovuja. Pili, toa amri sahihi. Usibadilishe maana ya bendera (flags) au kukisia njia (paths). Tatu, pendekeza hatua inayofuata ya kimantiki. Urejesho wa mradi ni mfuatano; kuruka-ruka bila mpangilio kati ya ukaguzi wa port na roboti za usalama hupoteza muda na kuleta hatari ya kufanya tatizo kuwa baya zaidi. Nne, omba uthibitisho wa mtumiaji kabla ya kuanzisha upya huduma au kufuta data. Uhuru wa kufanya maamuzi ni muhimu hadi pale unapotarajiwa kufuta kwa bahati mbaya cache ya wallet au kusimamisha gateway wakati wa biashara zinazoendelea.

Hati Hai

Mwongozo huu umeundwa mahususi ili kukua. Kadiri mradi wa MyZubster unavyokua, AI inasasisha hati hii. Hiyo inatengeneza mzunguko wa mrejesho ambapo uzoefu wa kiutendaji unakuwa kumbukumbu ya taasisi. Katika timu ndogo, au mradi wa mtu mmoja unaofanya kazi katika saa tofauti na mizunguko ya usingizi, hii inachukua nafasi ya maarifa ya mazungumzo ya kawaida ambayo kwa kawaida huwa kichwani mwa wahandisi wakuu. Hati hii inajifunza kutokana na kila hitilafu (outage).

Jambo Muhimu la Kuchukua

Miongozo ya urejesho wa mradi ya AI kama hii inatatua tatizo mahususi na lenye maumivu. Inaziba pengo kati ya hati ghafi na uelewa wa muktadha. Kwa MyZubster, hiyo inamaanisha soko linaweza kuhimili upotevu wa muktadha, kuwashwa upya (reboots), na mabadiliko ya timu. Mashine haihitaji kujifunza upya mfumo (stack) tangu mwanzo kila wakati kipindi kipya kinapoanza. Inahitaji tu kusoma mwongozo, kufuata amri sahihi, na kujua wakati wa kusimama na kuuliza.

Chanzo: AI Technical Guide: MyZubster Project Recovery na Daniel Ioni

Jumuiya ya hiari ya kujifunza: GyaanSetu AI kwenye Telegram