Skip to content

[DRAFT] WIP QML Generate Snapshot Signet #446

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

D33r-Gee
Copy link
Contributor

@D33r-Gee D33r-Gee commented Mar 4, 2025

Based on #424. For evaluation purposes only!

GUI Integration for Generating UTXO Snapshots

Overview

This PR adds initial GUI support for generating a signet UTXO snapshot at height 160,000, building on Bitcoin Core's assumeutxo infrastructure.

What This PR Does

  1. Adds a basic GUI interface for generating UTXO snapshots via the Connection Settings panel
  2. Implements non-blocking snapshot generation via QT Thread
  3. Provides visual confirmation of snapshot generation
  4. Adds a snapshot progress notifications accessible via a handler

Implementation Details

Core Components Modified

  1. Node Interface (src/node/interfaces.cpp)
  • Implements a notification handler for snapshot generation progress (rewind and restore)
  1. Snapshot Qml (src/qml/models/snapshotqml.h)
  • Introduces a worker class to manage snapshot generation
  1. QML Integration (src/qml/models/nodemodel.cpp)
  • Manages snapshot generation state and progress
  • Uses Qt's thread system to prevent UI blocking
  • Provides progress updates via Qt signals
  1. UI Components (src/qml/components/SnapshotGenSettings.qml)
  • File view for snapshot generation
  • Snapshot generation progress and completion

Key Design Decisions

  1. Non-blocking Implementation
  • Snapshot generation runs in separate QT thread
  • UI remains responsive during generation
  • Node is disconnected from the network during generation
  1. Extensibility
  • Interface designed to accommodate future assumeutxo changes
  • Error handling framework in place

Testing Instructions

  1. Build
  2. Launch Bitcoin Core QML GUI
  3. Navigate to Connection Settings
  4. Wait for IBD to complete
  5. Click "Generate Snapshot"
  6. Verify (see screenshots below):
    • "Snapshot Generated" confirmation appears
    • snapshot file is created in the signet data directory
Ubuntu 22.04 Screenshots

Screenshot 2025-03-04 115218
Screenshot 2025-03-04 115246
Screenshot 2025-03-04 115309
Screenshot 2025-03-04 115323
Screenshot 2025-03-04 115356
Screenshot 2025-03-04 115641
Screenshot 2025-03-04 gen file view

Expected Behavior

  • File selection dialog works
  • Success/failure state properly displayed
  • Node is disconnected from the network during generation

Future Work

  1. Cancel Snapshot Generation
  • Add ability to cancel snapshot generation
  1. Integration
  • Coordinate with upstream assumeutxo changes
  • Add support for network-specific snapshots (testnet and mainnet)

Notes for Reviewers

Snapshot Compatibility

  • Currently only works with signet
  • Limited to specific 160,000 height
  • Validates against chain parameters m_assumeutxo_data
    (the changes there can be discarded once synced since m_assumeutxo_data is already hardcoded)

This is a work in progress - feedback welcome on the approach and implementation details.

@D33r-Gee D33r-Gee force-pushed the qml-gen-snapshot-signet branch from d44eb7f to abc189a Compare March 5, 2025 16:20
@yashrajd
Copy link

yashrajd commented Mar 5, 2025

Great start! Thanks for continuing to do this man. I have not tested on my machine, responding to screenshots below.

What This PR Does

  1. Adds a basic GUI interface for generating UTXO snapshots via the Connection Settings panel
  2. Implements non-blocking snapshot generation via QT Thread
  3. Provides visual confirmation of snapshot generation
  4. Adds a snapshot progress notifications accessible via a handler

...

  1. UI Components (src/qml/components/SnapshotGenSettings.qml)
  • File view for snapshot generation
  • Snapshot generation progress and completion

Key Design Decisions

  1. Non-blocking Implementation
  • Snapshot generation runs in separate QT thread
  • UI remains responsive during generation
  • Node is disconnected from the network during generation
  1. Extensibility
  • Interface designed to accommodate future assumeutxo changes
  • Error handling framework in place

Top-tier PR write-up, kudos!

Screenshot 2025-03-04 115309

My main gripe still is that 'load/generate snapshot' makes no sense in Connection Settings. Otherwise looks good.

Screenshot 2025-03-04 115323

"A snapshot captures the current state of bitcoin transactions on the network. It can be imported into other bitcoin nodes to speed up the initial setup. You can generate a snapshot of the current chain state.

Isn't the snapshot generated a pre-decided block height only? not the current block height?

  • if so, we should mention the date/block height in the text.
  • we should also update the text so as to avoid giving wrong impression
  • long-standing issue with reference to transactions

Suggested copy: "A snapshot captures the state of the bitcoin network up to a certain date in the recent past. It can be imported into other bitcoin nodes to speed up their initial sync.
Snapshot date: 23rd September 2023 (block 657478)

Screenshot 2025-03-04 115356

Perhaps the "Rewinding" text is placeholder. Should be something like:
**This might take a while.

You can continue using the application while the process continues in the background.**

Good to have would be to show some a % progress number

Screenshot 2025-03-04 115641

The View File button is awesome! Consider adding a Done button too that will send the user back to home screen/block clock...

@D33r-Gee
Copy link
Contributor Author

D33r-Gee commented Mar 6, 2025

My main gripe still is that 'load/generate snapshot' makes no sense in Connection Settings. Otherwise looks good.

in the figma design where would you idealy prefer these options would be placed under?

@D33r-Gee
Copy link
Contributor Author

D33r-Gee commented Mar 6, 2025

Isn't the snapshot generated a pre-decided block height only? not the current block height?

  • if so, we should mention the date/block height in the text.
  • we should also update the text so as to avoid giving wrong impression
  • long-standing issue with reference to transactions

Great suggestions will update with the next push

@D33r-Gee
Copy link
Contributor Author

D33r-Gee commented Mar 6, 2025

Good to have would be to show some a % progress number

Could you share some design ideas for this?

@D33r-Gee
Copy link
Contributor Author

D33r-Gee commented Mar 6, 2025

Consider adding a Done button too that will send the user back to home screen/block clock...

Could you update the figma to reflect that?

@D33r-Gee D33r-Gee force-pushed the qml-gen-snapshot-signet branch from abc189a to 34a6f54 Compare March 19, 2025 16:39
@D33r-Gee
Copy link
Contributor Author

with 34a6f54 rebased over main and addressed feedback from @yashrajd (see screenshots below)

WSL Ubuntu 22.04 screenshots

Screenshot 2025-03-19 085821
Screenshot 2025-03-19 085754

@D33r-Gee
Copy link
Contributor Author

@GBKS could you take a look at the current iteration of the design and user flow, and le me know your thoughts?

@GBKS
Copy link
Contributor

GBKS commented Mar 26, 2025

Nice progress here. I just tried to test and just see the message that IBD is not complete:

image

However, the block status tells me it's all synced, as well as the CLI:

image

The signet explorer also showed this block as the latest one. Do you maybe know what the problem might be?


On a different note, my assumption was that we show either snapshot import (during IBD) or snapshot creation (post-IBD). We only need one at a time, right?

@D33r-Gee
Copy link
Contributor Author

However, the block status tells me it's all synced, as well as the CLI:

Thanks for testing. Ok going to take a look I think I know what the issue is

On a different note, my assumption was that we show either snapshot import (during IBD) or snapshot creation (post-IBD). We only need one at a time, right?

Yep that's correct. That said, in terms of display if the user has loaded a snapshot my assumption is that we still want to display that, is that correct? (see screenshot below)

Connection Settings Snapshot Loaded

Screenshot 2025-03-26 093610

@yashrajd
Copy link

yashrajd commented Mar 26, 2025

Yep that's correct. That said, in terms of display if the user has loaded a snapshot my assumption is that we still want to display that, is that correct? (see screenshot below)

Makes sense.

On the flip side, if they *did not load a snapshot during IBD, the green check icon should not be present. (the Load Snapshot text has could be greyed out too). The description part could read "Cannot load a snapshot because sync is already completed".

@D33r-Gee D33r-Gee force-pushed the qml-gen-snapshot-signet branch from 34a6f54 to fd78f7e Compare March 27, 2025 17:48
@D33r-Gee
Copy link
Contributor Author

with fd78f7e rebased and addressed @GBKS feedback (please see screenshots below)

Generate Button appears after IBD completion

Screenshot 2025-03-27 104639

Next: will address the use case that @yashrajd mentioned...

On the flip side, if they *did not load a snapshot during IBD, the green check icon should not be present. (the Load Snapshot text has could be greyed out too). The description part could read "Cannot load a snapshot because sync is already completed".

@GBKS
Copy link
Contributor

GBKS commented Mar 28, 2025

Let's clarify the situation around having an imported snapshot. Is there any user benefit to showing that a snapshot was imported, after the import is done? Of course, during the import, the user wants to see progress and at the end they want to see a confirmation that it was completed successfully. But after that, is there any reason to keep this note around?

@D33r-Gee
Copy link
Contributor Author

Let's clarify the situation around having an imported snapshot. Is there any user benefit to showing that a snapshot was imported, after the import is done? Of course, during the import, the user wants to see progress and at the end they want to see a confirmation that it was completed successfully. But after that, is there any reason to keep this note around?

Great questions, going to let @yashrajd respond first... then will share my thoughts

@yashrajd
Copy link

Let's clarify the situation around having an imported snapshot. Is there any user benefit to showing that a snapshot was imported, after the import is done? Of course, during the import, the user wants to see progress and at the end they want to see a confirmation that it was completed successfully. But after that, is there any reason to keep this note around?

I don't have a strong preference as I said earlier, but here's why I think it should be there:

  • Christoph's description above reminds me of in-app CTAs. Interface elements can take up valuable space (say CTAs on Home Screen), so it's natural to get rid of them once they're not relevant. But this is a Setting item deep in the navigation, and I'm not aware of a pattern where we remove settings that are not applicable.

  • One pattern we do see is Settings items that also serve a communication or marketing purpose but are not actionable (Proton VPN and Signal do this IIRC) are still displayed as a way of informing the user that the app has this feature.

  • Though this scenario is a bit different, if Load snapshot has been used then it serves to communicate that fact. If it hasn't, the item communicates that the feature exists. After all, the generated snapshot is intended to be used somewhere else, and the presence of this item communicates that and indicates to the user where to load generated snapshot on their other machine.

@D33r-Gee
Copy link
Contributor Author

Thanks @GBKS and @yashrajd for the feedback.

So got a compromise in the form of 3 potential use cases:
  1. The user's node has just started, therefore the snapshot load option is available (visible)

Screenshot 2025-03-31 093125

  1. The user has loaded a snapshot:

Screenshot 2025-03-31 093210

  1. the user's node has reached full sync (IBD complete) without a snapshot:

Screenshot 2025-03-31 093245

Please let me know your thoughts?

@D33r-Gee D33r-Gee force-pushed the qml-gen-snapshot-signet branch from fd78f7e to db364e3 Compare April 1, 2025 21:19
@GBKS
Copy link
Contributor

GBKS commented Apr 2, 2025

Christoph's description above reminds me of in-app CTAs. Interface elements can take up valuable space (say CTAs on Home Screen), so it's natural to get rid of them once they're not relevant. But this is a Setting item deep in the navigation, and I'm not aware of a pattern where we remove settings that are not applicable.

One pattern we do see is Settings items that also serve a communication or marketing purpose but are not actionable (Proton VPN and Signal do this IIRC) are still displayed as a way of informing the user that the app has this feature.

Though this scenario is a bit different, if Load snapshot has been used then it serves to communicate that fact. If it hasn't, the item communicates that the feature exists. After all, the generated snapshot is intended to be used somewhere else, and the presence of this item communicates that and indicates to the user where to load generated snapshot on their other machine.

@yashrajd we're not removing anything and it's not a marketing thing. There is a single item for this feature that is always visible and shows the appropriate state. If you can generate a snapshot, it shows that. If you can't, it shows that you can import a snapshot. It's one or the other, or am I missing something?

@yashrajd
Copy link

yashrajd commented Apr 2, 2025

TL;DR: IMO it's just a couple of list items that don't take up prominent or important space. They can serve multiple functions (as actionable elements, show state: enabled/disabled/progress) and we always display both, it even serves as marketing/education/communication. Happy to mockup different states if @D33r-Gee needs it.

Let's clarify the situation around having an imported snapshot. Is there any user benefit to showing that a snapshot was imported, after the import is done? Of course, during the import, the user wants to see progress and at the end they want to see a confirmation that it was completed successfully. But after that, is there any reason to keep this note around?

my impression is that you are saying: the Load Snapshot list item should be removed after snapshot has been imported. sorry if I misunderstood you & don't have to read the stuff below

.
.

@yashrajd we're not removing anything and it's not a marketing thing. There is a single item for this feature that is always visible and shows the appropriate state. If you can generate a snapshot, it shows that. If you can't, it shows that you can import a snapshot. It's one or the other, or am I missing something?

actually it's not just one or the other...it's never BOTH afaik but there's cases where it's NEITHER: if you have a pruned node, you cannot generate a snapshot. Do we not show the Generate Snapshot list item in that case? Users can un-prune their nodes btw. Users can also delete their bitcoin folders in which you have to do IBD again & want to load a snapshot.

With your proposed approach (if I understood you correctly), content/list-items will appear and disappear as situation changes... I don't think the user wants/expects Settings items to do that.

@D33r-Gee
Copy link
Contributor Author

D33r-Gee commented Apr 2, 2025

Happy to mockup different states if @D33r-Gee needs it.

Yes that would be helpful to visualize the different use cases/states.

@D33r-Gee D33r-Gee force-pushed the qml-gen-snapshot-signet branch from db364e3 to d7523cd Compare April 22, 2025 20:23
@D33r-Gee
Copy link
Contributor Author

with d7523cd updated both the snapshot loading and snapshot generation pages to reflect @GBKS video (thanks for providing that) and thanks @yashraj for meeting and providing clarification.

Please let me know your thoughts...

hebasto and others added 3 commits May 26, 2025 09:50
3b7d57f add missing #include <cstdint> for GCC 15 (Matt Whitlock)

Pull request description:

  I'm not sure what broke here, but I'm unable to build without adding these `cstdint` includes, otherwise both GCC and clang complain for me on Fedora 42:

  ```
  $ ./autogen.sh
  $ ./configure --with-qml
  $ make
  Making all in src
  make[1]: Entering directory '/home/kepler/btc/gui-qml/src'
  make[2]: Entering directory '/home/kepler/btc/gui-qml/src'
  make[3]: Entering directory '/home/kepler/btc/gui-qml'
  make[3]: Leaving directory '/home/kepler/btc/gui-qml'
    CXX      bitcoind-bitcoind.o
    CXX      libbitcoin_node_a-banman.o
    CXX      libbitcoin_node_a-httpserver.o
  In file included from httpserver.cpp:11:
  ./chainparamsbase.h:23:5: error: ‘uint16_t’ does not name a type
     23 |     uint16_t RPCPort() const { return m_rpc_port; }
        |     ^~~~~~~~
  ./chainparamsbase.h:11:1: note: ‘uint16_t’ is defined in header ‘<cstdint>’; this is probably fixable by adding ‘#include <cstdint>’
     10 | #include <memory>
    +++ |+#include <cstdint>
     11 | #include <string>
  ./chainparamsbase.h:24:5: error: ‘uint16_t’ does not name a type
     24 |     uint16_t OnionServiceTargetPort() const { return m_onion_service_target_port; }
     ```

     <details>

     <summary>configure output</summary>

  ```
  checking for pkg-config... /bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking for a BSD-compatible install... /bin/install -c
  checking whether sleep supports fractional seconds... yes
  checking filesystem timestamp resolution... 0.01
  checking whether build environment is sane... yes
  checking for a race-free mkdir -p... /bin/mkdir -p
  checking for gawk... gawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports nested variables... yes
  checking xargs -n works... yes
  checking whether to enable maintainer-specific portions of Makefiles... yes
  checking for g++... g++
  checking whether the C++ compiler works... yes
  checking for C++ compiler default output file name... a.out
  checking for suffix of executables...
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether the compiler supports GNU C++... yes
  checking whether g++ accepts -g... yes
  checking for g++ option to enable C++11 features... none needed
  checking whether make supports the include directive... yes (GNU style)
  checking dependency style of g++... gcc3
  checking whether g++ supports C++17 features with -std=c++17... yes
  checking whether the compiler supports GNU Objective C++... no
  checking whether g++ -std=c++17 accepts -g... no
  checking dependency style of g++ -std=c++17... gcc3
  checking how to print strings... printf
  checking for gcc... gcc
  checking whether the compiler supports GNU C... yes
  checking whether gcc accepts -g... yes
  checking for gcc option to enable C11 features... none needed
  checking whether gcc understands -c and -o together... yes
  checking dependency style of gcc... gcc3
  checking for a sed that does not truncate output... /bin/sed
  checking for grep that handles long lines and -e... /bin/grep
  checking for egrep... /bin/grep -E
  checking for fgrep... /bin/grep -F
  checking for ld used by gcc... /bin/ld
  checking if the linker (/bin/ld) is GNU ld... yes
  checking for BSD- or MS-compatible name lister (nm)... /bin/nm -B
  checking the name lister (/bin/nm -B) interface... BSD nm
  checking whether ln -s works... yes
  checking the maximum length of command line arguments... 1572864
  checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
  checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
  checking for /bin/ld option to reload object files... -r
  checking for file... file
  checking for objdump... objdump
  checking how to recognize dependent libraries... pass_all
  checking for dlltool... no
  checking how to associate runtime and link libraries... printf %s\n
  checking for ranlib... ranlib
  checking for ar... ar
  checking for archiver @file support... @
  checking for strip... strip
  checking command to parse /bin/nm -B output from gcc object... ok
  checking for sysroot... no
  checking for a working dd... /bin/dd
  checking how to truncate binary pipes... /bin/dd bs=4096 count=1
  checking for mt... no
  checking if : is a manifest tool... no
  checking for stdio.h... yes
  checking for stdlib.h... yes
  checking for string.h... yes
  checking for inttypes.h... yes
  checking for stdint.h... yes
  checking for strings.h... yes
  checking for sys/stat.h... yes
  checking for sys/types.h... yes
  checking for unistd.h... yes
  checking for dlfcn.h... yes
  checking for objdir... .libs
  checking if gcc supports -fno-rtti -fno-exceptions... no
  checking for gcc option to produce PIC... -fPIC -DPIC
  checking if gcc PIC flag -fPIC -DPIC works... yes
  checking if gcc static flag -static works... no
  checking if gcc supports -c -o file.o... yes
  checking if gcc supports -c -o file.o... (cached) yes
  checking whether the gcc linker (/bin/ld -m elf_x86_64) supports shared libraries... yes
  checking whether -lc should be explicitly linked in... no
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... yes
  checking whether to build static libraries... yes
  checking how to run the C++ preprocessor... g++ -std=c++17 -E
  checking for ld used by g++ -std=c++17... /bin/ld -m elf_x86_64
  checking if the linker (/bin/ld -m elf_x86_64) is GNU ld... yes
  checking whether the g++ -std=c++17 linker (/bin/ld -m elf_x86_64) supports shared libraries... yes
  checking for g++ -std=c++17 option to produce PIC... -fPIC -DPIC
  checking if g++ -std=c++17 PIC flag -fPIC -DPIC works... yes
  checking if g++ -std=c++17 static flag -static works... no
  checking if g++ -std=c++17 supports -c -o file.o... yes
  checking if g++ -std=c++17 supports -c -o file.o... (cached) yes
  checking whether the g++ -std=c++17 linker (/bin/ld -m elf_x86_64) supports shared libraries... yes
  checking dynamic linker characteristics... (cached) GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking for ar... /bin/ar
  checking for gcov... /bin/gcov
  checking for llvm-cov... /bin/llvm-cov
  checking for lcov... no
  checking for python3.8... no
  checking for python3.9... no
  checking for python3.10... no
  checking for python3.11... no
  checking for python3.12... no
  checking for python3... /bin/python3
  checking for genhtml... no
  checking for git... /bin/git
  checking for ccache... /bin/ccache
  checking for xgettext... /bin/xgettext
  checking for hexdump... /bin/hexdump
  checking for objcopy... /bin/objcopy
  checking for doxygen... /bin/doxygen
  checking whether C++ compiler accepts -Werror... yes
  checking whether the linker accepts -Wl,--fatal-warnings... yes
  checking whether C++ compiler accepts -Wall... yes
  checking whether C++ compiler accepts -Wextra... yes
  checking whether C++ compiler accepts -Wgnu... no
  checking whether C++ compiler accepts -Wformat -Wformat-security... yes
  checking whether C++ compiler accepts -Wvla... yes
  checking whether C++ compiler accepts -Wshadow-field... no
  checking whether C++ compiler accepts -Wthread-safety... no
  checking whether C++ compiler accepts -Wloop-analysis... no
  checking whether C++ compiler accepts -Wredundant-decls... yes
  checking whether C++ compiler accepts -Wunused-member-function... no
  checking whether C++ compiler accepts -Wdate-time... yes
  checking whether C++ compiler accepts -Wconditional-uninitialized... no
  checking whether C++ compiler accepts -Wduplicated-branches... yes
  checking whether C++ compiler accepts -Wduplicated-cond... yes
  checking whether C++ compiler accepts -Wlogical-op... yes
  checking whether C++ compiler accepts -Woverloaded-virtual... yes
  checking whether C++ compiler accepts -Wsuggest-override... yes
  checking whether C++ compiler accepts -Wunreachable-code-loop-increment... no
  checking whether C++ compiler accepts -Wimplicit-fallthrough... yes
  checking whether C++ compiler accepts -Wdocumentation... no
  checking whether C++ compiler accepts -Wunused-parameter... yes
  checking whether C++ compiler accepts -Wself-assign... no
  checking whether C++ compiler accepts -fno-extended-identifiers... yes
  checking whether C++ compiler accepts -msse4.2... yes
  checking whether C++ compiler accepts -msse4.1... yes
  checking whether C++ compiler accepts -mavx -mavx2... yes
  checking whether C++ compiler accepts -msse4 -msha... yes
  checking whether C++ compiler accepts -mpclmul... yes
  checking for SSE4.2 intrinsics... yes
  checking for SSE4.1 intrinsics... yes
  checking for AVX2 intrinsics... yes
  checking for x86 SHA-NI intrinsics... yes
  checking whether C++ compiler accepts -march=armv8-a+crc... no
  checking whether C++ compiler accepts -march=armv8-a+crypto... no
  checking for ARMv8 CRC32 intrinsics... no
  checking for ARMv8 SHA-NI intrinsics... no
  checking whether byte ordering is bigendian... no
  checking how to run the C preprocessor... gcc -E
  checking for egrep -e... (cached) /bin/grep -E
  checking whether gcc is Clang... no
  checking whether pthreads work with "-pthread" and "-lpthread"... yes
  checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
  checking whether more special flags are required for pthreads... no
  checking for PTHREAD_PRIO_INHERIT... yes
  checking whether std::atomic can be used without link library... yes
  checking for gcc option to enable large file support... none needed
  checking for g++ -std=c++17 options needed to detect all undeclared functions... none needed
  checking whether strerror_r is declared... yes
  checking whether strerror_r returns char *... yes
  checking whether C++ compiler accepts -fPIC... yes
  checking whether C++ compiler accepts -fstack-reuse=none... yes
  checking whether C++ compiler accepts -Wstack-protector... yes
  checking whether C++ compiler accepts -fstack-protector-all... yes
  checking whether C++ compiler accepts -fcf-protection=full... yes
  checking whether C++ compiler accepts -fstack-clash-protection... yes
  checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=3... yes
  checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
  checking whether the linker accepts -Wl,--enable-reloc-section... no
  checking whether the linker accepts -Wl,--dynamicbase... no
  checking whether the linker accepts -Wl,--nxcompat... no
  checking whether the linker accepts -Wl,--high-entropy-va... no
  checking whether the linker accepts -Wl,-z,relro... yes
  checking whether the linker accepts -Wl,-z,now... yes
  checking whether the linker accepts -Wl,-z,separate-code... yes
  checking whether the linker accepts -fPIE -pie... yes
  checking for endian.h... yes
  checking for sys/endian.h... no
  checking for byteswap.h... yes
  checking for sys/select.h... yes
  checking for sys/prctl.h... yes
  checking for sys/sysctl.h... no
  checking for vm/vm_param.h... no
  checking for sys/vmmeter.h... no
  checking for sys/resources.h... no
  checking whether getifaddrs is declared... yes
  checking whether ifaddrs funcs can be used without link library... yes
  checking whether freeifaddrs is declared... yes
  checking whether ifaddrs funcs can be used without link library... yes
  checking whether fork is declared... yes
  checking whether setsid is declared... yes
  checking whether pipe2 is declared... yes
  checking for timingsafe_bcmp... no
  checking whether le16toh is declared... yes
  checking whether le32toh is declared... yes
  checking whether le64toh is declared... yes
  checking whether htole16 is declared... yes
  checking whether htole32 is declared... yes
  checking whether htole64 is declared... yes
  checking whether be16toh is declared... yes
  checking whether be32toh is declared... yes
  checking whether be64toh is declared... yes
  checking whether htobe16 is declared... yes
  checking whether htobe32 is declared... yes
  checking whether htobe64 is declared... yes
  checking whether bswap_16 is declared... yes
  checking whether bswap_32 is declared... yes
  checking whether bswap_64 is declared... yes
  checking for __builtin_clzl... yes
  checking for __builtin_clzll... yes
  checking for getmemoryinfo... yes
  checking for mallopt M_ARENA_MAX... yes
  checking for posix_fallocate... yes
  checking for default visibility attribute... yes
  checking for dllexport attribute... no
  checking for thread_local support... yes
  checking for gmtime_r... yes
  checking for Linux getrandom function... yes
  checking for getentropy via sys/random.h... yes
  checking for sysctl... no
  checking for sysctl KERN_ARND... no
  checking for if type char equals int8_t... no
  checking for fdatasync... yes
  checking for F_FULLFSYNC... no
  checking for O_CLOEXEC... yes
  checking for __builtin_prefetch... yes
  checking for _mm_prefetch... yes
  checking for strong getauxval support in the system headers... yes
  checking for std::system... yes
  checking for ::_wsystem... no
  checking for Qt5Core >= 5.11.3... yes
  checking for Qt5Gui >= 5.11.3... yes
  checking for Qt5Widgets >= 5.11.3... yes
  checking for Qt5Network >= 5.11.3... yes
  checking for Qt5Test >= 5.11.3... yes
  checking for Qt5DBus >= 5.11.3... yes
  checking for Qt5Qml >= 5.11.3... yes
  checking for Qt5QmlModels >= 5.11.3... yes
  checking for Qt5Quick >= 5.11.3... yes
  checking for Qt5QuickControls2 >= 5.11.3... yes
  checking for static Qt... no
  checking whether -fPIE can be used with this Qt config... yes
  checking for moc-qt5... /usr/lib64/qt5/bin/moc-qt5
  checking for uic-qt5... /usr/lib64/qt5/bin/uic-qt5
  checking for rcc-qt5... /usr/lib64/qt5/bin/rcc-qt5
  checking for lrelease-qt5... /usr/lib64/qt5/bin/lrelease-qt5
  checking for lupdate-qt5... /usr/lib64/qt5/bin/lupdate-qt5
  checking for lconvert-qt5... /usr/lib64/qt5/bin/lconvert-qt5
  checking whether to build Bitcoin Core GUI... yes (Qt5)
  checking whether main function is needed for fuzz binary... checking whether the linker accepts ... no
  yes
  checking for __builtin_mul_overflow... yes
  checking for Berkeley DB C++ headers... /usr/include/libdb/
  checking for sqlite3 >= 3.7.17... yes
  checking whether to build wallet with support for sqlite... yes
  checking whether Userspace, Statically Defined Tracing tracepoints are supported... yes
  checking for miniupnpc/miniupnpc.h... no
  checking for miniupnpc/upnpcommands.h... no
  checking for miniupnpc/upnperrors.h... no
  checking for natpmp.h... no
  checking for Boost headers >= 1.64.0 (106400)... yes
  checking whether C++ preprocessor accepts -DBOOST_NO_CXX98_FUNCTION_BASE... yes
  checking whether Boost.Process can be used... yes
  checking for libevent >= 2.1.8... yes
  checking for libevent_pthreads >= 2.1.8... yes
  checking if evhttp_connection_get_peer expects const char**... no
  checking for libqrencode... yes
  checking for libzmq >= 4... yes
  checking for libmultiprocess... no
  checking whether to build bitcoind... yes
  checking whether to build bitcoin-cli... yes
  checking whether to build bitcoin-tx... yes
  checking whether to build bitcoin-wallet... yes
  checking whether to build bitcoin-util... yes
  checking whether to build experimental bitcoin-chainstate... no
  checking whether to build libraries... yes
  checking if ccache should be used... yes
  checking whether C compiler accepts -fdebug-prefix-map=A=B... yes
  checking whether C preprocessor accepts -fmacro-prefix-map=A=B... yes
  checking if wallet should be enabled... yes
  checking whether to build with support for UPnP... no
  checking whether to build with support for NAT-PMP... no
  checking whether to build GUI with support for D-Bus... yes
  checking whether to build GUI with support for QR codes... yes
  checking whether to build test_bitcoin-qt... no
  checking whether to build test_bitcoin... yes
  checking whether to reduce exports... no
  checking that generated files are newer than configure... done
  configure: creating ./config.status
  config.status: creating libbitcoinconsensus.pc
  config.status: creating Makefile
  config.status: creating src/Makefile
  config.status: creating doc/man/Makefile
  config.status: creating share/setup.nsi
  config.status: creating share/qt/Info.plist
  config.status: creating test/config.ini
  config.status: creating contrib/devtools/split-debug.sh
  config.status: creating doc/Doxyfile
  config.status: creating src/config/bitcoin-config.h
  config.status: src/config/bitcoin-config.h is unchanged
  config.status: executing depfiles commands
  config.status: executing libtool commands
  === configuring in src/secp256k1 (/home/kepler/btc/gui-qml/src/secp256k1)
  configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr/local'  '--with-qml' '--disable-shared' '--with-pic' '--enable-benchmark=no' '--enable-module-recovery' '--disable-module-ecdh' --cache-file=/dev/null --srcdir=.
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking for a BSD-compatible install... /bin/install -c
  checking whether sleep supports fractional seconds... yes
  checking filesystem timestamp resolution... 0.01
  checking whether build environment is sane... yes
  checking for a race-free mkdir -p... /bin/mkdir -p
  checking for gawk... gawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports nested variables... yes
  checking xargs -n works... yes
  checking for gcc... gcc
  checking whether the C compiler works... yes
  checking for C compiler default output file name... a.out
  checking for suffix of executables...
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether the compiler supports GNU C... yes
  checking whether gcc accepts -g... yes
  checking for gcc option to enable C11 features... none needed
  checking whether gcc understands -c and -o together... yes
  checking whether make supports the include directive... yes (GNU style)
  checking dependency style of gcc... gcc3
  checking dependency style of gcc... gcc3
  checking for ar... ar
  checking the archiver (ar) interface... ar
  checking how to print strings... printf
  checking for a sed that does not truncate output... /bin/sed
  checking for grep that handles long lines and -e... /bin/grep
  checking for egrep... /bin/grep -E
  checking for fgrep... /bin/grep -F
  checking for ld used by gcc... /bin/ld
  checking if the linker (/bin/ld) is GNU ld... yes
  checking for BSD- or MS-compatible name lister (nm)... /bin/nm -B
  checking the name lister (/bin/nm -B) interface... BSD nm
  checking whether ln -s works... yes
  checking the maximum length of command line arguments... 1572864
  checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
  checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
  checking for /bin/ld option to reload object files... -r
  checking for file... file
  checking for objdump... objdump
  checking how to recognize dependent libraries... pass_all
  checking for dlltool... no
  checking how to associate runtime and link libraries... printf %s\n
  checking for ranlib... ranlib
  checking for archiver @file support... @
  checking for strip... strip
  checking command to parse /bin/nm -B output from gcc object... ok
  checking for sysroot... no
  checking for a working dd... /bin/dd
  checking how to truncate binary pipes... /bin/dd bs=4096 count=1
  checking for mt... no
  checking if : is a manifest tool... no
  checking for stdio.h... yes
  checking for stdlib.h... yes
  checking for string.h... yes
  checking for inttypes.h... yes
  checking for stdint.h... yes
  checking for strings.h... yes
  checking for sys/stat.h... yes
  checking for sys/types.h... yes
  checking for unistd.h... yes
  checking for dlfcn.h... yes
  checking for objdir... .libs
  checking if gcc supports -fno-rtti -fno-exceptions... no
  checking for gcc option to produce PIC... -fPIC -DPIC
  checking if gcc PIC flag -fPIC -DPIC works... yes
  checking if gcc static flag -static works... no
  checking if gcc supports -c -o file.o... yes
  checking if gcc supports -c -o file.o... (cached) yes
  checking whether the gcc linker (/bin/ld -m elf_x86_64) supports shared libraries... yes
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... no
  checking whether to build static libraries... yes
  checking if gcc supports -Werror... yes
  checking if gcc supports -std=c89 -pedantic -Wno-long-long -Wnested-externs -Wshadow -Wstrict-prototypes -Wundef... yes
  checking if gcc supports -Wno-overlength-strings... yes
  checking if gcc supports -Wall... yes
  checking if gcc supports -Wno-unused-function... yes
  checking if gcc supports -Wextra... yes
  checking if gcc supports -Wcast-align... yes
  checking if gcc supports -Wcast-align=strict... yes
  checking if gcc supports -Wconditional-uninitialized... no
  checking if gcc supports -Wreserved-identifier... no
  checking if gcc supports -fvisibility=hidden... yes
  checking for valgrind support... yes
  checking for x86_64 assembly availability... yes
  checking that generated files are newer than configure... done
  configure: creating ./config.status
  config.status: creating Makefile
  config.status: creating libsecp256k1.pc
  config.status: executing depfiles commands
  config.status: executing libtool commands

  Build Options:
    with external callbacks = no
    with benchmarks         = no
    with tests              = yes
    with ctime tests        = yes
    with coverage           = no
    with examples           = no
    module ecdh             = no
    module recovery         = yes
    module extrakeys        = yes
    module schnorrsig       = yes
    module ellswift         = yes

    asm                     = x86_64
    ecmult window size      = 15
    ecmult gen prec. bits   = 4

    valgrind                = yes
    CC                      = gcc
    CPPFLAGS                =
    SECP_CFLAGS             = -O2  -std=c89 -pedantic -Wno-long-long -Wnested-externs -Wshadow -Wstrict-prototypes -Wundef -Wno-overlength-strings -Wall -Wno-unused-function -Wextra -Wcast-align -Wcast-align=strict -fvisibility=hidden
    CFLAGS                  = -g -O2
    LDFLAGS                 =

  Options used to compile and link:
    external signer = yes
    multiprocess    = no
    with libs       = yes
    with wallet     = yes
      with sqlite   = yes
      with bdb      = no
    with gui / qt   = yes
      with qml      = yes
      with qr       = yes
    with zmq        = yes
    with test       = yes
    with fuzz binary = yes
    with bench      = yes
    with upnp       = no
    with natpmp     = no
    use asm         = yes
    USDT tracing    = yes
    sanitizers      =
    debug enabled   = no
    gprof enabled   = no
    werror          = no
    LTO             = no

    target os       = linux-gnu
    build os        = linux-gnu

    CC              = /bin/ccache gcc
    CFLAGS          = -pthread -g -O2
    CPPFLAGS        =  -fmacro-prefix-map=$(abs_top_srcdir)=.  -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3  -DHAVE_BUILD_INFO -DPROVIDE_FUZZ_MAIN_FUNCTION
    CXX             = /bin/ccache g++ -std=c++17
    CXXFLAGS        =   -fdebug-prefix-map=$(abs_top_srcdir)=.  -fstack-reuse=none -Wstack-protector -fstack-protector-all -fcf-protection=full -fstack-clash-protection  -Wall -Wextra -Wformat -Wformat-security -Wvla -Wredundant-decls -Wdate-time -Wduplicated-branches -Wduplicated-cond -Wlogical-op -Woverloaded-virtual -Wsuggest-override -Wimplicit-fallthrough  -Wno-unused-parameter    -fno-extended-identifiers -g -O2
    LDFLAGS         =  -lpthread  -Wl,-z,relro -Wl,-z,now -Wl,-z,separate-code -pie
    AR              = /bin/ar
    ARFLAGS         = cr

  ```

ACKs for top commit:
  hebasto:
    ACK 3b7d57f.

Tree-SHA512: 75662734d131906d2524de0a65908ffc5796410bed8776b3a2ec35610ac3b050adf98bb5ae8f1f7324c697f19a39b61e1a7b9d2734061232f793ed9f83e110b6
- Extend node interface with virtual functions for UTXO snapshot loading
- Add signal mechanism to monitor snapshot loading progress
- Include predefined signet UTXO dataset in chainparams for validation
This introduces a Rewind Progress notification so that it is available when generating an AssumeUTXO snapshot through the UI.
@D33r-Gee D33r-Gee force-pushed the qml-gen-snapshot-signet branch from d7523cd to 1eaec25 Compare May 26, 2025 17:27
@D33r-Gee
Copy link
Contributor Author

1eaec25 rebased over main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants