Bytecoin is the first cryptocurrency created with CryptoNote technology. Bytecoin allows users to make absolutely anonymous money transfers through the CryptoNote algorithm. CryptoNote uses CryptoNote ring signatures to provide anonymous transactions and allows you to sign a message on behalf of a group. The signature only proves the message was created by someone from the group, but all the possible signers are indistinguishable from each other. Even if outgoing transactions are untraceable, everyone may still be able to see the payments received and thus determine one's income. By using a variation of the Diffie-Hellman exchange protocol, a receiver has multiple unique one-time addresses derived from his single public key. After funds are sent to these addresses they can only be redeemed by the receiver; and it would be impossible to cross-link these payments. As a primarily peer-to-peer (p2p) payment system, Bytecoin has many of the same use-cases as Bitcoin. Created in 2012, Bytecoin is one of the earliest developed cryptocurrencies. Until recently, the team behind the coin has kept themselves anonymous. Now, though, they’ve opened up multiple communication channels, removed some layers of anonymity, and even built several local communities. Bitcoin’s PoW consensus algorithm heavily favors miners that use powerful GPU and ASIC machines over those trying to mine with CPUs. This causes the network to centralize around the more powerful miners. Bytecoin attempts to close the gap between these two classes of miners with a new algorithm, Egalitarian Proof-of-Work (PoW). Egalitarian PoW uses a version of skrypt, a proof of work function similar to the hashcash function used by Bitcoin. The difference between the two is that scrypt isn’t memory bound. Because of this, you can produce highly efficient CPU mining rigs. GPUs will always be about 10 times more effective, though. The Bytecoin project has been fairly fractured since its inception in July 2012. Previously, several isolated teams worked on the project without seemingly communicating with each other. This led to numerous forks and versions of the coin. In July 2017, the team decided to change their image and provide more transparency to the community. The team still remains pseudo-anonymous by only providing names and headshots on their webpage – no bios or social media links. But, it’s tough to expect more from a project that’s focused on privacy. The team has been busy at work refactoring their code and are planning to release a new public API on February 6, 2018. They’ll also be entering the Asian, Middle East, and African markets throughout 2018.
Mainframe is the platform for decentralized applications. Resistant to censorship, surveillance, and disruption, the Mainframe network enables any application to send data, store files, manage payments, run tasks, and more. With the exception of a catastrophic asteroid event or an aggressive alien invasion, the Mainframe network is simply unstoppable. We build with five fundamental principles as our guide. The Mainframe network is the messaging layer for the new web. This goes beyond human-to-human messaging. There are many use-cases and applications for reliably, privately, and securely routing data packets through the Mainframe peer-to-peer network. Mainframe is resistant to censorship, surveillance, and disruption. With the exception of a catastrophic asteroid event or an aggressive alien invasion, the Mainframe network is simply unstoppable. We build with five fundamental principles as our guide. The Mainframe platform is a developer-friendly SDK providing all these services in a secure peer-to-peer fashion. It is designed to be modular and pluggable, so developers and users can configure which projects they prefer to use for the underlying service layers. Our mission is to delight developers by providing an SDK that is well-documented, supported and backed by strong developer communities. Because it is not always clear which projects will gain the most momentum, and because developers often have varying preferences, we feel that it is important to design our underlying service architecture to be modular and pluggable, allowing developers and users to configure which projects they prefer to use for each service layer and abstracting away as much of the differences as possible. A single medium of exchange in the form of Mainframe tokens (MFT) is also used to improve the developer and user experience. Where underlying service layers cannot be retrofitted to accept MFT, we will implement atomic swaps between native service-layer tokens and MFT.