<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Beldex Marketing</title>
    <description>The latest articles on DEV Community by Beldex Marketing (@beldex).</description>
    <link>https://dev.to/beldex</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4164216%2F3a296f3e-5997-4382-bf74-21ba8f56a096.jpg</url>
      <title>DEV Community: Beldex Marketing</title>
      <link>https://dev.to/beldex</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/beldex"/>
    <language>en</language>
    <item>
      <title>Beldex Browser v1.4.2 Is Live: AI That Doesn’t Know Who You Are</title>
      <dc:creator>Beldex Marketing</dc:creator>
      <pubDate>Fri, 06 Nov 2026 11:31:46 +0000</pubDate>
      <link>https://dev.to/beldex/beldex-browser-v142-is-live-ai-that-doesnt-know-who-you-are-2l37</link>
      <guid>https://dev.to/beldex/beldex-browser-v142-is-live-ai-that-doesnt-know-who-you-are-2l37</guid>
      <description>&lt;p&gt;Every AI assistant asks for something in return: an account, a phone number, a history of everything you’ve ever asked.&lt;/p&gt;

&lt;p&gt;Beldex Browser v1.4.2 brings AI to your browser on different terms. Ask, summarize, create and listen, without handing over who you are.&lt;/p&gt;

&lt;h2&gt;
  
  
  What’s new in v1.4.2
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Summarize your files
&lt;/h3&gt;

&lt;p&gt;Attach a document and get the key points in seconds. Beldex Browser reads PDF, Word, Excel, TXT and CSV files, plus common image formats. Attach up to 10 files per message (up to 10 MB per document and 5 MB per image).&lt;/p&gt;

&lt;p&gt;Text is extracted on your phone, and photo metadata is stripped from images before anything is sent. Your files are deleted when you close the session, and nothing is cached.&lt;/p&gt;

&lt;p&gt;The same works for web pages: get a quick summary of what you’re reading without leaving the tab.&lt;/p&gt;

&lt;h2&gt;
  
  
  Generate images
&lt;/h2&gt;

&lt;p&gt;Describe what you want and get a 1K image back. Every user gets a free daily allowance of 20 images, no sign-up needed. Generated images carry provenance markers, so they can be identified as AI-made.&lt;/p&gt;

&lt;h2&gt;
  
  
  Talk instead of type
&lt;/h2&gt;

&lt;p&gt;Tap the microphone and speak your question. The mic turns on only when you tap it. There is no wake word and no always-listening mode.&lt;/p&gt;

&lt;h2&gt;
  
  
  Hear the answer
&lt;/h2&gt;

&lt;p&gt;Tap a button on any reply and Beldex Browser reads it aloud. Great for when your hands are busy. Voice currently supports English (en-US), with more on the way.&lt;/p&gt;

&lt;p&gt;The part that makes it different: AI without a name attached&lt;br&gt;
Most AI tools know exactly who you are. Beldex Browser’s AI is built so the AI provider doesn’t.&lt;/p&gt;

&lt;h3&gt;
  
  
  Here is the path every AI request takes:
&lt;/h3&gt;

&lt;p&gt;Your phone → BelNet (onion-routed) (encrypted, hop by hop)&lt;/p&gt;

&lt;p&gt;→ Exit node (sees only the destination)&lt;/p&gt;

&lt;p&gt;→ AI provider (sees your request, not who sent it)&lt;/p&gt;

&lt;p&gt;Your&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt; IP address is hidden. Requests travel through BelNet, our decentralized VPN, so the AI provider sees an exit node’s address, not yours.&lt;/li&gt;
&lt;li&gt;Encrypted all the way. Your connection to the AI provider is protected by TLS, so the relays and the exit node can’t read what you send.&lt;/li&gt;
&lt;li&gt;No Beldex server in the middle. Beldex doesn’t run a server that your AI requests pass through.&lt;/li&gt;
&lt;li&gt;No account, no login. There’s no user account, device ID or install ID attached to your requests.&lt;/li&gt;
&lt;li&gt;No tunnel, no request. The Browser checks that BelNet is connected before sending a
nything.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The result: the AI can answer your question without learning that it was you who asked it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Being straight with you
&lt;/h2&gt;

&lt;p&gt;Privacy claims only mean something when they’re specific. So here’s what this does and doesn’t mean:&lt;/p&gt;

&lt;p&gt;The AI provider reads what you send it. It has to, to answer. What it can’t do is tie the request to your identity or location. Think of it as asking a question through a mask, not whispering it. Don’t send anything you wouldn’t be comfortable sending anonymously.&lt;/p&gt;

&lt;p&gt;Voice input uses your phone’s built-in speech recognition. On most Android phones that’s provided by Google, and it may process audio on its own servers. Beldex Browser never records or stores your audio. If you’d rather not use it, just type.&lt;/p&gt;

&lt;p&gt;Nothing runs until you tap. Each AI feature starts only when you choose to use it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Don’t take our word for it
&lt;/h2&gt;

&lt;p&gt;The AI client code is public on the Beldex Browser GitHub repository. Read it, test it, tell us what you find.&lt;/p&gt;

&lt;h2&gt;
  
  
  What’s next
&lt;/h2&gt;

&lt;p&gt;We’re just getting started. On our roadmap: AI-generated files, more control over which AI features you use, more languages for voice, and continued security testing of the AI features.&lt;/p&gt;

&lt;h2&gt;
  
  
  Update now
&lt;/h2&gt;

&lt;p&gt;Beldex Browser v1.4.2 is available on Google Play.&lt;/p&gt;

&lt;p&gt;Update on Google Play → &lt;a href="https://play.google.com/store/apps/details?id=io.beldex.beldex_browser" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=io.beldex.beldex_browser&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Questions? Join the conversation with the Beldex community.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>automation</category>
      <category>bitcoin</category>
    </item>
    <item>
      <title>Privacy Token Standard Goes Live on the Beldex Testnet</title>
      <dc:creator>Beldex Marketing</dc:creator>
      <pubDate>Tue, 06 Oct 2026 10:00:46 +0000</pubDate>
      <link>https://dev.to/beldex/privacy-token-standard-goes-live-on-the-beldex-testnet-1of7</link>
      <guid>https://dev.to/beldex/privacy-token-standard-goes-live-on-the-beldex-testnet-1of7</guid>
      <description>&lt;p&gt;Privacy shouldn’t be something developers have to add after an application or asset has already been built. It has to be built in. That’s the maxim with which Beldex has built its network, products, and infrastructure.&amp;nbsp;&lt;/p&gt;

&lt;p&gt;With the launch of &lt;strong&gt;Confidential Assets, also known as Privacy Tokens, on the Beldex testnet&lt;/strong&gt;, we are taking another step toward making privacy part of the infrastructure itself.&lt;/p&gt;

&lt;p&gt;Privacy Tokens enable developers and projects to issue their own privacy-preserving tokens directly on the Beldex network, with transaction confidentiality built into the asset layer from the beginning.&lt;/p&gt;

&lt;p&gt;The implementation is being introduced through the &lt;strong&gt;Proto testnet hard fork at testnet block height 4,242,200.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Developers can now begin deploying and testing Privacy Tokens on the Beldex testnet at &lt;strong&gt;&lt;a href="https://testnet.beldex.dev/" rel="noopener noreferrer"&gt;testnet.beldex.dev&lt;/a&gt;.&lt;/strong&gt; Similarly, they can obtain the testnet BDX from &lt;strong&gt;&lt;a href="https://faucet.beldex.dev/" rel="noopener noreferrer"&gt;faucet.beldex.dev&lt;/a&gt;.&lt;/strong&gt;&amp;nbsp;&lt;/p&gt;

&lt;h2&gt;
  
  
  What Are Privacy Tokens?
&lt;/h2&gt;

&lt;p&gt;Most blockchain assets operate on transparent networks where transaction activity can be publicly inspected. Even when an application adds privacy features at another layer, the underlying asset and its transaction history may remain completely visible.&lt;/p&gt;

&lt;p&gt;Privacy Tokens take an entirely different approach.&lt;/p&gt;

&lt;p&gt;They are assets issued directly on the Beldex network that inherit transaction-level privacy from the network. At launch, Privacy Tokens use Beldex's &lt;strong&gt;UTXO-based architecture&lt;/strong&gt;, extending the privacy model already used for BDX to independently issued assets.&lt;/p&gt;

&lt;p&gt;This means projects can create tokens where sensitive transaction information, including sender and recipient details, transferred amounts, and balances, is protected from public visibility.&lt;/p&gt;

&lt;p&gt;Instead of building a token first and finding a way to make it private later, developers can start with privacy at the asset layer.&lt;/p&gt;

&lt;p&gt;As Beldex Chairman &lt;strong&gt;Afanddy Bin Hushni&lt;/strong&gt; explains:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Privacy Tokens lets developers build an entire application economy where privacy is the starting point. It isn’t just another token standard. Whether it’s a private DeFi protocol, a confidential rewards system, or a new dApp entirely that no one has previously imagined, these assets all inherit the same cryptographic guarantees that protect every BDX transaction on our network.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  From a Privacy Ecosystem to Privacy Infrastructure
&lt;/h2&gt;

&lt;p&gt;Beldex has spent years building applications around private digital interactions.&lt;/p&gt;

&lt;p&gt;Today, the ecosystem includes &lt;strong&gt;BChat&lt;/strong&gt; for private messaging, &lt;strong&gt;BelNet&lt;/strong&gt; for decentralized network routing, the &lt;strong&gt;Beldex Browser&lt;/strong&gt; for private web access, the &lt;strong&gt;Beldex Wallet&lt;/strong&gt;, and &lt;strong&gt;BNS&lt;/strong&gt; for decentralized blockchain-based names.&lt;/p&gt;

&lt;p&gt;Privacy Tokens expand what can be built on top of this existing infrastructure.&lt;/p&gt;

&lt;p&gt;Instead of Beldex being the only team building privacy-focused applications within the ecosystem, developers can begin creating their own applications and asset economies on the network.&lt;/p&gt;

&lt;p&gt;A project could issue a Privacy Token and use it as the native asset of a privacy-focused application. Depending on the application, the token could support private payments, rewards, access mechanisms, community utilities, or entirely new use cases.&lt;/p&gt;

&lt;p&gt;The important distinction is that privacy does not need to be recreated separately by every project. It begins at the network and asset layers itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Developer Stack Behind Privacy Tokens
&lt;/h2&gt;

&lt;p&gt;Launching a token standard alone is not enough. Developers also need practical tools that allow applications and users to interact with those assets.&lt;/p&gt;

&lt;p&gt;Alongside Privacy Tokens, Beldex is introducing the infrastructure required to start building web-based applications around them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Beldex Extension Wallet
&lt;/h3&gt;

&lt;p&gt;The &lt;strong&gt;&lt;a href="https://chromewebstore.google.com/detail/beldex-wallet/onhnehjhhionmnbidajneakngpiefapa" rel="noopener noreferrer"&gt;Beldex Extension Wallet&lt;/a&gt;&lt;/strong&gt; provides a browser-based interface through which users can create and manage their Beldex wallets and interact with supported applications.&lt;/p&gt;

&lt;p&gt;For developers, it creates the connection between a web application and the user's wallet.&lt;/p&gt;

&lt;h3&gt;
  
  
  Web3JS SDK
&lt;/h3&gt;

&lt;p&gt;The &lt;strong&gt;&lt;a href="https://www.npmjs.com/package/@bdxi/web3js" rel="noopener noreferrer"&gt;Beldex Web3JS SDK&lt;/a&gt;&lt;/strong&gt; gives developers the tools required to integrate Beldex functionality into web applications.&lt;/p&gt;

&lt;p&gt;Together, the Extension Wallet and Web3JS SDK allow applications to connect to wallets, retrieve relevant wallet information, initiate supported transactions, and integrate Privacy Tokens into application workflows while preserving the underlying privacy model.&lt;/p&gt;

&lt;p&gt;With these components available alongside Privacy Tokens, developers now have the beginnings of a complete stack for building privacy-first applications on Beldex:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Privacy Tokens → Extension Wallet → Web3JS SDK → Privacy-first dApps&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What Can Developers Build?
&lt;/h2&gt;

&lt;p&gt;Privacy Tokens are the underlying infrastructure rather than a single predetermined use case.&lt;/p&gt;

&lt;p&gt;They could support applications such as private payment systems, private swap platforms, confidential rewards programs, privacy-focused DeFi applications, decentralized platforms, membership or access systems, and other applications where publicly exposing users' financial activity would be undesirable.&lt;/p&gt;

&lt;p&gt;And because Privacy Tokens are issued on Beldex, developers do not need to create an entirely new privacy blockchain simply to launch a private asset.&lt;/p&gt;

&lt;p&gt;They can build on an existing Layer 1 designed around transaction privacy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Start With UTXO?
&lt;/h2&gt;

&lt;p&gt;Privacy Tokens have initially launched using Beldex's UTXO-based architecture.&lt;/p&gt;

&lt;p&gt;This allows the first version of the standard to build directly on the privacy architecture already used by the Beldex network instead of attempting to retrofit privacy onto a transparent account-based environment.&lt;/p&gt;

&lt;p&gt;But UTXO-based Privacy Tokens are only the first stage.&lt;/p&gt;

&lt;p&gt;Beldex is also developing &lt;strong&gt;account-based addresses&lt;/strong&gt; and a planned &lt;strong&gt;EVM-compatible sidechain.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Once these components are introduced, the goal is to provide a path for projects that begin with UTXO-based Privacy Tokens to move / bridge into an EVM-compatible environment while retaining privacy-oriented capabilities.&lt;/p&gt;

&lt;p&gt;The approach is deliberate:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Privacy first. EVM compatibility second.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;So, instead of beginning with a transparent architecture and adding privacy afterward, Beldex is building outward from its existing privacy foundation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building an Open Privacy Economy
&lt;/h2&gt;

&lt;p&gt;Privacy Tokens represent a broader change in how Beldex is evolving.&lt;/p&gt;

&lt;p&gt;Beldex began by building its own privacy-focused ecosystem. The next phase is about giving developers the infrastructure to build their own products, applications, and economies on top of it.&lt;/p&gt;

&lt;p&gt;Privacy Tokens provide the asset layer.&lt;/p&gt;

&lt;p&gt;The Extension Wallet provides the user interface.&lt;/p&gt;

&lt;p&gt;The Web3JS SDK provides the developer interface.&lt;/p&gt;

&lt;p&gt;Together, they move Beldex closer to becoming an open infrastructure layer for applications where privacy is a default property rather than an optional feature.&lt;/p&gt;

&lt;p&gt;And this is only the testnet stage.&lt;/p&gt;

&lt;p&gt;Developers can now begin deploying Privacy Tokens, testing integrations, experimenting with applications, and providing feedback ahead of the planned mainnet rollout. &lt;strong&gt;They can also start applying for grants at &lt;a href="https://www.beldex.io/grants" rel="noopener noreferrer"&gt;beldex.io/grants&lt;/a&gt;.&lt;/strong&gt;&amp;nbsp;&lt;/p&gt;

&lt;h2&gt;
  
  
  Start Building on the Beldex Testnet
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;Proto testnet hard fork&lt;/strong&gt; introduces Privacy Tokens at &lt;strong&gt;block height 4,242,200.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Developers can explore the Beldex testnet at: &lt;strong&gt;testnet.beldex.dev&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The Beldex Extension Wallet and Web3JS SDK provide the supporting tools for developers looking to begin integrating Beldex into web applications.&lt;/p&gt;

&lt;p&gt;For Beldex, this launch marks an important transition: from building privacy applications ourselves to providing the infrastructure for others to build the next generation of them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Privacy Tokens are now live on testnet. It's time to build privacy into the asset itself.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>webdev</category>
      <category>web3</category>
      <category>testdev</category>
    </item>
  </channel>
</rss>
