Matthew Mitchell

I ran with `cargo build` and when I generated into an empty directory, there are no warnings and curiously no `rust_ffi.g.dart` generated. The generated files are OK: ``` ▾ api/...

No issue using `flutter_rust_bridge_codegen generate` either, so not sure what happened before.

They are two different numbers. One is `0x1112131415` and the other is `0x57c74942` (encoded as little-endian). In ASM, they are displayed the same. Using `0x` before hex is consistent with...

> Edit: Curious if anyone knows the original rationale for displaying small values as decimal, it was carved out [by satoshi](https://github.com/bitcoin/bitcoin/blob/4405b78d6059e536c36974088a8ed4d9f0f29898/script.h#L298-L305). It is because any numerical/arithmetic operations only allow 32-bit...

Is it a problem prefixing public keys with `0x`? I'm not overly fussed on the solution as long as the ambiguity is removed. > It seems like this could break...

Thank you @conradoplg, it looks like `verify_signature_share` should be perfect. For my Taproot use-case, it is only further required that it is provided alongside https://github.com/ZcashFoundation/frost/pull/584.

This is still a bug. `shutdown()` does not force streams to close and waits for them to finish. The only workaround is to ensure the streams are closed before calling...

The workaround I have at the moment looks like this in the service RPC implementation: ```dart // sendTrailers is not always called automatically when the stream ends // despite the...

@conduition Perhaps a simple solution is to tweak the DKG output in a way similar to BIP32? It could be as simple as tweaking by the group public key hash?...

Isn't the key already tweaked at sign-time anyway? Looking at my own code, I've used an earlier version of this branch and I see that a TapTweak is already done....