D33r-Gee

> There is no snapshot data set for mainnet yet, so you cannot use AssumeUTXO on mainnet without modifying the code. Yep Bitcoin Core v26 only has the hardcoded hashes...

@GBKS thanks for starting this issue... It is addressed in here https://github.com/bitcoin-core/gui-qml/pull/397 I like having the address under the header will look into how to pull that off :)

> Based on both the figma and the web prototype, the path should only be displayed on the custom selection after the user has made a choice. > > https://lively-kashata-cfde7e.netlify.app/screen/first-use/storage-location?state=default...

> > To be clear we don't want to display the default datadir path here, correct? > > As of figma, and the web prototype (link above) no, but it...

Rebased over main [dfc0023 ](https://github.com/bitcoin-core/gui-qml/commit/dfc002306b6e6445703c75a87b0725786db33133)to [2fbb27a](https://github.com/bitcoin-core/gui-qml/commit/2fbb27a37a7c666f49a25465863dcafd9d0713f5)

@GBKS and @pablomartin4btc Thanks for the feedback regarding the storage amount and the error messaging. those will be addressed in a different PR since this is only for datadir display...

> [8e8aadf](https://github.com/bitcoin-core/gui-qml/commit/8e8aadf2396e54428c0ca5ae562030734d0650cf) I cannot repro the double-click issue anymore #399 friendly ping @pablomartin4btc > That's great to hear... > one issue/inconsistency: the selected custom data dir is not updated/displayed correctly...

@MarnixCroes Thanks for the screenshots... I see what you mean... Looking into it

Thanks @pablomartin4btc for testing it > I'm not sure about showing the default path when the user has selected the custom one but not a blocker. I could go either...

with the latest commit [2a301e1](https://github.com/bitcoin-core/gui-qml/commit/2a301e117f6e83611b08a3d6242ed6aaa1f4caa5) addressed @MarnixCroes comment about the datadir not displaying properly during onboarding. Turns out made the mistake of not using the setter function for the customDataDir...