Search Results for "parallel"

conflux-rust is the Rust implementation of Conflux, a high-performance Layer 1 blockchain designed to deliver high throughput without compromising decentralization or security. Conflux introduces a Tree-Graph consensus mechanism that allows parallel block processing while maintaining consensus integrity. This implementation focuses on performance and is compatible with the Ethereum Virtual Machine (EVM), enabling developers to deploy smart contracts written for Ethereum. It provides a robust foundation for dApps, DeFi, and Web3 applications in regions requiring regulatory compliance and scalability.

Libplanet is a .NET library for creating multiplayer online game in decentralized fashion, which means the whole gameplay occurs on a peer-to-peer network among equal nodes rather than an authorized central server. Under the hood, it incorporates many features (e.g., digital signature, BFT consensus, data replication) of a blockchain.

...Unlike Proof of Work, PoST leverages unused hard drive space to secure the network, enabling anyone with a computer to participate without specialized hardware. Spacemesh introduces a mesh-based block DAG (Directed Acyclic Graph) structure for scalable and parallel consensus. The project aims to build a decentralized, permissionless, and egalitarian financial operating system accessible to everyone.

...It is useful for developers who need testing, deployment, transaction handling, chain data access, and contract interaction tools in one workflow. The toolkit supports advanced development needs such as cheatcodes, state forking, fuzz testing, multicall, parallel test execution, and debugging-oriented utilities. Its main value is giving Starknet developers a Foundry-style experience tailored to Cairo and Starknet contract development.

...The most salient feature of the LBRY blockchain is the association of a normalized string of characters (a “name”) with a structured set of metadata. This coupling is called a claim. The LBRY blockchain stores names and metadata in a parallel Merkle tree, separate from the tree used to store transaction data. This allows LBRY URLs to be trustfully resolved even without a full copy of the blockchain.