# Bless

> Bless is a decentralized edge-computing network that aggregates spare capacity from everyday devices for applications and workloads such as AI, data processing, and gaming.

- Canonical URL: https://iq.wiki/wiki/bless
- Categories: Projects & Protocols
- Tags: AIInfrastructure, Infrastructure
- Created: 2026-11-18T02:38:41.870Z
- Last updated: 2026-11-18T02:38:41.870Z
- Source: IQ.wiki — the world's largest blockchain and crypto encyclopedia (https://iq.wiki)

---

**Bless** is a decentralized edge-computing network that combines spare computing capacity from everyday devices so applications can run workloads closer to their users. Founded in 2022, it was developed by TX Labs and aims to provide an alternative to relying solely on centralized cloud infrastructure. Its design lets applications draw computing resources from devices used by their own communities, so available capacity can grow as an application attracts more users.[[1]](#cite-id-l8lf4xgc7g)[[2]](#cite-id-mep5ll62ke)[[3]](#cite-id-xrensevn7q)

Bless has also developed services for analyzing user interactions with large language models (LLMs). The project describes these services as using consent-based behavioral data to provide insights into user intent, audience journeys, and conversion drivers.[[4]](#cite-id-jslask1t78)

## Overview

Bless is a decentralized edge-computing network that pools spare capacity from everyday devices for applications. Its network-neutral framework and nested-node infrastructure coordinate workloads across those devices, using mechanisms for matching resources to tasks, distributing tasks, and verifying results.[[1]](#cite-id-l8lf4xgc7g)[[2]](#cite-id-mep5ll62ke)

Bless launched its [mainnet](https://iq.wiki/wiki/mainnet) on September 23, 2025.[[11]](#cite-id-zz6ekqh81h) It also provides services that analyze consent-based interactions between users and large language models (LLMs) to identify user intent and conversion drivers.[[4]](#cite-id-jslask1t78)

## History

Bless was founded in 2022. Its founders came from [blockchain](https://iq.wiki/wiki/blockchain) and infrastructure organizations including [Akash Network](https://iq.wiki/wiki/akash-network), [Binance](https://iq.wiki/wiki/binance) Research, and NGC Ventures. A 2024 report identified Michael Chen, Derek Anderson, Butian Li, and Liam Zhang as creators of the project; it described their work as an effort to combine fragmented computing resources into a more accessible network. A separate account identifies Li Butian as the chief executive officer, Anderson as chief technology officer, and Chen as a co-founder.[\[1\]](#cite-id-l8lf4xgc7g)​[\[5\]](#cite-id-55mwf2o9cf)​[\[6\]](#cite-id-hh5pmhssr2)​

In late 2024, Bless launched an incentivized [testnet](https://iq.wiki/wiki/testnet) and released a Chrome extension for joining the network. It also released developer documentation and the open-source b7s [node](https://iq.wiki/wiki/node) client. On March 5, 2025, a Bless post reported 3 million active nodes and said final testing of command-line interface and software development kit versions was underway.[\[6\]](#cite-id-hh5pmhssr2)​[\[7\]](#cite-id-gwqd0yuo9j)​

Bless had planned a [mainnet](https://iq.wiki/wiki/mainnet) launch in the first quarter of 2025. Its September 2025 white paper still described mainnet as the next significant milestone, with production application deployments as its intended purpose. The paper listed planned priorities including improved verification, broader programming-language support, better orchestration, and additional security features. Bless announced the mainnet launch on September 23, 2025, and BLESS trading began that day.[\[5\]](#cite-id-55mwf2o9cf)​[\[2\]](#cite-id-mep5ll62ke)​[\[11\]](#cite-id-zz6ekqh81h)​[\[12\]](#cite-id-q69y1yuyy2)​

## Funding

In March 2022, Bless raised a reported $3 million pre-seed round led by NGC Ventures. It raised a further $5 million in a seed round led by M31 Capital and Frachtis, which began in February and closed in April 2024 and was announced on May 20, 2024. Other named participating investors included No Limit Holdings, MH Ventures, Interop Ventures, Plassa Capital, and Chorus One. The rounds brought reported funding to $8 million; another 2024 account also reported the total and named NGC Ventures and M31 Capital as leads.[[13]](#cite-id-d3uxqzguff)[[6]](#cite-id-hh5pmhssr2)[[5]](#cite-id-55mwf2o9cf)

## Network Design

Bless combines idle CPU, graphics processing unit (GPU), memory, and other device resources in a distributed network. Its white paper describes a network-neutral application framework, called nnApp, and “nestled [node](https://iq.wiki/wiki/node)” infrastructure through which applications can use computing resources contributed by their users. Under this model, an application’s capacity can expand as it gains users and participating devices. The project presents this design as a way for applications to perform intensive off-chain computation while continuing to use [blockchains](https://iq.wiki/wiki/blockchain) for functions that benefit from on-chain execution.[\[2\]](#cite-id-mep5ll62ke)​[\[5\]](#cite-id-55mwf2o9cf)​

The white paper identifies four core technologies:

* **Dynamic Resource Matching** assigns tasks to devices according to factors such as response time, throughput, reliability, past performance, geographic proximity, and device availability.
* **Randomized Distribution** uses Greco-Latin-square schemes to make task assignments harder to predict while respecting resource-allocation constraints.
* **WebAssembly (WASM) Secure Runtime** isolates workloads from host devices and is intended to provide memory safety, control-flow integrity, and controls over resources such as CPU cores, GPUs, and memory.
* **Dynamic Verification** selects ways to check results according to the type of computation being performed.[\[2\]](#cite-id-mep5ll62ke)

Bless’s orchestration system monitors device availability, performance, location, and workload conditions, routes requests to suitable device clusters, and can reassign tasks when a device fails or degrades. The white paper claims that reassignment can occur within 800 milliseconds and that failover can take less than a second. It also describes ahead-of-time compilation and bytecode obfuscation, and elsewhere refers to just-in-time compilation and in-memory encryption. These mechanisms are intended to protect workloads and reduce exposure of application code on participating devices.[\[2\]](#cite-id-mep5ll62ke)​

Verification methods described in the paper include aggregating results and identifying outliers for quantitative tasks, weighting results according to participant reliability and performance, recording reputation, and using consensus methods such as Practical [Byzantine Fault Tolerance](https://iq.wiki/wiki/byzantine-fault-tolerance) or RAFT for binary decisions. It also proposes [zero-knowledge proofs](https://iq.wiki/wiki/zero-knowledge-proofs-zkps) as a way to verify results without revealing underlying data or algorithms. The paper presents these methods as modular and adaptable to application requirements.[\[2\]](#cite-id-mep5ll62ke)​

## Participation and Applications

People can register devices through desktop applications, Chrome extensions, mobile apps, or Docker images. The desktop, mobile, and Docker clients can expose CPU, GPU, and memory resources for more demanding workloads; the Chrome extension is presented as a lighter option that can use WebGPU. Device benchmarking assesses computing performance, memory, storage, and network connectivity, while ongoing monitoring tracks task completion, execution time, result accuracy, and availability. A reputation system uses past performance in future task assignment and compensation.[\[2\]](#cite-id-mep5ll62ke)​

The project’s website also offers a desktop quick-start installer and browser extension for contributing idle computing capacity. It says laptops, desktops, phones, and tablets can participate without specialized hardware, provided they have a stable internet connection. Users’ devices and preferences are matched to tasks, and data collection is described as opt-in.[\[8\]](#cite-id-e5uqccsk2d)​

Developers can use a Bless framework to specify workload type, performance and geographic requirements, and security needs. The white paper lists machine-learning inference, data processing, cryptographic operations, and custom computations as possible workloads. Tasks may be distributed as WASM binaries with cryptographic integrity checks, and results are checked through predetermined verification functions. The b7s client, command-line tools, WASM framework, APIs, and plugins are described as ways to package and submit tasks or integrate applications.[\[2\]](#cite-id-mep5ll62ke)​[\[6\]](#cite-id-hh5pmhssr2)​

The project identifies artificial intelligence and machine learning, [blockchain](https://iq.wiki/wiki/blockchain) infrastructure, and traditional and [Web3](https://iq.wiki/wiki/web3) applications as target areas. Proposed uses include AI inference, edge AI, agentic applications, web hosting, content delivery, data processing near its source, and Internet of Things workloads. For blockchains, Bless proposes running [validators](https://iq.wiki/wiki/validator) and infrastructure independently of centralized cloud providers and performing off-chain computation for decentralized applications. The white paper also describes distributing parts of a workload across devices with different capabilities.[\[2\]](#cite-id-mep5ll62ke)​[\[3\]](#cite-id-xrensevn7q)​

Bless’s website describes multiplayer gaming as another possible use: devices near players could process game logic, physics, and state updates. Other reported examples include real-time rendering and running AI models on user devices, while autonomous driving and voice recognition are cited as potential applications where rapid processing could matter. These are presented as potential uses rather than documented deployments.[\[8\]](#cite-id-e5uqccsk2d)​[\[6\]](#cite-id-hh5pmhssr2)​

Bless presents its distributed model as a way to reduce latency by placing computing closer to users and to reduce reliance on centralized infrastructure. Its white paper claims that costs can be about 10% of conventional cloud costs, attributing the difference to the use of existing devices rather than purpose-built data centers. The paper also claims low latency, cost savings, and security and sustainability benefits; these are project claims rather than independently established performance results.[\[2\]](#cite-id-mep5ll62ke)​[\[3\]](#cite-id-xrensevn7q)​

## Node Rewards and Network Scale

​[Node](https://iq.wiki/wiki/node) operators contribute spare computing capacity and can earn rewards for verified work. The project’s FAQ says contributions are initially calculated according to the time the extension is actively running; completed computing tasks are expected to become part of the calculation in the future. Referrals and specified achievements may also earn bonuses. Bless says device and user preferences are used to match participants with computing tasks.[\[8\]](#cite-id-e5uqccsk2d)​

The white paper describes a [testnet](https://iq.wiki/wiki/testnet) on [Solana](https://iq.wiki/wiki/solana) with more than 5 million [nodes](https://iq.wiki/wiki/node) or node operators and says the four core technologies had been implemented. Bless’s AI service page separately reports more than 5 million active users in 170 countries, while its broader website describes a behavioral-data marketplace drawing on more than five million user-maintained nodes. These figures are project-reported measures of network reach and activity.[\[2\]](#cite-id-mep5ll62ke)​[\[4\]](#cite-id-jslask1t78)​[\[8\]](#cite-id-e5uqccsk2d)​

## Data and AI Services

Bless describes a service for analyzing interactions between real users and LLMs. Its stated purpose is to identify user intent and conversion drivers from conversations, which the company argues are not adequately captured by existing attribution models. The product offering includes a Real-User LLM Insight Lens for examining high-value conversations and their financial impact, and a Real-User Query Engine for querying audience behavior data at scale. The company provides structured JSON feeds designed to connect with analytics and AI pipelines.[[4]](#cite-id-jslask1t78)

Listed applications include studying user–LLM interactions; tracking information sources, tone, and accuracy; benchmarking changes over time; mapping user journeys and drop-offs; analyzing assistive content; segmenting findings by geographic and demographic characteristics; tracking brand narratives; assessing how LLMs perceive a brand; and measuring response effectiveness. Bless characterizes its data as capturing intent rather than only clicks, and describes the service as designed for enterprise governance and compliance.[[4]](#cite-id-jslask1t78)

The company describes a four-stage data process: it collects session indicators and minimal personally identifiable information with explicit consent; anonymizes data locally before upload; checks sessions against integrity constraints; and delivers anonymized, labelled feeds to secure cloud endpoints. It says the architecture uses two layers of personally identifiable information removal and independent anonymization intended to prevent re-identification. Users can pause collection, inspect their data, and revoke consent. Bless characterizes the design as privacy-first and intended to meet legal data-privacy standards.[[4]](#cite-id-jslask1t78)

## BLESS Token and Governance

The white paper defines BLESS as Bless Network’s native utility and [governance token](https://iq.wiki/wiki/governance-tokens). It describes uses that include paying for computing services, compensating [node](https://iq.wiki/wiki/node) operators for verified work, qualifying operators or devices for service pools, providing performance [collateral](https://iq.wiki/wiki/collateral), and participating in protocol governance. Developers and enterprises pay protocol-defined fees based on workload type, volume, and performance requirements. Of those fees, 90% is allocated to node operators supplying computing resources and 10% to a network treasury for development, security, and ecosystem operations. Operators are paid for verified work; participants who perform no work receive no payment.[\[2\]](#cite-id-mep5ll62ke)​

The white paper proposes a [collateral](https://iq.wiki/wiki/collateral) model under which service providers, including [node](https://iq.wiki/wiki/node) operators, stake BLESS. Stake may be partially or fully forfeited for failing to complete tasks, reporting inaccurate results, or otherwise undermining network integrity. It describes governance proposals and votes on technical parameters, upgrades, verification and [staking](https://iq.wiki/wiki/staking) rules, and ecosystem-resource allocation, including grants. Governance is described as voluntary and uncompensated, with voting rights conferring no ownership, dividend, or profit-sharing interest in Bless Network, TX Labs, or affiliated entities.[\[2\]](#cite-id-mep5ll62ke)​

The white paper specifies a fixed total supply of 10 billion BLESS tokens at genesis, with the following allocation and vesting schedule:

* **Pre-seed sale:** 6.25%, with a 12-month cliff followed by quarterly vesting over 24 months, fully vested 36 months after the token generation event (TGE).
* **Seed sale:** 10%, on the same schedule as the pre-seed sale.
* **Advisors:** 3%, with a 12-month cliff and quarterly vesting over 60 months, fully vested 72 months after TGE.
* **Team:** 15%, on the same 72-month schedule as the advisor allocation.
* **Grants:** 2.75%, with a six-month cliff and quarterly vesting over 24 months, fully vested 30 months after TGE.
* **Foundation:** 10%, with a six-month cliff and semiannual vesting over 60 months, fully vested 66 months after TGE.
* **Liquidity provisioning:** 3%, unlocked at TGE.
* **Ecosystem and marketing:** 5%, unlocked at TGE.
* **Community** [**airdrop**](https://iq.wiki/wiki/airdrop)**:** 10%, unlocked at TGE for eligible community participants and early network contributors.
* **Community incentives:** 35%, vested monthly over 84 months from TGE as compensation for verified contributions, including node-operator work.[\[2\]](#cite-id-mep5ll62ke)

The paper says grants support developers and researchers; foundation tokens fund protocol development, audits, and network operations; and ecosystem and marketing tokens fund integrations, developer onboarding, and network growth. Bless’s posts also describe longer [staking](https://iq.wiki/wiki/staking) periods as earning users more BLESS. The project said its 12-month staking positions unlocked on September 23, 2026, when users could withdraw them through the Bless dashboard, and described the associated “9.23” distribution as its largest [airdrop](https://iq.wiki/wiki/airdrop) to date. Separately, Bless announced that BLESS spot trading would open on [KuCoin](https://iq.wiki/wiki/kucoin) at 10:00 UTC on August 28, 2026.[\[2\]](#cite-id-mep5ll62ke)​[\[9\]](#cite-id-elpv5jjqy9)​[\[14\]](#cite-id-3jc0q53u1n)​[\[15\]](#cite-id-anc9r36r61)​

A third-party profile refers to the ecosystem token as BLS and describes it as being used for contributor incentives, transaction payments, governance, and staking. The white paper and Bless’s own announcements use the ticker BLESS.[\[6\]](#cite-id-hh5pmhssr2)​[\[2\]](#cite-id-mep5ll62ke)​[\[9\]](#cite-id-elpv5jjqy9)​

## Security Review

Halborn assessed Bless’s Bless Token and Bless Time Solana programs from August 25 to August 29, 2025; its report was last updated September 4, 2025. The reviewed programs support token management and distribution, including [airdrops](https://iq.wiki/wiki/airdrop) to whitelisted users. [Merkle trees](https://iq.wiki/wiki/merkle-tree) are used to verify claim eligibility, amounts, and potential lock-up periods. The assessment used manual review and scripted testing; third-party dependencies, economic attacks, and features implemented after remediation commits were outside its scope.[\[10\]](#cite-id-svhv8085by)​

Halborn reported one informational finding and no critical, high-, medium-, or low-severity findings. The issue concerned an instruction that initialized an [airdrop](https://iq.wiki/wiki/airdrop) state without validating that the supplied token mint matched the mint configured in the Bless Time token state. Because the airdrop state also creates a vault, use of the wrong mint could associate later administrative actions, such as vault funding and setting a Merkle root, with an incorrect state; funds sent to the vault could then be locked in an unrelated context and the airdrop campaign could fail. Halborn rated the finding informational, with a BVSS score of 1.0, and recommended requiring the token-state account associated with the same mint.[\[10\]](#cite-id-svhv8085by)​

The report records that the Bless team acknowledged the finding on September 3, 2025, but preferred to retain control over the token supplied to the function rather than hard-code that control. Its summary states that 100% of reported findings had been addressed. Halborn also reported dependency-audit results concerning timing variability in curve25519-dalek scalar subtraction and a signing-function oracle attack in ed25519-dalek, and recommended a follow-up assessment within six months or after a material codebase change, whichever came first.[\[10\]](#cite-id-svhv8085by)​

## Competition and Challenges

Bless characterizes traditional cloud providers such as Amazon Web Services, Google Cloud Platform, and Microsoft Azure as concentrated sources of computing capacity that can expose users to providers’ outages, regulatory decisions, and business choices. The white paper contrasts its approach with earlier distributed-computing systems that it says often required technical expertise, complex setup, and manual coordination. Bless presents browser extensions, desktop software, and automated orchestration as ways to simplify participation and task management.[\[2\]](#cite-id-mep5ll62ke)​

A [Gate](https://iq.wiki/wiki/gate) Learn account places Bless in a crowded decentralized physical infrastructure network computing sector alongside projects including [Akash Network](https://iq.wiki/wiki/akash-network) and [Golem Network](https://iq.wiki/wiki/golem-network). It identifies network stability, user trust, educating nontechnical participants, and attracting both developers and device operators as challenges. The article also reports complaints about unstable node connections during [testnet](https://iq.wiki/wiki/testnet) activity and says that early [node](https://iq.wiki/wiki/node) numbers and reliability could affect service quality. It identifies technical risks involving node security, fraud prevention, disconnections, and computation errors, as well as regulatory scrutiny concerning shared computing and access to user devices or sensitive data.[\[6\]](#cite-id-hh5pmhssr2)​

Bless’s [whitepaper](https://iq.wiki/wiki/white-paper) describes plans to collaborate with application developers, infrastructure providers, and technology platforms, and to pursue compatibility with major [blockchain](https://iq.wiki/wiki/blockchain) networks and AI development frameworks. The project’s broader claims about reducing cloud costs, providing reliable low-latency computing, and serving large-scale workloads depend on the performance and adoption of its distributed network.[\[2\]](#cite-id-mep5ll62ke)​[\[6\]](#cite-id-hh5pmhssr2)​
