We’ve just rolled out a major update to the X-Cash website.

This is more than a redesign — it’s a clear step forward in how we present the future of the project.

X-Cash is not just about technology anymore.
It’s about real-world payments, local discovery, business growth, and a living ecosystem built around real activity.

The new site reflects where we’re going:
– Simple digital payments anyone can use
– A social layer built on real transactions
– Real-world rewards, reputation, and opportunities
– Tools for businesses to grow, not just accept payments

This is a big leap forward — and a clearer view of what X-Cash is becoming.

Take a look 👇
https://xcash.tech/

Payments shouldn’t be invisible.

What if every transaction helped you:
• discover places
• build reputation
• drive real growth

We’re thrilled to announce that X-Cash will be at Consensus 2026

Join us in Miami, May 4–7 to talk partnerships, growth, and the future of crypto.

Let’s connect.

🚀 X-Cash Closed Beta (Android) — Applications Open

We’re launching a closed beta of X-Cash in ~1 week.

This first test focuses on Proof of Presence —
you visit a real-world location (café, restaurant, shop, etc.), check in, and upload a receipt as proof.

⸻

⚙️ What you’ll do
• Install the Android prototype
• Visit real places
• Check in
• Upload a receipt photo
• Earn X-Cash points

⸻

🎁 Rewards

Participants will receive bonus points, which will later be converted into real X-Cash tokens.

⸻

⚠️ Selection

We’re selecting 150–200 real users.
Low-effort and bot-like applications will be filtered out.

⸻

🧠 How to get in
1. Fill out the form
👉 https://forms.gle/izvGSj2BMUXJCg4n7
2. Comment below this post:

What is the biggest weakness or risk in Proof of Presence?

We will prioritize people who:
• give thoughtful answers
• understand the product
• actively engage in discussion

⸻

⏳ Selection starts soon. Access will be granted to chosen participants only.

Proof of Presence is broken — but only if it’s cheap to exploit

Most people point to the same risks:
fake check-ins, fake receipts, Sybil attacks.

And they’re right.
If your system can be manipulated at near-zero cost — it will be.

⸻

In most existing designs, abuse is trivial:
• GPS spoofing
• Reused or edited receipts
• Unlimited fake accounts

This creates a simple dynamic:
zero cost → infinite scale → broken system

⸻

But the real question is not:
“Can it be faked?”

Everything can be faked.

The real question is:
“What does it cost to fake?”

⸻

Now consider a different model:

What if every “proof” requires
real-world spending at a real location?

Suddenly, manipulation stops being a technical trick
and becomes an economic action.

⸻

To “game” the system, an attacker now has to:
• Physically go to a place
• Spend real money
• Perform a real transaction

This completely changes the equation.

No more infinite scaling.
No more free abuse.

Every action has a cost.

⸻

And here’s the interesting part:

If someone is “manipulating” the system by spending money at a business…
the business still benefits.

⸻

The same logic applies to reviews.

Yes, a customer can still lie.
But they can only do it after a real interaction.

No more mass fake reviews from people who were never there.
No more bots flooding ratings without ever touching the business.

⸻

This doesn’t make the system perfect.

There are still risks:
• Reward farming (if rewards > spend)
• Merchant collusion
• Multi-account scaling

But now all of them are bounded by cost, not infinite.

⸻

This is the shift:

From
“hard to fake”

To
“not worth faking”

⸻

What we’re building is a social layer on top of payments

Where every action —
visits, transactions, reviews —

is provably tied to real-world interaction.

⸻

Read, challenge, discuss.

We just recorded our first X-Cash app prototype demo.

Stay tuned!

We’ve completed the migration and published the results.

Full Merkle distribution dataset is now available:
https://github.com/Xcash-Tech/xcash-distribution-merkle-tree

What’s included:

Complete list of eligible addresses and allocations
Merkle root and proofs for independent verification
Open, reproducible dataset

This ensures full transparency — anyone can verify their allocation.

TGE date and the start of distribution will be announced in May.

Miami was incredibly productive for our team. Meetings and negotiations every 20 minutes, dozens of valuable new connections, and several promising partnership discussions across different areas.

One of the biggest highlights was the live demo of our contactless phone-to-phone payment technology — the response was outstanding and exceeded expectations.

Now it’s time to process all the new information, follow up on opportunities, and continue improving the project. More updates are coming by the end of next week, as we still have several important business visits across the US ahead.

Stay tuned!

Over the past several weeks, we've been traveling across the United States following Consensus, meeting with investors, payment providers, infrastructure companies, and potential strategic partners.

The trip has been extremely productive. We held a large number of discussions, established valuable new connections, and opened several opportunities that are now moving into follow-up stages.

One of the most exciting moments was demonstrating our contactless phone-to-phone payment technology. The response was overwhelmingly positive and confirmed that the market is actively looking for practical payment solutions that go beyond traditional crypto use cases.

While business development takes time and many discussions are still ongoing, the trip helped validate several key assumptions behind our long-term vision and provided valuable feedback for the next stage of development.

Our focus for the coming weeks includes:

• Finalizing the new token infrastructure and allocation process.
• Continuing development of the X-Cash Wallet.
• Advancing fiat on-ramp and payment card integrations.
• Expanding phone-to-phone payment capabilities.
• Evaluating L2 infrastructure options to support future scalability.
• Moving partnership and pilot discussions forward.

Our mission remains the same: building practical financial infrastructure for the AI era, where trust, payments, identity, and reputation work together seamlessly.

More updates will be shared as milestones are reached.

As summer begins, business activity naturally slows down across many markets. Many partners, investors, and teams enter the holiday season, and we believe that launching the token during this period would not give the project the attention and momentum it deserves.

For this reason, we have decided to move the token launch to autumn, when market and business activity will be stronger. This will give us a better window for a more effective and confident launch.

In the meantime, we are not slowing down.

Our nearest major milestone is the test launch of our new L1 network with a cross-bridge to Base.

The core of the network still includes an anonymous layer inspired by Monero, but significantly improved and reworked. The entire codebase has been migrated to Rust, giving us a major boost in performance, reliability, and long-term maintainability.

We are also introducing a new consensus protocol based on Narwhal technology, designed to reach performance levels of up to 100,000 TPS.

And the cherry on top: a seamless L2 Base bridge, working with a concept similar to Polygon AggLayer. This will allow transparent and reliable transaction flow between the L2 network and our L1.

The technology is currently going through internal testing, and by the end of this month we plan to open applications for beta testers.

We are building something much bigger than just a token launch. The token is only one part of the ecosystem — the real value comes from the technology, the network, and the products we are bringing to life.

Thank you for your patience, support, and belief in the project.

The next stage is coming!

To our early believers: yes, we’ve been quiet — but definitely not idle.

The dev cave is alive, the coffee is disappearing, and some big pieces are coming together.

1. Banking Cards integration

We’re working with partners to connect Banking Cards directly to the XCASH wallet.

This is a major step toward making the wallet not just another crypto app, but a real payment tool for everyday use.

Once this stage is ready, we’ll start inviting beta participants to test the card flow and wallet experience.

2. AnoX — our new anonymous transport layer

We’re also finalizing development of our new anonymous network, code-named AnoX.

AnoX is based on Monero privacy concepts, rebuilt and adapted for the XCASH ecosystem, with a cross-bridge to L2 Base.

In simple words: AnoX will become the main transport layer for the ecosystem — private, fast, scalable, and connected to the broader L2 world.

Or, less officially: it’s a privacy-powered brain explosion with blackjack and advanced cryptography.

The quiet phase is not a pause. It’s the part where the serious pieces are being assembled.

More updates soon.

🚀 AnoX Public Testnet Update

We know, we know — everyone is already waiting with one finger hovering over the “Launch” button. 😄

We’re actively preparing the AnoX public testnet. During internal testing, however, we discovered a serious security issue in the Base → AnoX module. The good news: this is exactly why internal testing exists. It’s much better to catch such things now than after opening the doors to everyone.

The module is currently being improved and hardened. Once this work is complete, we’ll deploy everything publicly and begin inviting testers.

We’re almost there — just a little more patience. More announcements are coming very soon! 👀

Please be patient with us. As they say, Rome wasn’t built in a day. 🙂

The new technology is being tested very carefully, and even launching the public testnet will be a huge milestone for the project.

We’re building something genuinely unusual: an anonymous L1 blockchain with a native bridge in and out of L2 — and specifically into the Base ecosystem. Base has actually been one of the main sources of technical complexity during the bridge development, but we still believe choosing Base was the right decision. Building something similar around Polygon would probably have been easier, but Base gives us much stronger long-term opportunities.

There is also another challenge on the native L1 side: privacy itself.

Because transactions are anonymous, you cannot simply open a wallet, query an address, and immediately get its balance like you would on a transparent blockchain. The wallet has to synchronize transactions and decrypt relevant data locally in order to reconstruct the user’s ownership history.

That means we have to find the right balance between good UX and real privacy. We don’t want anonymity that looks good on paper but becomes unusable in practice — and we don’t want convenience at the cost of privacy either.

I also see many comments and questions about the token launch.

Yes, I completely understand the expectations. And yes, the market seems to be waking up again… although with crypto, you never really know. 🙂

But if we did what many projects do — launch a token as quickly as possible just to raise money and catch the market — we would probably end up following the same familiar lifecycle:

Pump → dump → forgotten.

That is not what we are building.

The token will come. Right now, however, we are working on finding the right economic balance so that the launch does not turn into uncontrolled chaos.

A healthy launch requires liquidity, and attracting meaningful liquidity is much easier when the project already has something real behind it. Launching the public testnet is therefore an important step not only technically, but economically as well.

The testnet work is now almost complete. I know we have said “soon” more than once already, and I completely understand the skepticism around that word. 🙂

But we are very close.

Please keep an eye on the announcements. I sincerely hope that this month we will finally bring the public testnet into the light.

Thank you for staying with us.

A quick update for everyone waiting for the ANOX public testnet.

One of the biggest things we are finishing right now is a new privacy-preserving indexing layer for wallet synchronization.

Private chains have an awkward UX problem: a node cannot simply expose address → balance / transactions like Ethereum without weakening privacy. Normally, the wallet has to walk through the chain and locally determine which outputs belong to it.

Our approach is different.

Instead of forcing every wallet to repeatedly read and parse full blocks, ANOX nodes maintain a compact append-only scan index derived from the canonical chain. It contains only the minimal metadata required for scanning, organized by block height and protected by reorg-safe checkpoints.

Some early numbers from the current spike:

• ~45,600 outputs/sec local scanning throughput
• ~512× reduction in candidate checks from the prefilter stage
• a theoretical 2-year recovery window can be reduced to roughly 385k candidate outputs instead of scanning the complete transaction set
• synchronization becomes incremental — once caught up, the wallet only processes newly indexed data

And importantly, the node still does not learn which outputs belong to the wallet. There is no server-side wallet → transaction graph.

The wallet remembers its last synchronized checkpoint, requests only the delta, quickly filters candidate outputs using compact tags/metadata, and performs the actual ownership detection and decryption locally.

So the node knows:

give me index data from height X → Y

but it does NOT know:

which outputs belong to this wallet.

This gives us:

• near-instant incremental wallet synchronization
• no repeated O(n) full-block scans
• much lower bandwidth and CPU usage
• fast rollback/replay after chain reorganizations
• no server-side wallet → transaction database

The same principle is also being applied to several bridge read-models that currently require historical chain rescans.

A little more engineering before launch — but it removes an entire class of scaling problems before they become production problems.

Wen testnet? - Soon™ — now with considerably fewer O(n) adventures.

Personal note.

I really hope you understand at least roughly how ridiculously hard the problem we are solving actually is.

“Fast wallet sync” sounds simple until you add the tiny requirement of:

don’t tell the server which outputs belong to the wallet.

At that point the problem suddenly becomes a cocktail of privacy-preserving indexing, probabilistic filtering, incremental state, reorg handling, client-side ownership detection and enough edge cases to ruin several perfectly good weekends.

Monero has been dealing with the same fundamental problem for years: if you want strong privacy, the wallet has to do real work locally. There is no magical GET /balance endpoint without introducing privacy trade-offs.

So yes, when we say we are trying to make private-wallet synchronization feel almost instant, this is not just “another optimization”.

It is one of those engineering problems where the easy solution breaks privacy, and the private solution usually breaks UX.

Naturally, we decided we want both.

Because apparently making a normal blockchain was too boring.

Please set panic mode OFF 😄

I know everything is moving slow as hell. But it goes as it goes. If we force TGE next week without proven results, it’s going to be a fail — and I’d rather be late than launch something that isn’t ready.

As luck would have it, I’ve also had a bunch of personal things come up recently that I simply had to prioritize. Things are finally getting back to normal now, so I can fully focus on XCASH again.

The good news: all internal network tests are now passing.

The next stage is deploying the contracts and taking the whole thing into the “open sea” — public network testing with real contracts and real transactions.

I promise I’ll share the first real transactions with you guys 😄 Hopefully that will bring the mood back up.

And once we prove that everything works properly in the wild, then we announce the TGE.

We’re not stuck. We’re just finishing the part where “almost works” is not good enough.