Crypto
Stellar's Protocol 28: Adapter Upgrade Boosts Consensus Speed and Smart Contract Efficiency
Stellar's Protocol 28: Adapter Upgrade Now Live on Mainnet
A major upgrade, known as Protocol 28: Adapter, has been deployed to Stellar's mainnet. This update is primarily aimed at developers who create smart contracts on the Stellar blockchain, and it includes improvements to consensus mechanisms and smart contract functionality.
The adapter introduces three changes proposed in Stellar's Core Advancement Proposal (CAP): CAP-83, which improves consensus even under high network loads; CAP-85, which enables atomic upgrades for fleets of contracts; and CAP-86, which provides a safer way to migrate contract data by introducing a sparse data structure.
CAP-83 allows validators to vote on the next ledger even before receiving the entire transaction set. If the transaction set is incomplete or invalid after a certain period, validators can remove it from the current ledger. This change aims to improve throughput and reduce latency in case of slow transaction propagation.
CAP-85 allows developers to update multiple contracts with shared code in a single transaction, reducing the need for individual updates. It introduces externally managed executable code that enables contracts to reference common code managed by another contract.
CAP-86 introduces sparse data structures, allowing developers to add or remove fields from contract data without affecting existing contracts. This change enables more flexible and efficient data migration processes.
The adapter's adoption requires a basic update to the latest SDK for services using traditional SDKs. However, CAP-85 and CAP-86 are optional features that require new SDK adoption, and existing smart contracts do not need to be modified for compatibility.
A major upgrade, known as Protocol 28: Adapter, has been deployed to Stellar's mainnet. This update is primarily aimed at developers who create smart contracts on the Stellar blockchain, and it includes improvements to consensus mechanisms and smart contract functionality.
The adapter introduces three changes proposed in Stellar's Core Advancement Proposal (CAP): CAP-83, which improves consensus even under high network loads; CAP-85, which enables atomic upgrades for fleets of contracts; and CAP-86, which provides a safer way to migrate contract data by introducing a sparse data structure.
CAP-83 allows validators to vote on the next ledger even before receiving the entire transaction set. If the transaction set is incomplete or invalid after a certain period, validators can remove it from the current ledger. This change aims to improve throughput and reduce latency in case of slow transaction propagation.
CAP-85 allows developers to update multiple contracts with shared code in a single transaction, reducing the need for individual updates. It introduces externally managed executable code that enables contracts to reference common code managed by another contract.
CAP-86 introduces sparse data structures, allowing developers to add or remove fields from contract data without affecting existing contracts. This change enables more flexible and efficient data migration processes.
The adapter's adoption requires a basic update to the latest SDK for services using traditional SDKs. However, CAP-85 and CAP-86 are optional features that require new SDK adoption, and existing smart contracts do not need to be modified for compatibility.