user127077: From Mastering Bitcoin:
"The second advantage of HD wallets is that users can create a sequence of public keys without having access to the corresponding private keys. This allows HD wallets to be used on an insecure server or in a receive-only capacity, issuing a different public key for each transaction. The public keys do not need to be preloaded or derived in advance, yet the server doesn’t have the private keys that can spend the funds."
How can the user can create public keys? Doesn't he need at least to have the seed?

user208: In BIP32 key derivation, having the parent extended public (xpub) key suffices for computing child public keys.
That parent xpub can be derived in a number of ways, but all eventually boil down to a seed. However, that seed is only used indirectly to construct the xpubs. Once you have the xpub, you can compute the child keys.

127077: <p>From <a href="https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch05.asciidoc#Type2_wallet" rel="nofollow noreferrer">Mastering Bitcoin</a>:
&quot;The second advantage of HD wallets is that users can create a sequence of public keys without having access to the corresponding private keys. This allows HD wallets to be used on an insecure server or in a receive-only capacity, issuing a different public key for each transaction. The public keys do not need to be preloaded or derived in advance, yet the server doesn’t have the private keys that can spend the funds.&quot;</p>
<p>How can the user can create public keys? Doesn't he need at least to have the seed?</p>
 208: <p>In BIP32 key derivation, having the parent extended public (xpub) key suffices for computing child public keys.</p>
<p>That parent xpub can be derived in a number of ways, but all eventually boil down to a seed. However, that seed is only used indirectly to construct the xpubs. Once you have the xpub, you can compute the child keys.</p>
