-
Given a number of staves in a staff group in a flowable, if the staves have different key signatures that are not declared at the same point, the calculated flowable margin can be incorrect. This is b…
-
This is the issue that Steve L. reported on the dev list.
"Both published fine, but when I downloaded the document and ran the verify code, it failed. I'm just wondering if anyone else is having tro…
-
Ability to set default signatures by groupadmins, with variables such as "group" "user" ...
Why? Getting it right for every user is quite hard.
Should look like this:
> Kind regards
> %user%
…
-
Hi!
First off, thank you for this analysis tool!
I am analyzing some Perturb-Seq data and have followed the vignette. I ran Mixscale_Scatterplot and interestingly the perturbation score seems p…
-
Pravici would like to voice its support of the creation of the W3C Linked Data Signatures Working Group. We see LDS as a critical technology in supporting an open trust and assertion ecosystem.
-
We've kicked around a few ideas for how best to do this. After researching #31 we know BLS aggregated signatures aren't an option due to the expensive pairing check scaling with the group size.
-
As a member of a multisig group, I want to be able to catch up with events signed by other multisig participants.
Consider a group of three members A,B,C and a signing threshold of 2
- Member A …
-
**Describe the bug**
When selecting all time signatures in a conductor's stave, when one goes to edit their properties, the edits only apply to the individual time signature that was most recently cl…
-
Current Context Contains:
- the APP name
- Signature
- User
Revocation list
- Ceramic is the location where we store this list.
Define sign method on connect
- On connect a private key is being cre…
-
We are using the `frost-secp256k1` crate for verification of WSTS-generated signatures: `frost-secp256k1 { git = "https://github.com/LIT-Protocol/frost" }`.
In theory, the math should be identical …