Kaizen_Kintsugi has quit [Ping timeout: 252 seconds]
c_arc has joined #bitcoin-core-dev
Guest99100 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<Guest99100>
Hi, I'm looking for someone to help me dig up old bitcoin-dev archives. I'm analyzing consensus change events in Bitcoin for a research project, and have realized that there is an important gap in the IRC logs that I'm looking at. The missing samples are mainly 2015-07-03, 2015-07-04 and 2015-07-05. I've gathered chat-logs in this period from
<michaelfolkson>
Guest99100: I can't help with your missing logs but I'd recommend looking at the #bitcoin-core-dev log archives too if you haven't already. I suspect a lot of consensus discussions were on that channel as the separation between Core as an implementation and the protocol was potentially less understood/less recognized 5-6 years ago
mikehu44 has joined #bitcoin-core-dev
cmdcode has quit [Quit: Client closed]
Kaizen_Kintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has quit [Ping timeout: 260 seconds]
Guest99100 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<Guest99100>
michaelfolkson Thanks for the reply. I have noticed the Bitcoin-core-dev channel as well, though I have worked my way from old to new chats (Currently in 2015). Do you have any idea when the core team 'officially' switched from bitcoin-dev ti butcoin-core-dev?
<michaelfolkson>
Guest99100: No, sorry. Not without looking at the logs like you are doing. And obviously nothing is "official", it is just where people ended up having discussions on IRC
<michaelfolkson>
Someone else may be able to help, I wasn't around :)
<bitcoin-git>
bitcoin/master fa8d492 MarcoFalke: rest: Return error when header count is not integral
<bitcoin-git>
bitcoin/master 810ce36 MarcoFalke: Merge bitcoin/bitcoin#23213: rest: Return error when header count is not i...
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #23213: rest: Return error when header count is not integral (master...2110-restInt) https://github.com/bitcoin/bitcoin/pull/23213
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
drnet has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has quit [Ping timeout: 252 seconds]
drnet has quit [Quit: Leaving]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
gleb7 has quit [Ping timeout: 252 seconds]
gleb7 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
igh4st has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
igh4st has quit [Client Quit]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] brunoerg opened pull request #23267: test: bip125-replaceable in listsinceblock (master...2021-10-test-bip125-listsinceblock) https://github.com/bitcoin/bitcoin/pull/23267
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
c_arc has joined #bitcoin-core-dev
goatpig has quit [Remote host closed the connection]
Kaizen_Kintsugi has quit [Ping timeout: 245 seconds]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
bomb-on has joined #bitcoin-core-dev
bomb-on has quit [Client Quit]
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
mikehu44 has quit [Ping timeout: 265 seconds]
c_arc has joined #bitcoin-core-dev
Jackielove4u has quit [Quit: Connection closed for inactivity]
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
tla2k21 has quit [Remote host closed the connection]
tla2k21 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Guest8587 has joined #bitcoin-core-dev
Guest8587 has quit [Client Quit]
jtrag has quit [Quit: <----- is PODAK (Passed out drunk at keyboard), and he has somehow managed to quit/disconnect...]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 252 seconds]
AaronvanW has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
morcos has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Talkless has joined #bitcoin-core-dev
commmon has quit [Read error: Connection reset by peer]
commmon has joined #bitcoin-core-dev
<achow101>
is anyone else unable to reach github right now?
<cfields>
wfm. web and git fetch.
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 260 seconds]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<TallTim>
I can resolve it, if it helps.
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<cfields>
sipa: what do you think about a c++ shim-wrapper (like aes.cpp for ctaes) around secp for Core, so we could build it as c++? With tighter integration, that'd save us from having to add all of the c buildsystem machinery for the single secp object.
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
ghostkeeper has joined #bitcoin-core-dev
KenCox94 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
KenCox94 has quit [Quit: Ping timeout (120 seconds)]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Talkless has quit [Quit: Konversation terminated!]
Kaizen_Kintsugi has quit [Remote host closed the connection]
KaizenKintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
KenCox94 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
smartin has quit [Quit: smartin]
AaronvanW has quit [Quit: Leaving...]
AaronvanW has joined #bitcoin-core-dev
gene has joined #bitcoin-core-dev
gene has quit [Remote host closed the connection]
gene has joined #bitcoin-core-dev
KaizenKintsugi has quit [Remote host closed the connection]
Kaizen_Kintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has quit [Ping timeout: 252 seconds]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
DavidBakin has quit [Quit: Client closed]
Guyver2 has quit [Quit: Going offline, see ya! (www.adiirc.com)]
c_arc has joined #bitcoin-core-dev
KenCox94 has quit [Ping timeout: 256 seconds]
ghostkeeper has quit [Remote host closed the connection]
ghostkeeper has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
ghostkeeper has quit [Ping timeout: 252 seconds]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
ghostkeeper has joined #bitcoin-core-dev
ghostkeeper has quit [Ping timeout: 250 seconds]
Kaizen_Kintsugi has quit [Remote host closed the connection]
Kaizen_Kintsugi has joined #bitcoin-core-dev
Kaizen_Kintsugi has quit [Remote host closed the connection]
Kaizen_Kintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has quit [Remote host closed the connection]
Kaizen_Kintsugi has joined #bitcoin-core-dev
Kaizen_Kintsugi has quit [Ping timeout: 260 seconds]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has joined #bitcoin-core-dev
Kaizen_Kintsugi has quit [Ping timeout: 252 seconds]
jarthur_ has joined #bitcoin-core-dev
jarthur has quit [Ping timeout: 265 seconds]
Kaizen_Kintsugi has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
bitdex has joined #bitcoin-core-dev
grettke has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<Davidbak>
I'm a little confused about GPG signing commits - is this for everyone who contributes (e.g., commits in a PR need to be signed) or just for the maintainers who do the merge to master/
c_arc has joined #bitcoin-core-dev
<gene>
davidbak: pretty sure all commits should be GPG signed
<gene>
contributors are encouraged to sign, merge commits must be signed
<gene>
hrm, looks like merge commits have the "should be signed"
<Davidbak>
ok, that's what I saw, just wanted to make sure it was definitive, thanks (because, maybe practice had changed without the doc getting update)
<gene>
that's just my reading of the section. maintainers will have a more definitive answer
<Davidbak>
ah, ok i'll wait
tla2k21 has quit [Ping timeout: 276 seconds]
c_arc has joined #bitcoin-core-dev
Kaizen_Kintsugi has quit [Remote host closed the connection]
Kaizen_Kintsugi has joined #bitcoin-core-dev
<sipa>
davidbak: i think most contributors do not sign their commits
<sipa>
i generally don't
<sipa>
when a maintainer merges a PR, that _must_ be signed (CI will set off alarms when it isn't)
<Davidbak>
ok! that's the validation I wanted (because setting up GPG on my system might lead to running down a rathole I'd rather not do at the moment when I'm keen on getting the bitcoin core build running)
Kaizen_Kintsugi has quit [Ping timeout: 260 seconds]
ghostkeeper has joined #bitcoin-core-dev
<Davidbak>
speaking of which - is there a container already set up for building bitcoin core? I didn't spot anything like that at github.com/bitcoin or github.com/bitcoin-core
<gene>
sipa: do you think it would be worthwhile to investigate LXC container builds?
<sipa>
gene: who would use it?
<gene>
me :)
<gene>
seriously though, anyone who wanted a container setup without installing docker
<sipa>
ok, i'm not really familiar with either of them
<gene>
LXC is linux specific, built by Canonical
<gene>
you can also setup LXC to be rootless, where I think dockerd always needs root
<gene>
pretty sure LXC is also more lightweight than docker
<gene>
LXC doesn't have the community/proprietary split that docker uses
<Davidbak>
i'm not a docker fanboy, and have no stake in this, but you know, consider the use case - docker is ubiquitous, and sufficiently free for individual developers, and lightweight isn't really an issue for development/build machines (unlike deployment targets), etc. etc. but that's just what occurs to me.
<sipa>
my understanding is that LXC is a much more low-level isolation mechanism, and that docker actually used LXC under the hood on certain systems
<Davidbak>
and I wasn't looking for anything _supported_ by the project (though that would have been nice) just something to get me rolling, i'll look at those repos you found for me, gene
<sipa>
that said, i haven't directly used either
<gene>
davidbak: right, for CI it's less important. more thinking for poeople that wanted a container on a constrained device
<Davidbak>
i think that's true too: I just saw a page that said something like that
<sipa>
davidbak: i think it'd be cool to have a project-maintained docker image; the question is really just who would build/maintain it, as it seems so far nobody has stepped up
<Davidbak>
ah! my use case wasn't _running_ bitcoin core (i've got _that_ set up) but building - a container that had all tools + dependencies would be sweet ...
<gene>
davidbak: don't skip the packaging issue sipa linked, it has more community repos
<sipa>
oh, for building, i recommend guix actually
<Davidbak>
i know, well, if I get there ... i'll speak up and volunteer ...
<sipa>
that's what is used for release builds since 22.0
<Davidbak>
ok
* gene
still needs to try guix builds
<sipa>
and apart from guix itself (which can be a pain...), it needs no basically nothing
<sipa>
or, slightly more lowlevel/lightweight, the depends build system
<sipa>
this requires C++ compilers etc from the host system, but not much else, as the dependencies are fetch/built automatically
<Davidbak>
huh, i'll look at that - guix labels itself as a 'package manager' that can 'instantiate and manage unix-like oses' - didn't occur to me that it was a build mechanism for an individual project
<Davidbak>
(or could be used as such)
<sipa>
davidbak: it's not a very obvious choice no, but i think it's amazing
<gene>
guix useful for reproducible builds since you can statically define deps
<sipa>
because it's designed to be deterministic and reproducable from the bottom up
<gene>
jinx
<Davidbak>
well i see now at wikipedia that it is built on top of Nix and I know what _that_ is, so yes, I'll consider it thank you!
<sipa>
so it lets bitcoin core's build script (the contrib/guix/guix-build) instantiate an exactly specified build environment, with exact versions of compilers, dependencies, everything
<sipa>
it's inspired by nix, not built on top of
<Davidbak>
ok, well, the wikipedia article says "based on" several times, I misinterpreted that
<Davidbak>
but interesting: Guix itself can run in a Docker container! so ... that might be the way to go ... i'll report back next week ...
<sipa>
sure, or in any VM
<sipa>
in recent debian/ubuntu it's just apt install guix, and you're good
<sipa>
also, this discussion is perhaps more appropriate for #bitcoin-core-builds
<fanquake>
install guix binary on alpine, or apt install guix on debian
<Davidbak>
this is great! thanks both of you for your help! seriously, I wouldnt have looked at the guix stuff in the tree for awhile becuase I assumed (<=mistake!) it was for packaging up your artifacts _after_ building!
<sipa>
so the outermost layer for release builds is guix, which creates the deterministic env to build in
<Davidbak>
i'll check out that channel too, yep
<sipa>
then inside that, the depends system is invoked (which you can also invoke yourself directly, if you like release-like builds apart from the determinism), which builds dependencies