Hao

I think It should be consistent at least among those flow official SDK, otherwise it just will cost hazard to developer if people like us wanna implement multi-sign transaction across...

Update description with more context.

Hi @psiemens Here is the example code : For the fcl js part, that's how we send the transaction request by using the `voucher` in signable project. ``` const tx...

Hi @psiemens @sideninja @turbolent Unfortunately, I found some other issue when encode the `UFix64` or `Fix64`, the **precision** is not aligned 🙁. ( I guess I need move lilico payer...

Is there any update on this 😿 ? More and more dev running into this issue on our end. And the new wallet connect method will be affected as well.

Hi @alxflw Sure, got it. We will work on it and update here.

Hey @alxflw Sorry for the late reply, some distraction on our end. I have update the milestone base on your comments, please have a look.

Yeah, the adoption was planning to track and generate a usage report to flow developer experience team. If it's no need, we can simply remove it. :)

I figure it out. :) Thanks so much

Hi @psiemens Team Zed will focus on Swift SDK implementation. ✊🏻