user372: Daedalus wallet is a 'full node wallet' does that mean it  acts like a validator node on the network while active? or does it simply mean that it validates all the transactions on the blockchain for internal use only?
Does the distinction make sense?
If I leave Daedalus running on my laptop will it do meaningful work for the network?

user252: Just to add clarification to answer from @Yanis , in the current implementation - Daedalus plays a role in helping network only when serving an incoming connection, which would be the case if your node is listening on publicly reachable IP:port combination and you have a peer who specified your IP:port in their topology.
However, it does provide you assurance of any transaction you submit is directly submitted to network by broadcasting to the topology (by default only IOG nodes, who would relay it further to network).

user13: 
does it simply mean that it validates all the transactions on the blockchain for internal use only?

Yes.

does that mean it acts like a validator node on the network while active?

No.

Does the distinction make sense? If I leave Daedalus running on my laptop will it do meaningful work for the network?

No.
The description you are referring to:

Daedalus is a full node wallet. This means that unlike light wallets
(e.g.Yoroi, Adalite etc.) Daedalus downloads a full copy of the
Cardano blockchain and independently validates every transaction in
its history. That way you get maximum security and completely
trustless operation, without centrally hosted 3rd party servers.

only means that Daedalus holds a full copy of the ledger which means the wallet can validate every single block from the past. There is no pruning as you would have with lightweight wallets.
However, Daedauls runs cardano-node in wallet-mode/passive mode, meaning it cannot verify new transactions coming to the network - only producer nodes do that. They can extend the blockchain.


user801: From my understanding, it does meaningful work for the network. When you run Daedalus, you run a local cardano-node with which Daedalus' back-end interacts via the node-to-client IPC protocol (more info). From documentation we can see that cardano-node does validate and relay blocks. I wasn't able to find anything about how validation affects relaying but I suppose nodes don't relay invalid blocks.
[update]
I think my assumption was correct. I found a superb video from Andrew Westberg's youtube channel. He talks in more details about how Tx is propagated. Take a look at step 3.3, where cardano-node runs a validation before relaying info further.
1. Cardano-node to mempool (transactions aggregation phase, where mempool is a place where store transactions we hear in a network)

Cardano-node places the tx into its mempool.
Nodes connected to yours ask it “You seen any new transactions lately?”
Your node responds with “Sure have, you want them too?”
Their node asks “Yes, I’d like to have those particular transactions”
Your node says, “Here you go”.
Rinse/repeat and everybody’s mempool looks roughly similar with the transactions it holds.

2. From mempool to block

Some stakepool out there wins the lottery and decides to mint a newhblock.
They add txns from their mempool into the block until it is exhausted or the
maximum block size is reached.
The stakepool then places the block at the tip of its own blockchain.
Any transactions added to the block are removed from the stakepool’s
mempool.

3. From block to the network

Other nodes ask the stakepool, “You seen any blocks lately”
The stakepool responds, “I sure have. Looks like I’ve got one more than you
do. Here’s the header information and the hash.”
“That looks like a valid block, do you mind sending me the whole thing?”
“No problem, here you go!”
Rinse/Repeat and now the whole network agrees that the new block is valid.
All nodes remove the transactions that occur in the block from their
mempools.


372: <p>Daedalus wallet is a 'full node wallet' does that mean it  acts like a validator node on the network while active? or does it simply mean that it validates all the transactions on the blockchain for internal use only?</p>
<p>Does the distinction make sense?
If I leave Daedalus running on my laptop will it do meaningful work for the network?</p>
 252: <p>Just to add clarification to answer from @Yanis , in the current implementation - Daedalus plays a role in helping network only when serving an incoming connection, which would be the case if your node is listening on publicly reachable IP:port combination and you have a peer who specified your IP:port in their topology.</p>
<p>However, it does provide you assurance of any transaction you submit is directly submitted to network by broadcasting to the topology (by default only IOG nodes, who would relay it further to network).</p>
 13: <blockquote>
<p>does it simply mean that it validates all the transactions on the blockchain for internal use only?</p>
</blockquote>
<p>Yes.</p>
<blockquote>
<p>does that mean it acts like a validator node on the network while active?</p>
</blockquote>
<p>No.</p>
<blockquote>
<p>Does the distinction make sense? If I leave Daedalus running on my laptop will it do meaningful work for the network?</p>
</blockquote>
<p>No.</p>
<p>The description you are referring to:</p>
<blockquote>
<p>Daedalus is a full node wallet. This means that unlike light wallets
(e.g.Yoroi, Adalite etc.) Daedalus downloads a full copy of the
Cardano blockchain and independently validates every transaction in
its history. That way you get maximum security and completely
trustless operation, without centrally hosted 3rd party servers.</p>
</blockquote>
<p>only means that Daedalus holds a full copy of the ledger which means the wallet can validate every single block from the past. There is no pruning as you would have with lightweight wallets.</p>
<p>However, Daedauls runs <code>cardano-node</code> in wallet-mode/passive mode, meaning it cannot verify new transactions coming to the network - only producer nodes do that. They can extend the blockchain.</p>
<p><a href="https://i.stack.imgur.com/Hddcx.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Hddcx.png" alt="enter image description here" /></a></p>
 801: <p>From my understanding, it does meaningful work for the network. When you run Daedalus, you run a local cardano-node with which Daedalus' back-end interacts via the node-to-client IPC protocol (<a href="https://docs.cardano.org/en/latest/explore-cardano/cardano-architecture-overview/index.html?highlight=daedalus#id2" rel="noreferrer">more info</a>). From <a href="https://docs.cardano.org/en/latest/explore-cardano/cardano-architecture-overview/index.html?highlight=daedalus#nodes-and-remote-nodes" rel="noreferrer">documentation</a> we can see that cardano-node does <code>validate and relay blocks</code>. I wasn't able to find anything about how validation affects relaying but I suppose nodes don't relay invalid blocks.</p>
<p>[update]</p>
<p>I think my assumption was correct. I found a superb <a href="https://www.youtube.com/watch?v=K7c-5S-23dg" rel="noreferrer">video</a> from <a href="https://www.youtube.com/channel/UCymuph1bMuWC4PhjE67uf7g" rel="noreferrer">Andrew Westberg's</a> youtube channel. He talks in more details about how Tx is propagated. Take a look at step 3.3, where cardano-node runs a validation before relaying info further.</p>
<p><strong>1. Cardano-node to mempool</strong> (transactions aggregation phase, where mempool is a place where store transactions we hear in a network)</p>
<ol>
<li>Cardano-node places the tx into its mempool.</li>
<li>Nodes connected to yours ask it “You seen any new transactions lately?”</li>
<li>Your node responds with “Sure have, you want them too?”</li>
<li>Their node asks “Yes, I’d like to have those particular transactions”</li>
<li>Your node says, “Here you go”.</li>
<li>Rinse/repeat and everybody’s mempool looks roughly similar with the transactions it holds.</li>
</ol>
<p><strong>2. From mempool to block</strong></p>
<ol>
<li>Some stakepool out there wins the lottery and decides to mint a newhblock.</li>
<li>They add txns from their mempool into the block until it is exhausted or the
maximum block size is reached.</li>
<li>The stakepool then places the block at the tip of its own blockchain.</li>
<li>Any transactions added to the block are removed from the stakepool’s
mempool.</li>
</ol>
<p><strong>3. From block to the network</strong></p>
<ol>
<li>Other nodes ask the stakepool, “You seen any blocks lately”</li>
<li>The stakepool responds, “I sure have. Looks like I’ve got one more than you
do. Here’s the header information and the hash.”</li>
<li>“That looks like a valid block, do you mind sending me the whole thing?”</li>
<li>“No problem, here you go!”</li>
<li>Rinse/Repeat and now the whole network agrees that the new block is valid.</li>
<li>All nodes remove the transactions that occur in the block from their
mempools.</li>
</ol>
