May Development Update

In April, we introduced the treasury vault direction. In May, the work shifted toward the practical questions fund managers, operators, and partners care about:

• Can the team control token issuance from an admin workflow?
• Can we see what happened on-chain and explain it to stakeholders?
• Can fund operations run with fewer engineering handoffs?
• Can the platform support demos, pilots, and client onboarding more reliably?

The answer moved meaningfully forward across treasury operations, wallet infrastructure, admin tooling, and deployment reliability.

Fund Treasury: Closer to Operational Use

The treasury vault is the core operating layer for tokenized fund activity. In May, we made that layer more usable for real fund operations.

What improved

Clearer readiness checks. The admin panel now checks whether the fund manager's wallet is ready before key vault actions continue. This reduces avoidable support issues during onboarding and closing.

Better treasury control setup. We added support for treasury controller information, which helps represent who is allowed to participate in fund treasury actions. This is an important step toward multi-party governance without slowing down the first client rollout.

Token minting and investor delivery. Operators now have admin flows for minting tokens and sending tokens to investors. This brings the platform closer to a repeatable issuance workflow instead of a one-off technical process.

More useful vault screens. The vault view now includes clearer charts, token allocation information, and a close-offer action. That gives business and operations teams a better view of where an offering stands.

The business value is simple: fewer manual steps, fewer engineering dependencies, and a clearer path from investor commitment to token delivery.

On-Chain Visibility and Wallet Reliability

For a tokenized fund platform, it is not enough to send transactions. The platform also needs to understand transaction status, wallet state, balances, and execution history.

May improved that visibility.

Automatic blockchain event tracking. We improved the way blockchain events flow into the platform, so wallet and transaction updates can be captured automatically.

More accurate transaction information. Token amounts, token pricing, wallet balances, and transaction details were tightened so teams can rely on the numbers shown in the dashboard and admin panel.

Stronger wallet activation flow. Wallet activation and authorization continued to improve, including checks that help confirm whether a wallet is ready for the next action.

This matters for sales and client success because every pilot eventually gets the same questions: "Did the transaction happen?", "Where is the investor's token?", "Can we prove it?", and "Can support explain it quickly?" May's work makes those answers easier.

Admin Tools for Operators

We also improved the tools used by the internal team to support fund managers and investors.

• The profile list now includes a send-email action, making it easier to contact users directly from the admin workflow.
• Admin logs now show more event activity, which helps teams trace what happened when a transaction or notification runs.
• Notification infrastructure moved forward with websocket support for real-time user communication.
• Vault-related admin screens gained more useful information for reviewing an offering and its token allocation.

These changes are small individually, but important commercially. They help turn the platform from a development environment into an operating system that a support, compliance, or fund operations team can use.

Platform Reliability and Client Delivery

May also included a large amount of behind-the-scenes work to make the platform easier to deploy, demo, and maintain.

More reliable environments. Dev and stage environments were cleaned up, including internal API URLs, HTTPS setup, static asset deployment, and frontend rebuild triggers.

Cleaner release process. Admin and EVM deployment workflows were improved so new changes can move through environments with fewer manual fixes.

Brand migration. Public surfaces continued moving toward Torque Global and Torque Investments branding.

Wallet Experience

The wallet experience also continued to improve. The authorization dialog now gives clearer summaries of what the user is signing, OTP entry behavior was improved, and exchange and withdrawal flows received additional authorization handling.

This is important because fund managers and investors should not need deep crypto knowledge to complete basic platform actions. The product direction remains the same: make blockchain-backed fund operations feel like normal financial software.

What This Means for Clients

May's work moved Torque closer to a client-ready operating model for tokenized funds:

• Fund managers get clearer treasury and wallet workflows.
• Operators get better admin tools and fewer manual handoffs.
• Investors can be issued tokens through a more structured process.
• Support teams get better visibility into transaction and notification activity.
• Business teams get more reliable demos, staging environments, and pilot delivery.

The next phase is to continue tightening the multi-controller treasury flow, legal and platform approval rules, and timelock rollout while using the current operating flow with early clients.