Grinwell: Web3 platform.
React and .NET over Web3.js, with Solidity contracts on Ethereum built on OpenZeppelin. The hard part was never the chain: it was making pending, confirmed and failed legible to people who do not think in transactions.
Selected clients since 2008
Power to LiveRBM GlobalDragonflySquiblerMOOSainsbury'sMPCX-LinkPower to LiveRBM GlobalDragonflySquiblerMOOSainsbury'sMPCX-LinkPower to LiveRBM GlobalDragonflySquiblerMOOSainsbury'sMPCX-Link
The challenge.
- The product needed to transact on-chain while staying approachable for non-crypto users.
- Wallets, tokens and contract calls had to be wired safely into a clean interface.
- On-chain state had to reconcile with an off-chain view users could trust.
- Gas costs, failed transactions and pending states had to be communicated honestly rather than hidden.
Our approach.
- Built the interface with React, integrating wallet connection and signing.
- Wired on-chain interactions through Web3.js, Solidity, Ethereum and OpenZeppelin.
- Reconciled on-chain events with an off-chain read model for fast, readable state.
- Kept flows guarded so users understand each transaction before signing.
- Surfaced transaction state honestly — pending, confirmed, failed — with clear recovery paths.
The outcome.
- Users transact on-chain from an interface that hides the plumbing.
- On-chain and off-chain state stay reconciled and readable.
- The contract layer is isolated so it can evolve safely.
- Users always know the true state of a transaction, including when it fails.
Where AI fits in financial services.
Retrieval over policies, filings and statements, assistants for analysts and operations teams, and document checks that leave an audit trail a regulator can follow.
Explore AI development“Enigmatix Global did some great work for Sainsbury's, bridging complex interactions between some older less flexible systems, some rigid vendor solutions and the new systems we were building. The software Enigmatix Global developers wrote stood up well, long beyond the interim scope of it needing to work for 12 to 18 months, and was still in active use 5 years after its creation, since it was part of mission-critical systems.”
Let's build from here.
Thirty minutes with an engineer who builds. No sales, no drip campaign. If we're the wrong fit we'll tell you and point you somewhere better.


