EthereumCommonwealth
BOUNTY: Privacy protocol implementation (zero-coin/bulletproof)
Proposal
The Callisto team allocates 6,000,000 CLO for the implementation of one of zero-knowledge privacy protocols:
We are willing to hire a developer or a group of developers to implement one of the described protocols at rust-callisto client (a port of Ethereum's Parity).
Payment will be made in 6 stages and doubled as goals are achieved:
- 187,500
- 187,500
- 375,000
- 750,000
- 1,500,000
- 3,000,000
We are open for any proposals [email protected].
Changing the code called EIP 1024, created by the developer Toup Alabi, should implement a simple encryption-decryption function on the Ethereum block system.
Explaining his proposal, Alabi said that "EIP 1024 allows you to generate a pair of encryption keys using your private Ethereum key. A new pair of keys can be used to securely transfer data to any other Ethereum address. "
Again, while such technologies already exist, EIP 1024 sets a standard that will work across the entire Ethereum network. That is, application developers do not have to worry about creating multiple implementations of encryption and you can just concentrate on creating your application.
@Dexaran Could it be better to do so? My team can do this.
EIP 1024 and zero-coin/bulletproof do different things. EIP 1024 allows to send encrypted data, zero-coin/bulletproof - allows to make secure payment with hidden payment amount and recipient address.
@yuriy77k I'm aware of the problem https: //satoshi.team If we had the opportunity to securely encrypt data, then it's easy to implement the zero-knowledge proofs protocol on a smart contract. In this case, it is possible anonymously to carry out mutual settlements not only CLO, but also in any tokens. In this case, no one will know the amount, the address of the sender, or the address of the recipient.
@AnonymizerEthereum I've studied your website, but I have not found what kind of protocol Zero-knowledge proof you use.
In the whitepaper it is written: "This smart contract is
verified (Contract Source Code Verified) and is always available for audit.". Can you give us this Contract Source Code for audit by our Security Department? You can open new issue for it.
@yuriy77k Yuri, the source code is here But I do not understand why you need this contract. It is written for Ether. If it is possible to encrypt the data at the protocol level, then the smart contract for the anonymous transfer of the CLO and the token will be completely different. The principle can also be looked at in this scheme
@AnonymizerEthereum, I need a smart contract source code to see where the protocol of zero-knowledge proofs is being used, because it's not indicated anywhere on the principle scheme.
@yuriy77k Yuri, the source code is here
It is known who uses a smart contract, but no one else knows anything about the transactions.
@AnonymizerEthereum thank you.
Give me, please, source code for contract Helper too.
@yuriy77k The proposed code change is necessary for us to exclude the need to use this smart contract (Helper).
P.S. Helper is responsible for encryption. There's nothing unusual there. The source code will be hidden while our project is working.