---
title: "Discussion on \"A Draft Proposal for Integrating RGB with Move\" | Hashnode"
description: "Discussion on \"A Draft Proposal for Integrating RGB with Move\". 1. Problem\nBitcoin provides settlement finality but is limited in programmability. RGB extends Bitcoin with client-side validation and smart contract schemas, but its native virtual machine (AluVM) is still evolving. Developers who wish to model rich..."
url: "https://hashnode.com/posts/a-draft-proposal-for-integrating-rgb-with-move/68cc49de68032cd388183c3b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A Draft Proposal for Integrating RGB with Move](https://tondi.hashnode.dev/a-draft-proposal-for-integrating-rgb-with-move?utm_source=hashnode&utm_medium=feed)

1\. Problem Bitcoin provides settlement finality but is limited in programmability. RGB extends Bitcoin with client-side validation and smart contract schemas, but its native virtual machine (AluVM) is still evolving. Developers who wish to model rich...

Sep 18, 2025 · 3 min read · tondi.hashnode.dev  
Updated Sep 20, 2025  
Read the article

-   [#rgb](https://hashnode.com/tag/rgb)
-   [#move](https://hashnode.com/tag/move)

## Written by

[Charlie-D](https://hashnode.com/@charlieavato)

@charlieavato

  
[View profile](https://hashnode.com/@charlieavato)

Dubito, ergo cogito, ergo sum

## Responses 1

Markdown supported · ⌘↵ to post

[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.
