How This Started,
and Why It Matters
The beginning
This did not start as a project. It started as a problem I wanted to solve for a small group of people I genuinely cared about.
At the time, every new member being onboarded to the Pool Funding community had to import our custom tokens into their wallet by hand. Every single one. And at the time there were four of them. Even for someone who knew what they were doing — which was rare — it was a tedious, time-consuming process. A lot of back and forth, a lot of opportunities for something to go wrong, a lot of minutes lost on every single call.
I built a tool that changed that. Instead of walking someone through a manual import step by step, the tool fired token suggestions directly to MetaMask. All the person being onboarded had to do was tap a few buttons, and every custom token was added. What had been a drawn-out process became something close to effortless.
I built it for the Executive team — people I had real rapport with, people I worked alongside regularly, people whose time I wanted to respect. I did not build it for an audience. I did not build it to be noticed. I built it because I could, and because it would help.
Back then, the whole thing lived as a widget on the sidebar of a Blogspot blog. It was not elegant. But it worked, and it worked well enough that the Executive team started relying on it.
The second tool — and a test under fire
About two months later, I built the RPC Switcher.
If that phrase means nothing to you — an RPC node is essentially the connection point between your wallet and the blockchain. Without it, your wallet cannot communicate, and transactions cannot go through. Most people rely on shared public nodes, which means that when those nodes go down — which they do, sometimes due to outages at major infrastructure providers like AWS or Cloudflare — wallets stop working. Members cannot make their payments. Support calls spike. Frustration runs high.
When one such outage hit the community, I wrote a manual guide as fast as I could — a step by step walkthrough for changing your RPC endpoint by hand. It was highly technical for a crypto newcomer. I broke it down as best I could, but most people found it difficult. I started working on an automated solution immediately.
My solution was ready by the time that particular outage had resolved. A few weeks later, another outage hit. This time, the RPC Switcher was ready. Members who used it avoided the manual process entirely — a few button clicks instead of a technical procedure many of them would have struggled with alone. It came through with flying colors, and I knew then that what I was building had real value beyond convenience. It was starting to matter in moments of genuine need.
Outgrowing the blogspot sidebar
With two tools now, and a growing sense that there was more I could build, the Blogspot sidebar had become too limiting. It was clunky, inflexible, and not something I could take further without fighting the platform at every turn.
I needed something more flexible, maybe slightly more professional, and free. GitHub Pages fit that description. So I rebuilt everything from scratch, moved it over, and gave the project a proper home for the first time.
From there, the tools grew steadily. A calculator for token values. Live charts. Quick links to BscScan. One-click swap shortcuts to PancakeSwap. A wallet approval scanner that checks your connected permissions against a live security database and a curated list of known malicious contracts. Support for non-MetaMask wallets. Mobile fallbacks for users on phones. Dark mode. Accessibility features most tools in this space do not bother with...
None of it was asked for. All of it was built because I saw something that could be better, and I had the ability to make it so.
How the community found it
I want to be clear about something: I did not announce this to the community. Rather, the community found it.
After sharing it with the Executive team, I quietly passed it along to a handful of high-profile community members — people I trusted, people with teams of their own who I thought would benefit. I did not make a public announcement. I was not looking for recognition. I just wanted the people I was closest to in this community to have access to something useful.
Knowledge of the tools spread from there on its own. Word got around. More people started using them. Eventually it became clear that the tools had outgrown their quiet origin, and I made the decision to "officially" announce them to the community at large — not because I sought the audience, but because the audience had already arrived.
What this became
Hunter's Toolbox has, in some ways, become part of who I am in this community. It is one expression of a broader commitment — to show up, to contribute, to help every member have as good an experience with crypto as possible.
I have poured my heart and soul into it. The weekly community calls. The documentation. The hours spent on accessibility so that the tools work properly for everyone. The security scanner, built because I wanted members to have a way to protect themselves that did not require them to already know what they were looking for.
I think of this project as a love letter to the community. That is not a phrase I use lightly. It reflects something I genuinely believe — that the people here deserve tools built with real care, real attention, and real investment. And they always will have had that, whatever happens next.
There is more I want to build. There are features planned that do not exist yet. There is a private AI assistant I want to offer, available around the clock for members who have questions when I am not around. There is infrastructure I want to move to so that these tools are more reliable, more resilient, and more capable of growing with the community.
Whether that happens depends on what comes next.
— Hunter Rodriguez