Ales

> Hello again @alessandrokonrad > > Some more thoughts: I suspect this affects Lucid as well. I can't use Lucid's `vasil` branch with other wallets (for example: eternl) - only...

@TotallyNotChase I just updated the vasil branch for Nami. It should support now the legacy output serialization. Actually Nami makes now the witness on the raw cbor encoded tx body...

> Did this change? I was told by someone about this issue popping up again in the newest nami build. Mhh lemme check. Should not be the case tho. I...

@TotallyNotChase can you send me an example tx in cbor where it's failing for you? I can't figure out the "issue". The body is signed with the original bytes.

Hey I'm sorry to hear this... unfortunately there is not much anyone can do about this, since Nami is a non custodial wallet and we can't control user's actions.

Oh wow, didn't expect such a PR hahaha. I'm gonna check that out!

@vineeth2941 was able to successfully build. How does the communication between the app and the browser work exactly? I see it works with Intents somehow, but how do I call...

> @alessandrokonrad Intents work only for App to App communication, We need to build a dApp browser if it has to be between a website and the wallet app. For...

The problem is, if Nami has to balance the tx it also has to calculate the fees. Plutus Core is not available in the browser yet, so Nami could not...

Calculating fees based on tx size is something different than also taking execution units into account. If you add inputs and outputs to the transaction you change the `ScriptContext` and...