✨ Sticker Challenge Submission Ended! ✨

Hey Humanode community! 👋

The Humanode Sticker Challenge has officially ended. Thank you to everyone who participated and helped make a statement! 🎉

If you participated, you have 2 days to claim your Ninja NFTs on Tide. Remember, claiming the NFT is a must to be eligible to win your share of the prize pool.

📌 Steps to Claim Your NFT:
1. Head over to Tide
2. Obtain the Verified Human role in Humanode Discord
3. Submit your tweet, video and picture.

Make sure to claim your NFT by the deadline to ensure you're in the running for the rewards!

Good luck! 🥷✨

🚨Important Update for the Human Nodes 🚨

Hey hey, human nodes!

We recently encountered two incidents related to finality stalls (an occurrence when the consensus process fails to decide on the final state of the block within a specified period). As a quick response, we have implemented a workaround that is now deployed. Rest assured, devs are actively working on a more comprehensive fix, which we will ship after thorough testing.

🔑 Key Details about the issue:
The cause of the issue seems to be that with our network growing to over 1,000 validators (yes we have crossed the 1K nodes landmark), we are pushing the limits of our core consensus and gossip algorithms. This has caused us to encounter rarely visited code paths that are typically dormant. While Kusama and Polkadot, with whom we share our codebase have not seen these issues, we are committed to resolving this for the Humanode.

👉What you need to do:

Update your node. If you are running the node using Humanode Launcher, go to Settings and Click on Check for Peer Updates.

We’ll be closely monitoring the rollout via https://telemetry.humanode.io/ and you are welcome to follow along as well. The target version is f5bccf0d13193e070aeef1472a2a4726e836cd93

Note that this update will delay the finality target for 5 blocks behind the best block which is expected so no need to worry. Please adjust monitoring and your dApp settings accordingly.

We appreciate your cooperation and attention.

Humanode Core

Hey hey humanode community members!

We're pleased to announce that Humanode has crossed the milestone of 1000 validators.🎉

Yes, 1000 unique human nodes are now safeguarding the Humanode chain! 🤝

Unlike traditional networks relying on capital and computational power, Humanode is secured by real, unique humans across the globe, making it the most decentralized network.

While this is a major achievement within two years of mainnet launch, the goal is to expand to the technical limit of 10,000 validators.

If you’re not a human node yet, join us! Becoming a human node doesn’t require heavy investment or capital. You can find the details here: https://gitbook.humanode.io/docs/launcher/about

Hello humanode community members!

Paid Network, a decentralized crowdfunding powerhouse, has integrated BotBasher into its Discord and also with their newly launched gamification platform: The Rewards Odyssey to fight Sybil accounts: https://paid.network/Humanode

Join the Paid Network Discord and get your ‘Verified $PAID Warrior’ role: https://discord.gg/MMZdCxqSch

How do we protect DAOs against Humpy, who recently humped $25M from Compound?

Remember this ain't Humpy's first rodeo - he's hit Sushi, Balance, and others in the past. And while there's a debate on whether it's a governance attack, we know that governance attacks are a longstanding issue for DAOs with token-weighted voting.

So what can be done to deal with it? We at Humanode suggest:

1. Create a one account - one vote veto mechanism.
2. Split governance 50/50: 50% token-based voting, 50% based on one human = one vote

To implement one human = one account = one vote or hybrid DAOs using cryptobiomeric technology, check out our Biomapper SDK: https://github.com/humanode-network/biomapper-sdk

Humanode Biweekly vol.79

Stay up-to-date with all the latest developments, updates, and progress. Dive in! 👉

TL;DR
• Humanode has crossed the milestone of 1000 validators
• Finality incident analysis & resolution
• Human nodes update
• Subquery now supports data query from both Humanode Substrate and EVM
• Collaboration with Paid Network
• The Humanode Sticker Challenge submission ended

https://blog.humanode.io/humanode-biweekly-vol-79/

decentralized oracles loading...
[█████████ ] 97%

https://x.com/humanode_io/status/1818918422299672601

Supra, a leading provider of real-time data feeds and blockchain interoperability, has launched its oracle price feeds on the Humanode chain. This integration enhances dApp functionality on Humanode with reliable off-chain and cross-chain data from 85 blockchains.

Supra oracle price feeds will improve DeFi apps on Humanode by providing accurate asset prices and exchange rates as well as allowing decentralized lending, borrowing, and other Web3 applications.

Apart from that, Humanode will develop a cross-chain Biomapper using Supra, allowing users to pay fees from other blockchains and L2 solutions without holding HMND or buying from CEXs.

Learn more about the integration: http://blog.humanode.io/supra-is-now-humanodes-official-decentralized-oracle-provider/

Delve into the documentation to integrate Supra oracles into your dApps: https://github.com/humanode-network/biomapper-docs

Human nodes,
Please update your node to the latest version!

If you are running the node using Humanode Launcher, go to Settings and Click on Check for Peer Updates.

And to check what's new in the latest update, check the release notes.

Development Update
30th July – 6th August

Check out the latest from Humanode's development team:

🔺 Finality incident analysis
This month, we faced a finality stall, which was quickly resolved, and the chain is back to normal. Our incident analysis confirmed the root cause. The node responsible for the primary slot (A1) took unusually long to distribute its block. Consequently, the chain continued with the block produced by the secondary slot node (B1), which produced two more blocks (B2, B3). Nodes began voting to finalize B1 on the fork (B1, B2, B3). Meanwhile, A1 continued producing blocks on the best chain (A1, A2, A3, etc.), leading to a chain reorganization. Finalization on B1 remained in progress but couldn't be finished since B1 was not part of the best chain. The Parity team acknowledged the complexity of this issue.

Since then, we have improved our internal alert systems to promptly respond to potential finalization lags. The code related to Grandpa logic has been deeply studied, and we issued a fix for the Grandpa RPC endpoint in mainnet 119 runtime.

Last week, we started experiencing frequent finalization stops again, prompting the creation of a tracking issue, Humanode Issue #1104, to actively track all occurrences. The Parity team has actively engaged in resolving the problem, and our research has been instrumental, in leading to a proposed fix from their side. The regression test, which checks the logic for block finalization after chain reorganization, was used to validate the fix. The pull request containing the fix and our test was merged: Polkadot SDK PR #5153.

However, the fix was not rolled out immediately due to potential unknown impacts on certain modules. It was decided to first reproduce the problem and then observe network behavior with the fix. Last week, we successfully reproduced the block finalization stop within the dev environment.

According to our plan, if the fix shows specific results in the dev environment without any side effects, we will promptly roll it out to the mainnet.

🔺Gossip fix
Additionally, this week, we rolled back an update to improve the state of gossip. For more detailed information, visit the Humanode GitHub.

🔺 Exploring CVM attestation
We've collaborated with the Rustwasm team to address some Web WASM/Rust infrastructure issues. Stay tuned for the new version of the wasm-bindgen crate, which will include fixes for API generation and the async fn bindgen definitions.

🔺 Introducing a new flow for the web app
We continued integrating the new flow for the web app, including a transition to a new authorization signature format and an improved error display format for users, providing detailed text on why the error occurred.

🔺 Front-end updates
We have updated the active validators counter on the mainnet landing.

ELI5 on how Supra decentralized oracles work and why they stand out: https://x.com/humanode_io/status/1821196266509910032

📢 Community asked - we ship!

Update to the UX of BotBasher, our Discord integration.
In order to achieve max Sybil-resistance and privacy in BotBasher re-registration of accounts is impossible for a 6 months period. There was a popular issue for users with multiple accounts: they bonded a Discord account they had in the browser, which is different from their account in the app. On a scale of 10k-100k people coming at the same time for a few days many bioverified a wrong account.

Now after a private biometric session our app asks users to check and verify account name and user ID once again.

Hello, Humanode community! 👋🏼

It’s been a while since we’ve had a good sit-down, so we thought, why not do just that this Friday? We’re hosting Founders' Talk—nothing formal 😉 just a casual hangout where we can catch up, share what we’ve been working on, and get your thoughts.

Here’s the plan ⬇️

🗓 When: Friday, August 16
⏰ Time: 14:00 UTC
📍 Where: We’ll be live on YouTube | Humanode Announcements Telegram Channel | X | Discord | Instagram | TikTok

Join us on whichever platform suits you best—we’re excited to connect with you!

See you there! 🫡

Over a thousand of unique humans in consensus and growing.

Sharing our ❤️ to devoted human nodes

🔈Founders Talk is starting in 1 hour!

🗓 When: Friday, August 16
⏰ Time: 14:00 UTC
📍 Where: We’ll be live on YouTube | Humanode Announcements Telegram Channel | X | Discord | Instagram | TikTok

Join us on whichever platform suits you best—we’re excited to connect with you!

See you there! 🫡

Intract, a web3 community engagement platform with 12 million users has integrated our chain. Now projects on Humanode can create web3 campaigns with automatic distribution of ERC-20 tokens and NFTs.

Learn more: https://x.com/humanode_io/status/1824498340761149923

We know people do not like articles these days, but here it is: https://blog.humanode.io/intract-integrates-the-humanode-chain/

People tend to confuse ZK-KYC and Humanode’s tech - cryptobiometrics. If you want to understand it on a technical level, read the article on our blog here.

TL;DR
KYC = Know Your Customer. Even in ZK-KYC, to get an encrypted credential, you have to give out data in plaintext to verify your legal identity.

Cryptobiometrics only prove you’re a unique and real human without knowing who you are with zero data shared in plaintext from your device - it’s always encrypted.

Victor and Dato discussed how bots and Sybils are ruining multiplayer games by disrupting their economies.
Check it out! ▶️

https://x.com/humanode_io/status/1826607568229425619