[Mimblewimble] First development funding campaign

Hi all, We need your help. The new funding page explains why and our values better than I could here, so please have a look: http://grin-tech.org/funding.html Our first ask is for Yeastplume, who has been doing an outstanding job on the project for over 6 months now and has done so in addition

Re: [Mimblewimble] Hashed switch commitments

Just to add a couple of bits of info to this discussion - We were actually experimenting with including a secret key as part of the blake2 hashing - using the lock_height of coinbase outputs in the switch commit hash here (not merged, still under discussion, parked due to testnet1) - https://git

Re: [Mimblewimble] Hashed switch commitments

I need to resurrect this thread. What's currently implemented in Grin [1] is (vG + bH), BLAKE2(bJ), where the hash is truncated to 160 bits. Hashed switch commitments are supposed to give you two main properties: 1. Switch binding: even if you have unlimited computation power from to