Collaboration suite, end-to-end encrypted and open-source.
-
Updated
May 30, 2022 - JavaScript
{{ message }}
Collaboration suite, end-to-end encrypted and open-source.
FISCO BCOS是由微众牵头的金链盟主导研发、对外开源、安全可控的企业级金融区块链底层技术平台。 单链配置下,性能TPS可达万级。提供群组架构、并行计算、分布式存储、可插拔的共识机制、隐私保护算法、支持全链路国密算法等诸多特性。 经过多个机构、多个应用,长时间在生产环境中的实践检验,具备金融级的高性能、高可用性及高安全性。FISCO BCOS is a secure and reliable financial-grade open-source blockchain platform. The platform provides rich features including group architecture, cross-chain communication protocols, pluggable consensus mechanisms, privacy protection algorithms, OSCCA-approved (Office of State Commercial Cryptography Administration) cryptography algorithms, and distributed storage. Its performance, usability, and security have been testified by many institutional users and successful business applications in a live production environment.
A Decentralized Operating System for Zero-Knowledge Applications
The privacy-focused cryptocurrency
Bulletproofs are short non-interactive zero-knowledge proofs that require no trusted setup
RISC Zero is a zero-knowledge verifiable general computing platform based on zk-STARKs and the RISC-V microarchitecture.
Is your feature request related to a problem? Please describe.
Adding a new member to a Semaphore group changes the root, invalidating any currently-generated proofs. This makes it so that a transaction submitted with a valid proof can become invalid if another transaction modifying a group is submitted first.
Describe the solution you'd like
Root history kind of solves this (by accep
Tor Iptables script is an anonymizer that sets up iptables and tor to route all services and traffic including DNS through the Tor network.
A privacy-preserving blockchain on Substrate
using an invalid character in an import name gives no error information
Error [EPAR0370000]: ~
--> D:\Work\leo-playground\src/main.leo:1:12
|
1 | import test~.lib.func;
it should display the same error message as when an uppercase letter is used:
Error [EPAR0370012]: package names must be lowercase
Describe what you want implemented
Remove the bit_iterator macro.
Describe "Why" this is needed
As far as I can see we only invoke the macro once to create BitIterator8 so I don't see the need to have a macro for it. Creating BitIterator8 directly is much clearer.
Describe alternatives you've considered
Leave as is.
Additional context
NA
STARK-based virtual machine
Anonymous Airdrops using ZK-SNARKs
Solidity crypto libraries, ring signatures, proof of knowledge, packed signatures etc. with matching Python implementations for secp256k1 and (alt)BN-256
A zkRollup DEX & Payment Protocol
Zero-knowledge virtual machine written in Rust
A Virtual Machine for Zero-Knowledge Executions
Mobile apps for ente.io, a simple, encrypted photo storage.
Mobile ZK Puzzle Game with NFT rewards
A fix has been made for Macs using the intel chip as of this commit: https://github.com/AztecProtocol/barretenberg/tree/9861b2c230723e73c188865d47b67e161b0371f1
We should update the dependency in the aztec backend crate
In this PR we used the method from this post from Daniel Lubarov https://mirprotocol.org/blog/Adding-zero-knowledge-to-Plonk-Halo to update our blinding method to one that does not increase the degree of polynomials.
This method is sound, but the post was written for Halo2-style polynomial commitments which are hiding by nature, meaning they need
Welcome to Aleo. Where Applications Become Zero-Knowledge
Experimental zero-knowledge proof compiler in Rust macros
Proves knowledge of an ECDSA-P256 signature under one of many public keys that are stored in a list.
Collection of papers in the field of distributed systems, game theory, cryptography, cryptoeconomics, zero knowledge
A library for generating zk-STARKs.
Library for programming zk-SNARKs directly in Python
Add a description, image, and links to the zero-knowledge topic page so that developers can more easily learn about it.
To associate your repository with the zero-knowledge topic, visit your repo's landing page and select "manage topics."
#306 addresses a term-precedence bug with exponentiation. However, we do not have an end-to-end test case for this.
It should be included, ideally for all operators.