Attention - Smart Contract, DApp and SDK Developers. Casper Node 1.
01 Oct 2023, 08:28
š¢ Attention - Smart Contract, DApp and SDK Developers š¢
Casper Node 1.5.3 will soon be in the integration and then subsequently to testnet environment. Whilst there is no impact to existing contracts and we highly recommend and encourage Smart Contract, DApp and SDK developers to test their existing contracts on integration or testnet version of 1.5.3.
We also recommend checking the new feature that we have added and taking any necessary steps where required We have added a configurable way via the config and chainspec files, to allow for a small amount of clock drift to prevent the deploy acceptor from rejecting deploys that are future dated. The top ceiling value is set in the chainspec and adjustable value in config, PR.
Other key changes;
1. We addressed an issue in v1.5.3, where post upgrade to v1.5.2 some nodes exhibited slow historical sync, operators would now notice an improvement in performance when historically syncing.
2. We fixed an issue in v1.5.3 where the āchain_get_block_transfersā rpc returned ānullā instead of an empty array ā[]ā , this would manifest when a joiner node is synchronizing historical blocks and the blocks do not have any deploys. This followed the data definition of the JSON RPC, but was unexpected behavior for users who did not read the specifications closely. Earlier when querying the block using the chain_get_block_transfers would return null, this is now changed to [],
3. The BlockValidator component has also been enhanced to reduce the number of fetch events.
4. Couple of security updates have also been added to the release, the details of which will be furnished post Mainnet release.
Important Note:
Testnet Activation Point 10827
Date - 2023-10-02 14:28 UTC
Same news in other sources
4
02 Oct 2023, 13:58
Attention blockchain enthusiasts! š¢
The digital world is changing, and NFTs are leading the way.
In this episode of the Casper podcast, we explore the world of NFTs. Discover how NFTs are reshaping the way we interact with digital content.
Our special guest, blockchainā¦
Attention blockchain enthusiasts. The digital world is changing, and NFTs are leading the way.
Attention blockchain enthusiasts! š¢
The digital world is changing, and NFTs are leading the way.
In this episode of the Casper podcast, we explore the world of NFTs. Discover how NFTs are reshaping the way we interact with digital content.
Our special guest, blockchainā¦
01 Oct 2023, 14:30
Top reasons why you should build on Casper today:
1. It's a new month.
2. See above.
Top reasons why you should build on Casper today:. It's a new month. See above.
Top reasons why you should build on Casper today:
1. It's a new month.
2. See above.
01 Oct 2023, 14:15
Finish the sentence:
Casper Network is _____
Finish the sentence:. Casper Network is _____.
Finish the sentence:
Casper Network is _____
01 Oct 2023, 08:28
š¢ Attention - Smart Contract, DApp and SDK Developers š¢
Casper Node 1.5.3 will soon be in the integration and then subsequently to testnet environment. Whilst there is no impact to existing contracts and we highly recommend and encourage Smart Contract, DApp and SDK developers to test their existing contracts on integration or testnet version of 1.5.3.
We also recommend checking the new feature that we have added and taking any necessary steps where required We have added a configurable way via the config and chainspec files, to allow for a small amount of clock drift to prevent the deploy acceptor from rejecting deploys that are future dated. The top ceiling value is set in the chainspec and adjustable value in config, PR.
Other key changes;
1. We addressed an issue in v1.5.3, where post upgrade to v1.5.2 some nodes exhibited slow historical sync, operators would now notice an improvement in performance when historically syncing.
2. We fixed an issue in v1.5.3 where the āchain_get_block_transfersā rpc returned ānullā instead of an empty array ā[]ā , this would manifest when a joiner node is synchronizing historical blocks and the blocks do not have any deploys. This followed the data definition of the JSON RPC, but was unexpected behavior for users who did not read the specifications closely. Earlier when querying the block using the chain_get_block_transfers would return null, this is now changed to [],
3. The BlockValidator component has also been enhanced to reduce the number of fetch events.
4. Couple of security updates have also been added to the release, the details of which will be furnished post Mainnet release.
Important Note:
Testnet Activation Point 10827
Date - 2023-10-02 14:28 UTC
Attention - Smart Contract, DApp and SDK Developers. Casper Node 1.
š¢ Attention - Smart Contract, DApp and SDK Developers š¢
Casper Node 1.5.3 will soon be in the integration and then subsequently to testnet environment. Whilst there is no impact to existing contracts and we highly recommend and encourage Smart Contract, DApp and SDK developers to test their existing contracts on integration or testnet version of 1.5.3.
We also recommend checking the new feature that we have added and taking any necessary steps where required We have added a configurable way via the config and chainspec files, to allow for a small amount of clock drift to prevent the deploy acceptor from rejecting deploys that are future dated. The top ceiling value is set in the chainspec and adjustable value in config, PR.
Other key changes;
1. We addressed an issue in v1.5.3, where post upgrade to v1.5.2 some nodes exhibited slow historical sync, operators would now notice an improvement in performance when historically syncing.
2. We fixed an issue in v1.5.3 where the āchain_get_block_transfersā rpc returned ānullā instead of an empty array ā[]ā , this would manifest when a joiner node is synchronizing historical blocks and the blocks do not have any deploys. This followed the data definition of the JSON RPC, but was unexpected behavior for users who did not read the specifications closely. Earlier when querying the block using the chain_get_block_transfers would return null, this is now changed to [],
3. The BlockValidator component has also been enhanced to reduce the number of fetch events.
4. Couple of security updates have also been added to the release, the details of which will be furnished post Mainnet release.
Important Note:
Testnet Activation Point 10827
Date - 2023-10-02 14:28 UTC