Mainnet db is huge (116Gb) : can we move it elsewhere ?

[RupertBarrow]

Describe the bug
Mainnet db (.../Application Support/com.tari.universe/node/mainnet) is huge : 116Gb.
Can I move this folder elsewhere, eg on my local NAS ?

To Reproduce
Steps to reproduce the behavior:

1. On Mac, go to .../Application Support/com.tari.universe/node/mainnet
2. See the size of the folder

Expected behavior
I would like to move this elsewhere and configure the app to find it there.

Screenshots
If applicable, add screenshots to illustrate the problem.

Desktop (please complete the following information):

• OS & Version: MacOS 15.7.2
• Browser & Version: Safari 26.1

Smartphone (please complete the following information):

• Device: [e.g. iPhone 15]
• OS: [e.g. iOS 17.4.1]
• Browser & Version: [e.g. Safari 17.0]

Additional context
Any other context or information relevant to the issue.

[brianp]

I think this is a very reasonable request. We actually had a similar Pitch in the backlog for a long time. but it was closed as stale. We will revisit this idea.

[brianp]

@RupertBarrow I just had a thought about this. Uncompressed chain data is only about 65GB right now.

Would you mind inspecting that folder a bit more and seeing which files are taking up that kind of storage?

Edit:

If your node is ultra long running it may be storing re-orgs. Which typically get cleaned out on restart.

[RupertBarrow]

mainnet/data/base_node/db/data.mdb

is 116Gb

[brianp]

Wowza.

Would you be able to do an app restart and see if it shrinks at all?

[RupertBarrow]

It does not shrink when I restart

[RupertBarrow]

3 days later, the data.mdb has grown by 1.3Gb to 118.45 Gb.

[brianp]

500mb a day is pretty average for the chain right now. But the protocol team is currently investigating what's causing some db's to inflate without coming back down, and investigating other compression possibilities.

If you'd like to save nearly half of your space right away. You can always drop the db, and have your node resync. Alternatively, download a compressed version, and replace the existing DB.

We're also moving forward with exploring the custom location options, but can't promise when that may go live.

[brianp]

I also understand it's a very large file, but if there was some way to make it available I think. the protocol team would be interested in seeing exactly what it's storing.

[RupertBarrow]

Oh, I'm sorry.
I deleted the file and it's rebuilt itself up to 61.88Gb this morning, so it's too late to get a copy of the db.

FYI, I started mining Tari in May 2025, so maybe the db contained outdated data which had not been purged.

If you REALLY need it, I can take time to fish it out of my TimeMachine backup.

[RupertBarrow]

OK, I've got the data.mdb file out of backup : it's 118Gb.
Tell me where I can drop it to send it to you.

[RupertBarrow]

poke @brianp

[brianp]

@RupertBarrow Hey! Just discussing best ways to transfer the data. Probably a large file service such as https://file.kiwi/ would be okay.