Kaspa network brings the initial stable Rusty Kaspa (RK) node to the table, via which they will be moving towards an enhanced and maximized engine.
Presently, being a segment of open beta, RK nodes consist of one-fourth of the P2P network and 29% related to hashrate mined via them.
Transitioning to RK is critical for prime network advancements like speeding up the mainnet to 10 BP, scaling to DagKnight, backing smart contract opcodes, and other factors. It offers instant advantages to node managers, such as near-constant storage, quick syncing, and an rPC software stack.
The company seeks slow and steady progress wherein added nodes shift towards RK. It offers complete guidance for scaling, depending on individual use cases like rust open beta participants, galang node managers, galang archive node managers, mining pools and exchanges, wallet builders and casual users.
The RK node comes with a CLI connection akin to golang nodes. The CLI alterations include RPC defaults to localhost, UPnP backed by default, configuration file format, and configurable RAM cache utilization.
A robust software stack has been created on the RK codebase. There is the KNG, a desktop service filled with various features incorporating the RK P2P node and the potential to link up with the public P2P node framework.
Added to that is the WASM SDK, which allows the rusty Kaspa infrastructure to function in the WASM2 scenario, bringing about connectivity with JavaScript and TypeScript. This compatibility enables the RK infrastructure to be utilized within Web3 browsers, Node.js scenarios, and Chrome browser extensions.
Credit: Source link
