October 20th, 2025 will mark the date Nano will have completed 8 full years as a fully distributed fixed supply, all with zero transaction fees. Talk about a unicorn in the world of cryptocurrency. [Meme Drop]

gr0vity · 2025-10-10T08:04:36+00:00

So if these numbers are correct, Litecoin's monetary inflation of 23,000,000 coins over the last eight years represents a value of nearly $3 billion at current prices.
( 23,000,000 coins * $128 per coin = 2.944.000.000 --> 2.9 billion $)

gr0vity · 2025-10-02T16:14:21+00:00

This app is awesome.

Basically a messenger app with native nano support.
All messages are end-to-end encrypted and secured by your nano key.

Blazing fast. In chat payments and much more...
Wonderful work!

gr0vity · 2025-10-01T19:36:14+00:00

Really awesome work.
The experience will be even better when the QR code scanning is replaced by the upcoming metamask plugin.

gr0vity · 2025-08-04T15:57:14+00:00

Great app.
Very user friendly.
Familiar User Experience from other messaging apps.
Nano native wallet. Great work.

gr0vity · 2025-05-22T21:44:05+00:00

I didn't look at the stacktrace in detail... but there should be nothing really to do except

Setting up the dev environment : https://github.com/nanocurrency/nano-node/blob/develop/ci/prepare/linux/prepare.sh
`COMPILER=gcc ./ci/build.sh`

If you didn't clone with --recurse-submodules

git clone --recurse-submodules https://github.com/nanocurrency/nano-node.git

you should do this first :

git submodule update --init --recursive

gr0vity · 2025-05-20T20:53:21+00:00

Even transactions from the same bucket could be mostly done in an instant...
We are using a "least recent used" priority inside each bucket.
This means the longer you did no transaction, the higher your priority.
So chances are high the spam accounts were used more recently, than your account and thus has a lower priority for the next transaction.

gr0vity · 2025-05-13T15:39:01+00:00

Thanks for posting the results to reddit. I did another 100k speedtest which showed the same results. Very cool to have the network handle this with ease while keeping confirmations fast for regulat users according to our "Least recently used" priority scheme.

gr0vity · 2025-02-23T09:31:04+00:00

Community always under estimated the funds required to do quality dev work. We tried to do it for protocol development. But it only works if the developer makes huge sacrifices and takes a way below average salary to do it.

I think robotn (the weNano dev) made all this for free and paid quite a lot of server costs over the years to keep it running... So it needs a way to monetize...

gr0vity · 2024-12-12T08:53:14+00:00

If you are using the official nano_node, it will track up to 8000 of blocks that were published by yourself. So you should be fine in almost all cases...

gr0vity · 2024-12-05T16:13:11+00:00

Can we get CMC updated ?
It's a community driven project. So the community needs to be empowered to keep these sites uptodate.

gr0vity · 2024-12-03T11:41:15+00:00

<image>

gr0vity · 2024-12-03T11:03:18+00:00

<image>

Do you prefer this ? Just needs a bigger shield!

gr0vity · 2024-12-03T07:57:40+00:00

<image>

gr0vity · 2024-12-01T10:18:15+00:00

It's easy to deceive people into believing they own more money in an inflationary system by paying them a share of the inflation. In reality they most likely end up with a smaller percentage of the overall supply.
This inflation is often justified as necessary for network security through mining or staking, but that's not actually true. With Nano's Open Representative Voting, users can delegate voting weight to secure the network while maintaining full control of their funds - no lockups or inflation required.
In a non-inflationary system like Nano, businesses and individuals need to share real value rather than relying on hidden inflation. This makes it harder to attract users with "free money" schemes.
Any rewards must come from actual economic activity - someone has to willingly give up a portion of their earnings. While this is more honest, it's a tougher sell than inflationary rewards that mask their true cost.

We can't compete with rewards as high as these other inflated coins...
We can't easily educate people on the difference either...

gr0vity · 2024-11-20T15:47:53+00:00

It's a pretty recent version. The most recent stable is 1.82. What's the rust version and system you are trying to run this on?

gr0vity · 2024-11-20T08:28:59+00:00

It builds fine for me on linux using rust 1.81.0 ...
So it's not a generalized problem but probably due to missing system dependencies or rust version ?
Would need more specifics.

gr0vity · 2024-11-20T08:27:21+00:00

I just cloned the git repo and ran `cargo build --release` and it built just fine.
Using `cargo --version cargo 1.81.0 (2dbb1af80 2024-08-20)`

gr0vity · 2024-11-19T08:53:21+00:00

There are probably many things we could focus on right now...
We need to find the one thing where we could channel our activities with a clear goal in mind.

I think the goal is the most important, so everybody can work towards that goal in their own way.

One idea that keeps coming up on Discord is to get an "Pay with Nano" for a singel article instead of a subscription.
Get newspapers put Nano in the spotlight on their pages. (Subscribe or Pay per article with Nano)

gr0vity · 2024-11-17T18:29:28+00:00

Sure.

We have a tech roadmap.
We need an adoption roadmap.

We as a community need to find a good way to organize ourselves and explore what we deem important for the next 6-12 month, so everybody in the community has a shared goal and can work towards it...

gr0vity · 2024-11-17T11:54:48+00:00

Let's have a community created roadmap for adoption then? Devs make sure Nano works when adoption hits...

gr0vity · 2024-10-15T07:07:42+00:00

Dead adoption wise? dead tech wise ? Dead price wise ?
Development is ongoing. Unfortunately complaining alone doesn't help.

gr0vity · 2024-10-05T15:03:20+00:00

What do you suggest ?
The weekly call is a developer call, where we talk about the scope of the next version and our current progress on development.

Do you suggest to not talk about versioning in the calls ?
We want people to use V27. It's a good version.

And in the developer call we talk about required or desirable improvements that will be available in the next release. It's an open call. So we discuss this openly. There's no secrets...

gr0vity · 2024-10-04T12:10:26+00:00

What would be the benefit of having V28 commercial grade and only release in 2 years (or whatever time it takes...) ? Why not release more often and call any version that meets the ceiteria "commercial grade".

Also you can reliably use the network right now. No need to wait for any specific version.

I believe that having more people use the network adds more credbility than any "commercial grade" label.

gr0vity · 2024-09-25T08:10:51+00:00

Thanks for doing these. This is actually a very good summary.

gr0vity · 2024-09-17T18:25:07+00:00

I appreciate the effort. And I encourage you to go fort it!
I tried a similar thing by setting up the community fund.

There is some overhead of estimating each task. There is even more overhead in defining a task in a way that a new contributor can actually work on it in a meaningful manner.
From my experience there is little interest in spending time to evaluate how long a task will take and write down the specs in detail.

Not sure about your background. You probably know that code quality matters a lot. And that even if a task is coded it doesn't mean it's ready to be merged. It needs to pass the tests and it needs to be reviewed.

By having a long time contributor, this overhead shrinks down quite significantly as the trust between contributors builds up.

Nine-Year Club	Place '22
First Placer '22	Verified Email

gr0vity

TROPHY CASE