Here you will find the most frequently asked questions about RSK, its vision, technology and other aspects
Navigate our main topics
Changes that aim to improve the network in terms of privacy, scalability, security or ease of use will be proposed by RSK Labs team, as well as the rest of the RSK community. The RSK community must collectively decide to accept or reject any change proposed by RSK Labs or by any other member of the community. While we do not have the ability to control community decisions, we believe that proposals that are aligned with the original RSK whitepaper will be more likely to be accepted by the community than those that are highly misaligned with the original Whitepaper.
RSK Labs has no right or ability to force a hard-fork on the RSK network. Also, RSK LABS WILL NEVER PROPOSE A FORK TO INTERVENE IN A CONFLICTING SITUATION BETWEEN PRIVATE PARTIES (SUCH AS THE DAO EVENT). THE ONLY HARD FORKS THAT RSK LABS WILL EVER PROPOSE ARE THOSE THAT IMPROVE THE SECURITY, PRIVACY, FAIRNESS OR FUNCTIONALITY OF THE RSK PLATFORM.
RSK Labs is working on a RSK Improvement Proposal or RSKIP for a protocol code-named SIGILO to provide transaction privacy. Some members of the community are also evaluating a zCash-style privacy for RSK. Additionally, RSK Labs is working on an enterprise version of the RSK platform with PBFT consensus that will provide transaction privacy by default. The primary goal of the RSK platform, however, is to help companies integrate with the network.
RSK Labs presented an RSKIP to enable user-defined signature schemes (also called “account abstraction”). This means that RSK users will be able to choose other signature schemes for their accounts (for example, a quantum-cryptography-proof schemes). The RSKIP adds to accounts a state-less script that verifies transaction signatures, such as Merkle-Winternitz, RSA, edDSA.
If you cannot find an answer to your question here, contact us