The story
Building a multi-network operating business
The programme developed around Vodafone Digital Asset Broker and subsequently Pairpoint, its Economy of Things venture with Sumitomo.
The founder's practice supported protocol business development, architecture and operating arrangements across Chainlink, Energy Web, NEAR, Aleph Zero and later opportunities including Nillion, Allora and ZetaChain.
The network relationships were at different stages; an active service, a deployment in progress and a proposal under negotiation did not carry the same commercial or technical obligations.
Designing wallet and treasury operations
The team worked on wallet and transaction controls, network-specific funding, token conversion and reward-accounting workflows.
This involved distinguishing node transaction wallets from payout wallets, documenting how assets were moved for approved corporate purposes and maintaining the information needed for finance and audit reporting.
The operational record contains procedures for token conversion, access and exchange operations, as well as technical reporting that brought balances and protocol activity into a more usable management view.
Managing operators and service economics
Some infrastructure ran in the venture's cloud environment; other arrangements involved specialised external providers.
The programme required ongoing coordination of delegation terms, provider costs, uptime and incident responsibilities, protocol updates and payment arrangements.
The records include actual service activity and commercial changes, but there is no defensible single figure for total programme profit or for how many different categories of node were simultaneously operating. These details are better represented by named service stages than an inflated network count.
Preparing a 2025 handover
The most concrete cross-portfolio deliverable in the final source record is a substantial technical handover prepared by Lionscraft.
The handover described active and developing services, operating parties, expected revenue mechanisms, important contacts, wallet purposes, financial procedures, outstanding agreements and technical dependencies.
It also required decisions about access control, vendor relationships, monitoring and continuing responsibilities.
A handover document was prepared; its existence does not prove every proposed transfer was completed or accepted by a successor.