Casper Labs will be tokenizing and listing equity in the company, via INX, a U.S.-regulated broker-dealer, alternative trading system and transfer agent. It’s an exciting milestone not only for Casper Labs, but for privately-held companies at large that want to open up new opportunities for investors seeking access to opportunities that were previously only available to select groups of institutions. What if we all could have invested in Facebook back in 2007 – or Amazon in 1995?

Read more on CasperLabs blog here:
https://www.casperlabs.io/blog/casper-labs-to-tokenize-and-list-equity-shares-on-inx-platform

Mrinal Manohar CEO at CasperLabs was a special guest on the recent RobotCache podcast focusing on the gaming industry and game development. His insights about Casper's role and vision in this dynamic industry are not to be missed. Tune in to learn more about what we're doing at Casper. It promises to be an engaging and enlightening listen!

https://podcast.robotcache.com/

🔊 Casper Wallet has just launched its 1.4.0 update, bringing important enhancements to its user experience.

🌟 Users can now send and receive $CSPR directly within their wallet, simplifying transactions and boosting efficiency.

🌟 For ERC-20 token collectors, the new update enables sending and receiving of any ERC-20 token on the Casper Network, greatly simplifying token management.

🌟 A noteworthy new feature: users can now replenish their $CSPR balance more easily. Direct purchase of $CSPR using a debit or credit card is now possible, thanks to the innovative Topper integration.

Join the CSPR product hub on Telegram here
https://www.tg-me.com/CSPRhub

This live update underscores Casper Wallet's commitment to continuously enhancing its user experience. For more details, and to support and retweet follow this link
https://twitter.com/casper_wallet/status/1682400047999369217?s=20

🚨‼️ Attention, the CoinList Twitter account has been hacked, do not interact with it. Always be vigilant.

Join the WOLF Financial Spaces event to hear from Mrinal Manohar alongside INX Group and many other speakers on the topic of Tokenizing Equity. LIVE NOW!

➡️ Join here

We look forward to reconnecting with you during our Twitter Space next month! After a summer break ☀️

Behind the scenes, our dedicated team is tirelessly working to refine and enhance the platform for your benefit.

Remember to stake your $CSPR tokens, enabling you to relax and fully enjoy your holidays.

Why staking is crucial for Layer 1 blockchains

At Casper, we are deeply saddened to relay the tragic news of our colleague Taylor Acree's passing. Known in our community as @Taylor_CasperLabs on Telegram and as Kavma on Discord, Taylor was a cornerstone of our Technical Support team. Tragically, he lost his life due to complications arising from a head injury on July 6th.

Taylor joined us as our first support engineer in February 2021, bringing with him extensive experience from notable firms such as AT&T, Live Nation, and Joynet. More than just a coworker, Taylor was a friend and a source of inspiration within our digital environment. His authenticity, kindness, and unwavering commitment to our blockchain project resonated strongly, even within our remote, virtual workspace.

In light of these circumstances, we've established a GoFundMe page to support Taylor's wife Jenny and their family during this difficult time. We warmly invite you to contribute and help in any way you can: https://gofund.me/138376e6.

Taylor's contributions to Casper are enduring, leaving a lasting impact on our project and community. His passion, dedication, and friendly spirit enriched our remote work environment, drawing us closer as a team. Rest in peace, Taylor. Your absence reverberates through our community.

Join this Month's Discord Developer Community Call for several technical updates!

We have Medha Parlikar, CTO @ CasperLabs join us to talk about the much-anticipated 1.5.2 upgrade. You don't want to miss this!

🗓 29th August, 6 PM CEST | 4 PM UTC
📍Join Here

🚀 Casper 1.5 offers improved experiences across the board for the Casper users, including streamlining the node creation process on the network, key security upgrades and a more accurate gauge for estimating future transaction costs, along with the ability to more efficiently redelegate tokens.

https://casper.network/en-us/news/casper-upgrade

On the Real Maxime Podcast, Mrinal Manohar, CEO of Casper Labs, discusses his journey from Bain Capital to leading billion-dollar TMT sector investments. Tune in for the insightful conversation!

Listen here

Mrinal Manohar recently sat down with Jeff Wilser at CoinDesk to discuss the realistic path forward for blockchain and AI.

Read full article

We are back tomorrow with the monthly Twitter Space!

Tune in to hear updates about our presence (and goals!) at Token2049 and other ecosystem news 👇

🗓 26 September, 6 PM CEST | 4 PM UTC
📍 Set Reminder & Join Here

📢 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

❗ Casper Node Release 1.5.3 Information ❗

Summary:
Casper network v1.5.3 update is a patch release which includes bug fixes, security fixes and some enhancements to the network operations.

Informational: There are no high priority or severity defects open for release v1.5.3, however we will be including an enhancement in the next release, where the last_progress of the status endpoint will be updated on every block being executed when in validate mode.

Key Changes:
1. In v1.5.3 we fixed a bug, where an existing delegator to a validator, who had exceeded the limit of 1200 delegators per validator was unable to increase their delegation stake to that validator.

2. 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.

3. 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 [], https://github.com/casper-network/casper-node/pull/4272.

4. 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.

5. We did some optimization in the storage component which fixed a bug - where users were reporting missing transfers.

6. The BlockValidator component has also been enhanced to reduce the number of fetch events.

7. Couple of security updates and reward fixes have also been added to the release, the details of which will be furnished post Mainnet release.

How do the changes impact Network Operators?
There is no impact to network operations and no downtime. The operators may notice an improvement to historical syncing.

How do the changes impact Smart contract/dApp/sdk Developers?
There is no impact to existing contracts and our contract developers are highly encouraged to test their existing contracts on integration or testnet version of 1.5.3. PS: Bullet 4 under key changes above is of value to our developer community,


Mainnet Activation Oct 12 2023
Installation Instructions https://github.com/casper-network/casper-node/wiki/Upgrade-to-Casper-node-v1.5.3

Dear Casper Community,

The upcoming Developer Community Call scheduled for today has been cancelled.

We apologize for any inconvenience this may cause and appreciate your understanding. We look forward to engaging with you all in our next session. Please stay tuned for updates on the next call.

Thank you for your ongoing support and understanding!

The Casper Team

Dear Community and Validators,

We have identified an issue with the 1.5.3 mainnet upgrade. Our core team is working on a fix in coordination with the validators. Updates and a post-mortem will be shared soon.

Thank you for your understanding.

Casper Network v1.5.3 Release Memo

Summary:
Casper network v1.5.3 update is a patch release which includes bug fixes, security fixes and some enhancements to the network operations.

Informational: There are no high priority or severity defects open for release v1.5.3, however we will be including an enhancement in the next release, where the last_progress of the status endpoint will be updated on every block being executed when in validate mode.

Key Changes:
1. In v1.5.3 we fixed a bug, where an existing delegator to a validator, who had exceeded the limit of 1200 delegators per validator was unable to increase their delegation stake to that validator.

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.

1. 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 [], https://github.com/casper-network/casper-node/pull/4272.

1. 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.

1. We did some optimization in the storage component which fixed a bug - where users were reporting missing transfers.

1. The BlockValidator component has also been enhanced to reduce the number of fetch events.

1. We fixed an issue with users re-delegation, where a user trying to re-delegate under a specific node state, that is when the validator is evicted at the same time as the delegation is being processed, would result in lost funds.

1. Couple of security updates around wasm interpreter backport and use of a private fork of parity-wasm and fixes around overflow conditions during specific reward calculation scenarios have also been added to the release.

How do the changes impact Network Operators?

1. There is no impact to network operations and no downtime. The operators may notice an improvement to historical syncing.

How do the changes impact Smart contract/dApp/sdk Developers?

1. There is no impact to existing contracts and our contract developers are highly encouraged to test their existing contracts on integration or testnet version of 1.5.3.