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

Hey Blurtians! Today is an important day for BLURT!

Six months ago, BLURT lost its last centralized exchange. When ProBit shut down, it did not just remove a trading venue — it effectively left BLURT without any CEX exposure. From that moment on, the market became entirely dependent on a single environment: Hive-Engine.

For six months, that was the reality, but things have changed now

BLURT is now listed again on a centralized exchange, with a BLURT/USDT pair on KlingEx.

And yes — there’s a 250 BLURT gift code somewhere in this post for the fastest among you.

This listing was first announced by @megadrive in his post:
Pre-announcement Scoop - BLURT listed on Klingex.io

But beyond the announcement itself, what matters here is the change in market structure.

Until now, BLURT was effectively confined to a single ecosystem, with liquidity split between order books and pools on Hive-Engine, and tightly linked to the Hive environment .

With KlingEx, BLURT now exists across two distinct layers:

• a DEX-like environment via Hive-Engine
• and a centralized exchange with a direct USDT pair

That does not automatically mean deep liquidity or sustained volume.

But it does change how BLURT can be accessed, traded, and potentially priced going forward.

KlingEx is also not limited to simple spot trading. The platform already exposes several features around BLURT:

• a BLURT/USDT liquidity pool
• a BLURT faucet, claimable every 24 hours
• and the ability to create redeemable gift codes

Some of these features go beyond what is currently available on Hive-Engine, and make the platform worth testing beyond the listing itself.

Rather than speculating on what this could become, I wanted to see how it behaves right now from a user perspective.

So I started with the most basic operation: depositing BLURT directly from the blockchain.

1. Depositing BLURT from the blockchain

The process is straightforward.

On KlingEx, each account is assigned a deposit memo. Sending BLURT simply requires transferring funds to @klingex with that memo, which makes it immediately familiar for anyone used to standard exchange-style deposits on Graphene-based chains.

A few parameters are worth noting.

• The minimum deposit is 1 BLURT
• Funds are credited after 21 block confirmations

In practice, the transfer worked as expected. The transaction was processed without friction, and the funds appeared on the exchange after the confirmation delay.

From a usability standpoint, this is important.

It means that, at a basic level, the bridge between the Blurt blockchain and KlingEx is already functional and reliable enough for standard usage — which is the first condition for any market to exist beyond theory.

2. Depositing LTC from Hive-Engine

After confirming that BLURT deposits were working correctly, the next step was to test the other side of the equation: bringing external liquidity into the system.

Since I wanted to interact with the BLURT/USDT pool, I needed USDT in addition to BLURT . Rather than using an external wallet, I chose a path that would feel natural for most Blurtians: sending assets from Hive-Engine.

In this case, I used LTC.

The idea was simple — transfer LTC to KlingEx, then convert it into USDT directly on the exchange, and use that USDT for both trading and liquidity testing.

The deposit process itself worked without issue. The LTC sent from Hive-Engine was credited on KlingEx after the expected confirmation time, with no friction or unexpected behavior.

From a practical standpoint, this is an important point.

It shows that KlingEx is not only connected to the Blurt blockchain, but also usable as a bridge between other assets and a more standard trading pair like USDT — which is essential if the platform is to support actual liquidity flows, not just isolated BLURT deposits.

3. Trading test: LTC → USDT → BLURT

With LTC successfully deposited, the next step was to test actual trading conditions on the platform.

I first converted part of my LTC into USDT, then used that USDT to buy BLURT through the BLURT/USDT pair.

One important point to highlight is that Klingex is still a relatively young exchange, with limited usage at this stage. At the time of testing, the reported 24h volume was around $15.45, which is extremely low by any standard.

Despite that, both trades were executed without any issue.

• The LTC → USDT conversion went through smoothly
• The USDT → BLURT trade was also executed without friction

There were no unexpected delays, no failed orders, and no visible issues on the execution side.

This does not mean the market is deep or liquid — far from it.

But it does show that, even at this early stage and with very low activity, the trading infrastructure itself is already functional. Orders can be placed, matched, and executed as expected, which is a necessary baseline before any meaningful liquidity can develop.

4. Testing the other side: placing sell orders

After buying BLURT , I also wanted to test the opposite side of the market.

Being able to buy is one thing, but a market only becomes meaningful if both sides — buy and sell — can function properly.

To verify that, I placed a few small sell orders on the BLURT/USDT pair.

The orders were accepted without issue and correctly placed in the order book. No abnormal behavior was observed at this stage, and the interface behaved as expected.

I also chose to leave some of these orders open, in order to observe over time how the market evolves and whether they eventually get filled.

At this stage, this does not provide enough data to draw conclusions about liquidity or execution speed under real conditions.

However, it confirms that the basic mechanics are in place: orders can be created, displayed, and maintained in the book without issue — which is a necessary condition before any meaningful trading activity can develop.

5. Liquidity test: BLURT/USDT pool

Beyond trading, I also wanted to test the liquidity layer available on KlingEx.

As mentioned earlier, the platform offers a BLURT/USDT liquidity pool, similar in spirit to what exists on Hive-Engine, but within a different environment and directly connected to a USDT pair.

To test this, I added 2000 BLURT and 4 USDT to the pool.

At the time of writing, this represents approximately 25.33% of the total pool share, which highlights how early this market still is and how limited the current liquidity remains.

The process itself was straightforward. Funds were added without issue, and the position was immediately reflected in the pool.

From a structural perspective, this is an important component.

Liquidity pools play a key role in early-stage markets, especially when order book activity is still limited. They can provide a baseline level of liquidity, reduce friction for smaller trades, and help bootstrap activity before deeper participation emerges.

However, the current state of the pool also makes one thing very clear.

At this stage, the BLURT/USDT market on KlingEx is still in its infancy. Liquidity is low, participation is limited, and the sustainability of the pool will depend entirely on whether more users decide to contribute and interact with it over time.

6. Testing the BLURT faucet

Another feature available on KlingEx is a BLURT faucet, which can be claimed once every 24 hours.

At the time of testing, the faucet distributes 0.1 BLURT per claim.

The process is straightforward: after logging in, the claim can be executed directly on the platform, and the tokens are credited to the account.

While the amount itself is small, this type of feature can still play a role in onboarding and user engagement. It allows new users to interact with the platform without needing to deposit funds first, and provides a simple way to test basic functionalities such as transfers or trading.

In early-stage markets, even small mechanisms like this can contribute to activity, especially if they encourage repeated interactions over time.

7. Testing an additional feature: BLURT gift codes

KlingEx also offers a feature that is not currently available on Hive-Engine: the ability to create redeemable crypto gift codes.

As part of this test, I decided to try it out directly.

The process is simple: you can generate a code containing a specific amount of tokens, which can then be shared and redeemed by anyone through the dedicated page on the exchange.

To make this test a bit more practical, I created a gift code containing 250 BLURT.

The code is:

58U2-TS4J-CEPS-MTBM

It can be redeemed here:
https://klingex.io/gift-codes

The first person to enter the code and redeem it will receive the full amount.

Beyond the obvious incentive, this feature is interesting from a usability standpoint. It opens up simple distribution mechanisms, whether for onboarding, rewards, or community initiatives, without requiring direct transfers on-chain.

If you manage to claim it, I’d be interested to hear your feedback — feel free to share it in the comments.

Conclusion

At this stage, KlingEx already provides a functional environment for BLURT.

Deposits are working, trading is operational on both sides of the market, and additional features such as the liquidity pool, faucet, and gift codes are already accessible and usable. From a technical standpoint, the foundation is there.

That said, the market is still at a very early stage.

Liquidity remains limited, volume is extremely low, and the long-term viability of the BLURT/USDT pair will depend entirely on whether users decide to actively use it — by depositing, trading, and contributing to the pool over time.

In other words, the infrastructure exists. Now it needs activity.

If you are curious, I would encourage you to test the platform yourself, explore the different features, and see how it behaves from your own perspective. As always, only deposit what you can afford to lose, especially on a young exchange with limited track record.

I would also be interested in your feedback.

Have you tried KlingEx yet?
Did you test deposits, trading, or the liquidity pool?
How does your experience compare?

Let me know in the comments.

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.

Today I am just in awe of what has unfolded, we have always allowed religious posts and discussion on Blurt and more so in the past God has been a big part of our community, we have had even some pastors post here before.

This week I was literally led to this solution for us, in a divine way you might say.

Earlier this week @kingscrown sent me a Discord invite to the NNS-Coin (996 Coin) server, I joined and noted they were listed on the Klingex.io exchange and they seems like a nice bunch.

I put a comment in general chat asking for a direct contact at Klingex for a potential listing of BLURT and this user (who is also a coin founder LRGK), who now has a Blurt account @ragnok710, gave me the link to the Klingex Discord server and told me who to speak to.

Everything fell wonderfully into place, one of the main admins I spoke to knew about Graphene as he had worked on Bitshares before, and indicated they would list us in a few days.

I pulled in @drakernoise and @saboin to assist in providing the api calls they would need to integrate BLURT.

Today this link was shared with me 😱🤯😱 in the group chat

https://klingex.io/trade/BLURT-USDT?ref=1BE81556

We got a USDT exchange listing!!!

Our contact at Klingex is so lovely, I noticed there was a faucet feature and a liquidity pool feature, so I asked about them and within minutes both were up and running and I will explain them to you shortly.

I asked about Coingecko and CMC, their aim is to list on Coingecko as soon as their volume increases, so let's please as a community help them achieve this goal.

Referral Link

Signup to Klingex with our referral link and then get your own and shill it far and wide!

https://klingex.io/trade/BLURT-USDT?ref=1BE81556

I noticed the ref link only worked on the register page, I requested that it could be ubiquitous across the site, and in minutes the UI was updated to include local storage of the ref code which then gets applied on the registration.

Amazing service!

Deposit Some Coin Yo!

How awesome is this to see BLURT on the deposit screen of an exchange again! Simply send BLURT to @klingex and use the memo assigned to your account.

You can also send USDT from Tribaldex / Hive-Engine on the Ethereum (ERC20) network, just make sure you have some ETH for gas.

Both deposits are fairly quick and arrive in minutes.

For those Monero fans, Klingex also has XMR deposits!

Liquidity Pool

Check this out, I seeded a pool with 5000 BLURT and 10 USDT to kickstart the pool at a 0.002 USD price (IMO BLURT shouldn't trade lower than this after all the recent wins we've had!)

This isn't an ordinary swap pool, this pool actually fuels the BLURT/USDT market AMM, after I created the pool I saw all these random market orders pop up that weren't mine.

As a Liquidity Provider you earn 0.3%, when you add liquidity their bot places buy/sell orders, once they are filled it closes older ones and places new ones to follow market price.

Keep in mind that if prices move a lot on one direction only, it will end up having just BLURT or just USDT (similarly to Uniswap LPs) - and it will need a rebalance.

Personal No Code AMM Bot, no API, no External Scripts!

How crazy is this, on the trading page you can click on the MM button and you will get this personalised market making bot to place orders based on your setting, no code, no api, no script running on external servers.

The help tooltips are useful to understand what each feature does.

BLURT Faucet

If you head on over to https://klingex.io/faucet you will notice the BLURT faucet, Klingex were nice enough to deposit their remaining 900 test tokens into the faucet for us, we decided to set it as 0.1 BLURT every 24 hours as a daily check-in.

There are also other coins to get which is great, @offgridlife the faucet king will love this!

As the faucet depletes we will top it up as long as it is viable, so this is great for fees, if anyone is ever stuck and needs some coin for fees they can grab it here.

This will also enhance signups and make it easier for new users to purchase BLURT to create a new account.

Gift BLURT

And the gifts still keep giving!

Go to https://klingex.io/gift-codes and you can gift BLURT to anyone with a code redeemable on Klingex. You can add a message and a surprise hidden amount, there is even a bulk create which might be useful for marketing.

Homeplay

Homeplay is a better term than homework am I right?

Here are some things you can do to help BLURT, Klingex and the wonderful coin communities that pointed us in this direction.

• Signup on Klingex.io
• Get your own referral code
• Shill your code!
• Claim BLURT and other coins from the faucet
• Deposit BLURT and USDT to Klingex
• Add BLURT and USDT into the pool - https://klingex.io/liquidity - let's get the BLURT/USDT pool to the top of the list as free marketing!
• Setup your own AMM bot with your remaining funds
• Gift BLURT to someone
• Support KGK Klingex coin as they have been good to us and didn't charge for the listing
• Follow https://blurt.blog/@klingex and their other socials
• Support NNS-Coin and soon to be listed LRGK coin, they are awesome communities that helped us find this solution.
• Lastly, trade BLURT/USDT like there is no tomorrow, let's help Klingex get more volume so they can list on Coingecko.

Please look out for the official announcement on the @klingex Blurt account, we will reblog, pin and add to annoucements. They have already announced us in their Discord!

WARNING: Don't let this market get stale like Probit, in the Klingex Discord there is a comment "we delisted btcs for 0 trading activity in 2+ months" don't let that happen to us.

We as a community need to come together and trade BLURT, use it or lose it!

1. The Person Behind This Proposal

My name is Aftab Irshad. I am the founder and sole developer of HivePostify.cloud, a fully operational blockchain-based publishing and social platform. I built it from the ground up with no external funding, no team, and no shortcuts. It manages content publishing, blockchain interaction, user management, wallet integration, and community tools, all in one unified product that is live and serving real users.

That platform is my track record. It’s not a whitepaper or a pitch deck. It’s a working product you can access in your browser today.

I joined Blurt after the personal invitation from @offgridlife, who noticed HivePostify.cloud and thought that a similar approach was just what Blurt needed. Since then, I have done what I always do before building: I listened. I connected with @megadrive, @saboin, @drakernoise, @balvinder294, @khrom, @agorise, and @mariuszkarowski. I read the development discussions on Discord. I studied the existing infrastructure, identified gaps, and learned about the community's values. This proposal reflects that process every decision in it comes from what the community shared with me.

2. Why Blurt Is the Right Place to Build This

Blurt has something that no other major blockchain social network has: a truly creator-first economic structure. Removing downvotes is not a minor user experience choice. It eliminates the main way that stake has historically silenced, punished, and driven away creators on other networks. Every creator on Blurt publishes knowing that their rewards cannot be wiped out by someone who disagrees with them. That represents real freedom of speech.

Yet, having a good social contract doesn't automatically lead to growth. Growth needs infrastructure, tools that help new users come in, create, earn, and stay. That’s what is currently lacking, and it’s exactly what BlurtPostify aims to provide.

3. What BlurtPostify Is Full Vision

BlurtPostify is not just HivePostify.cloud with a different name. It is a carefully designed publishing and social ecosystem built specifically around Blurt's values, its technical makeup, and the needs of the next generation of content creators.

The platform is centered on one key insight: the biggest barrier to Blurt's growth isn’t the blockchain quality or community strength. It’s friction. Friction in signing up, friction in publishing, friction in understanding how rewards work, and friction in accessing the value earned. BlurtPostify is an end-to-end system aimed at removing that friction.

Core Publishing Features

Zero-friction onboarding: New users can sign up in one click using Blurt Keychain. No email, phone number, WhatsApp, or identity verification is required. A creator anywhere can go from discovering Blurt to publishing their first post in under two minutes.

Long-form text publishing: A full-featured markdown editor offers live preview, drafts, scheduled publishing, tag suggestions, and community-specific posting. It's designed to provide the best writing experience on any blockchain social platform.

Short-form video first-class support: This is the biggest feature gap in the current Blurt ecosystem. @megadrive identified it directly: video is the main content medium for everyone under 30, and Blurt currently lacks a native way for users to upload video content. BlurtPostify solves this at launch. Video content is stored on BlurtPostify's own servers, giving the platform full control over performance, speed, and reliability. Videos are posted directly to the author's own Blurt account. Your video, your account, your rewards.

Image and rich media support: Full drag-and-drop media upload with IPFS pinning, inline image galleries, and responsive rendering for all device sizes.

Wallet and Financial Tools

Integrated wallet dashboard: Users can see their BLURT balance, BLURT POWER, pending rewards, and transaction history within the platform. They can power up, power down, transfer, and claim rewards without leaving the publishing interface.

Reward transparency: Every post has a clear, real-time breakdown of reward distribution. BlurtPostify defaults to 95-100% for the author. Any beneficiary fee is disclosed before publishing and is always optional.

Native token swap decentralized, cross-chain: BlurtPostify will include a native, decentralized swap layer that allows BLURT to be exchanged with tokens from connected blockchain ecosystems. This addresses the most critical liquidity challenge in the Blurt ecosystem today. The swap uses a multi-sig smart contract design no single party, including me, can move funds or change parameters alone. It’s auditable, transparent, and community-governed from the start.

Community and Discovery Tools

Curator and Power User Tools

Onboarding and Growth Engine

New user onboarding flow: First-time users are guided through Blurt's core concepts in an easy, non-technical walkthrough that takes under five minutes. This helps convert curious visitors into active community members.

Community account creation program: BlurtPostify will cover the account creation fee for new users during the initial growth phase. New creators should not have to pay to join.

Creator referral system: Built-in referral tracking rewards current community members for bringing in new active creators. Growth is driven by the community itself.

50,000 active user target Year 1: This is ambitious but achievable with the right infrastructure. Combining zero-friction onboarding, video support, and a native swap tool creates enough value to attract creators who have never thought about using a blockchain platform before.

4. Current Ecosystem Gaps and How BlurtPostify Solves Them

5. Funding Request Full Transparency

I want to be clear: I have the skills to build everything described in this proposal. What I lack is the capital to cover infrastructure costs during the pre-revenue phase.

What the funding covers

Total 12-month infrastructure cost: approximately $800–900-1200+.

This is not a salary. It is not a profit. It is the actual cost of running servers, storing media, and deploying contracts for one year while the platform works toward self-sustainability. Every cent is accounted for above, and every expense will be reported publicly on Blurt every 30 days.

Support options

6. Delivery Roadmap

Every phase ends with a public report covering what was built, what was spent, what is next, and what changed.

7. The People Who Shaped This Proposal

The zero-KYC signup design came from @agorise and @megadrive. The video-to-author-account setup originated from a discussion between @megadrive and @saboin about the current limits of blurt.media. The multi-sig swap security model was based on @balvinder294's Safe{Wallet} proposal and @drakernoise's multi-sig Blurt implementation. The self-sustaining fee model stemmed from @offgridlife's advice to build and earn instead of asking and waiting. The roadmap for curator tools was influenced by @khrom's views on the needs of independent developers. The multi-chain publishing feature on the long-term roadmap was suggested by @mariuszkarowski.

If you see your suggestion in this proposal, it’s because it was included intentionally. You played a role in shaping this.

8. My Commitment

I will post a development update on Blurt every week from the day this proposal is funded. I won’t wait for the right moment. Every week, without fail.

I will share a complete financial report every 30 days, detailing every dollar received and spent, along with every receipt.

If for any reason the project cannot be completed, I will return all unspent funds to the community and publicly explain what went wrong.

I am asking for one opportunity. One chance to show this community what a dedicated builder with the right support can achieve. The cost of that chance, $800 to $1200+, is a small investment for the potentially high return for the entire Blurt ecosystem.

9. How to Support This Proposal

Upvote and resteem. The more community members who see this proposal, the better decision the community will make.

Comment honestly. If you notice a gap in the plan, point it out. I would prefer to make adjustments now rather than after deployment.

Delegate to @aftabirshad. If you want to support this project without providing direct funds, delegation is the most flexible and reversible option.

Contact me on Discord (@aftabirshad). For detailed technical discussions, funding arrangements, or any questions that need more than a comment thread.

I have spent years building in Web3 with just my skills and dedication. I am asking Blurt for the one thing I have never had: a community that believes in the work early enough to help make it happen at full scale.

Check out HivePostify.cloud. Then come back and tell me this isn't worth funding.

Well, one thing to remember is that I have papers due and I will start working on them after I submit them, meaning that I will start working on the dates that will be given.

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

The new feature makes it possible to assign the person who referred a given user.

How it works in practice

The whole process was designed to be as simple as possible — especially for people who are just beginning their adventure with Blurt.

1. Entering through a special link

A new user can enter the creator through a link containing a voucher.

Example of such a link:

https://blurtplugin.online/account/?voucher=BLURTTEZD4ZPGEQ6L

After entering:

• the voucher code is filled in automatically,
• the system immediately checks whether it is valid,
• the user does not have to type anything manually.

2. Automatic setting of the referring person

Since every voucher created by my.blurtplugin.online is assigned to a specific user who created it or for whom it was generated, the system automatically suggests that person as the referrer.

The user sees the option:

• “Use voucher owner as referrer”

And in most cases they do not have to change anything — everything is already set.

3. Possibility to change the referrer

If someone wants to, they can:

• uncheck the option,
• enter another username as the referring person.

This gives full freedom — nothing is imposed rigidly.

4. Account creation

After that, everything works just like before:

• the user enters the account name,
• the keys are generated,
• the account is created.

The whole process is fast and does not require any technical knowledge.

5. Saving the referral

At the end, the system saves the referral information, so it is known who invited the new user.

The ref link generator is not working yet, but it will be available from the my.blurtplugin.online panel.

However, if you take a voucher and place it in the link instead of the example one and send it to your friends, it will already work:

https://blurtplugin.online/account/?voucher=enter_voucher_here

Summary

The new referral system makes the Account Creator not only a tool for creating accounts, but also a simple way to invite new users to Blurt.

The whole process is:

• simple,
• fast,
• and works practically automatically.

I encourage everyone to test the system and invite new users with the help of referrals.

Btw:
The link added in the post is also a working voucher that you can use.

Best regards :)