I will have opinions about these but will most likely not make it as I’m out of the country and attending to other matters. Please let me know the outcome and consider my current PRs and other message

#SharedCrypto

Hi Everyone, This is just a reminder of our biweekly meeting tomorrow, now for Ursa (we can use the name!). I’d like to spend most of the meeting discussing repo layout, setup, and structure, as well

#SharedCrypto

FYI, the Ursa mailing list is available for you to subscribe to at https://lists.hyperledger.org/g/ursa. ---- Tracy Kuhrt Community Architect, Hyperledger The Linux Foundation tkuhrt@...

#SharedCrypto

When making the CD pipeline. I propose we make the most common artifacts that consumers will want to use. For now, these are the ones I can think of RPM (RedHat distros) DEB (Debian distros) MSI (Wind

#SharedCrypto

Hi Everyone, This is just a reminder email for tomorrow’s crypto-lib meeting (at the usual time). Some agenda items: 1. Discuss the “tiering” process for implementations and any guidelines we want to

#SharedCrypto

Hi Dan, Sounds great! On your points: 1. I think there will also be some grey area for tiering. We will probably have to have maintainers collectively decide these things through votes. We can have a

#SharedCrypto

Government crypto is something which came up within the EEA. Essentially you have NIST standards and then there are Chinese and Russian equivalents which are mandatory for regulated (mainly banking) i

#SharedCrypto

I’m fine with the updated maintainers concept. We can enforce n maintainer reviews with github. We already do that in sawtooth. I’m still planning to get the contributor rules writeup in as a PR befor

#SharedCrypto

Hi Everyone, This is just a reminder for tomorrow’s crypto-lib meeting (7:00 AM Pacific time, as usual). Some things to discuss: 1. My perception is that we’re on the cusp of proposing crypto-lib to t

#SharedCrypto

I’ll be there I think. If we have a hackathon I’ll be there for sure. Dave

#SharedCrypto

Hi Everyone, I’m cancelling tomorrow’s crypto-lib meeting due to the fact that a large amount of our regular participants will be attending the Montreal hackfest. I hope that we can come out of the me

#SharedCrypto

Thanks for wrangling this, Hart. Not sure if I can make it to today’s call. In case I can’t I’ve added a couple comments in the proposal. As further high-level thoughts, though, it might be helpful to

#SharedCrypto

Hi Everyone, I’ve updated the project proposal document for crypto-lib. Please take a look and tell me what you think. I believe it reflects the current status of the work being done, as well as what

#SharedCrypto

I am based on Toronto. Can I remote in? Max

#SharedCrypto

Hi Everyone, This is just a reminder for tomorrow’s (today’s, for many of you) crypto-lib meeting. The plan is the following: 1. Continue the discussion on Z-mix from the Monday meeting on Z-mix (with

#SharedCrypto

more details » Crypto lib discussion #sharedcrypto #crypto-lib When Weekly from 8am to 9am on Monday Pacific Time - Los Angeles Where https://zoom.us/j/594175308 (map) Calendar labs@....

#SharedCrypto

Hi Everyone, This is just a reminder for tomorrow’s shared crypto library meeting. There are a few topics people have brought up for discussion: 1. An update on Zmix. 2. Discussion on when we can move

#SharedCrypto

Hi Everyone, This is just a reminder email for the shared crypto-lib meeting tomorrow. We have a lot of things to discuss, including: 1. Recap of the discussion at the Amsterdam hackfest. 2. Recent wo

#SharedCrypto

The paper on SNARGs that I was referring to today that has a good explanation of non-falsifiable assumptions in the introduction: https://eprint.iacr.org/2010/610.pdf Thanks, Hart

#SharedCrypto

Hi everyone, Attached is the link to the crypto-lib meeting notes document. https://docs.google.com/document/d/1Z_8o8k_PFRM4XfZyv9jH1_-IyN0CsCMI2JlrGsCX378/edit?usp=sharing Thanks, Hart

#SharedCrypto