If you manage multiple Splinterlands accounts and feel like half your day disappears into “the usual rituals” — claims, staking, swaps, token flow, land operations — you’re not alone. Splinterlands shouldn’t feel like a second job if you're running it at a slightly bigger scale. I’ve been building a tool to compress all of that into a single, reliable automation control room.

It’s called ShardWorks.

This isn’t a public launch. This is just information for what I'm currently doing:
a clean, security‑first automation layer for Hive + Splinterlands that does the boring work consistently, so you can focus on other aspects of the game.

Why some operations require an Active Key - and why you can also use ShardWorks without

Many operations in Splinterlands can be handled just with the Posting Key, which is really cool! However, I also have certain flows which require Active Key privileges. So ShardWorks also does automation of transaction that require an active key. Otherwise, automation would not be possible to the degree it's built-in currently.

Of course, it is not mandatory to store the Active Key. It just limits the possible operations for respective accounts.

Architecture-wise, keys are never stored in plaintext and also not directly within the application itself. All keys are encrypted using an external Vault + envelope encryption:

• A per‑record data key encrypts the Hive key
• Data keys are protected by Vault transit keys
• Decryption happens only in memory
• Keys are never shown again after input
• Once saved, keys are never returned to the UI or logs.

What ShardWorks does

Claims & Rewards

• Claim rewards for selected accounts
• Claim staking rewards
• Frontier claims

Token Flow

• Collect SPS from farming accounts → bank
• Stake SPS in the bank
• Swap SPS → DEC
• Distribute DEC to accounts based on configuration

Season Pass Automation

• Auto‑purchase season passes
• Auto‑fund DEC when needed
• Flexible thresholds per account

Land Automation

• Harvest land for all regions
• Add liquidity for resources (STONE/WOOD/GRAIN/IRON)
• Region‑level controls & resource targeting
• Optional auto‑buy grain

Voucher Liquidity

• Add VOUCHER / DEC liquidity
• Auto‑scaling parameters + precision control

Scheduling

• Each operation can run on a schedule
• Cron‑based under the hood
• Human‑friendly setup in the UI
• Runs in your local timezone, executed in UTC

More pictures

What do you think about this? How do you manage your Splinterlands accounts and workflows?