Bitcoin Forum
May 27, 2024, 07:29:30 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: What will you run?
I will remain full node - 16 (76.2%)
I will use a pruned (lite) node - 5 (23.8%)
Total Voters: 21

Pages: « 1 [2]  All
  Print  
Author Topic: Are you going to run a lite node when 0.12 comes out or you will remain full?  (Read 1133 times)
Kprawn
Legendary
*
Offline Offline

Activity: 1904
Merit: 1073


View Profile
February 18, 2016, 03:31:31 PM
 #21

I think the disk space is not a issue with second hand smaller drives going for as little as $50 to $100. Running a full node is not really a problem at all.. I am

lucky to have some spare bandwidth and spare drives and will be running several nodes from different locations. {Home & business} We offer a service in

securing the network... and running either a full or pruned node, will still be contributing to that.  Wink

THE FIRST DECENTRALIZED & PLAYER-OWNED CASINO
.EARNBET..EARN BITCOIN: DIVIDENDS
FOR-LIFETIME & MUCH MORE.
. BET WITH: BTCETHEOSLTCBCHWAXXRPBNB
.JOIN US: GITLABTWITTERTELEGRAM
Amph
Legendary
*
Offline Offline

Activity: 3206
Merit: 1069



View Profile
February 18, 2016, 03:34:46 PM
 #22

always a full, i don't mind downloading the whole blockchain, game nowadays are 60giga each soem time and we download them easily why we should not do the same with the blockchain?
Jet Cash
Legendary
*
Offline Offline

Activity: 2716
Merit: 2457


https://JetCash.com


View Profile WWW
February 18, 2016, 03:36:33 PM
 #23

I'll run a full node for Bitcoin, and probably full nodes for a couple of alts. That's using public WiFi as well.

Offgrid campers allow you to enjoy life and preserve your health and wealth.
Save old Cars - my project to save old cars from scrapage schemes, and to reduce the sale of new cars.
My new Bitcoin transfer address is - bc1q9gtz8e40en6glgxwk4eujuau2fk5wxrprs6fys
Cuidler
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
February 18, 2016, 03:59:01 PM
 #24

Any changes in 0.12 in regard to pruning vs current situation ? Especialy whether wallet will work or you can choose what HDD space to use for random very old blocks (probably most needy feature imo so thousands of pruned nodes can have at least few complete copies of the whole blockchain together...).

imagine 5200 nodes are running.. imagine in april 3000 of them(old) wont be full validating nodes. and the remaining 2200 that are the updated core clients. wont all be running in full validation mode with full archival storage..


Most peope dont give shit if the blockchain is over 100 GB, but for these HDD space really matters like having VPS limit 100 GB, it is preffered if they at least run pruned node which is much better than nothing. If they can set like 20 GB most recent blocks + overhead and 80 GB random old blocks, they can run this pruned node on their VPS plan forever and when the total blockchain will be 400 GB in many years they still have 20% of all old blocks so for every 5 such pruned nodes they still keep the whole 400 GB blockchain record on average for new full/pruned nodes to synchronize.

Anyway there should be only few full nodes who set to pruned with significantly smaller size than 60 GB. I mean unless you really need more free HDD space there is not reason to set from 60 GB to 10 GB and instead of 350 GB free HDD space have 400 GB free HDD space Smiley

.Liqui Exchange.Trade and earn 24% / year on BTC, LTC, ETH
....Brand NEW..........................................Payouts every 24h. Learn more at official thread
bctmke
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
February 18, 2016, 05:49:31 PM
 #25

Full node for me.  I have a few tiny VPS that might get pruned nodes but we'll see.

NXS is on the move!   Come subscribe to our subreddit  https://www.reddit.com/r/nexusearth/
Come mine NXS at http://nxsminingpool.com
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!