Moneygram’s Strategic Infrastructure Staging Ground
Global remittance giants have traditionally operated as consumers of network infrastructure. Moneygram’s deployment of an active Solana validator node—and its integration into the Solana Developer Platform (SDP)—marks a notable shift. Moneygram is no longer just using the tracks; it is helping run the engine.
Yet as traditional financial institutions (TradFi) step into permissionless consensus layers, they face significant engineering, security and economic friction. Harry Hwang, CEO of Flowra, breaks down the architectural realities, zero-trust requirements, regulatory tightropes and the emerging fight over compliant institutional MEV.
The announcement that Moneygram is actively validating blocks on Solana sparked speculation that real-time retail remittances are settling directly through its node. Hwang urges a more grounded interpretation.
“Moneygram is a great example of a major trend. But I would not interpret this as meaning that its payment system is already directly integrated with validator operations. It is more accurate to see it as Moneygram entering protocol-level infrastructure operations, opening the door to longer-term integration with stablecoin and payment rails.”
By establishing an infrastructure-first presence, Moneygram effectively implements an operational staging ground. Operating a validator in isolation allows the legacy payment giant to stress-test its technical capabilities, master high-frequency key management, and navigate public- node zero-trust architectures in production. This strategic buffer ensures Moneygram can fully resolve the unique engineering and security friction of public consensus layers before exposing its multi-billion-dollar core settlement ledger to the live network.
Still, integrating a public validator into an institution’s hardware security module (HSM) architecture exposes a core conflict: tradfi demands cold storage and isolation, while Solana consensus requires relentless speed.
“Under Solana’s current architecture, validator identity and vote authority must be signed very frequently, so they are generally required to exist in the hot path of the validator system. By contrast, the authorized withdrawer key is not needed during normal operation and controls the vote account, so it should be managed through cold storage, HSM, MPC [multi-party computation] or an offline key ceremony.”
The high-frequency signing requirement has historically made full HSM isolation a performance bottleneck. However, Solana’s Alpenglow upgrade introduces off-chain, lightweight messages aggregated through BLS signature schemes.
“This is where Alpenglow becomes meaningful. If on-chain vote transactions are removed and the system moves toward BLS-based voting, the burden of high-frequency vote signing in the hot path may be reduced. Solana has also discussed designs around secure-enclave-based vote signing, so HSMs, enclaves and remote-signing architectures could become more realistic over time.”
Meanwhile, when a heavily regulated entity participates in consensus, it effectively confirms transactions for a global pool of pseudonymous users—creating tension with compliance mandates.
“When a payment company directly participates in consensus on a public permissionless network, it is not yet fully settled how that activity should be treated under AML, sanctions, the Travel Rule, payment licensing, outsourcing and operational resilience frameworks,” Hwang said.
He added that for companies like Moneygram, validator participation may be better understood as part of building open stablecoin rails with compliance and operational scale, rather than as an immediate extension of the payment settlement engine.
Compliant Order-Flow and Base-Layer Neutrality Risks
As enterprises adopt the SDP alongside compliant providers such as Anchorage Digital and Chainalysis, demand is shifting from pure staking yield toward regulatory alignment. Because Solana lacks an Ethereum-style global public mempool, this demand manifests as isolated order-flow lanes.
“In practice, this demand is more likely to evolve into compliant order-flow lanes, policy-based execution and permissioned asset layers. For example, institutional orders may be routed through KYT-screened paths, while validators select execution routes based on policies such as no-sandwich, low-risk, no-toxic MEV or compliance-friendly flow.”
However, if these compliant lanes become dominant, Solana faces a systemic paradox: it attracts institutional capital but risks centralizing liquidity.
“If compliant order-flow lanes become too dominant, real liquidity and high-quality execution may concentrate in a small number of approved routes. In that case, the protocol may remain permissionless in theory, but gatekeepers could emerge in practice.”
To maintain validator autonomy, Flowra uses a policy-based proposer (PBP) framework. The goal, Hwang said, is not to lock validators into a single builder or block engine, but to allow them to choose among multiple builders and order-flow sources based on yield, toxicity, risk, and compliance criteria.
Perhaps the most complex friction point when traditional finance capital meets decentralized infrastructure is maximal extractable value (MEV). MEV has become a major revenue driver for blockchain validators, yet predatory practices like frontrunning and sandwich attacks directly conflict with institutional best-execution policies and Wall Street market conduct standards. For corporate operators, MEV presents a sharp economic double-edged sword.
“This question is not really about whether institutions should participate in MEV or not. It is about which forms of MEV should be allowed and which should be restricted,” Hwang said. “If an institutional operator gives up MEV entirely, it may be leaving revenue on the table that could otherwise go to delegators or investors.”
But if it allows aggressive MEV strategies without limits, especially strategies built on user harm, it may conflict with fiduciary duty and market conduct standards.
