# Required specs for neptune-core

**URL:** <https://talk.neptune.cash/t/required-specs-for-neptune-core/288>\
**Category:** General\
**Created:** [May 15, 2026, 10:01am UTC](https://talk.neptune.cash/t/required-specs-for-neptune-core/288 "2026-05-15T10:01:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sword-smith](https://talk.neptune.cash/user_avatar/talk.neptune.cash/sword-smith/32/20_2.png) [@sword-smith](https://talk.neptune.cash/u/sword-smith)\
**Post date:** [May 15, 2026, 10:01am UTC](https://talk.neptune.cash/t/required-specs-for-neptune-core/288/1 "2026-05-15T10:01:47Z")

</div>

Someone asked me in a private chat for the required specs for the (archival version) of neptune-core. I can’t say exactly, but I’m running two instances `neptune-core`(one main net and one on testnet-0) and other services on a VPS with 4 cores and 8GB RAM. I think it would still run fine with 1 core and 4GB RAM though. But I haven’t tried yet.

Does anyone have a runinng `neptune-core` instance on a machine with lower specs than mine?

The only place where the requirements are somewhat high is in diskspace. The main net `neptune-core` instance currently uses 42GB.

---

<div class="post-metadata">

**Author:** ![sword-smith](https://talk.neptune.cash/user_avatar/talk.neptune.cash/sword-smith/32/20_2.png) [@sword-smith](https://talk.neptune.cash/u/sword-smith)\
**Post date:** [May 15, 2026, 10:46am UTC](https://talk.neptune.cash/t/required-specs-for-neptune-core/288/2 "2026-05-15T10:46:23Z")

</div>

In terms of bandwidth, a lot of the network traffic comes from passing transactions around. There ought to be an option to not accept any transactions. That way, you could still initiate transactions, but you wouldn’t spend bandwidth passing other people’s transactions around. I believe bitcoin-core has this option.
