BitShares Forum

Main => Technical Support => Topic started by: warmach on July 26, 2016, 12:24:58 am

Title: Delayed Node
Post by: warmach on July 26, 2016, 12:24:58 am
What is the purpose of the Delayed Node? 
Title: Re: Delayed Node
Post by: xeroc on July 26, 2016, 05:34:55 am
blocks that are accepted by the non-delayed node have been accepted at least once.
The delyed only returns blocks when they are irreversible (confirmed by ~2/3 of all witnesses) .. The delay is usually about 30 blocks which is 90 seconds.
Title: Re: Delayed Node
Post by: warmach on July 26, 2016, 07:54:43 pm
Thanks....

So is the witness_node and CLI_wallet the same except that the CLI can initiate transactions?
Title: Re: Delayed Node
Post by: xeroc on July 27, 2016, 06:19:47 am
Thanks....

So is the witness_node and CLI_wallet the same except that the CLI can initiate transactions?
the witness nodes takes care of the blockchain and p2p stuff .. and the cli-wallet is a light-client that merely connects to a witness node .. could be yours, or anyone elses (if you trust them)
Title: Re: Delayed Node
Post by: warmach on July 28, 2016, 08:07:16 pm
blocks that are accepted by the non-delayed node have been accepted at least once.
The delyed only returns blocks when they are irreversible (confirmed by ~2/3 of all witnesses) .. The delay is usually about 30 blocks which is 90 seconds.

I wanted to do some development against Bitshares and have tried running a delayed node.  It looks like it keeps its own blockchain and uses a reasonable amount of memory and cpu resources.  As a developer, couldn't I just use the witness node and only take action against blocks with at least 30 confirmations?  If so, that would save me HDD, memory, and cpu resources. 
Title: Re: Delayed Node
Post by: xeroc on July 29, 2016, 07:03:51 am
You can do whatever you think is easier for you to do ..

Here are some docs for you:
http://docs.bitshares.eu/integration/index.html