Why Get XNO is coming to an end

Making the decision to shut down Get XNO was not easy.

The project started many years ago, when I was still a teenager. I had much more free time back then, a lot of energy, and most importantly, I was genuinely excited about Nano.

Get XNO started as a small faucet. Over time, the project grew, more users joined, and more features, offerwalls, and things to maintain were added.

For many years, it was much more than just a faucet to me. It was a huge project that taught me a lot about programming, running a website, infrastructure, managing money, dealing with users, and many other things.

But over time, both Get XNO and my life started to change.

One of the immediate reasons for shutting down is the current problem with withdrawals. At some point, they stopped working correctly because of a bug that I have not been able to definitively identify. The problem is particularly difficult to fix because everything works correctly in my testing environment, while the issue only appears in the real production environment.

The Get XNO codebase is also no longer in a good state. The project was built over many years, when my programming skills were much more limited. Looking at it today, there are many things I would do completely differently. The code would require significant refactoring, security improvements, and parts of the infrastructure would need to be rebuilt.

Fixing a single problem would therefore not solve the bigger situation.

There is also a much simpler reason: I no longer have the time to run the project.

When I created Get XNO, I was a teenager. I had plenty of free time and could spend hours developing the website, fixing bugs, and taking care of users.

Today, I am a young adult. I have a job, family, responsibilities, and my own life. I spend most of my time away from home, and when I am back, I would rather spend my free time with people close to me, relax, or work on my own hobbies.

I do not want to keep running a project simply because I created it years ago. Get XNO requires regular attention, and I am no longer able to give it that attention.

Offerwalls were also an important part of Get XNO for a long time. Eventually, another problem appeared: the quality of the available offers started to decline. There were no new, better providers joining the platform, and the available options were not good enough to keep developing the project in that direction.

At the same time, fraud became an increasingly serious problem. I had to significantly reduce the payout rate because the amount of fraud and chargebacks started causing real losses. At one point, running the website meant putting my own money into it.

That is not a model I could maintain indefinitely.

There were also the ongoing infrastructure costs, including the VPS servers that had to be paid for regardless of how much the website earned in a given month. Get XNO was never a project intended to make me a lot of money, but over time it became increasingly difficult to justify even the cost of keeping it running.

There is also a more personal part of this decision.

When I started Get XNO, I genuinely believed in Nano. I liked its simplicity, speed, and especially the lack of transaction fees. At the time, it was a project I was very interested in and genuinely enjoyed following.

Over the years, however, my view of cryptocurrency has changed significantly. Today, I am much more interested in Bitcoin, Lightning Network, stablecoins, and a smaller number of larger projects than I am in Nano.

I simply lost the same excitement for XNO that I had several years ago.

Looking at the project from a distance over the years also left me with more doubts about its direction, adoption, and practical usefulness.

That does not mean I think Nano is a “bad” project, or that everyone should stop being interested in it. I simply stopped being someone who wants to spend his time developing and promoting it.

And running Get XNO without that motivation would not make much sense.

Someone might reasonably ask why I do not simply fix everything later.

Technically, I could rewrite the website, fix the withdrawal system, rebuild parts of the code, find new offerwall providers, and try to start over.

The problem is that doing so would essentially mean rebuilding the project from the ground up. More importantly, it would require time that I simply do not have anymore.

I also do not want to promise users that “we will be back next month” or that “everything will be fixed soon” when I do not know whether I will actually have the time to make that happen.

I would rather make a clear decision and close the project than keep it running indefinitely in a state where I cannot guarantee that it will work properly.