Armando CD

I intent make a review that today, ok?

Hi @cryptoquick and @josediegorobles , we can make solve it, if add optional parameter in invoice called network. This maintain compatibility with other wallets and prevents the problem use invoices...

> This should already be on the RGB invoice struct Yes, but it is only used in case you know the beneficiary (see [here](https://github.com/RGB-WG/rgb-wallet/blob/master/src/invoice/parse.rs#L297-L307)).

> So, that would be an invoice that includes a blinded UTXO? That's fine I think. No, RgbInvoice parse the chain only when beneficiary is a bitcoin address, not when...

> Right now, it's not possible to create a transfer back to yourself, because the receive UTXO is the same as the spend UTXO. However, if we can detect that...

> What is the error output if you add this to the route handler? `#[axum_macros::debug_handler]` > > Also, what command are you running to build, and on which branch? I...

> Is this still an issue? Yes.

Does make sense we try solve that by "infra" approach? We can make an "explorer proxy/load balance" and if request failed or server does not response, we can try request...

I will start some tests about that, but this does not happen after RGB Watcher because we can create PSBT with a tweak now. If tests works, I will close...

> The invoice for 100.00 of an asset with precision 2 or more should look like `rgb:/RGB20/100.00+tb:utxob:...` (independently from whether the precision is 2 or 8) and not like `rgb:/RGB20/10000+tb:...`...