As you know, I'm a big fan of crypto dapps and Status messenger I use for years. To be honest - still so many people even among my friends don't use it. But it's very usable - you can use it as dapp browser and Ethereum wallet.

I'm happy that Status is being actively developed and that's why I'm sharing the technical updates about Nimbus client. I understand that it might be too technical post, so for non-technical people - I just suggest - start using Status. Try it. You can message me there, you can find me by @ cryptotexty, or cryptotexty.stateofus.eth (this is my ENS name which I bought in the past for only 10 SNT).

Nimbus has released a production-ready version of its validator client, addressing a key demand from node operators and advanced users. The client is highly performant and requires low resources, allowing it to run on a range of devices — from embedded systems to enterprise servers.


Release v22.11.0 allows users to run the Nimbus validator client independently with beacon nodes from other clients, giving operators greater flexibility and the ability to introduce Nimbus into their existing setups with minimal change. This configuration is ideal for operators running hundreds to thousands of validators.

Here are also 10 major updes for Nibmus in 2022:

The long-awaited split client mode. This mode enables a more flexible setup: running the Nimbus validator client independently of the beacon node.

Marked enhancements leading up to a successful Ethereum Mainnet Merge and the stable performance of Nimbus in the post-merge network.

Support for trusted node sync (also known as checkpoint sync).

Support for external block builders — aka MEV — leading up to the Merge.

Support for the Ethereum-defined REST API endpoints for light client sync.

Beta release for the Nimbus stand-alone light client.

Improved metrics to track validator activity.

Continued improvement in client efficiency. Now Nimbus requires less CPU, lower bandwidth, and smaller memory space.

Support for the Keymanager API and remote keystores. With the Keymanager API, users can add, remove and migrate validators on the fly.

Significant improvement in the Nimbus guide in terms of content and coverage.

Binance is announcing the 29th project on Binance Launchpad - Hooked Protocol (HOOK). The token sale for Hooked Protocol will follow the Launchpad subscription format, with the recording of user BNB balances starting at 2022-11-24 00:00 (UTC).

By the way, if you don’t have a Binance account yet - with this special partner link, you can get -20% trading fees. And, of course, an additional -25% if you use BNB.




Binance will record user BNB balances for seven days from 2022-11-24 00:00 (UTC) to 2022-12-01 00:00 (UTC). The final BNB holding amount for each user will be determined as the average of the seven days, using the Daily Average BNB Balance calculation previously announced here.

HOOK Token Sale Details:

Token Name: Hooked Protocol (HOOK)

Launchpad Hard Cap: 2,500,000 USD

Hard Cap Per User: 15,000 USD (150,000 HOOK)

Total Token Supply: 500,000,000 HOOK

Total Tokens Allocated to Binance Launchpad: 25,000,000 HOOK (5% of Total Token Supply)

Public Sale Token Price: 1 HOOK = 0.1 USD (price in BNB will be determined prior to subscription)

Token Sale Format: Subscription

Supported Sessions: BNB only

Subscription Timeline:

Preparation Period 2022-11-24 00:00 (UTC) to 2022-12-01 00:00 (UTC): During this period, user BNB balances will be calculated in hourly snapshots for each day over a seven-day period. Your final average daily BNB balance over these seven days will determine the maximum amount of BNB that you can commit later on.

Subscription Period 2022-12-01 06:00 (UTC) to 2022-12-01 09:00 (UTC): Subscription will open at this time for all eligible users for a three-hour period. Users must also sign the Token Purchase Agreement at the same time, prior to committing their BNB. Please note that once committed, your BNB will be locked and you will not be able to redeem or access any other functions such as transfers, withdrawals or trading until final token distribution.

Calculation Period 2022-12-01 09:00 (UTC) to 2022-12-01 10:00 (UTC): Subscription closes and token allocation calculation begins.

Final Token Distribution 2022-12-01 10:00 (UTC): Your final token allocation will be calculated and the corresponding BNB will be deducted from your already-locked BNB amount. Once deducted, your HOOK and BNB tokens will both be transferred to your spot wallet.

To learn more about Hooked Protocol (HOOK), read Binance Research's in-depth report here.

How to work for Cardano blockchain



Article:
https://read.cash/@cryptotexty/how-to-work-for-cardano-blockchain-185476a1

Акція від Binance та WOG - заправляй пальне і вигравай призи!



https://read.cash/@cryptotexty/akciya-vid-binance-ta-wog-zapravlyai-palne-i-vigravai-prizi-655dffb7

My crypto-blog readers know that I like to read and read almost all interesting crypto-related books. It helps to understand the market better, the history of projects, and the people behind them.

For years I'm using Status crypto messenger and I was happy to find a history of Status ICO in the book "The Cryptopians: Idealism, Greed, Lies, and the Making of the First Big Cryptocurrency Craze" by Laura Shin.

"Another big ICO went up to bat, but this time it was going to try other ideas to democratize the sale. Jarrad Hope, a Perth native and internet marketer who had made money with poker bots, and his longtime business partner Carl Bennetts were building Status, an open-source messaging platform, and web 3.0 browser. After getting negged by VCs, Jarrad and Carl turned to the crowd. At first, their Slack had more than three thousand fans, but once Status.im announced its ICO, membership ballooned to more than fifteen thousand."


Since 2017 many ICOs are already forgotten, didn't accomplish anything, or just vanished, but Status messenger continues its development throughout these years. An interesting point is that Status founders didn't give up after the rejection by VCs but turned to the crowd. That's one more proof that when you have a good idea and team - there are always ways to fund it and develop it.

Let's read one more passage about the Status ICO process:

The scheme, the white paper said, was “an attempt to discourage big money investors, whales, from consuming the entire SNT allocation.” If someone sent too much money, some would be accepted, the rest returned. When the sale started at 4 a.m. Singapore time, Jarrad’s heart sank. No money was coming in. He eventually realized people were sending in such large amounts that the contract was rejecting the transactions. Just minutes in, there were almost eleven thousand unconfirmed transactions worth 450,481 ETH ($161.7 million). This clogged up the network with many more transactions than it would have had otherwise, since people whose transactions were rejected then sent new ones. It was nearly impossible for anyone to do anything else on Ethereum. Some bids for Ethereum domain name auctions failed because Ethereum itself was too congested. The Status ICO went on for twenty-four hours, allowing every time zone to participate. By the end, Status had raised more than $100 million... However, the contract had refunded more than it had accepted, so without the hidden ceilings, it would have garnered over $200 million. Unfortunately, Jarrad says, the design didn’t deter whales, who bought tokens under each cap but later complained they had paid a lot in transaction fees.

That's an interesting to remeber to see how the Ethereum blockchain was overloaded during those times (this was also a case with other ICOs). But also that's interesting to see how Status team decided to make more equal ICO, and to include as many people as possiple, preventing whales to buy the majority of tokens.

It's also inreresting to see that Status would have collected over $200 million and because of making the cap and increasing the time of ICO - got much less. But of course the main thing is that Status messenger became one of the most interesting crypto-projects, which brings new crypto adoption, web3 popularization and the real use-case as people will always need more ways to communicate and transact.