As vincenzopalazzo accurately famous, each channel within the route should be RGB-aware — there isn’t any method to ahead RGB property by a channel that doesn’t help the protocol.
The reason being architectural. In RGB over Lightning, the asset just isn’t carried “alongside” a standard satoshi cost: it’s embedded contained in the dedication transaction of every channel as an RGB state transition.
Since every hop in a multi-hop cost, the intermediate node should do two issues:
- Add a brand new HTLC output to their dedication transaction (normal Lightning)
- Add a corresponding RGB allocation within the RGB state transition, assigning the asset quantity to that HTLC output
Because the official RGB v0.11.1 documentation states:
“For every cost that’s being routed by the channels, a
devoted HTLC output will likely be added to the lightning dedication
transaction. Along with the brand new HTLC output, a brand new allocation wants
to be added to the RGB state transition, which is able to ship the quantity of
property concerned within the cost in direction of the brand new HTLC output. Whoever
manages to spend the HTLC output, both by data of a secret
or by ready for a timelock expiration, will be capable to transfer each the
satoshis that had been within the output, and all of the property assigned to it.”
A channel that does not help RGB has no mechanism to create this state transition. In actual fact, it can not allocate RGB property to an HTLC output, so it can not ahead the asset.
In follow: RGB funds on Lightning require a devoted path of RGB-capable channels, the place each node within the route has applied the RGB Lightning protocol. This is identical constraint that applies to any asset in a cost channel community: intermediate nodes should communicate the identical protocol because the asset being routed.
