---
title: "Matthew Hine"
url: "https://radix.wiki/community/matthew-hine"
version: "1.0.0"
updated: 2026-08-22
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# Matthew Hine

| Matthew Hine |  |
| --- | --- |
| Also known as | Matt |
| Occupation | Product executive; systems architect |
| Known for | Chief Product Officer of [RDX Works](/ecosystem/rdx-works); author of the Radix blog's [asset-oriented](/contents/tech/core-concepts/asset-oriented-programming) design essays |
| Education | BSc mechanical engineering, [Rice University](https://www.rice.edu/) |
| Before Radix | [Texas Instruments](https://www.ti.com/) — DLP display systems |
| Radix blog | 25 posts, [14 November 2019](https://www.radixdlt.com/blog-author/matthew-hine) to [9 September 2024](https://www.radixdlt.com/blog-author/matthew-hine-3) |
| UK directorships | None recorded in the [Radix group](https://find-and-update.company-information.service.gov.uk/company/10864928/officers) |

**Matthew Hine** is the Chief Product Officer of [RDX Works](/ecosystem/rdx-works), the company that built the [Radix](/contents/tech/releases/radix-mainnet-babylon) network, and the author of most of the essays in which Radix set out its [asset-oriented](/contents/tech/core-concepts/asset-oriented-programming) argument to a technical audience. Where [Dan Hughes](/community/dan-hughes) wrote the protocol and [Piers Ridyard](/community/piers-ridyard) carried the project to a general crypto audience, Hine wrote the explanations: [twenty-five posts on the Radix blog](https://www.radixdlt.com/blog-author/matthew-hine) between November 2019 and September 2024, covering [Radix Engine](/contents/tech/core-protocols/radix-engine), [Scrypto](/contents/tech/core-protocols/scrypto-programming-language), [transaction manifests](/contents/tech/core-protocols/transaction-manifests), [Smart Accounts](/contents/tech/core-concepts/access-controller) and [native pools](/contents/tech/core-concepts/radix-pools).

He was publishing as Head of Product by [July 2021](https://www.radixdlt.com/blog/meet-the-team-matt-josh), and his bylines read "Matthew Hine, CPO of RDX Works" from [June 2022](https://www.radixdlt.com/blog/asset-oriented-soulbound-tokens-done) onwards. He has never been a registered director of any UK company in the Radix group, so unlike his two better-documented colleagues he leaves no trace on the company register at all.

## Career before Radix

Hine holds a bachelor's degree in mechanical engineering from [Rice University](https://www.rice.edu/) and spent roughly a decade at [Texas Instruments](https://www.ti.com/), where — by his own account in the company's ["Meet the Team" profile of 17 July 2021](https://www.radixdlt.com/blog/meet-the-team-matt-josh) — he championed opto-mechanical system designs for DLP display products and created the automotive DLP display group that went on to produce head-up displays. He subsequently worked across medical devices, cinema projection, head-mounted displays, 3D scanning and hyperspectral imaging.

In the same profile he describes his job at Radix as defining "product vision and strategy, and working across our teams to make those products happen", and himself as "a bit of a resident generalist" interested in the economics, law, governance and philosophy around the technology as much as in the technology itself. That range shows in the published work, which moves between ledger architecture, developer ergonomics, wallet interaction design and standards proposals without changing voice.

## Role at RDX Works

The title on the byline changed once, in the spring of 2022. ["Is Scrypto Turing complete?"](https://www.radixdlt.com/blog/is-scrypto-turing-complete) of 9 March 2022 is signed simply "Matthew Hine"; the blog post of [31 May 2022](https://www.radixdlt.com/blog/austin-developer-event-consensus-2022) announcing the [Austin Developer Event](/contents/history/austin-developer-event) bills him as RDX Works Chief Product Officer, opening that day's programme with a keynote alongside chief executive [Piers Ridyard](/community/piers-ridyard); and from [9 June 2022](https://www.radixdlt.com/blog/asset-oriented-soulbound-tokens-done) through to his last post in September 2024 the sign-off reads "Matthew Hine, CPO of RDX Works".

The executive role has no counterpart on the UK register. The Companies House officer list for [RDX Works Ltd (10864928)](https://find-and-update.company-information.service.gov.uk/company/10864928/officers), read on 22 August 2026, records eight officers and six resignations and none of them is Hine; the [officer index](https://find-and-update.company-information.service.gov.uk/search/officers?q=Matthew+Hine) returns four people of that name, none connected to a Radix company. A chief product officer need not be a registered director, so there is no contradiction here — but it does mean the register, which is where this wiki dates [Ridyard's](/community/piers-ridyard) and [Hughes's](/community/dan-hughes) arrivals and departures to the day, says nothing whatever about his.

## The asset-oriented essays

His first two posts, ["Radix Engine and Ledger: the road to adoption"](https://www.radixdlt.com/blog/radix-engine-and-ledger-the-road-to-adoption) (14 November 2019) and ["Moving past smart contracts"](https://www.radixdlt.com/blog/moving-past-smart-contracts-natively-composable-dlt-with-radix) (3 December 2019), already carry the thesis the rest of the run elaborates: that a ledger should treat tokens as native objects the engine moves and accounts for, rather than as balances a contract remembers in its own storage. The wiki's [Asset-Oriented Programming](/contents/tech/core-concepts/asset-oriented-programming) page describes the model that followed.

The 2021 sequence is the closest thing Radix has to a design rationale published in public. ["The problem with smart contracts today"](https://www.radixdlt.com/blog/the-problem-with-smart-contracts-today) (4 October 2021) states the failure mode; ["Radix Engine v2"](https://www.radixdlt.com/blog/radix-engine-v2-an-asset-oriented-smart-contract-environment) (7 October 2021) introduces the [engine](/contents/tech/core-protocols/radix-engine) that answers it; ["Scrypto: an asset-oriented smart contract language"](https://www.radixdlt.com/blog/scrypto-an-asset-oriented-smart-contract-language) (12 October 2021) introduces [the language](/contents/tech/core-protocols/scrypto-programming-language); and ["How Radix Engine is designed to scale dApps"](https://www.radixdlt.com/blog/how-radix-engine-is-designed-to-scale-dapps) (11 November 2021) connects the execution model to the scaling argument. ["Is Scrypto Turing complete?"](https://www.radixdlt.com/blog/is-scrypto-turing-complete) (9 March 2022) answers the question developers kept putting to the asset restrictions.

Two earlier posts belong to the pre-[Olympia](/contents/tech/releases/radix-mainnet-olympia) period and read now as period documents rather than as current description: ["On-ledger recurring developer revenue"](https://www.radixdlt.com/blog/on-ledger-recurring-developer-revenue-incentives-to-buidl) (6 August 2020) and ["Reducing DeFi hacks, exploits and failures on Radix"](https://www.radixdlt.com/blog/reducing-defi-hacks-exploits-failures-on-radix) (4 December 2020).

## Wallet, transactions and standards

From 2023 the subject shifts from the engine to what a user sees. ["Radix’s asset-oriented transactions"](https://www.radixdlt.com/blog/radixs-asset-oriented-transactions) (26 June 2023) and ["Using transaction manifests to give wallet users confidence"](https://www.radixdlt.com/blog/using-transaction-manifests-to-give-wallet-users-confidence) (7 August 2023) make the case that a [manifest](/contents/tech/core-protocols/transaction-manifests) is readable precisely because the engine, not the contract, is what moves the assets — so the [Radix Wallet](/contents/tech/core-protocols/radix-wallet) can show a user what a transaction will do before it is signed. ["How Radix multi-factor Smart Accounts work"](https://www.radixdlt.com/blog/how-radix-multi-factor-smart-accounts-work-and-what-they-can-do) (25 August 2023) is the public explanation of the [Access Controller](/contents/tech/core-concepts/access-controller); ["Using native pools and pool units"](https://www.radixdlt.com/blog/using-native-pools-and-pool-units-for-intuitive-liquidity-provider-ux) (7 August 2023) of [native pools](/contents/tech/core-concepts/radix-pools); and ["Asset-oriented soulbound tokens: done"](https://www.radixdlt.com/blog/asset-oriented-soulbound-tokens-done) (9 June 2022) argues for non-transferable tokens as a resource behaviour rather than a contract convention.

His last individually bylined post, ["Feedback wanted: interface standard for on-ledger name service providers"](https://www.radixdlt.com/blog/feedback-wanted-interface-standard-for-on-ledger-name-service-providers) (9 September 2024), is a standards proposal rather than an explainer: one interface any name-service provider can implement, so that the wallet resolves a human-readable name without an app-specific integration per provider. It credits [XRD Domains](/ecosystem/xrd-domains) with product-requirement input, and records that the feedback round closed without changes to the proposal.

## Publication record

The Radix blog splits his posts across three author records — [matthew-hine](https://www.radixdlt.com/blog-author/matthew-hine) (fifteen posts, November 2019 to January 2023), [matthew-hine-3](https://www.radixdlt.com/blog-author/matthew-hine-3) (ten posts, June 2022 to September 2024) and [matthew-hine-2](https://www.radixdlt.com/blog-author/matthew-hine-2), which carries none at all. The split is an artefact of the site's content model rather than of anything he did, but it means neither populated page shows the whole run, and a reader who finds the first one concludes he stopped writing in January 2023.

Nothing on the blog carries an individual byline after mid-2025. Read on 22 August 2026, the newest post under any named author is [Adam Simmons's](https://www.radixdlt.com/blog-author/adam-simmons) of 4 July 2025, and the 2026 run — the [2026 strategy](https://www.radixdlt.com/blog/2026-strategy-the-next-chapter-of-radix) posts, the [Foundation operational stack](https://www.radixdlt.com/blog/the-foundation-operational-stack-mapping-the-2026-transition) and the [Hyperscale](/contents/tech/research/hyperscale-rs) updates — is signed "Radix" as an institution. His absence from recent bylines therefore describes how Radix now publishes, and says nothing on its own about his role; no announcement has stated a change in it.

## External links

- [The Radix Blog — posts by Matthew Hine (2019–2023)](https://www.radixdlt.com/blog-author/matthew-hine)
- [The Radix Blog — posts by Matthew Hine (2022–2024)](https://www.radixdlt.com/blog-author/matthew-hine-3)
- [Meet the Team: Matt and Josh (Radix blog, 17 July 2021)](https://www.radixdlt.com/blog/meet-the-team-matt-josh)
- [Companies House — RDX Works Ltd officers](https://find-and-update.company-information.service.gov.uk/company/10864928/officers)