From War Log to tools — why I’m turning crypto articles into small browser panels
Most of us in crypto have the same pattern:
We read a lot, save threads, subscribe to newsletters…
But our behaviour? It doesn’t really move.
With CryptoSlug I decided to treat this as a design problem.
Instead of publishing only “nice theory” in the War Log (my long-form blog), every important concept should eventually become a small tool that lives in your browser.
The first one in this line is SlugSentinel V1, a panel that helps early-stage Hodlers build and keep a basic security routine.
Why “just reading” didn’t cut it for me 📚
I love long-form content. But after a while I realised:
Saving articles and threads wasn’t what changed my decisions.
Repeating simple habits with a minimal structure did.
In the War Log I write about:
- security for accounts and devices
- risk management for Hodlers
- exchange vs wallet
- security routines and 24h plans
People read, nod, agree… and then real life happens.
The missing piece was a bridge between “I get it” and “I actually do this every week”.
The model: Article → Concept → Tool 🛠️
Here’s how I’m trying to solve it:
Article — start from a real problem (“I keep postponing security”, “I don’t know my monthly investment”, “I have no idea what my total exposure is”).
Concept — use the article to explain context, show traps and end with something like “OK, do it like this”.
Tool — once the structure proves useful in practice, turn it into a small HTML/JS panel in the browser:
- no login
- no cloud
- localStorage only
- designed to make the routine repeatable, not perfect
That way the War Log is not just “content”, it’s the design document for tools.
Example: Security Routine → SlugSentinel V1 🛡️
Security was the first big topic.
Before talking about bots or PnL, I wanted a foundation:
- initial security setup (email, 2FA, passwords, devices, APIs)
- a short weekly / bi-weekly routine
- a deeper monthly review
- a clear 24h plan if something goes wrong
Problem: without a visual calendar and a clear state (“on track” vs “slipping”), the routine dies quickly.
So SlugSentinel V1 was born:
- every action in the Security Routine becomes a task
- each task has a frequency and a state (on time / late)
- everything shows up in a single cockpit with LEDs and a Risk Shield
The idea is simple:
If your armour is green, you keep going.
If it’s yellow or red, you fix that before thinking about new trades or bots.
You can see the tool here:
👉 https://cryptoslug.pt/en/slug_tools/slugsentinel_v1_en.html
And the full article that explains the model here:
👉 https://cryptoslug.pt/en/blog/from-war-log-to-tools.html
How to use it in practice (short version) 🧭
If you want to try this approach for your own security:
Initial Setup
- open SlugSentinel V1 in your main browser/device
- go through the initial setup card and tick items off
- split it into a few sessions if needed
Quick Routine (weekly / bi-weekly)
- pick a fixed day
- on that day, open the tool and run through the quick checks
- watch the LEDs and the Risk Shield for your state
Monthly Review + 24h Plan
- once a month, combine your portfolio review with the monthly security review
- use the 24h plan in the tool if something feels off instead of improvising
It’s not magic.
But it’s a lot better than “I’ll do it when I have time”.
What’s next? 🚀
SlugSentinel V1 is the Spawnling / Basic Hodler tool for security.
The plan for CryptoSlug is:
- early ranks: security tools, Hodler Diary, simple DCA and exposure simulators
- later ranks: tools that talk to real data (dashboards, SCAA, more advanced SlugSim)
Always with the same rule: War Log first, tool second.
What about you?
I’m curious:
- Do you already have a security routine for your accounts and devices?
- Would a small panel like this make it easier to stick to it?
Let me know in the comments — and if you test SlugSentinel V1, I’d love feedback.
More on cryptoslug.pt — Gunbot strategies, automation & discipline.
