< coinmonks>
Also I have created a survey to understand Bitcoin protocol development.. So for only 1 person filled it.. I would like you pls take 2 minutes and check it ..
< coinmonks>
I want to understand how BItcoin protocol development is getting funded now and are contributors in good economic condition
< tryphe>
coinmonks, it's mostly contributed to by folks in their spare time who have other avenues of income
< coinmonks>
Yes,, I want this statement backed by real data.. the only way is to ask from everyone..
< coinmonks>
The 1 response I got (I won't name them),,tells that he is a freelancer, want to work on Bitcoin fulltime and currently use some economic help in that direction..
< coinmonks>
We can always help these folks and create a path for more people working fulltime on Bitcoin
< bitcoin-git>
bitcoin/master c79bf32 Wladimir J. van der Laan: Merge #16625: scripts: remove github-merge.py
< elichai2>
Question about the translations. how does it works? is there a way to supervise changes? I see that a lot of it is filled with google translated strings (at least in Hebrew)
< * luke-jr>
wonders if BIP70-protocol support should be split from BIP70-parsing support, so wallets can continue to show past payments correctly once BIP70 is removed
< luke-jr>
(at least until we manage to get the data migrated to a protobuf-free format)
< elichai2>
sipa: https://github.com/bitcoin/bitcoin/issues/15621 requires a batch `secp256k1_ecdsa_recover` that recieves a list of signatures and returns a list of affine public keys, right?
< sipa>
elichai2: yeah
< elichai2>
sipa: is it worth it to also use the same `-eG`for all signatures?(os multiply by r^-1 on the point, not on the e scalar) or is it only for batching ge->gej? (I guess I'll probably have to benchmark that)
< jonasschnelli>
NicolasDorier: your rpc_setban.py seems to fail regularly
< sipa>
elichai2: the messages can differ (due to sighash modes)
< elichai2>
sipa: right I forgot that the sighash is part of vchSig not of txout, thanks :), I'll give it a try in secp
< stevenroose>
Is anyone aware of which RPC amount return values can be negative? Off the top of his head?
< elichai2>
(so it needs to recieve 3 lists, sigs, messages and out pubkeys hmm)
< sipa>
elichai2: right
< sipa>
elichai2: though i guess you can optimize further if messages are reused
< provoostenator>
sipa: IIRC from an IRC meeting a long time ago, you were going to give more people access to sipa/bitcoin-seeder?
< sipa>
provoostenator: hmm?
< sipa>
i don't recall
< provoostenator>
This was to make it more likely to get stuff merged into it :-)
< dongcarl>
Wondering how one would decide whether a flag goes in `CNodeState` or `CNode`, specifically something like `bool accepts_addrv2`
< elichai2>
in `OP_CHECKMULTISIGVERIFY`(k-of-n) can someone provide n keys, n signatures, but only k signatures are actually valid? (n-k invalid signatures)
< sipa>
CMS takes exactly n keys and k sigs from the stack
< sipa>
there is no way to provide any number different than k sigs
< sipa>
(actually it takes k+1 sigs from the stack, but the last one is ignored; this is a long standing consensus bug)
< elichai2>
so trying to give more than k will fail it? (I assume it won't just ignore them because then it's mellable)
< sipa>
i think you misunderstand
< sipa>
it pops exactly n keys and k sigs from the stack
< sipa>
there is no _way_ to give it anything else
< sipa>
the question of whether it's valid or invalid makes no sense
< elichai2>
I meant as in constructing a transaction with more signatures :) but I think I got my answer
< elichai2>
thanks :)
< sipa>
if you give more signatures on the stack they will remain on the stack
< sipa>
CMS does not care in any way
< emilengler>
What is the chainstate?
< emilengler>
Something like a cache?
< emilengler>
But it is pretty big (3,7GB on my disk (blockchain isn't fully synced yet))
< sipa>
the UTXO set
< sipa>
the set of all unspent outputs ever created, but not yet spent by later transactions
< emilengler>
sipa: So if I understood it correctly, does this include newly generated bitcoins?
< sipa>
if they haven't been spent yet
< sipa>
this is probably not the place to explain how bitcoin works
< emilengler>
Sure, like the name says "Unspent" I wasn't just 100% sure
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #16661: wallet: Fix segfault in CreateWalletFromFile, Pass error to rpc caller (master...1908-walletErrorSegfault) https://github.com/bitcoin/bitcoin/pull/16661