Bihu consists of two main components: an identity system and a community for crypto investors. Bihu ID(bihu.com)is a self-sovereign ID system based on blockchain technology and decentralized storage. It aims to be the gate keeper for Web3.0, in order to protect users’ wealth, data and privacy. Bihu ID strives to be the 'KEY to Digital Liberty'. Bihu Community is an platform for crypto investors to share and obtain token-investment-related information. It will the first use case for Bihu ID. KEY is the utility token for both Bihu ID and Bihu Community. It is an ERC20 token on the Ethereum blockchain. KEY is used to incentivize content generation within the Bihu Community, as well as the primary method for good content discovery. KEY also is the value exchange method within the Bihu Community, such as tipping between users. Since a single Bihu ID lives on multiple blockchains, it is desired that users will be able to pay KEY for generic network fees (AKA gas). KEY also acts as the generic payment method in the Bihu ID system, for instance, to recover lost IDs.
Beam Mimblewimble is a scalable, fungible, and confidential cryptocurrency based on the Mimblewimble implementation. WHY BEAM? Core features include complete control over your privacy, All transactions are private by default, No addresses or other private information are stored on the blockchain, Superior scalability due to compact blockchain size, Opt-in Auditability, Support online and offline transactions, atomic swap, hardware wallets integration. Governance model No premine, No ICO. Backed by Treasury Establishing a non-profit foundation to govern the protocol after Mainnet launch How does it work? Wallets’ owners create new transaction using secure channel either online or offline Both wallets participate in signing the transaction using Schnorr protocol Wallet sends transaction to node Each transaction contains a list of Inputs and Outputs represented by Pedersen Commitments, as well as explicit fees and kernels. Each transaction also contains non-interactive zero knowledge range proof to verify that the output transaction value is positive Transaction is verified by the node Each transaction is verified with respect to the recent blockchain state which is stored as a Merkle Tree. The root hash of the tree is recorded in block header along with a proof of work. In addition, each node periodically creates compacted history to allow ‘fast sync’ of new and existing nodes. Transaction is added to the mining pool A block is mined every minute and is sent back to the node for verification and distribution. Mined blocks containing the new transactions are sent to the known peers A valid block that is extending the longest chain is accepted as a new Tip and propagated further until full consensus is reached. Fast sync When a new node connects to the network for the first time it can request compacted history containing only system state and blockchain headers. There is no need to retrieve the entire transaction history.