Vlad

Hi! It is a real problem, march 2021 still not merged, please do it

Just disable ivy in tsconfig.app.json (and in tsconfig.server.json if you use Angular Universal) `"angularCompilerOptions": { "enableIvy": false },` Not all the main libraries already support Ivy, so the only solution...

https://medium.com/@fessbespalov/enabling-initialnavigation-with-localizerouter-and-angular-universal-8d514f1faad9 I had the same problem and wrote an article when solved, mb it'll help someone :)

I just added a second draft to the PR using an additional field in the MultisigSpendingCondition struct, it doesn't remove the rolling hash but adds a correct order vector which...

Hey @jcnelson, thanks a lot for your feedback! Your second point about signatures being equal from different owners is a bit hard to imagine now, could you elaborate on that?...

@jcnelson Oh thanks a lot for the explanation! that's what I tried to do with my first approach, but I thought it was rejected, and then I created this one...

@jcnelson Yeah I understood that, I don't like this approach either that's why it's the second draft Could you check the first commit? Is it the way to go? I...

Hey @jcnelson! First of all, thanks so much for your comment, now it's very much clear where to proceed, that's exactly what I was looking for! And sorry for bothering...

Hey @jcnelson, @jbencin! I had to jump on our Stacks multisig release preparations and PRs to Hiro and Stacks.js, and finally back now Implemented the new logic based on your...

@jbencin @jcnelson fixed all comments except one, commented on that one too, and added more autotests for different multisig thresholds