user6918: Using Blockfrost API, I can query a stake address, and receive known addresses that have "state=used" like when I query them on my local node via Cardano-Wallet.
I am interested in "state=unused" though.
How can I get unused receiving addresses for a stake key using Blockfrost API?
EDIT:
When I use:

localhost:[port]/v2/wallets/[wallet id]/addresses?state=unused' | jq '.[0]

...on my local instance of cardano-wallet, I get the first addr for the wallet that has state=unused I was hoping for something similar from the blockfrost api - so I could avoid having to setup something that provides it to my web app from my local linux box where I have cardano-node & cardano-wallet running

user252: The ask seems fundamentally wrong, as unused wallets - by definition - are not on-chain and can only be derived using root public keys (in case you haven't, could be helpful for you to check BIP-44 spec that is used by cardano-wallet ). The derivation of addresses can be easily achieved via one of the SDK/libs offline (you can find many of them at developer portal - most popular ones being  cardano-serialisation-lib and cardano-multiplatform-lib).
Some notes tho about these (adding here, tho it may not be relevant for your context):

There can be close to infinite unused addresses for a given stake account. You may see limited number of addresses because of default BIP-44 address gap (20), but that will not be all-inclusive list.
One can only derive addresses at different address idx if they have the root pub key, wouldn't be a good practice to rely on external services, especially when you have libraries to do it locally.
Even if you were to use a remote service that would provide list of addresses , from query pov - it would never be guaranteed to include different combinations of payment and stake key credentials , as they can also be merged across from different wallets.


6918: <p>Using Blockfrost API, I can query a stake address, and receive known addresses that have &quot;state=used&quot; like when I query them on my local node via Cardano-Wallet.
I am interested in &quot;state=unused&quot; though.
How can I get unused receiving addresses for a stake key using Blockfrost API?</p>
<p>EDIT:
When I use:</p>
<blockquote>
<p>localhost:[port]/v2/wallets/[wallet id]/addresses?state=unused' | jq '.[0]</p>
</blockquote>
<p>...on my local instance of cardano-wallet, I get the first addr for the wallet that has state=unused I was hoping for something similar from the blockfrost api - so I could avoid having to setup something that provides it to my web app from my local linux box where I have cardano-node &amp; cardano-wallet running</p>
 252: <p>The ask seems fundamentally wrong, as unused wallets - by definition - are not on-chain and can only be derived using root public keys (in case you haven't, could be helpful for you to check <a href="https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki" rel="nofollow noreferrer">BIP-44</a> spec that is used by <a href="https://input-output-hk.github.io/cardano-wallet/design/Notes-about-BIP-44" rel="nofollow noreferrer">cardano-wallet</a> ). The derivation of addresses can be easily achieved via one of the SDK/libs offline (you can find many of them at <a href="https://developers.cardano.org/tools?tags=library" rel="nofollow noreferrer">developer portal</a> - most popular ones being  <code>cardano-serialisation-lib</code> and <code>cardano-multiplatform-lib</code>).</p>
<p>Some notes tho about these (adding here, tho it may not be relevant for your context):</p>
<ol>
<li>There can be close to infinite unused addresses for a given stake account. You may see limited number of addresses because of default BIP-44 address gap (20), but that will not be all-inclusive list.</li>
<li>One can only derive addresses at different address idx if they have the root pub key, wouldn't be a good practice to rely on external services, especially when you have libraries to do it locally.</li>
<li>Even if you were to use a remote service that would provide list of addresses , from query pov - it would never be guaranteed to include different combinations of payment and stake key credentials , as they can also be merged across from different wallets.</li>
</ol>
