upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/scripts
AgeCommit message (Collapse)Author
2026-09-03payout: fail review when a money line lands on collapsing LogPrintbitflash-maintainer
scripts/check-money-log-lines.sh flattens each LogPrint call in src/rpc.cpp and fails if a money-moving phrase appears in a plain LogPrint call. A new line that reports money moving needs LogPrintAlways and one more phrase in the list.
2026-08-26Merge upstream v1.2.19 into the forkbitflash-maintainer
Merges upstream tag v1.2.19 (9e39a50) into merge/upstream-1.2.18 (991853f). Unlike the 1.2.15->1.2.18 replay, bc3de30 is a true ancestor of our branch via a9b4f89, so this is an ordinary three-way merge with merge-base bc3de30. Delta: 36 files, +3265/-163, the Tor onion transport (managed Tor, signed direct onion endpoints, onion-only dial mode) and the nHDNext restore fix. src/main.cpp, main.h, script.cpp/h and db.cpp/h are byte-identical between the two tags, and the poll() socket loop carries no diff hunks, so the merge is consensus-neutral and the soak-tested socket paths are unchanged. relay/ is untouched; the payout ledger (rpc.cpp) is untouched. 7 conflict blocks in 6 files, resolved as follows. Makefile -- VERSION. Ours: stays 1.2.19+sec with the naming comment updated, so artifacts from this tree cannot be mistaken for the upstream release. src/Makefile, src/makefile.mingw -- HEADERS list. Ours (no market.h) plus their tor.h. NODE_OBJS auto-merged correctly: no market.o, tor.o present. src/selftest.cpp -- known-tests list. Union: payout-ledger (ours) and managed-tor (theirs). src/main_gui.cpp -- one block. Our /dumpaddresses kept; their BtfStopManagedTor() on the StartNode failure path taken. The /rvrelay pin, /noannounce and the marketplace removal auto-merged and were verified intact. src/nostr.cpp -- two blocks in ResolveDescriptor. Signature takes both out-params (our fExchangeOk, their rawOut). The body keeps our drain-to-EOSE read -- returning early poisons the pooled socket for the next caller -- and adds their rawOut capture. Our TLS 1.2 floor (SSL_CTX_set_min_proto_version) is untouched by this merge; upstream 1.2.19 still has no floor of its own. Upstream's release commit also added four build logs and a compiled Python cache (build-1219.log, build-17.log, build-appimage.log, build-node.log, scripts/__pycache__/bitflash_chain.cpython-313.pyc). Removed here; they are build output, not source.
2026-08-13release: v1.2.19 (nHDNext restore fix, Tor onion transport: managed Tor, ↵bitflash
direct onion peers, onion-only mode)
2026-08-13net: add onion-only btf dial modeNsable-sh
2026-08-13release: verify bundled Tor signaturesNsable-sh
2026-08-13release: package Windows builds with managed TorNsable-sh
2026-08-12site: document public deployment contractNsable-sh
2026-08-11tools: address audit follow-upsNsable-sh
2026-08-11tools: harden chain audit scriptsNsable-sh
2026-08-11tools: add UTXO inclusion proofsNsable-sh
2026-08-11Merge pull request 'tools: add deterministic UTXO commitment verifier' (#19) ↵Bitflash
from utxo-set-commitment into main
2026-08-11Merge main into utxo-set-commitment (union README)bitflash
2026-08-11Merge main into mining-calculator (union README)bitflash
2026-08-10tools: add Bitflash mining calculatorNsable-sh
2026-08-10tools: add deterministic UTXO commitment verifierNsable-sh
2026-08-10tools: add fair launch verifierNsable-sh
2026-08-10tools: static block explorer generator (v0)Bitflash
2026-08-07pool: publish round proof ledgerNsable-sh
2026-08-07tools: reject non-http(s) dashboard URLs in the pool directoryBitflash
A pool's dashboard URL comes from its self-published status file. Escaping it for HTML is not enough: a javascript: or data: scheme would still render as a clickable script-injection on the public directory page. Only emit a link for http(s) schemes; anything else shows as no link.
2026-08-07tools: build a static pool directoryNsable-sh
2026-08-06release: sign SHA256SUMS with a pinned key, verify against itBitflash
verify-release.sh embeds the Bitflash release signing key and now requires that the checksum signature validate against that exact key, not merely against some key in the caller's keyring (#138). It also fetches releases from releases.bitflash.network instead of the retired GitHub host, resolving 'latest' from latest.txt. Release signing key fingerprint: 910A 2B4C CA87 9E81 FB4B 2AEA 1D4A 53D3 B78A A4B8
2026-08-04Add release verification tooling (#108)mtg0001
Co-authored-by: Gilcimar Duarte <ti@gpm.infra>