How do new wallets bootstrap Dust on mainnet?

Technical Questions
,
1

A developer asked how non-genesis wallets are expected to fund transactions, since Dust (the fee token) is generated by holding Night, but transacting with Night requires Dust.

On testnet this is solved by the faucet. On mainnet:

  1. How is Night initially distributed to new users?
  2. If receiving Night requires a transaction, and transactions require Dust, how does a new wallet bootstrap?
  3. Is the payFees dust sponsorship feature (currently on dapp connector-api HEAD) the intended solution for onboarding new users?
  4. Are there other mechanisms planned for bootstrapping (e.g., fee free first transaction, initial Dust allocation)?

Context: midnight-ledger/spec/dust.md defines Dust generation at 5 Dust per Night over ~1 week.
The fees() API returns values in Specks (1 Dust = 10^15 Specks), so even “30 trillion” in the CLI is only 0.03 Dust — fees are small, but getting the first Dust is the question.

2 Likes
2

What is the strategy to put in place at the moment in order to claim the first Dust in the Lace Midnight Preview wallet ?

This issue occurs for Night Forces recruits when claiming Testnet tokens. Need guidance for this case.

1 Like
3

I like your question, I’m intrigued by it tbh. I’m wondering if the solution could be that as part of the transfer transaction it could be also included the registration transaction so the recipient starts getting DUST automatically when receiving the NIGHTs. I’m not sure if making this by default may be a problem or undesirable for some users, or if it’s even feasible, just thinking out loud.

1 Like
4

would love to read more answers but I think since it’s a native token you don’t need to hold any dust to receive, but to interact with dapps you do. Might be wrong tbh

1 Like