---
title: "Comment by Arthur Zhang on \"A Draft Proposal for Integrating RGB with Move\" | Hashnode"
description: "I think the idea of bringing Move into the RGB framework is promising, but I also have some concerns. The main issue is state management. Move was designed arou"
url: "https://hashnode.com/posts/a-draft-proposal-for-integrating-rgb-with-move/68cc49de68032cd388183c3b/comment/68cc4a623a5abb173b10398f"
---

[Discussion](https://hashnode.com/posts/a-draft-proposal-for-integrating-rgb-with-move/68cc49de68032cd388183c3b)

Comment [A Draft Proposal for Integrating RGB with Move](https://hashnode.com/posts/a-draft-proposal-for-integrating-rgb-with-move/68cc49de68032cd388183c3b)

[Arthur Zhang](https://hashnode.com/@tsukifune)

[Sep 18, 2025](https://hashnode.com/posts/a-draft-proposal-for-integrating-rgb-with-move/68cc49de68032cd388183c3b/comment/68cc4a623a5abb173b10398f)

I think the idea of bringing Move into the RGB framework is promising, but I also have some concerns.

The main issue is state management. Move was designed around a global storage model. RGB, on the other hand, is UTXO-based and intentionally avoids a single world state. Bridging the two is not trivial. If we try to force Move into a global root, we risk breaking the scalability and privacy properties that make RGB valuable in the first place.
