Space Robots ⚡

//: Exexute --upgrade #SpaceRobot Successful mainnet upgrade of a Space Robot. Process: -- Original Robot burned -- RoboParts burned -- Upgrade Robot minted -- Sent to mint wallet for manual verification

//: Beep mxpy --verbose contract upgrade <ADDR_GABMA> \ --recall-nonce \ --pem <KEY_CENTAURI> \ --gas-limit 50000000 \ --bytecode <WASM_GOLBOT> \ --arguments 0x5352432D**** 0x5352502D**** 0700 <ADDR_GABMA> \ --send \ --Process still running \

//: Dummy 🤖 #SpaceRobots Ugprade Protocol This is a call to action for a limited number of #Robots — up to 5. Join us for the final testing of DummyRobots on Mainnet. Drop a message in our Discord main channel or reply here if you’d like to participate.

//: Dummy 🤖 #SpaceRobots Test Protocol After quite a period from launch on Devnet. Our development team in Mainnet #Upgraded the first few Robots on the dummy collection. Making progress 🦾 Transaction: explorer.multiversx.com/transactions/8…

//: Wallpaper protocol 73 # Status: published //: 🦾Majestic Pose #SpaceRobots

#Spacelog Update #0607 - Update 37 //: Status: Sending Power Waves 🤖Blog.spacerobotsclub.com/spacelog-updat… //: Running Command: #Spacelog //: Backlog status: 2 weeks //: Log date: 2025/06*

//: Wallpaper protocol 63 # Status: published //: The Fight - Dramatic Angle #SpaceRobots

#Spacelog Update #0531 - Update 36 //: Status: Transmitting blog.spacerobotsclub.com/spacelog-updat… //: Running Command: Spacelog //: Backlog status: 1 week //: Log date: 2025/05*

//: Wallpaper protocol 53 # Status: published //: The Close Up Shot #SpaceRobots

#Spacelog Update #0510 - Update 35 //:Status: Transmitting //: Running Command: Spacelog # Backlog status: Not Found //: Log date: 2025/04* blog.spacerobotsclub.com/spacelog-updat…

//: Wallpaper protocol 43 # Status: published //: The Blue Fighter #SpaceRobots

#Spacelog Update #0426 - Update 34 //: Status: Transmitting //: Running Command Spacelog # Processing Backlog: 2 months Due to recent events. We decided to stop paying for the X Premium. You can read the update on our Discord or our blog: blog.spacerobotsclub.com/spacelog-updat…

//: Wallpaper protocol // Status: published //: The 4K #SpaceRobots 🤖Eye

@EGLDNinja //: Alert: 🤖are grinding into the future with synced gears and quantum rhythms!

@SpaceRobotsNFT Robots are grinding 🤖

#Spacelog Update #0205 - Update 33 //: Status: Transmitting //: Running Command Spacelog # Processing Backlog: 0 month //: Log date: 2025/01* Website Development and Optimization: • Progress made on the new website, including work on story content • Published on Netlify a work-in-progress web version • Modified the pop-up functionality for “Read More”; still refining appearance and usability • Backend changes completed Database and Performance Fixes: • Changed query that had issues with spam entries, improving performance, though execution time remains high • Improved Cron Job timeout • Encountered database truncation issues that need resolution • Issues with ranking and other DB-related services persisting after migration, ongoing investigation Server Transition and Backend Issues: • Identified backend API request issues after transitioning to new servers • Backend endpoints occasionally failing with 500 errors and unexpected JSON input • PM2 logs analyzed, processes restarted, but issues remain unresolved • Observed high CPU load, consistently exceeding 300%, requiring further investigation • Determined that stopping the cron job completely causes the main process endpoints to stop working • If issues persist, consider moving to a cloud platform with dedicated physical CPUs like UpCloud Database Debugging Efforts: • Experimented with database indexes but no clear improvement • If issues persist, may need to increase cron job execution intervals Server Migration and Infrastructure Updates: • Moved one of the servers back to UpCloud due to insufficient resources on current setup • Linked new server to json2.spacerobotsclub.com on Netlify • Generated new SSL certificates on the Let’s Encrypt for testing server • New server is operational, with backups successfully restored

@SuperRare_Bears //: 👀 &❤️ protocol live

@SpaceRobotsNFT You guys are so under the radar as well. Such a unique way to communicate as well. We love it and we see you ❤️

#Spacelog Update #0123 - Update 32 //: Status: Transmitting //: Running Command Spacelog # Processing Backlog: -1 month //: Log date: 2024/12* Database and Performance Fixes: • Resolved the database restoration issue, though performance decreased, and efforts are ongoing to optimize it. • Identified the root cause of database issues but are still working on a full resolution. • Encountered issues with refreshing a materialized view after reimporting the database, which is being addressed. Smart Contract Updates: • Updated smart contracts to use the latest MultiversX libraries (0.54.5): • Refactored code to remove deprecated annotations and adjusted method signatures (e.g., switched send().direct() to send().direct_esdt()). • Resolved previous authentication and smart contract-building issues. • Implemented and tested new functions provided by the latest libraries. Virtual Environment Maintenance: • Recovered VirtualBox after GUI issues caused by cleanups. • Continued efforts to stabilize the environment, exploring alternatives like WSL for future-proofing. Goals and Timeline: • Due to family matters and other issues, the deadline was overly optimistic and was not met. The team is now aiming to release core functionalities by the end of the year. • Team vacation is planned between December 16th and January 7th, which could slightly affect timelines. Pending Tasks: • Ongoing testing of updated smart contracts. • Continued database optimization for improved performance. • Preparation for finalizing the release once these issues are resolved.

@EGLDNinja //: 🤖⚡

@SpaceRobotsNFT Happy new year @SpaceRobotsNFT

Welcome to the #2025! 🤖