Full node usefulness ???

[miguelmorales85]

Is my node still useful even if it has never relayed first a transaction on the blockchain?

Are pruned nodes good for the bitcoin network even when they never relay transactions? 

[1714607101]

1714607101

[1714607101]

1714607101

[1714607101]

1714607101

[1714607101]

1714607101

[shorena]

Is my node still useful even if it has never relayed first a transaction on the blockchain?

This sounds like something you have seen on blockchain.info. Their information hardly matters, they are just another node (with plenty of info about their state and a wallet service).

Your node constantly verifies and relays transactions for others. Open the debug.log (Help -> Debug Window -> "Open") and search for ERROR: AcceptToMemoryPool: to see which you did not relay. Enter getmempoolinfo in the console (Help -> Debug Window -> Console) to see how many you have relayed and are valid according to your nodes settings.

Are pruned nodes good for the bitcoin network even when they never relay transactions? 

Yes, a pruned node still verifies and relays new blocks and all transactions. You cant help new nodes sync though and you cant currently use a pruned node as a wallet, but it still supports the network to run one.

[Jet Cash]

I think it's good to run full ( or pruned ) nodes to help keep the miners honest.

[miguelmorales85]

Hi, I need you knowledge again shorena.

This SegWit and CSV information is getting all the attention but I have not seen what happened to pruned nodes and how does it affect the new soft fork its performance. Can you explain to me this?

 I have noticed that a full node get sync so much faster than before.

I would like to re-activate my RaspNode (pruned)

But I want it to be able to sync correctly

[Lauda]

This SegWit and CSV information is getting all the attention but I have not seen what happened to pruned nodes and how does it affect the new soft fork its performance. Can you explain to me this?

Segwit has been merged but has no activation date yet. I don't see either one of those things having an direct impact on node performance anytime soon. Keep in mind that the node will become more resource heavy once Segwit starts having an impact (more storage space and bandwidth requirements).

I have noticed that a full node get sync so much faster than before.

There was an huge improvement in version 0.12.0 called libsecp256k1.

I would like to re-activate my RaspNode (pruned) . But I want it to be able to sync correctly

I don't see what you mean with 'sync correctly'. There is no incorrect synchronization, else you just aren't synchronized with the network. If you want to activate your node today, nothing changes for you.

[miguelmorales85]

I would like to re-activate my RaspNode (pruned) . But I want it to be able to sync correctly

I don't see what you mean with 'sync correctly'. There is no incorrect synchronization, else you just aren't synchronized with the network. If you want to activate your node today, nothing changes for you.

I meant that my RaspNode always fall behind while syncing and never sync with the network.. It is always a step behind.
I have a rPi2+ with a 64 GB pendrive.

[Lauda]

I meant that my RaspNode always fall behind while syncing and never sync with the network.. It is always a step behind.
I have a rPi2+ with a 64 GB pendrive.

Then you mean that your Node is not able to catch up with the network. Interesting. I didn't know that the Pi couldn't handle being a node anymore. If it is not able to catch up using Bitcoin Core 0.12.1 I see no reason why it would be able to do so with 0.12.x or 0.13.0 (both haven't been released yet).