A lot has changed since I first introduced ShardWorks, my non-battle Splinterlands automation tool.
If you missed the original post, here it is:
@sc000/shardworks-my-non-battle-splinterlands-automation
Since then, the project has made a big jump in three areas:
- usability
- stability
- security
What changed for users
The biggest practical improvements are:
- a much cleaner and more polished web UI
- easier account and automation management
- better scheduling with human-readable timing
- clearer visual feedback when actions succeed or fail
- better statistics for SPS, DEC, swaps, staking, and liquidity activity
In short: ShardWorks is no longer just “a script with config”.
It is evolving into a proper automation platform.
What changed for security
Security has been one of the biggest focus areas since February 3.
Important improvements include:
- stronger authentication and session handling
- login allowlist support
- dedicated logging for login attempts
- stricter request limits and rate limiting
- improved tenant isolation
- safer key handling
- stronger production deployment with Nginx + Vault
- better fail-safe behavior when APIs or services are unavailable
That matters because ShardWorks can automate actions that affect real value.
So security is not an optional add-on. It has to be built into the core.
Why this matters
Compared to the February 3 version, ShardWorks is now:
- easier to use
- more robust
- safer to run
There is still more work ahead, but the foundation is now much stronger.
Closed Beta
I am not opening this widely yet.
If you are interested in becoming a closed beta tester, reach out to me directly.
Support My Validator
If you want to support my work, I would also appreciate a vote for my SPS validator:
Validator: sc000
Vote here:
https://peakmonsters.com/validators
Final Note
ShardWorks is being built for serious Splinterlands account automation outside of battles:
cleaner workflows, stronger safety, and more control.
If that sounds useful to you, now is a good time to start following the project.