Skip to content

guix: support PLATFORM_GUI=1 release builds - #7628

Draft
PastaPastaPasta wants to merge 9 commits into
dashpay:developfrom
PastaPastaPasta:guix-platform-gui
Draft

guix: support PLATFORM_GUI=1 release builds#7628
PastaPastaPasta wants to merge 9 commits into
dashpay:developfrom
PastaPastaPasta:guix-platform-gui

Conversation

@PastaPastaPasta

Copy link
Copy Markdown
Member

Issue being fixed or feature implemented

Final PR of the DashPay series (stacked on #7623#7626#7627; tracking: #7512). Makes Guix release builds able to produce --enable-platform-gui binaries.

What was done?

  • guix-build prefetches the Rust standard libraries and the platform_cxx vendored-crates archive outside the offline build container (host-independent, need network/git), and passes PLATFORM_GUI=1 through to the containerized depends build.
  • Manifest additions: patchelf + zlib (prebuilt Rust toolchain interpreter fix) and lbzip2 (bzip2 depends archives).
  • The Guix workflow gains workflow_dispatch with hosts and platform_gui inputs so a single-host Platform build can be exercised on demand. Scheduled and tag builds are unchanged and never set the knob — release binaries only include the Platform GUI when explicitly requested.

How Has This Been Tested?

  • Extracted from the composite integration branch; the manifest/prefetch changes are the ones its Guix attempts exercised.
  • A full x86_64-linux-gnu PLATFORM_GUI=1 Guix run against this exact series is queued and its result will be posted here before undraft. Until then treat this PR as the mechanism, not a proven artifact.

Breaking Changes

None. Default Guix builds (schedule, tags, guix-build label) are byte-for-byte unaffected — the knob defaults to off everywhere.

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

native_rust installs the pinned prebuilt Rust toolchain as a native package and rust_stdlib provides the precompiled standard library for every supported cross target; contrib/devtools/update-rust-hashes.py maintains both pins together. funcs.mk gains a cargo environment wired to the depends cross toolchain and a per-package crate-vendoring template: any package that declares a vendored archive name and a cargo manifest gets a vendor-<package>-crates target and extracts the archive before building, so cargo builds run locked and fully offline.
…I knob

PLATFORM_GUI=1 adds mbedtls, native_protobuf, tenderdash_sources and platform_cxx to the package set. platform_cxx builds libdash_platform_cxx.a and its installed headers from a pinned dashpay/platform commit (packages/rs-platform-cxx), offline via the per-package vendored crates. config.site.in exports enable_platform_gui and PLATFORM_CXX_{CFLAGS,LIBS} discovery for the configure flag that arrives with the first C++ consumer.
…lane

The new lane builds depends with PLATFORM_GUI=1 (producing and hash-verifying the Platform CXX archive offline from vendored crates), then builds dash-qt against that prefix and runs the unit tests. The cache-sources producer generates and caches the platform-cxx vendored-crates archive, handing it to same-run consumers as an artifact on cache miss.

The --enable-platform-gui configure flag is added to this lane's BITCOIN_CONFIG by the Platform client library PR; until then the lane proves the depends knob and prefix link-compatibility. build.yml runs PR validation from the base branch (pull_request_target), so the lane first runs on push CI for this branch and takes effect for PRs after merge.
libdash_platform.a is a DAPI client for the Dash Platform GUI: a gRPC-Web-over-TLS transport on mbedtls with per-query endpoint pinning and scoped freshness, GroveDB drive queries whose proofs verify through the Platform-owned CXX bridge bound to the quorum-signed root, DPP identity/document decoding and state-transition construction where the signable bytes are the broadcast bytes, and versioned serialization for DashPay's per-wallet records. The new --enable-platform-gui configure flag requires the GUI and wallet, autodetects mbedtls and link-tests the Platform CXX archive from depends. Nothing outside the flag changes: dashd and default builds do not compile or link any of this.
Unit suites for the transport (dechunking, retry, freshness), DPP and drive layers run against Rust-generated fixed vectors: GroveDB proofs (keys, ranges, subqueries, absence, references, sum trees), DPP identities and state transitions, drive queries and quorum signatures. platformkeys_tests gains Platform record round-trip and payment-cursor coverage, and a fuzz target exercises the bridge's decode and verify entry points.
…lane

The lane introduced with the depends knob now passes --enable-platform-gui to configure, so the platform unit suites run in CI.
createAssetLockTransaction builds and funds an asset lock paying credits to a Platform funding key, at the payload version consensus accepts: version 2 is invalid until the v24 hard fork applies to the next block, and version 1 stays valid after activation, so a transaction built at the boundary is safe either way. CommitTransaction gains an optional broadcast_error out-parameter and a matching interfaces::Wallet::commitTransaction overload: a mempool rejection is reported to the caller instead of only the log, while the transaction stays committed to the wallet so the caller may abandon it. Both seams are wallet-type-agnostic and compiled unconditionally.
Adds the DashPay tab behind --enable-platform-gui: username registration (asset lock, identity registration and DPNS preorder/domain as a crash-recoverable state machine), a profile dialog, contacts with encrypted DIP-15 xpub exchange and private receiving-chain import, send-to-username contact payments with per-contact payment cursors, and seed-only recovery that rediscovers identities, contacts and payment cursors from Platform and wallet history. The tab requires a descriptor wallet: legacy wallets get a migrate prompt and cannot reach any Platform flow or spend. The Send dialog's temporarily-unavailable distinction is guarded under ENABLE_PLATFORM_GUI so default builds keep their exact error behavior.
Guix builds accept a PLATFORM_GUI knob: guix-build prefetches the Rust standard libraries and the platform_cxx vendored-crates archive outside the offline container (they are host-independent and need network and git access), and passes the knob through to the containerized depends build. The manifest gains patchelf and zlib for the prebuilt Rust toolchain and lbzip2 for bzip2 depends archives. The Guix workflow gains workflow_dispatch with host and platform_gui inputs so a single-host Platform build can be exercised on demand; scheduled and tag builds are unchanged and never set the knob.
@DashCoreAutoGuix

Copy link
Copy Markdown

Guix Automation has failed due to the HEAD commit not being signed by an authorized core-team member. Please rebase and sign or push a new empty signed commit to allow Guix build to happen.

@github-actions

Copy link
Copy Markdown

This pull request has conflicts, please rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants