The recent listing of BLURT on Cexius Exchange marks an exciting milestone for the Blurt Blockchain ecosystem. Community members can now trade BLURT directly with USDT, making it much easier to buy, sell, and manage their BLURT holdings.

Cexius is a US-based cryptocurrency exchange that offers a simple and user-friendly trading experience. One of its notable features is that users can withdraw up to $5,000 every 24 hours without completing KYC, making deposits and withdrawals more convenient for many users.

I have personally tested both depositing and withdrawing BLURT on Cexius, and my experience has been excellent. The transactions were processed quickly, and everything worked smoothly.

To celebrate the BLURT listing, we're launching a community campaign where you can earn 100 BLURT simply by sharing your honest experience with Cexius on Trustpilot.

🏆 Reward

• 100 BLURT per participant
• Limited to the first 20 valid participants
• First come, first served

Once all 20 reward slots are filled, the campaign will automatically end.

📋 How to Participate

Step 1

Create an account on Trustpilot if you don't already have one.

Step 2

Visit the Cexius Trustpilot review page.

Step 3

Write an honest review based on your experience using Cexius Exchange.

Your review can mention things like:

• Deposit and withdrawal experience
• Trading interface
• User experience
• Customer support
• Overall satisfaction

Step 4

Take a screenshot of your published review.

Step 5

Share the screenshot in the comments of this post.

That's it! Once your submission is verified, you'll receive *100 BLURT, provided you're among the *first 20 eligible participants.

⚠️ Rules

• Only honest reviews are accepted.
• One reward per participant.
• Reviews must be genuine and based on your own experience.
• Edited, duplicate, fake, or spam reviews will not qualify.
• Rewards will be distributed only to the first 20 valid submissions on a first come, first served basis.

💬 Need Assistance?

If you experience any issues while using Cexius, including deposits, withdrawals, or trading, you can join the official Cexius Discord server. Their support team is active and ready to help resolve any questions or technical issues you may encounter.

🚀 Why Your Review Matters

Trustpilot reviews help new users make informed decisions before trying an exchange. Every genuine review contributes to building trust and credibility for both Cexius and the Blurt ecosystem.

As more exchanges support BLURT, community participation becomes increasingly important. By taking just a few minutes to share your experience, you're helping strengthen the ecosystem while earning a reward for your contribution.

🔗 Useful Links

🌐 Cexius Exchange
https://cexius.com/

⭐ Cexius Trustpilot
https://www.trustpilot.com/review/cexius.com

💬 Official Cexius Discord
https://discord.gg/eA3Z2YMUV6

This is a simple opportunity to support an exchange that now supports *BLURT, help other users through your honest feedback, and earn *100 BLURT in return.

Remember, only the first 20 valid participants will receive the reward, so don't miss out.

We look forward to reading your reviews. Good luck, and thank you for supporting the Blurt community!

Today we're excited to announce a major milestone for both the Blurt and Bloodstone communities.

The Blurt and Bloodstone teams have worked together to secure a joint listing on Cexius, bringing both ecosystems to a growing cryptocurrency exchange and opening new opportunities for traders and community members.

This collaboration reflects the close relationship between our projects. Blurt continues to provide one of the world's fastest social blockchains, with digital civilization aspirations , while Bloodstone is building the infrastructure layer for decentralized DePIN resources (compute, storage etc).

Together, we're expanding our reach and making it easier than ever for new users to discover both ecosystems.

📈 Start Trading

🔹 BLURT/USDT
https://cexius.com/trade/BLURT-USDT

🔹 STONE/USDT
https://cexius.com/trade/STONE-USDT

Cexius offers a clean spot trading experience with both limit and market orders, real-time order books, trade history, and transparent maker/taker fees.

The exchange is steadily expanding its listed assets while focusing on stable infrastructure and organic market growth rather than artificial volume.

🌊 Help Build Healthy Markets

Exchange listings are only the beginning.

Strong markets are built by active communities, and there are several ways you can help:

• Trade BLURT and STONE on Cexius.
• Place buy and sell orders to strengthen the order book.
• Consider providing liquidity through market-making or the AMM liquidity pool participation where available.
• Share the listing with your communities and invite new traders to discover both projects.

Healthy liquidity benefits everyone by improving price discovery, reducing spreads, and making it easier for new participants to enter and exit positions.

🤝 One Community, Two Economies ...

This listing represents more than two trading pairs.

It demonstrates what collaboration between decentralized communities can achieve. By working together instead of competing for attention, Blurt and Bloodstone are creating stronger network effects, broader visibility, and new opportunities for everyone involved.

Whether you're here for social media, infrastructure, mining, governance, or the future of digital civilization, this is another important step forward.

Thank you to everyone who helped make this possible—and welcome to everyone joining us through Cexius.

Trade smart. Support liquidity. Grow the ecosystem.

Disclaimer

Cexius is a relatively new exchange with lower trading volumes than established global platforms. Like any exchange, users should conduct their own due diligence before depositing funds or trading.

At the time of writing, we have not independently verified matters such as regulatory registrations, third-party security audits, proof of reserves, or corporate disclosures. As with any cryptocurrency platform, never deposit more than you can afford to lose, consider using self-custody for long-term holdings, and evaluate the risks based on your own circumstances.

This announcement simply informs the community that BLURT and STONE are now available to trade on Cexius following a collaborative listing effort. It should not be interpreted as financial, legal, or investment advice, nor as an endorsement of any exchange beyond our positive experience working with their team during the listing process.

Dear Blurt Community,

On the 4th of July, we proudly celebrate Blurt’s 6th Birthday!

We've had an incredible journey. From a passionate vision of a decentralized, creator-rewarding social platform to the thriving, resilient community we are today — thank you for every post, every vote, every contribution, and every moment of support you have contributed to our community.

Six years in, we’ve built something truly special: a space where voices are heard, creativity is rewarded, and independence matters.

Recent enhancements — faster performance thanks to the Nexus-Go migration, native video uploads, a sleek new native search experience, top-of-post editing, and countless quality-of-life improvements — show how far we’ve come together.

Special thanks to @drakernoise and @saboin for their tireless work in improving the Blurt experience.

You can explore the ongoing progress here: https://gitlab.com/blurt/condenser/-/commits/main

But we’re not stopping (Sorry guys, no rest for you!).

Today we’re excited to share our forward-looking roadmap.

These initiatives will advance in parallel, leveraging on community collaboration and open-source spirit to build the next era of Blurt.

Our Roadmap for Blurt’s Future

Civilizations Layer (CivLayer)

Creating a Web of Trust that brings discoverability, associations, endorsements, and organized collaboration to the forefront. With gamified elements, it will make building meaningful connections and communities even more engaging and rewarding.

Blurt Official Public MCP

What began as a community wish list item, became possible thanks to @nalexadre, who is generously open-sourcing his prototype repository.

We’re now focused on building an official public version with expanded capabilities, including transaction signing features powered by the next item on this list.

SSM Wallet (Software Security Module Wallet)

A modern, non-custodial, future-proof local wallet for secure and private interaction with the Blurt blockchain. Built with a modern stack, it will feature a secure local keystore, post-quantum cryptography hardening, device-native biometrics, optional TOTP 2FA, and headless server mode.

SSM Wallet is intended to be available across desktop (Windows/macOS/Linux), mobile (Android/iOS), and Linux VPS/Docker — enabling powerful use cases like LLM/MCP integration for AI-assisted posting with secure signing, semi-automated and automated workflows, and consistent privacy-first control everywhere.

Post-Quantum Hardening

We won't only stop at quantum-level security for the local wallet keystore, we wish to put together a coordinated task team to focus on hardening Blurt at right at the blockchain protocol. Early discussions point towards lighter (less bytes per tx) for frequent use social posting keys and heavier post-quantum cryptography for transactional (active), privacy (memo) and ownership (owner) keys.

It's my goal for Blurt to become the first quantum-hardened Graphene chain, serving as a beacon for others to follow. If you have knowledge and skill in this field please contact me to join the discussion.

Unified Public API Cluster

A robust aggregator layer that will bring our public nodes together into a more reliable, scalable, and developer-friendly gateway — making the entire Blurt ecosystem stronger and easier to build upon.

SEO + GEO Enhanced Blurt.blog

Optimizing for the new age of AI and LLMs, improving global discoverability so that quality Blurt content reaches more people around the world.

Continued UI/UX Enhancements to Blurt.blog

Ongoing improvements to speed, layouts, and user experience. From the recently implemented native search and video upload features to many more subtle delights coming soon.

Blurt Wallet Enhancements

Introducing a wallet indexer for much faster transaction history, plus advanced search and date-range reporting capabilities that go well beyond current limits.

These developments represent our commitment to security, usability, discoverability, and innovation — all while staying true to Blurt’s decentralized roots.

To the Blurt Community — Thank You!

You are the reason Blurt exists and thrives after six years. Your creativity, curation, feedback, and collaboration continue to inspire us.

Let’s keep building a platform we can all be proud of — one that rewards value creation and fosters genuine connection.

Here’s to many more years of growth, innovation, and community-driven success!

Happy upcoming

6th Birthday, Blurt! 🎉

Important Notice: KlingEx Announces Shutdown — BLURT Users Should Withdraw Funds

This is an important notice for the Blurt community, especially for users who traded BLURT on KlingEx or provided liquidity to the BLURT/USDT pool.

I have just received an official email from the KlingEx team announcing that the exchange will be shutting down.
This information has also been confirmed through their Discord server.

According to the announcement, KlingEx explains that the decision is mainly due to the current regulatory environment and the increasing compliance obligations imposed on cryptocurrency service providers. The team states that, for a project of their size, revenues are too low to justify the legal, regulatory, and operational costs required to continue operating as a fully licensed and regulated company.

Withdrawal Deadlines

KlingEx has announced the following withdrawal schedule:

• June 29, 2026 — final date to withdraw funds directly through the KlingEx website.
• After this date, withdrawals through the website will no longer be available.
• Users who still have funds remaining after June 29 may contact info@klingex.io to request a manual withdrawal.
• Manual withdrawal requests will be accepted until July 22, 2026.

Please do not wait until the last day.

BLURT/USDT Liquidity Pool

At the time I checked the KlingEx liquidity page, the BLURT/USDT liquidity pool still showed approximately $1,812.46 in TVL.

This means that some BLURT community members may still have funds deposited in the pool.

If you provided liquidity to the BLURT/USDT pool on KlingEx, you should log in and remove your liquidity as soon as possible.

This is especially important because once website withdrawals are disabled, the process may become manual and slower.

What BLURT Users Should Do Now

If you have used KlingEx, I strongly recommend that you:

1. Log in to your KlingEx account.
2. Check your spot balances.
3. Check whether you provided liquidity to any pool, especially BLURT/USDT.
4. Withdraw your BLURT, USDT, or any other remaining assets before June 29, 2026.
5. Keep a record of your withdrawal transaction IDs.
6. If you miss the website withdrawal deadline, contact info@klingex.io before July 22, 2026.

A Note to the Blurt Community

KlingEx was one of the platforms where BLURT had an active trading pair and liquidity pool.

As a Blurt witness, my priority is to make sure that community members are informed quickly and have enough time to act. This post is not financial advice, and it is not an accusation against KlingEx. It is simply a practical warning based on the shutdown notice received from the exchange and confirmed through their community channel.

If you know anyone who used KlingEx for BLURT trading or liquidity provision, please share this information with them.

The most important action is simple:

Withdraw your funds before the deadline.

Beyond Block Production

Running a witness node is only one part of my contribution to Blurt.

I actively operate and maintain:

• a public RPC server → https://rpc.beblurt.com
• the BeBlurt frontend → https://beblurt.com
• open-source tools available on my GitLab → https://gitlab.com/imtase
• advanced on-chain analytics
• a delegation system via @beblurt & manual curation
• experimental integrations connecting Blurt with AI environments and external systems

My role is not limited to producing blocks.

It is about:

• strengthening infrastructure
• improving accessibility
• increasing transparency
• enabling data-driven understanding
• supporting organic curation
• experimenting with new integrations

Supporting my witness is not about increasing my rewards —
it is about maintaining an actively developed infrastructure node within the Top 20.

If you believe that infrastructure, transparency, curation balance, and innovation matter,
your support is always appreciated.

Every social platform needs new people. But numbers alone are not enough. A healthy network is not built only by having many accounts. It is built by real interaction: comments, replies, conversations, support, feedback, and people taking the time to notice one another.

That is why this channel exists.

Why this matters

When someone writes their first post on Blurt, they should not feel like they are writing into an empty room.

A new user who receives a few genuine comments is much more likely to stay, explore the platform, publish again, and start building connections. A new user who receives no reaction may quickly feel that nobody is reading, nobody is listening, and nothing is happening here.

That is a problem for every social network.

Blurt becomes stronger when people interact with each other. Authors need readers. Readers become commenters. Commenters become familiar names. Familiar names become part of the community. And over time, those small interactions create the feeling that this platform is alive.

This is why welcoming new users is not just a nice gesture. It is an important part of building the future of Blurt.

What this channel will do

This channel will help highlight new accounts and first posts published by new users.

The goal is to make it easier for the community to discover newcomers, visit their posts, leave comments, and help them understand how Blurt works.

From time to time, this account will publish welcome posts containing:

• new accounts that recently joined Blurt,
• new users who have already published their first post,
• links to first posts when available,
• encouragement for the community to visit and comment,
• encouragement for new users to introduce themselves and meet each other.

If you are already active on Blurt, following this account will make it easier for you to find new people to welcome.

A request to the Blurt community

If you see a new user mentioned here, please take a moment to visit their post.

You do not need to write anything complicated. A simple, honest welcome can already make a difference. You can say hello, ask what brought them to Blurt, suggest useful tags, explain how rewards and comments work, or point them toward communities and authors they might enjoy.

The most important thing is to show that someone noticed them.

Blurt needs activity, but not just activity in the form of publishing posts. It needs interaction between people. It needs conversations. It needs replies. It needs users who are willing to engage with each other.

If we want more people to stay here, we should help them feel that their voice reaches someone.

A message to new users

If you are new to Blurt, welcome.

A good first step is to publish an introduction post using the introduceyourself tag. Tell people a little about yourself, your interests, what you create, what brought you here, and what kind of content you would like to read or publish.

Also, do not wait only for others to come to you.

Visit other new users. Leave comments. Reply to people. Ask questions. Follow authors you find interesting. Join conversations that are already happening.

The more you interact, the easier it becomes for others to discover you.

Why I am mentioning active users

For this first introductory post, I am also calling attention to active Blurt users from the last month.

I am doing this because I believe this initiative is important for the whole community. The goal is not to spam anyone, but to invite active users to help welcome newcomers and strengthen interaction on the platform.

If you were mentioned and you do not want to be mentioned in future posts from this account, please leave a comment and say so. I will remove you from the mention list.

Follow this channel

If you want to help Blurt become more active, more welcoming, and easier for new users to join, please follow this channel.

You will be able to discover new users more easily, welcome them, and help them take their first steps on the platform.

A community grows when people talk to each other.

Let’s make sure that when someone new arrives on Blurt, they feel that there are real people here — reading, replying, and ready to welcome them.

Active Blurt users invited to follow this channel

@a-0-0-0-real-dex @a-h-p @a0988901 @abazboy @abbak7 @abdulmomin @aburihan1 @abuse-watcher @ace108 @actifit @adelepazani @afzalqamar @agorise @ahlawat @ahmedsy @ahsansharif @akash001 @akash1712 @akiratsuki @alanvielve @alesandro1 @alessia25 @alex-coder @alexandrakirko @alexpmorris @alfamano @alim236 @amani2765 @amaterasusolar @andrianna @anfcjfja @angelica7 @annas58 @anshumankashawar @anthony347 @appreciator-app @arabisouri @architect1111 @aresteris @ariezeh @ariful71 @arman.ithm @arsalan7 @atma.love @atongis @awak-dalam @axeman @azamali @b-hive @baby1 @bai123 @bangsam @barski @basedcontent @bastilin @bdwomen @beben @beblurt @beefnoodles @bela91 @ben.dunk @ben.haase @bendotri @bennywb56 @benwb56 @bi-social @bigbdp @bilpcoinbpc @bitcoinman @bitphoto @blackeyedm @blackmedschn @blessed-girl @blogzone @bluengel @blurt-141776 @blurt-1561233 @blurt-161158 @blurt-168492 @blurt-171484 @blurt-178594 @blurt-179874 @blurt-180201 @blurt-188398 @blurt-194344 @blurt-lotto @blurt.media @blurtart38 @blurtbooster @blurtconnect-ng @blurtenamored @blurtfreestyle @blurtgardening @blurtify @blurtisforcunts @blurtlarecette @blurtlatam @blurtofficial @blurtphcurator @blurtpilipinas @blurtpower @blurtpowerbot @blurtspace @blurtstep @blurtwomen @boddhisattva @borghesegardens @bosferi123 @boylikegirl @bpcvoter1 @brave-smoke @bring @burn950 @c1udadan0x @candy49 @captainfrost @caturday.curator @ccnew @chaosmagic23 @chisdealhd @chizzys @chorock @chrisparis @circlebubble @cjsdns @cleanenergygarro @coachkasi @cointelegraff @condividisulweb @coregensis @corpsekaizen @cosmicboy123 @cosmos-proposals @coupon.fund @cryptopie @cryptorutas @cryptosir.dork @cryptospa @cryptoyzzyblurt @ctime @curatorcat @cutemimi @dagobert007 @daily-knol @dailyblurt @daisyphotography @danmaruschak @darakshan @daretodefy @darth-azrael @davidcentenor @davide-77 @davidesimoncini @de-maria @deepseek @dejan.vuckovic @dewiasih @dobartim @dodoim @dorian-dev @dorian-lee @dotevo @dotwin1981 @drakernoise @drax @dreloop07 @droida @ecoblurt @ecosynthesizer @ecotracker @edanbrookseo @edgerik @ekushya @elenasteem @elfhaymfronlohem @elizabethbit @elkezaksek @ellymin @emmali @emuhasan @esecholo @etette @ezun1 @ezunjoshy @ezuntimmy @fahvour810 @farjana07 @fasialkhan @fatema01 @faul @fervi @filmschchensonic @filosof103 @fizz0 @flatearthdavetv @flodner @fnzcmd @foryoubtc @fozlaalahi203 @franchescaroma @franciscoluis @frankbacon @franzpaulie @freakeao @fredkese @freevoluntarist @freevoter @fridee75 @frk.world @funcontent @gameguru @gamer0815 @gduran @geneeverett @genesishealthy @ggodson @giovanni0 @godlovermel25 @graphene-faucet @gtmatze @guntingblurt @hafizur46n @haideremtiaz @hangin @hansangyou @happydolphin @happypray1 @hasanurjaman @haseeb @helios.voter @hellobot @henryglowz @hhayweaver @hilaricita @hizik1312 @hkex @holovision @homer.rides @homesteadlt @honusurf @hornet-on-tour @hossain4152 @humbertonic @ieronimus @ilnegro @ilovemylife @imfarhad @imranahmed5298 @india-news @irisworld @irynochka @isabella20 @iyanpol12 @jadeaca @jahchebem @jakaria121 @jamal70 @jangin-jeongsin @jannat87 @jannie98 @jasonmunapasee @javalord @jazminru @jbmworks @jeenger @jeffjagoe @jgb @jhj8595 @jhoneab @jimliuroblox @jjy @jmehta @joeyarnoldvn @johnybrand @jompiy @joshbam @josueelinfame @joviansummer @jozef230 @jstory @jsup @juliomartinez @jungjunghoon @justyy @kalikalejawp @kamranrkploy @kencode @kentest @kentzz001 @kgakakillerg @khalid572 @khan75 @khang572 @khingaddy @khrom @khrom-proposals @khusbu78 @kim.kel @kingcoc @kingworld-line @kiryck @knaus @kolkamkwan @kryptodenno @kt-krazzytrukker @kyju @ladyaryastark @lamiyahaque @lanefrog @larasbpn @leems @leifasaur @lenonmc @lfu-radio @light-hearted @lightcaptured @limon88 @littledino @liumei @log01 @logen9f @logiczombie @ludevielucero @luminaryhmo @lutx0 @luzmb @lxsxl @maarnio @madpop @madventure @mahadi77 @mahmud552 @makniazi @makwafilms @mamun123456 @manuel78 @manuvert @marendan @mariacordoba @mariuszkarowski @marjuanm @marko499 @marymi @mastergerund @matthew1 @mattsanthonyit @maxinpower @mc5punk @mdshanto @me-tarzan @megadrive @megareigns @mehta @mein-senf-dazu @mes @metistv @mhmaruf @michelle1111 @michellectv @mickeymini @mimi23 @mimster @minbuja @mireczek @mirzaiqi @mists @mk-int-token @mk-pal-token @mk-sports-token @mmmmkkkk311 @moeenali @mohdrafi786 @mohsinkhan5 @moito @monirrohan @monopoli @mrsyria @mspbro @mtravel @mu47fa @mudassir55 @muneeb422 @mushanov @musicalzee @mustakin321 @naflz @nainaztengra @nalexadre @narocky71 @neongirl @nevlu123 @news-cast @newvisionlife @nhriyad @nilesh-khinchi @nj07 @node01 @oadissin @oasiskp2 @offgridlife @omgabunny @oneray @opong @orangecrush12 @osj @otisbrown @outofthematrix @owasco @ozelot47 @paopaoza @parkname @pascalukandy @paulindstrom @pedrobrito2004 @peerfaizan1 @peerhub.blurt @pestis @phasewalker @pi3434 @pichat @pingyuan @posel2 @potatogirl @powerego @pressedition24 @primeradue @princefm @psychkrhoz @public-money @puncakbukit @raghnok710 @ranesta @rasel8 @raufmalik @rayhan111 @rebejumper @rebloglottery @redrose72 @reetuahlawat @rekha-sunil @rex-kibreay @rhozolive01 @richmond2 @ride1 @riyanur @robert.stanberry @romanskv @ronnie10 @ronthroop @rosalestrust @rosasaez @rosatravels @royal01 @rubelynmacion @rubina203 @saboin @sabuon @sahin111 @samadbro08 @sammy00 @sebastian88 @selfinflicted @serenity1 @shadflyfilms @shaungerow @shawmeow @shemisahina @shopnilhasan @shopon01 @shula14 @silvertop @simpsonart0 @siphon @sliceit @solves @southside187 @spinbunny @squirrelbait @steemitwarrior @steemzzang @stmp04 @strosalia @subworld @summaiyarashid @sunai @sunmoon09 @surfgrrl @susanli3769 @swan1 @sweetpiebpn @syedazharuddin @symbionts @tahirazaman @tahirazaman7 @tahirniazi1122 @tammanna @tas.media @tasonya @tdvtv @teatree @tempertantric @testowy @tezzmax @the.witcher @theeone @thegolemseye @theindicators @theocu @thhridoy @tiamo1 @tof.poland @tokenindustry @tonybad @troll666 @true.moaaz @tydynrain @udabeu @udibekwe @ultratrain @ultravioletmag @umoh101 @unmutedsoul @unpoetaenamorad @vankushfamily @vegancomidas @vesytz @volf @volkova12 @wahaceggy @we1 @web2.support @web3diarygirl @webminevolta @webstorms @wjs @wml123 @world-travel-pro @xaaliyahholtx @xandar-cage @xiaohui @xstern93 @yayogerardo @yintercept @yoieuqudniram @yuanyuanzi @yyoungbo @zahidsun @zaink @zekepickleman @zubairkhan422 @zzan.atomy

Hello Blurt community! I'm excited to announce a new public RPC endpoint for everyone to use:

🔗 Public Blurt RPC Node

https://blurt-rpc.node01.org

✅ Features

🛠️ How to use it

curl:

curl -s -X POST https://blurt-rpc.node01.org \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"condenser_api.get_dynamic_global_properties","params":[],"id":1}'

JavaScript (with any blurtjs-compatible library):

const client = new Client(['https://blurt-rpc.node01.org'])

Python:

import requests
r = requests.post('https://blurt-rpc.node01.org', json={
    "jsonrpc": "2.0",
    "method": "condenser_api.get_dynamic_global_properties",
    "params": [],
    "id": 1
})
print(r.json())

🗳️ Why I'm running as a witness

My witness account is node01. I'm running a dedicated server with:

• CPU: Dedicated, low load
• RAM: 24 GB
• Disk: NVMe SSD
• Network: 1 Gbps
• Blockchain: Fully synced, running latest v0.9.0

I believe in Blurt's vision of a decentralized, censorship-resistant social network. By running a witness node and offering free public RPC services, I'm contributing to the network's resilience and accessibility.

✨ What I offer as a witness

✅ Public RPC node — free for everyone
✅ Low transaction fees (operation flat fee: 0.001 BLURT)
✅ Reliable infrastructure — monitored 24/7
✅ Long-term commitment — here to stay and grow

💚 How you can support me

If you appreciate my work and want to see more Blurt infrastructure, please:

1. Vote for node01 as witness → https://blurtwallet.com/~witnesses
2. Set node01 as your witness proxy if you manage multiple accounts
3. Tell others about the public RPC endpoint

Every vote helps me move up the ranks and eventually start producing blocks for the network!

📊 Current witness stats

• Rank: ~#148 (climbing!)
• Missed blocks: 0 (haven't been called yet, but ready when I am!)

Questions? Feedback? Drop a comment below or find me on Discord.

Let's build a stronger Blurt together! 🚀

node01 witness | Public RPC: https://blurt-rpc.node01.org

Hive-engine was recently hacked and several tokens drained, those affected were mainly EVM or Solana tokens, sovereign chain tokens like BTC, DODGE, LTC, HIVE, HBD, STEEM and BLURT have not been compromised.

We can confirm BLURT withdrawals test okay for the time being and as far as we know there has been no BLURT stolen in the hack.

To be safe you may wish to withdraw your BLURT back to the base chain and power up for additional four week time-locked security.

To withdrawal BLURT from Hive-Engine, simply go to hive-engine.com or tribaldex.com, head over to the wallet page and find the withdrawal button, select BLURT and nominate your Blurt account name to receive the funds.

Below is an excerpt from the official Engine team announcement:

Around 5am EST it appears multiple systems of EVM bridges were compromised.

Eth and BNB as well as the Solana bridges have been impacted. This also includes the BaseETH/Hive Bridge. This goes across multiple server systems and multiple projects operated by different developers.

Hive, HBD, BTC, LTC, STEEM, DOGE are reporting ok.

The approximate damage to the ecosystem is 85 Eth, 58 BNB, 33k Pol, and 257 Solana. Underlying tokens like GIFU, USDT, BUSD and others have been drained as well. All EVM gateway processes have been shut down.

Please refrain from doing any deposits or withdrawls from those tokens. We'll get the front end updated soon, but for now those gateway services are offline.

Our thoughts are with the Hive-engine team in this difficult time and we hope their DEX call pull through this, we are grateful that BLURT has been listed on Hive-engine and continued to trade issue-free for many years.

The goal is simple: instead of manually pasting a posting key, a user can scan a QR code, and the scanned value is automatically inserted into the login field. In the current login flow, after a valid QR code is scanned, the page can also continue with the signing process automatically.

You can check it here: https://my.blurtplugin.online/

This is especially useful on mobile devices, where copying and pasting long private keys is uncomfortable and error-prone. It will also be useful when, for example, you want to transfer keys from a printout to a mobile device or from a desktop computer/laptop to a phone/tablet.

Below I am also sharing a ready-to-use QR scanner module that anyone can download and add to their own front-end. It is designed to work with regular HTML/PHP pages, but there is also a version prepared for dynamic web applications such as Condenser-like interfaces, Blurt Media-style front-ends, PeerTube-like applications, React, Vue, or other SPA-based projects.

What the QR Scanner Does

The module opens a camera scanner in a modal window, scans a QR code, validates the scanned value, and inserts it into a selected input field.

For example, it can be attached to:

<input id="postingKeyInput" type="password">

Then, after scanning a QR code, the value from the QR code is automatically inserted into that input.

The module can be used for:

• posting keys,
• memo keys,
• active keys,
• master passwords,
• login codes,
• encrypted payloads,
• any other QR-encoded text value.

The scanner itself does not send the scanned value anywhere. It only fills the configured input field. What happens after that depends on your application.

QR Scanning Library Used

The module is built on top of the open-source JavaScript library:

html5-qrcode

This library handles the core QR scanning features:

• accessing the camera through the browser,
• displaying the live camera preview,
• detecting and decoding QR codes,
• working on both desktop and mobile browsers,
• supporting multiple cameras when available.

The module I prepared does not try to implement QR decoding from scratch. Instead, it wraps html5-qrcode into a simple reusable component that can be attached to any input field.

In short:

html5-qrcode = camera access and QR decoding
QRInputScanner = reusable input-field integration layer

So the ready-made module adds:

• a modal window above the page,
• automatic input filling,
• validation rules for Blurt keys,
• automatic button click after scanning,
• support for classic pages and dynamic web applications,
• simpler integration for other Blurt front-ends.

The full library file is included in the downloadable package as:

classic/assets/js/html5-qrcode.min.js
webapp/public/assets/js/html5-qrcode.min.js

The scanner module also contains fallback loading logic, so if the local file is missing, it can try to load html5-qrcode from public CDN sources.

For production use, I recommend hosting the library locally in your own project instead of relying only on CDN loading. This gives better reliability and avoids problems when a user’s browser, network, or privacy settings block external scripts.

Download the Module

You can download the ready-to-use package here:

https://blurt.pl/downloads/?folder=QR+Code+Scan

The package contains two versions:

classic/
webapp/
docs/
README.md

Classic version

Use this version for simple websites:

classic/assets/js/qr-input-scanner.js
classic/assets/js/html5-qrcode.min.js
classic/assets/css/qr-input-scanner.css
classic/README.md

Good for:

PHP
HTML
WordPress
classic login forms
server-rendered pages

WebApp version

Use this version for dynamic front-ends:

webapp/public/assets/js/qr-input-scanner.js
webapp/public/assets/js/qr-input-scanner-webapp.js
webapp/public/assets/js/html5-qrcode.min.js
webapp/public/assets/css/qr-input-scanner.css
webapp/README.md

Good for:

Condenser-like front-ends
Blurt Media-style apps
PeerTube-like interfaces
React
Vue
SPA applications
dynamic forms rendered by JavaScript

The package also contains examples:

webapp/examples/data-attributes-example.html
webapp/examples/react-component-example.jsx
webapp/examples/vue-component-example.vue
webapp/examples/peertube-plugin-frontend-example.js

Installation for a Classic HTML/PHP Page

First, copy these files to your project:

/assets/js/qr-input-scanner.js
/assets/js/html5-qrcode.min.js
/assets/css/qr-input-scanner.css

The file html5-qrcode.min.js is the QR scanning library used for camera access and QR code decoding.

Then add the CSS in your <head>:

<link rel="stylesheet" href="/assets/css/qr-input-scanner.css?v=1">

Add the JavaScript before the closing </body> tag:

<script src="/assets/js/html5-qrcode.min.js?v=1"></script>
<script src="/assets/js/qr-input-scanner.js?v=1"></script>

Now create your input and QR button:

<input id="wifInput" type="password" autocomplete="off" placeholder="Posting key">

<button id="scanQrBtn" type="button">
    QR Code
</button>

<button id="manualSignBtn" type="button">
    Sign with key
</button>

Then attach the scanner:

<script>
    QRInputScanner.attach({
        input: '#wifInput',
        button: '#scanQrBtn',
        title: 'Scan posting key',
        validate: QRInputScanner.validators.postingWif,
        invalidMessage: 'This QR code does not look like a valid Blurt posting WIF key.',
        autoClick: '#manualSignBtn',
        autoClickDelay: 150
    });
</script>

After scanning a valid QR code:

1. The modal closes.
2. The scanned value is inserted into #wifInput.
3. The module triggers input and change events.
4. The button #manualSignBtn is clicked automatically.

If you do not want automatic signing, remove these two options:

autoClick: '#manualSignBtn',
autoClickDelay: 150

Then the module will only fill the input field.

Installation for Dynamic Web Applications

For applications where forms are rendered dynamically, use the webapp version.

Copy these files:

/public/assets/js/html5-qrcode.min.js
/public/assets/js/qr-input-scanner.js
/public/assets/js/qr-input-scanner-webapp.js
/public/assets/css/qr-input-scanner.css

Load them globally:

<link rel="stylesheet" href="/assets/css/qr-input-scanner.css?v=1">

<script src="/assets/js/html5-qrcode.min.js?v=1"></script>
<script src="/assets/js/qr-input-scanner.js?v=1"></script>
<script src="/assets/js/qr-input-scanner-webapp.js?v=1"></script>

Then enable automatic binding:

<script>
    QRInputScannerWebApp.initAutoBind();
</script>

Now you can attach QR scanning to an input using only HTML attributes:

<input id="blurtPostingKey" type="password" autocomplete="off">

<button
    type="button"
    data-qr-input-button="1"
    data-qr-input-target="#blurtPostingKey"
    data-qr-validator="posting"
    data-qr-title="Scan Blurt posting key"
    data-qr-invalid-message="This QR code does not look like a valid Blurt posting WIF key."
    data-qr-auto-click="#loginWithPostingKey">
    Scan QR
</button>

<button id="loginWithPostingKey" type="button">
    Login
</button>

This version is useful when your form appears later, for example after a modal opens, after a route changes, or after a component is rendered by JavaScript.

The adapter uses MutationObserver, so newly added QR buttons can be bound automatically.

React Example

In React, attach the scanner after the component is rendered:

import { useEffect, useRef } from 'react';

export default function BlurtPostingKeyInput() {
    const inputRef = useRef(null);
    const buttonRef = useRef(null);
    const scannerRef = useRef(null);

    useEffect(() => {
        if (!window.QRInputScanner || !inputRef.current || !buttonRef.current) {
            return;
        }

        scannerRef.current = window.QRInputScanner.attach({
            input: inputRef.current,
            button: buttonRef.current,
            title: 'Scan Blurt posting key',
            validate: window.QRInputScanner.validators.postingWif,
            invalidMessage: 'This QR code does not look like a valid Blurt posting WIF key.',
            autoClick: '#loginWithPostingKey',
            autoClickDelay: 150
        });

        return () => {
            if (scannerRef.current) {
                scannerRef.current.destroy();
            }
        };
    }, []);

    return (
        <div>
            <input
                ref={inputRef}
                id="postingKeyInput"
                type="password"
                autoComplete="off"
                placeholder="Posting key"
            />

            <button ref={buttonRef} type="button">
                Scan QR
            </button>

            <button id="loginWithPostingKey" type="button">
                Login
            </button>
        </div>
    );
}

Vue Example

In Vue, attach the scanner in mounted() and destroy it before the component is removed:

<template>
    <div>
        <input ref="postingKeyInput" type="password" autocomplete="off" placeholder="Posting key">
        <button ref="scanButton" type="button">Scan QR</button>
        <button id="loginWithPostingKey" type="button">Login</button>
    </div>
</template>

<script>
export default {
    name: 'BlurtPostingKeyInput',

    mounted() {
        if (!window.QRInputScanner) {
            return;
        }

        this.scanner = window.QRInputScanner.attach({
            input: this.$refs.postingKeyInput,
            button: this.$refs.scanButton,
            title: 'Scan Blurt posting key',
            validate: window.QRInputScanner.validators.postingWif,
            invalidMessage: 'This QR code does not look like a valid Blurt posting WIF key.',
            autoClick: '#loginWithPostingKey',
            autoClickDelay: 150
        });
    },

    beforeUnmount() {
        if (this.scanner) {
            this.scanner.destroy();
        }
    }
};
</script>

Key Validation

The module includes several validators:

QRInputScanner.validators.any
QRInputScanner.validators.wif
QRInputScanner.validators.postingWif
QRInputScanner.validators.memoWif
QRInputScanner.validators.activeWif
QRInputScanner.validators.masterPassword

For Blurt private keys such as posting, memo and active keys, the basic text-level validation is the same:

/^5[1-9A-Za-z]{50,58}$/

This only checks whether the scanned value looks like a WIF private key.

It does not prove that the key belongs to a specific account.
It does not prove that the key is really the posting key, memo key or active key for that account.

To truly verify the key role, the application must:

1. derive the public key from the scanned private key,

2. fetch the account data from the Blurt blockchain,

3. compare the derived public key with the correct account authority:

   • posting authority for a posting key,
   • active authority for an active key,
   • memo_key for a memo private key,
   • owner authority for an owner/master-derived key.

For example, if the field expects a posting key, the derived public key should be checked against the account posting authority.

For memo keys, it should be checked against the account memo_key.

For active keys, it should be checked against the account active authority.

A master password is different. It is not a WIF private key, so it should not be validated with the WIF validator. For a master password field, use:

QRInputScanner.validators.masterPassword

or define your own rule:

validate: function (value) {
    return value.trim().length >= 12;
}

Security Notes

If you use this scanner for private keys, the safest approach is:

• use type="password" fields,
• use autocomplete="off",
• keep signing local in the browser,
• never send raw private keys to the backend,
• send only the generated signature,
• clear the input after signing,
• use HTTPS,
• avoid embedded mobile browsers such as Facebook, Messenger, Instagram or TikTok.

The scanner module only fills the input field. It does not transmit the key by itself.

Mobile Compatibility

Camera access on mobile devices requires HTTPS.

This should work:

https://your-domain.com

Local development may work on:

http://localhost

This usually will not work on a phone:

http://your-domain.com

For best results, open the page directly in Chrome, Safari or Firefox. Embedded browsers inside social media apps often block camera access or behave inconsistently.

Summary

Since I recently added the ability to create QR codes from keys to the account creator, the same feature has long been available in the wallet:

I believe everyone should finally add this small but very user-friendly module to their input fields for the posting key and active key. Of course, you should avoid entering keys directly into the browser, but many users do it anyway, and it is often done in a more insecure way. For example, to send keys to another device, they send them unencrypted via WhatsApp, Telegram, Discord, or email. Therefore, I think that introducing QR codes will significantly simplify user navigation within the ecosystem and, paradoxically, increase the security of using keys.

The actual camera scanning and QR decoding are handled by the html5-qrcode library, while my module provides the Blurt-oriented integration layer around it.

The same functionality is available as a reusable module that can be added to other Blurt-related front-ends, classic websites, Condenser-like applications, Blurt Media-style apps, PeerTube-like interfaces, React components, or Vue components.

The module is intentionally small, neutral, and easy to integrate. It can be used only to fill an input field, or it can continue the flow automatically after scanning by clicking a selected button.

I especially encourage people like @agorise @saboin @megadrive @nalexadre @freakeao @eastmael @tekraze @drakernoise and other Blurt app developers to consider adding this functionality.

All it takes is a small camera icon, some CSS, and a ready-made library, and Blurt users will have a better life ;)

Have a nice day!

Support the Development

If you find this work useful or valuable, consider supporting further development.

You can do so by sending a donation to my account on BLURT or by voting on @khrom-proposals account posts.

Every contribution helps to improve the tools and maintain the ecosystem.

Thank you for your support.

Today is not just another post. I am excited to officially announce that BlurtPostify is in active development. I am working on it right now.

No more waiting for the perfect moment. No more asking for permission. I am a builder. So, I am going to build.

Who Am I? (For Those Just Arriving)

My name is Aftab Irshad. I am the founder and sole developer of HivePostify.cloud. This is a fully functioning blockchain publishing platform built on the Hive ecosystem. I created it on my own, from the ground up, without external funding, co-founders, or shortcuts.

That platform is available today. You can open it in your browser now. It handles content publishing, blockchain interaction, user management, wallet integration, and community tools all in one product for real users.

That is my record. Not a whitepaper. Not a pitch. A working product.

My full introduction: Aftab Irshad, Founder of HivePostify.cloud | Stepping into Blurt

Why I Chose Blurt And Why Now

I have been watching Blurt for a long time. I stayed interested because of one quality: a blockchain social network that truly respects its creators.

No downvotes. No censorship fueled by stakes. No reward pool conflicts. Every creator can publish knowing their earnings won't be wiped out by someone who simply disagrees with them. This isn't just a minor feature; it's a fundamental commitment to freedom of expression that no other major blockchain social network provides.

Blurt has the right values. It also needs the right infrastructure.

That is where BlurtPostify comes in.

What is BlurtPostify?

BlurtPostify is a complete Web3 publishing ecosystem built just for the Blurt blockchain. It focuses on Blurt's creator-first values and the real needs of today’s content creators.

I have already published a detailed technical proposal. You can read the full vision here:

Full Proposal: BlurtPostify — A Complete Web3 Publishing Ecosystem for the Blurt Blockchain

The short version:

• ✅ Long-form publishing Full markdown editor, drafts, scheduled posts, tag suggestions
• ✅ Short-form video First-class native video upload, posted to YOUR account, YOUR rewards
• ✅ Integrated wallet dashboard BLURT, BLURT POWER, rewards, power up/down, transfers
• ✅ Decentralized token swap Multi-sig smart contract, community-governed, auditable
• ✅ Creator referral system Community-driven growth, rewards for bringing new users
• ✅ Mobile-first design Built for global audiences from day one

Phase 2 will add: auto-vote rules, curation analytics, delegation manager, witness voting, and more.

What Changed: Why I Am Starting Today

I received important feedback from the community from @megadrive, @drakernoise, @saboin, @mariuszkarowski, and others. The consistent message was clear:

Prove yourself first. Build, then ask for support.

I heard that. I respect it. And I am acting on it.

Starting today, May 4, 2026, BlurtPostify is in active development. I am not waiting for funds to begin. I am starting and asking for support to sustain what I am building.

How You Can Support BlurtPostify

Development has started. Here’s how the community can help:

Option 1 Delegate to @blurtpostify

Delegate any amount of BLURT POWER to @blurtpostify. All curation rewards will go directly toward:

• Server and hosting infrastructure
• Video storage costs
• Domain and SSL
• New user account creation fees

Even small delegations add up. Every bit of voting power helps keep the servers running.

Option 2 Transfer Funds to @blurtpostify

Direct BLURT transfers to @blurtpostify go into a dedicated infrastructure wallet. Every expense will be reported publicly on Blurt every 30 days with receipts.

Option 3 Upvote Development Updates

I will publish a development update post every single week starting now. Upvoting those posts is a zero-cost way to support sustained building.

Option 4 Spread the Word

ReBlurt this post. Share it with creators who are frustrated with downvotes on other platforms. Every new person who discovers Blurt through BlurtPostify is a win for the entire ecosystem.

My Commitment to This Community

I will not disappear after this post.

• 🔁 If the project cannot be completed All unspent funds returned to the community with a full public explanation

The Target: 50,000 Active Users in Year 1

This is ambitious. I know that. But it is achievable with the right combination of:

• Frictionless onboarding (no account fees during growth phase)
• Native video support (the content format that drives creator adoption)
• A community referral system (growth powered by Blurt members themselves)
• A decentralized swap (making BLURT earnings actually liquid and usable)

I built HivePostify.cloud alone. With community support, BlurtPostify will reach further, faster.

A Note on Collaboration

To @megadrive, @drakernoise, @saboin, and everyone who gave honest feedback: I am listening. I am not here to compete with what you are building. I am here to add to it.

If there are ways to contribute to existing repositories, integrate with blurt.media, or coordinate on shared infrastructure I am genuinely open to that. Blurt is better when its builders work together.

Final Word

I have spent years building in Web3 with nothing but skill and dedication. I came to Blurt because I believe in what it stands for.

Today, I stop talking about what I might build and start showing you what I am building.

BlurtPostify is live in development as of May 4, 2026.

Support it. Watch it grow. Come back next week for the first development update.

Aftab Irshad
Founder, HivePostify.cloud
Web3 Infrastructure Developer · Blockchain Publishing Ecosystem
Blurt: @aftabirshad · Discord: @aftabirshad · Support: @blurtpostify / @aftabirshad

First, Blurt is now officially listed on Klingex.io exchange 🎉
This marks an important step forward in expanding accessibility and liquidity, making it easier than ever for users to trade and engage with the Blurt ecosystem. Listings like this help strengthen our presence and bring more visibility to what we’re building.

Second, this post marks our very first article on the Blurt Blog.
We’re just getting started here.

Going forward, you can expect more updates, insights, and behind-the-scenes looks at what we’re building—from product developments to ecosystem growth and everything in between. This blog will be our space to keep you informed and connected.

Thanks for being part of the journey—more is coming soon 🚀

Trade BLURT here: https://klingex.io/trade/BLURT-USDT