While looking into @vangrid_io I also wanted to know who's actually building this thing.
I checked the team's background, and a couple of things caught my attention.
Robert Brighton, the CEO, has experience in deep tech and Web3, including work connected to Microsoft's Quantum Computing and HoloLens groups in Europe.
Khalid Benrafik, the CTO, has over 14 years of experience with distributed systems. He's also worked with companies like Booking.com, ING, and Mollie.
What I find interesting is that Vangrid isn't building a simple app. The idea involves collecting real-world data, verifying it, and turning it into something useful for AI and robotics.
So having people with experience in both technology and large-scale systems makes sense to me.
Of course, a good team doesn't automatically mean a successful project. The real test is how well they can execute the idea.
That's something I'll be watching as Vangrid moves forward.
gm ct
Before buying another device for decentralized compute, I'd first take a look at the phones already sitting around at home.
But there's something important people often overlook:
An unused phone and a useful compute device aren't necessarily the same thing.
The real question is what that hardware can actually handle.
That's where @Acurast caught my attention.
Its Processor Lite lets compatible Android phones and iPhones contribute during idle periods, while keeping their normal apps and personal data.
Processor Core takes a different approach. It turns a compatible Android into a dedicated compute device, with a factory reset required during setup.
But the more interesting part is what these phones can actually run.
In a recent technical demonstration, Acurast ran Qwen3.5-9B, a 9-billion-parameter language model, on Android phones with 16GB RAM.
The team also demonstrated Qwen3.5-4B on 8GB devices.
That tells me something important about the future of smartphone compute.
We shouldn't judge a device only by its age or whether it's currently being used.
We should look at its processor, memory, storage, compatibility, and the kind of workload it can support.
A spare phone with suitable hardware could become part of a distributed compute network instead of remaining unused in a drawer.
Of course, not every phone can run every workload, and connecting a device doesn't guarantee a fixed amount of earnings.
I'd rather understand the hardware first and choose the right Processor setup than rush into connecting every available phone.
Sometimes the next useful piece of infrastructure might already be sitting in your drawer.
Would you dedicate an old Android to Core, or keep your everyday phone flexible with Lite?
Another Rebel milestone unlocked!
ID Card #23330 is my entry into the @Acurast Cloud Rebellion.
Now let's collect MIST and keep building!
Claim yours and join the rebellion:
rebellion-backend.acurast.co…
14
19
308
gm family
Sometimes a small experiment can explain a big infrastructure idea better than a hundred technical promises.
That's what I find interesting about Laya on @Acurast.
Think about a Tetris game.
A new piece appears, and the software generates five possible placements. Instead of choosing the move itself, it sends the available options to an AI model running on an Android phone.
Laya evaluates those options and returns its decision.
The game creates the possibilities. The model makes the choice. A real smartphone handles the computation.
What makes this interesting is the execution path.
Each decision is sent to a phone through an HTTP request. Laya runs on the device's CPU and typically returns a response in around 0.2–1 second.
The demo even exposes information about the phone serving the request, including its country, processor and decision count. You can also inspect its on-chain record.
But I wouldn't stop at Tetris.
The same Laya model powers other experiments:
• Snake, where AI chooses the next direction.
• Doom, where it selects actions inside the game.
• Mail Sorter, where it classifies messages as inbox, spam or phishing.
These examples demonstrate something important for developers.
Not every AI task needs a model that writes paragraphs or performs complex reasoning. Some applications simply need a model to evaluate a situation and select one option from a defined set.
That's where smartphone-based compute becomes an interesting infrastructure option.
And after Acurast's November 16 discussion about the Microsoft outage, the question of relying on centralized infrastructure feels even more relevant.
Decentralization won't eliminate every outage or replace every data center overnight. But having alternative compute infrastructure is worth exploring.
My takeaway:
The real opportunity isn't making smartphones imitate traditional servers.
It's discovering which useful workloads can run efficiently on devices distributed across a global network.
Laya gives us a practical way to start understanding that possibility.
Have you tried making Laya play Tetris or Doom yet?
I have just claimed the #23330 @Acurast ID Card.
Join the Cloud Rebellion, collect MIST and claim your own ID Card! rebellion-backend.acurast.co…
A trading community is easy to build. Creating something valuable together is much harder.
That's why I find the Clan system in @zerufinance more interesting than just another community feature.
A Clan is not measured by follower count alone. Its Clan Score is built from the zScores of members who have minted, giving the community a way to reflect the onchain reputation of its participants.
There's also a practical role for Clans in campaigns.
Members can join multiple Clans, but each trader chooses one primary Clan for campaign credit. Leaders can earn a share of the creator pool based on their Clan's contribution, while traders receive the trader portion of the unlocked reward pool.
That creates a different relationship between creators and their communities.
A creator is no longer just bringing people into a group. They're building a network of traders whose genuine activity can contribute to a shared result.
And the latest Zaps documentation makes the bigger direction clear: Clans already support reputation, leaderboards and campaign economics, with eligible communities potentially getting their own activity markets in the future.
I think that's a more meaningful way to build a trading community.
Not just more members.
Not just more messages.
A community with measurable participation and something to grow together.
If you already have a trading circle, explore how Clans work:
zaps.markets/?invite=6nVpe4z…
One thing that stands out about Astraea is that it focuses on both storage efficiency and trust.
Storing 5.18 billion XRP Ledger transactions in 1.08 TB, with around 3x less disk usage than Clio over the same history range, is a notable improvement.
What makes it more interesting is the ability to independently verify ledger history through cryptographic proofs, without simply trusting an API provider.
Clio 2.8 compatibility and a simpler Rust-based setup could also make adoption easier.
Looking forward to seeing the public RPC endpoint from @XRPLLendingNet and how Astraea performs in practice.
Introducing Astraea
github.com/XRPL-Lending-Netw…
A new approach to storing and independently verifying XRP Ledger history.
Key features:
• 3× less disk usage.
5.18 billion transactions stored in 1.08 TB, compared with Clio over the same history range.
• Verified history.
Every ledger is checked before storage. Validator quorum is independently verified using archived signatures and UNL lists.
• Cryptographic proofs.
Verify historical ledgers, transactions and state objects offline, without trusting the API provider.
• Clio 2.8 compatibility.
Same JSON-RPC and WebSocket APIs. No client changes required.
• Simpler infrastructure.
A single Rust binary. No Cassandra or ScyllaDB required.
We're finalizing tests and benchmarks before opening Astraea's public RPC endpoint to the community within the next month.
good morning everyone gAcurast
If someone says their phone collected 5 ACU, my first question won’t be is this a good result or not?
My question will be – what was going on during that session?
What phone was used – Lite or Core? How long did it operate? Was it running any assigned workloads?
Without this information, numbers don't tell the whole truth.
This is why I believe Processor session reports could turn into one of the most helpful formats for the Acurast community to learn from each other.
A meaningful report should contain:
• Device model and Processor type
• Date of the session and online time
• Benchmarking info, if any
• ACU earned during the reported period
• Information about any interruptions or missing heartbeats
• Information whether the device executed an assigned deployment
And here is why this information is important.
Acurast rewards participants for the Base Benchmark Rewards according to the performance of the device among four benchmark pools. Providers who participate in the Staked Compute can get additional rewards depending on the performance of the hardware, stake size, and the term of commitment.
Besides, there is a 10% deployment execution bonus if the Processor runs the assigned workload during the epoch.
The interesting point is that the epoch consists of about 90 minutes and contains 3 heartbeat opportunities. Missing one heartbeat doesn't mean you lose all benchmark rewards during the epoch.
That's why two providers can report different results in terms of ACU earned, but both results are not misleading because their hardware, availability, workload, and reward participation could be different.
It is especially true now when Acurast continues developing its decentralized compute infrastructure. Their recent update on November 16 underlines a network of 360K+ devices in 175+ countries.
But network-wide statistics is only half of the story.
Statistics of individual providers helps people to understand what participation looks like.
As I see it:
Don't share your results without context. Let people understand the way they were achieved.
It will be more informative than numbers without explanations.
And if you're already working with Acurast Processor, what does your session look like?
@Acurast
I have just claimed the #23330 @Acurast ID Card.
Join the Cloud Rebellion, collect MIST and claim your own ID Card! rebellion-backend.acurast.co…
Most people join a points campaign and immediately ask one question: what should I do next to earn more?
But with @zerufinance, I think there's another question worth asking first:
What does my wallet history already say about me?
Zaps looks beyond the moment you join. By linking the wallets you actually use, your existing onchain activity can help establish your starting position.
And the interesting part goes deeper than a joining bonus.
Zeru's campaign system can also read historical activity with a sponsor's protocol. That means your past interaction may matter when a campaign measures participation, while the campaign's own registration and qualifying rules still determine what counts.
I like this direction because it connects three things:
Your history shows where you've been.
Your current activity shows how you participate.
Your qualifying contribution determines your share in a campaign.
There's also an important distinction: zScore and Zaps are not the same. zScore reflects your broader DeFi history, while Zaps measures activity within the Zaps ecosystem. Neither should be confused with a guaranteed token allocation.
For me, the bigger idea is that onchain reputation should be built around verifiable behaviour, not just how many tasks someone completes or how much noise they make.
Before chasing another points campaign, check your wallet history, link the wallets you genuinely use, and understand the rules of the campaign you're joining.
Explore Zaps:
zaps.markets/?invite=6nVpe4z…
gm family! gAcurast 🥱
Not all spare phones must become compute nodes, nor do all phones used in everyday life have to become dedicated ones.
I believe recognizing the difference between them is the first wise move to make while exploring @Acurast.
There are two ways to take part, and each serves a different purpose.
Processor Lite is based on flexibility.
You can download and install it on a compatible Android phone or iPhone, and have it work as a compute node during idle time. Your usual applications and personal information will stay intact, and there will be no need to wipe out your daily use device.
Processor Core is a different story.
It turns your compatible Android phone into a dedicated compute node. This process includes factory resetting the phone, and turning it into a device focused on computing rather than being your regular daily use device.
There is, however, one more thing to keep in mind: performance.
As mentioned in Acurast's documentation, Core devices usually show results 15–20% higher in benchmark tests compared to Lite. This means higher Base Benchmark Rewards and more computing power to stake.
This does not necessarily mean that everyone has to buy a new phone.
The better option depends on your available hardware, how much you depend on it, and whether you are ready to turn it into a dedicated compute device.
There is, however, one small yet important note before onboarding: check the latest compatibility requirements.
As per Acurast's latest documentation, it requires Android 12 or later versions, while iPhones should have iOS 16 or later version. Requirements may change, and checking them before onboarding will help avoid unnecessary troubleshooting.
My plan of action will be simple:
I will keep my phone used for everyday life on Lite.
I will consider using Core only when I have a spare Android device compatible with the requirements and am ready to factory reset it.
Decentralized infrastructure becomes more accessible when people can participate in the way fitting their hardware.
The point is not to connect every phone.
The point is to make the right hardware useful.
Which option seems better to you: flexible participation with Lite or dedicated compute device with Core?
gm family! gAcurast 🥱
Not all spare phones must become compute nodes, nor do all phones used in everyday life have to become dedicated ones.
I believe recognizing the difference between them is the first wise move to make while exploring @Acurast.
There are two ways to take part, and each serves a different purpose.
Processor Lite is based on flexibility.
You can download and install it on a compatible Android phone or iPhone, and have it work as a compute node during idle time. Your usual applications and personal information will stay intact, and there will be no need to wipe out your daily use device.
Processor Core is a different story.
It turns your compatible Android phone into a dedicated compute node. This process includes factory resetting the phone, and turning it into a device focused on computing rather than being your regular daily use device.
There is, however, one more thing to keep in mind: performance.
As mentioned in Acurast's documentation, Core devices usually show results 15–20% higher in benchmark tests compared to Lite. This means higher Base Benchmark Rewards and more computing power to stake.
This does not necessarily mean that everyone has to buy a new phone.
The better option depends on your available hardware, how much you depend on it, and whether you are ready to turn it into a dedicated compute device.
There is, however, one small yet important note before onboarding: check the latest compatibility requirements.
As per Acurast's latest documentation, it requires Android 12 or later versions, while iPhones should have iOS 16 or later version. Requirements may change, and checking them before onboarding will help avoid unnecessary troubleshooting.
My plan of action will be simple:
I will keep my phone used for everyday life on Lite.
I will consider using Core only when I have a spare Android device compatible with the requirements and am ready to factory reset it.
Decentralized infrastructure becomes more accessible when people can participate in the way fitting their hardware.
The point is not to connect every phone.
The point is to make the right hardware useful.
Which option seems better to you: flexible participation with Lite or dedicated compute device with Core?
I have just claimed the #23330 @Acurast ID Card.
Join the Cloud Rebellion, collect MIST and claim your own ID Card! rebellion-backend.acurast.co…
27
28
532
Before joining another points campaign, have you checked what your old wallets are already worth?
That's something worth looking at with @zerufinance.
Zaps doesn't ask everyone to build their history from zero. It can recognize eligible past trading activity and use it to establish a starting Zaps balance.
And there's been an important update.
Zeru has adjusted its scoring system so lifetime trading history now matters, not just activity since joining. Real trading activity gets more weight, while prolonged inactivity and Sybil behaviour can reduce your Zaps.
I think this makes the system more interesting.
It puts more focus on how consistently someone participates in the ecosystem, rather than how quickly they can farm points after joining.
You can also check a wallet's zScore without connecting it. Just look up the address and see its onchain reputation.
One thing to keep clear: zScore and Zaps are different. Zaps are points, not guaranteed tokens or a fixed airdrop allocation. Any future distribution depends on the official rules.
My suggestion is simple: check your existing wallet history first, understand your starting position, and focus on genuine activity from there.
Explore Zaps:
zaps.markets/?invite=6nVpe4z…
One of the most exciting things about Binance Qafila 2026 is the Referral Challenge!
Not only does the platform offer trading, but also it offers referral activities.
Using Qafila, eligible users can invite friends and take part in these activities.
The most interesting aspects of this program, according to me, include the following:
🔹 up to 20 USDC in referral rewards.
🔹 10,000 USDC reward for the best leaderboard participant.
However, referrals always have to be made based on trust.
When inviting someone, explain the idea of the campaign, provide official info, and never promise any guarantees of rewards.
Qafila also offers a combination of trading challenges and Simple Earn challenges in one campaign.
Campaign duration: up to November 30, 2026.
Have you taken part in Qafila already? If yes, would you prefer Referral Challenge or Trading Challenge?
Explore here:
binance.com/en/ti/act/Qafila
The $1M refers to the total campaign reward pool. Activities and eligibility may differ across different regions.
For all official information regarding this topic, see the Terms & Conditions of the campaign.
This is a general announcement. Products and services may not be available in your region.
Prices of digital assets are volatile and subject to high risks. You may incur losses of your investment. You are responsible for your investment decisions. This is not financial advice.
#Qafila #BinanceUpdate #Binance� #BinancePakistan
181
423
10,069
good morning everyone, Acurast builders. gAcurast!
I've been looking at what decentralized compute actually means for developers, and one Acurast demo made the concept surprisingly easy to understand.
It's not about putting an entire application inside a smartphone.
It's about giving a phone a specific computing task and letting it handle that task.
Take Laya Tetris.
When a new piece appears, the game generates five possible placements. An AI decision model running on an Android phone evaluates those options and selects one.
The game handles the board and possible moves. The model makes the decision. The phone processes that request and sends the answer back.
What's interesting is that this isn't happening inside a conventional cloud server.
The decision is sent to a real phone in the Acurast network through an HTTP request. The model runs on the phone's CPU and typically responds in around 0.2 to 1 second.
Even better, the demo lets you inspect information about the device handling the request, including its country, processor and decision count, with an option to verify its record on-chain.
That changes the way I look at the demonstration.
Instead of hearing that smartphones can provide decentralized compute, you can actually see a device performing a task and returning a result.
And Tetris is only one example.
Laya also powers demos involving Snake, Doom, phishing detection, chat moderation and prompt-injection protection.
For developers, the interesting opportunity is using this kind of infrastructure for workloads where a model needs to make quick decisions from a defined set of options.
Of course, not every AI workload belongs on a phone. Large and computationally intensive models still have different hardware requirements.
But that's exactly why these demonstrations matter. They help show where distributed smartphone compute can be useful instead of making unrealistic promises about replacing every data center.
My biggest takeaway:
The real value of decentralized compute isn't simply connecting thousands of phones.
It's making those phones useful to applications that need actual computing work done.
That's the direction I'm watching with @Acurast.
good morning everyone, Acurast builders. gAcurast!
I've been looking at what decentralized compute actually means for developers, and one Acurast demo made the concept surprisingly easy to understand.
It's not about putting an entire application inside a smartphone.
It's about giving a phone a specific computing task and letting it handle that task.
Take Laya Tetris.
When a new piece appears, the game generates five possible placements. An AI decision model running on an Android phone evaluates those options and selects one.
The game handles the board and possible moves. The model makes the decision. The phone processes that request and sends the answer back.
What's interesting is that this isn't happening inside a conventional cloud server.
The decision is sent to a real phone in the Acurast network through an HTTP request. The model runs on the phone's CPU and typically responds in around 0.2 to 1 second.
Even better, the demo lets you inspect information about the device handling the request, including its country, processor and decision count, with an option to verify its record on-chain.
That changes the way I look at the demonstration.
Instead of hearing that smartphones can provide decentralized compute, you can actually see a device performing a task and returning a result.
And Tetris is only one example.
Laya also powers demos involving Snake, Doom, phishing detection, chat moderation and prompt-injection protection.
For developers, the interesting opportunity is using this kind of infrastructure for workloads where a model needs to make quick decisions from a defined set of options.
Of course, not every AI workload belongs on a phone. Large and computationally intensive models still have different hardware requirements.
But that's exactly why these demonstrations matter. They help show where distributed smartphone compute can be useful instead of making unrealistic promises about replacing every data center.
My biggest takeaway:
The real value of decentralized compute isn't simply connecting thousands of phones.
It's making those phones useful to applications that need actual computing work done.
That's the direction I'm watching with @Acurast.
I have just claimed the #23330 @Acurast ID Card.
Join the Cloud Rebellion, collect MIST and claim your own ID Card! rebellion-backend.acurast.co…
Before chasing another airdrop or points campaign, take a look at what your wallet has already done.
That's one thing I find interesting about @zerufinance.
When you connect your wallets to Zaps, it reads your existing onchain history. Eligible past activity and your zScore can contribute to your starting Zaps balance.
But that's only the beginning.
You can build your position through qualifying trading activity and referrals. You can also participate in protocol campaigns, where rewards depend on your verified contribution to a funded pool.
One detail worth understanding: regular Zaps and campaign Zaps are different. Campaign Zaps measure your contribution to a specific campaign and determine your share of its reward pool.
And Zeru is building beyond a simple points system with Activity Markets like zETH and its growing ecosystem.
I wouldn't chase random transactions just to increase a number. I'd rather understand what my wallet has already contributed and focus on genuine activity going forward.
Sometimes your next step in crypto starts with looking back at your own wallet history.
Check yours here:
zaps.markets/?invite=6nVpe4z…
Decentralized compute onboarding should not be viewed as a technical challenge.
And this is one of the things that interest me regarding the improvements in the way that Acurast does its Processor onboarding.
First thing to consider is figuring out which processor will work better with your phone.
Lite Processor is intended for normal phones and you can continue using your everyday phone but enabling it to do some computing while idle - e.g. while charging during the night.
Core Processor is completely different and makes your Android device dedicated compute provider meaning that you'll have to reset your device.
Having decided which processor to use, the next step is quite simple for Lite processor:
1. Start Acurast Hub application and go to Add New Device;
2. Start Processor Lite app and go to Connect to Hub;
3. Connect both via QR code;
4. Follow the guide and confirm the processor status.
Also there's one useful improvement that is worth mentioning.
Modern Processors allow you to connect to the Hub via QR scan or clipboard paste. Also the Hub UI was upgraded to make some things simpler and allow user to do certain steps without having to rely on his desktop monitor.
Also it's nice to know about Android Work Profile.
It allows to isolate Acurast workloads from the rest of activities in your phone by creating a separate management environment.
So now we know that the onboarding is not only about phone connecting. It also includes choosing the proper mode and understanding the compute environment organization.
Conclusion:
Good decentralized network requires not only powerful infrastructure. Good onboarding process is also needed to make contribution possible for ordinary users.
This is an important part of decentralized network building.
It would be interesting to see how many of you are using Lite on your everyday phone and not Core device.
@Acurast
There are more ways to earn Zaps than just trading.
On @zerufinance, you can start by connecting your wallets and letting your previous onchain activity count.
From there, you can:
- Generate qualifying trading activity
- Participate in protocol campaigns
- Refer new users
- Join or create a Clan
Each one gives you a different way to contribute to the ecosystem.
What I like is that Zaps brings individual activity and community participation together in one place.
It's not just about chasing points. Real participation matters.
If you haven't explored it yet, take a look:
zaps.markets/?invite=6nVpe4z…
207
166
834














