<prayank>
fanquake: personally I consider personal lot of times medium accouunts and some stackexchange answers can be be of same level. and some answers even have those links. so there is nothing special with stackexchange. btw i am in top 5 based on 5 my answers in last year on bitcoin stackexchange..
<prayank>
I agree links could be avoided. However I felt people should have a choice to click and read something related but not edited.
<prayank>
> medium post suggests upgrading to an alternative client, which has an experimental fix, for a problem that bitcoin core didn't even post an advisory for (you can see why in the IRC logs). I think that would be confusing to link to, rather than just linking to our own documentation in json-rpc-interface.md, which was added in response to the same problem
<prayank>
if there is a better client people should use it
sipsorcery has joined #bitcoin-core-dev
<prayank>
I would have to read json-rpc-interface.md again which even I had changed once
<prayank>
people have lot of issues with it but nobody has the courage to open a pr that gets closed/nacked/something-else
<sipa>
Let's stay constructive please.
<sipa>
We all want the project to be the best it can be.
<sipa>
Topics like these are inevitably going to lead to constroversies. That doesn't mean we can't improve things
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
prayank has left #bitcoin-core-dev [#bitcoin-core-dev]
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
tla2k21 has quit [Ping timeout: 276 seconds]
AaronvanW has quit [Quit: Leaving...]
Guyver2 has quit [Quit: Going offline, see ya! (www.adiirc.com)]
tla2k21 has joined #bitcoin-core-dev
sipsorcery has quit [Ping timeout: 268 seconds]
brunoerg has joined #bitcoin-core-dev
<luke-jr>
fanquake: it lists Knots as one of several options to mitigate the vulnerability; this should only be a problem if you have a problem with any website acknowledging Knots even exists, which is absurd
<luke-jr>
(the language is even biased *against* that option, recommending the other options over it)
brunoerg has quit [Ping timeout: 256 seconds]
vysn has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
piku has joined #bitcoin-core-dev
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
bitcoin/master e158a2a 0xb10c: build: add systemtap's sys/sdt.h as depends
<bitcoin-git>
bitcoin/master c6d15c4 Pieter Wuille: [moveonly] Move MapIntoRange() to separate util/fastrange.h
<bitcoin-git>
bitcoin/master efab28b Pieter Wuille: Add FastRange32 function and use it throughout the codebase
<bitcoin-git>
bitcoin/master 96ecd6f Pieter Wuille: scripted-diff: rename MapIntoRange to FastRange64
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #23994: Consolidate all uses of the fast range mapping technique in util/fastrange.h (master...202201_fastrange) https://github.com/bitcoin/bitcoin/pull/23994
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
kexkey has quit [Ping timeout: 256 seconds]
kexkey has joined #bitcoin-core-dev
mikehu44 has quit [Ping timeout: 240 seconds]
earnestly has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
saranshsharma has joined #bitcoin-core-dev
bomb-on has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 268 seconds]
saranshsharma has quit [Ping timeout: 256 seconds]
saranshsharma has joined #bitcoin-core-dev
saranshsharma has quit [Ping timeout: 256 seconds]
kexkey has quit [Ping timeout: 256 seconds]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
sdfgsdfg has quit [Quit: ZzzZ]
sdfgsdfg has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 268 seconds]
bomb-on has quit [Read error: Connection reset by peer]
brunoerg has joined #bitcoin-core-dev
TheRec has quit [Ping timeout: 240 seconds]
TheRec has joined #bitcoin-core-dev
TheRec has quit [Changing host]
TheRec has joined #bitcoin-core-dev
TheRec has quit [Read error: Connection reset by peer]
TheRec has joined #bitcoin-core-dev
TheRec has quit [Changing host]
TheRec has joined #bitcoin-core-dev
TheRec has quit [Read error: No route to host]
TheRec has joined #bitcoin-core-dev
TheRec has quit [Read error: Connection reset by peer]
TheRec has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
TheRec has quit []
TheRec has joined #bitcoin-core-dev
TheRec has joined #bitcoin-core-dev
bitdex has quit [Quit: = ""]
Guest63 has joined #bitcoin-core-dev
Guest63 has quit [Client Quit]
bomb-on has joined #bitcoin-core-dev
Guest71 has joined #bitcoin-core-dev
Guest71 has quit [Client Quit]
yanmaani has quit [Ping timeout: 276 seconds]
rex4539 has joined #bitcoin-core-dev
sdfgsdfg has quit [Quit: ZzzZ]
yanmaani has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
TheRec has quit [Ping timeout: 256 seconds]
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] mzumsande opened pull request #24021: Rename and move PoissonNextSend functions (master...202201_jnewbery_poisson_rename) https://github.com/bitcoin/bitcoin/pull/24021
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
brunoerg has joined #bitcoin-core-dev
bomb-on has quit [Read error: Connection reset by peer]
brunoerg has quit [Ping timeout: 240 seconds]
TheRec has joined #bitcoin-core-dev
TheRec has quit [Changing host]
TheRec has joined #bitcoin-core-dev
rex4539 has quit [Remote host closed the connection]
rex4539 has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
Kaizen_K_ has quit [Remote host closed the connection]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 268 seconds]
Kaizen_Kintsugi_ has quit [Ping timeout: 256 seconds]
OP_NOP_ has quit [Ping timeout: 256 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 256 seconds]
jb55 has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
arythmetic has joined #bitcoin-core-dev
sirdigby727 has joined #bitcoin-core-dev
jb55 has quit [Ping timeout: 240 seconds]
jb55 has joined #bitcoin-core-dev
Guyver2_ has joined #bitcoin-core-dev
Guyver2 has quit [Ping timeout: 256 seconds]
Guyver2_ is now known as Guyver2
jarthur has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
Talkless has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
vysn has joined #bitcoin-core-dev
dgenr8 has joined #bitcoin-core-dev
vysn has quit [Ping timeout: 240 seconds]
brunoerg has quit [Remote host closed the connection]
sirdigby727 has quit [Quit: Connection closed for inactivity]
brunoerg has joined #bitcoin-core-dev
Talkless has quit [Quit: Konversation terminated!]
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
Talkless has joined #bitcoin-core-dev
Talkless has quit [Client Quit]
vysn has joined #bitcoin-core-dev
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 256 seconds]
rex4539 has quit [Remote host closed the connection]
grettke has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
rex4539 has joined #bitcoin-core-dev
sdfgsdfg has joined #bitcoin-core-dev
___nick___ has quit [Ping timeout: 240 seconds]
<Kaizen_K_>
Question, I'm reading up on segwit for the chaincode class, chapter 2, and I'm reading about the signature verification optimization of checksig and checkmultisig having their complexity dropped from O(n**2) -> O(n), how did it do this?
rex4539 has quit [Remote host closed the connection]
<Kaizen_K_>
This helps a lot, thanks. From my understanding, It is the way inputs were hashed. With the witness script removed, this solves the extra hashing for verification that is needed?
<sipa>
No, that's not it.
<Kaizen_K_>
derp
<sipa>
In BIP143 the part of the signature message that depends on the number of inputs is precomputed once for the entire transaction.
<Kaizen_K_>
ahhh
<sipa>
Rather than substituted into every signature message.
<Kaizen_K_>
thanks!
rex4539 has quit [Ping timeout: 276 seconds]
<Kaizen_K_>
Cool, and that pre computation looks like it is the hashPrevouts, hashSequence and hashOutputs from a previous transaction that can just be reused.
<sipa>
Indeed.
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] ryanofsky opened pull request #24024: Remove cs_main lock annotation from ChainstateManager.m_blockman (master...pr/block) https://github.com/bitcoin/bitcoin/pull/24024
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
mudsip has quit []
<Kaizen_K_>
Are nSequence and nLocktime used in conjunction to do a staggered payments? So I can construct a transaction with multiple inputs that sequentially unlock over a set time period?
<sipa>
A transaction always executes atomically. It either spends all its inputs, producing all its outputs, or doesn't do anything at all (because it is invalid).
rex4539 has joined #bitcoin-core-dev
<Kaizen_K_>
Oh okay
<Kaizen_K_>
that is good to know
<Kaizen_K_>
ty
<sipa>
You can construct chains of transactions where one depends on the previous one though.
<Kaizen_K_>
Cool
<sipa>
Or you can use OP_CSV / OP_CLTV to create outputs that can only be spent in transaction that have a certain locktime/nsequence.
<Kaizen_K_>
I will look those up
<sipa>
BIP 65 for OP_CLTV.
rex4539 has quit [Remote host closed the connection]
<Kaizen_K_>
perfect, the bips are excellent cause they provide the nitty gritty details of what I need to map my braad and foggy understanding of bitcoin to the implimentations of
<Kaizen_K_>
*implimentation.
<sipa>
implementations :)
<Kaizen_K_>
My spelling and grammar could use some improvement. :) ty
<sipa>
BIP 68 for the modern semantics of nSequence; BIP 112 for OP_CSV
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
andytoshi has quit [Ping timeout: 268 seconds]
sdfgsdfg has quit [Quit: ZzzZ]
grettke has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<dhruv>
Is there any history of running all functional test multiple times with varying CLI arguments? Working on BIP324, I am adding in a new CLI arg: -v2transport. I'm wondering if it would be prudent to run all functional tests with -v2transport=0 and also -v2transport=1