Hi Brian, Both of these protocols are based on RFC 4880, which I have linked below. https://tools.ietf.org/html/rfc4880 The RFC 4880 standard, and the crypto that it uses, all underwent heavy peer rev

This is well articulated. Thanks Marko for taking the time to explain this rationale. To clarify my own walls of text on this topic, while I think that (as always pointed out by Zaki Manian) Hyperledg

Hi Everyone, It looks like I’m in the minority here in terms of seeking academic review for consensus (and perhaps crypto) contributions. This is a democratic process, after all, so I’ll just have to

Hi Stefan, and all, Earlier today in the discussion of the Swirlds/Babble consensus algorithm during the TSC meeting, the topic of fairness came up. The proposal claimed that the consensus algorithm w

RE: [Hyperledger Project TSC] Continuing the TSC Discussion Hi Martin, The attack I am describing seems to work for arbitrary N. You only need a constant (in this case, 4) collusion in order to make t

RE: [Hyperledger Project TSC] Continuing the TSC Discussion Hi Martin, In the case that there are two competing transactions, the one that is propagated more quickly will win out. Bob’s transaction wi

RE: [Hyperledger Project TSC] Continuing the TSC Discussion Hi Martin, I think you are correct in that a fork will be created. However, if I understand, the fork will be on T_1’s validity, not T_2’s.

RE: [Hyperledger Project TSC] Continuing the TSC Discussion Hi Martin, I’m not Frank, but I assume this was meant to be sent to me. We should probably discuss this in the future off the TSC mailing li

+1. I agree with this approach completely. Do people have opinions on the best way to try to approach something like this? Would a consensus working group be a good start? We haven't done anything lik

Hi Brian, This is a good question, and a good thing to consider. I'm not an expert on all of the code bases like the maintainers and some of the core contributors are, but it seems to me that consensu

Hi Everyone, In light of the discussion on the TSC election procedure today, I had a few comments. The discussion centered around who was eligible to run for the TSC. While this is important, I also t

+1 Thanks, Hart

Hi Everybody, In regards to hackfest scheduling, I just wanted to point out that Money 20/20 is October 22-25 this year, and I don’t think this got brought up in the discussion today. I assume many pe

Hi Brian, One of the key features of privacy-preserving sidechains or lightning network-inspired projects is the ability to move things (the outputs of the all of the transactions on the subnet) back

Hi Everybody, This is attracting far more attention than I would expect on a technical list. My view on this is essentially the following: as long as the name doesn’t conflict with another project or

+2 from me as well. Thanks, Hart

Hi Dan, Would you mind sending out a link to a commentable google doc? That will make questions much easier to ask and follow. Also, is anyone outside of Clause, Inc. planning on working on this proje

Hi Dan, That sounds like a great plan. Would you consider giving a brief intro to some of the legal aspects behind executable smart legal contracts at the hackfest? As someone with a non-legal backgro

Hi Everyone, I’d like to give an update on the whitepaper, which we are now calling “An Introduction to Hyperledger”. We (the whitepaper working group) are finally approaching completion of the whitep

Hi Arnaud, Thanks a lot of the feedback. We’d love for someone closely affiliated with the Iroha project to rewrite that section, if possible. For anyone reading this that’s close to Iroha and wants t