Quote from: amnakhan2011 on Today at 05:30:28 PM

The fact that bitcoin prices have started to rise in the market is definitely good news for all users. The price of Bitcoin has been around the world at all times this year. But at the present time the price of Bitcoin has started to rise more. Bitcoin is a currency in the world that is a user-to-user transaction. So one of the easiest ways to transact. In a very short time, it is possible to do a lot more transactions at a lower cost. That is why global users prefer Bitcoin. That's why Bitcoin is so popular, so much speculation. Every day, various projects are planned around Bitcoin. I think the price of bitcoin will continue to rise in the coming days.

Questions about generic signmessage (BIP322)
July 11, 2020, 07:45:44 PM
Merited by dbshck (4), ETFbitcoin (2), o_e_l_e_o (2), pooya87 (1), Heisenberg_Hunter (1), Coolcryptovator (1)

Reply with quote #1
I have two questions regarding the generalization of message signing/verification that has until recently only been done with legacy addresses through the RPC commands signmessage/verifymessage.

1 - Why was it chosen to prepend the scriptPubKey (when not P2PKH) to the preimage? To me, this adds unnecessary complexity which will slow down the adoption of BIP 322 by bitcoin libraries.

2 - In https://bitcoinops.org/en/topics/generic-signmessage , it can be read "This means a signed message can be produced for any script or address that a wallet would be able to spend. Additionally, two or more wallets can cooperate to create a BIP322 signed message for multisig scripts.". Additionally, BIP322 states that in order to sign: (https://github.com/bitcoin/bips/blob/master/bip-0322.mediawiki#signing) "Derive the private key privkey for the scriptPubKey". I just don't know how this is possible, it should be impossible to derive a private key from a scriptPubKey of a multisig for example. For a multisig there are a set of private and public keys of the owners, can there be a single private key of the whole multisig that can sign anything without the other's approval? And even if yes, how can the public key of this derived master multisig private key match the public key hash which is a hash of the locking script?


PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
pooya87
Legendary
*

Activity: 2212
Merit: 3385

Remember tonight for it's the beginning of forever

View Profile Personal Message (Offline)

Ignore


Re: Questions about generic signmessage (BIP322)
July 12, 2020, 03:37:29 AM

Reply with quote #2
i find BIP322 generally bad because it is focusing too much on how it can use the bitcoin core code-base instead of coming up with an algorithm to sign messages in general. in fact i believe that is why it is using a field called "witness" in a message signature where it is not needed at all. it also has some flaws and doesn't address certain cases for example when the script contains locktime related OP codes.
this may be the reason why it was not adopted even though it is ~2 years old.

Quote from: tiagocs on July 11, 2020, 07:45:44 PM
"Derive the private key privkey for the scriptPubKey". I just don't know how this is possible, it should be impossible to derive a private key from a scriptPubKey of a multisig for example.

it is either talking about "fetching" the private key for that script from the wallet or it is referring to the "ephemeral elliptic curve key pair" usually referred to as "k" for the signing process.


░░░░░▄▄██████▄▄
░░▄████▀▀▀▀▀▀████▄
░███▀░░░░░░░░░░▀█▀█
███░░░▄██████▄▄░░░██
░░░░░█████████░░░░██▌
░░░░█████████████████
░░░░█████████████████
░░░░░████████████████
███▄░░▀██████▀░░░███
█▀█▄▄░░░░░░░░░░▄███
░░▀████▄▄▄▄▄▄████▀
░░░░░▀▀██████▀▀
   .ChipMixer.{ MIXING REINVENTED FOR YOUR PRIVACY #.ChipMixer.

░░░░░▄▄██████▄▄
░░▄████▀▀▀▀▀▀████▄
░███▀░░░░░░░░░░▀█▀█
███░░░▄██████▄▄░░░██
░░░░░█████████░░░░██▌
░░░░█████████████████
░░░░█████████████████
░░░░░████████████████
███▄░░▀██████▀░░░███
█▀█▄▄░░░░░░░░░░▄███
░░▀████▄▄▄▄▄▄████▀
░░░░░▀▀██████▀▀
gmaxwell
Moderator
Legendary
*
qt

Activity: 3262
Merit: 4694

View Profile Personal Message (Offline)

Ignore


Re: Questions about generic signmessage (BIP322)
July 12, 2020, 05:57:52 AM
Merited by ETFbitcoin (2), o_e_l_e_o (2), NotATether (1)

Reply with quote #3
Quote from: pooya87 on July 12, 2020, 03:37:29 AM
focusing too much on how it can use the bitcoin core code-base instead of coming up with an algorithm to sign messages in general.
I think you're mistaken.

If you want something that signs messages in general use GPG. It would be an extremely bad practice to come up with some novel cryptosystem just to sign messages when established audited and mature alternatives exists.

Bitcoin uses a novel cryptosystem for signing transactions called Bitcoin Script which allows all sorts of complex constraints on the signatures. It's why with Bitcoin you can do multisig-- but for GPG and whatnot, you can't really (technically it could be done, but would need complex MPC crypto which no one implements).

Sometimes you want to sign messages with bitcoin addresses, e.g. to have the operator of an address attest to something.

If you're going to do that and support all addresses, then you need to use Bitcoin script to do it. In doing so, you pick up some of the structure that goes around script-- some of which may not be as useful outside of the blockchain.

So I don't think anyone particularly wants to use the bitcoin core code base-- but rather they want a signmessage that works for all Bitcoin addresses.

Quote from: tiagocs on July 11, 2020, 07:45:44 PM
1 - Why was it chosen to prepend the scriptPubKey (when not P2PKH) to the preimage? To me, this adds unnecessary complexity which will slow down the adoption of BIP 322 by bitcoin libraries.
I'm not sure, but I could speculate:

Because that's how signing works in Bitcoin so it should make it simpler for existing code. Also signatures generally must commit to their public keys or weird vulnerabilities crop up where you think you're signing with one key, but you're really signing for a related key.

pooya87
Legendary
*

Activity: 2212
Merit: 3385

Remember tonight for it's the beginning of forever

View Profile Personal Message (Offline)

Ignore


Re: Questions about generic signmessage (BIP322)
July 12, 2020, 06:50:05 AM

Reply with quote #4
Quote from: gmaxwell on July 12, 2020, 05:57:52 AM
Bitcoin uses a novel cryptosystem for signing transactions called Bitcoin Script which allows all sorts of complex constraints on the signatures.
each implementation of bitcoin should have a way of producing and verifying ECDSA signatures and work with scripts to some extent (usually standard ones only) but they don't have to have the flags used in bitcoin core specially when it comes to message verification. for example none of these exist in SPV clients such as Electrum so their code has to significantly change if they wanted to implement this I.P.:
Quote from: https://github.com/bitcoin/bips/blob/master/bip-0322.mediawiki#verifying
Verifying
Verify a proof, given a standard flags value, a script sig, an optional witness, and a derived sighash as described above.
1. Verify Script with flags=consensus flags (currently P2SH, DERSIG, NULLDUMMY, CLTV, CSV, WITNESS), scriptSig=script sig, scriptPubKey=scriptPubKey, witness=witness, and sighash=sighash
3. Verify Script with flags=standard flags (above plus STRICTENC, MINIMALDATA, etc.), scriptSig=script sig, scriptPubKey=scriptPubKey, witness=witness, and sighash=sighash
also these flags are used during block verification and most of them are there for backward compatibility (eg. whether BIP-66 is enabled to use DERSIG or BIP-112 for OP_CSV), i don't see why they should be used in a message signature verification.

not to mention that certain things from bitcoin scripts can not even be imported into message verification. some are addressing malleability issues, some OP codes such as those involving locktimes cause a lot of problems as there is no transaction or block to use for verification, the "signature" that is popped from the stack in transaction during script evaluation has a sighash flag which makes no sense in a message since there is no txout/ins to sign based on that,...

Quote from: gmaxwell on July 12, 2020, 05:57:52 AM
So I don't think anyone particularly wants to use the bitcoin core code base-- but rather they want a signmessage that works for all Bitcoin addresses.
then the proposal could have been a lot simpler or even expand on BIP-137 instead.
for instance as i said above there is no reason to use "witness" in a message signature from a bitcoin address since we are not producing a transaction and backward compatibility of SegWit is not needed here.

take P2PKH and P2WPKH, both of them are the exact same thing there is a pubkey that is hashed using HASH160 and there is a signature that matches that pubkey. in a transaction it makes a difference when creating the hash digest for verification and where the "stack items" are placed, but it is the same when verifying a message.
same with P2SH and P2WSH.
Quick take:
The fact that bitcoin prices have started to rise in the market is definitely good news for all users. The price of Bitcoin has been around the world at all times this year. But at the present time the price of Bitcoin has started to rise more. Bitcoin is a currency in the world that is a user-to-user transaction. So one of the easiest ways to transact. In a very short time, it is possible to do a lot more transactions at a lower cost. That is why global users prefer Bitcoin. That's why Bitcoin is so popular, so much speculation. Every day, various projects are planned around Bitcoin. I think the price of bitcoin will continue to rise in the coming days.
Bitcoin has recaptured $23k and could be prepping to retest its recent all-time high of $23,800
The crypto fear and greed index has hovered around 90 since early November
Traders are bullish despite the pullback to the $22,300 level
Bitcoin could very well break $24k and aim for $25k
$20k is Bitcoin’s macro support level
The weekend is in full gear and Bitcoin has once again moved into bullish territory by recapturing the $23k price zone. At the time of writing, Bitcoin is trading at $23,500 which is a substantial bounce from yesterday’s low of $22,300.
https://igps.ru/dkr/G-7.html
https://igps.ru/dkr/G-7-bb.html
https://igps.ru/dkr/Glory-ba-be.html
https://igps.ru/dkr/Glory-ba-be1.html
https://igps.ru/dkr/Glory-ba-be2.html
https://igps.ru/jio/ba-v-be.html
https://igps.ru/jio/g-76-l.html

Crypto Fear and Greed Index Plateaus Above 90
The excitement surround Bitcoin can best be illustrated by the crypto and fear index continually maintaining a value above 90 since November 6th. At the latter date, Bitcoin was trading at around $13k and would go on to wow the crypto community by posting an all-time high of $23,800 on the 17th of December. This feat by Bitcoin was achieved exactly three years since its last all-time high of $20k.
http://www.johnshillidays.co.uk/rdf/uc-cc-es-cl01.html
http://www.johnshillidays.co.uk/rdf/uc-cc-es-cl02.html
http://www.johnshillidays.co.uk/rdf/uc-cc-es-cl03.html
http://www.johnshillidays.co.uk/rdf/uc-cc-es-cl04.html
http://dci-dsa.com/fgt/uc-cc-es-cl01.html
http://dci-dsa.com/fgt/uc-cc-es-cl02.html
http://dci-dsa.com/fgt/uc-cc-es-cl03.html
http://dci-dsa.com/fgt/uc-cc-es-cl04.html
https://igps.ru/xin/uc-cc-es-cl01.html
https://igps.ru/xin/uc-cc-es-cl02.html
https://igps.ru/xin/uc-cc-es-cl03.html
https://igps.ru/xin/uc-cc-es-cl04.html
https://et.water.ca.gov/ciz/uc-cc-es-cl01.html
https://et.water.ca.gov/ciz/uc-cc-es-cl02.html
https://et.water.ca.gov/ciz/uc-cc-es-cl03.html
https://et.water.ca.gov/ciz/uc-cc-es-cl04.html
http://www.wellspring.edu.lb/rok/uc-cc-es-cl01.html
http://www.wellspring.edu.lb/rok/uc-cc-es-cl02.html
http://www.wellspring.edu.lb/rok/uc-cc-es-cl03.html
http://www.wellspring.edu.lb/rok/uc-cc-es-cl04.html
http://www.johnshillidays.co.uk/rdf/j-v-p-drtta04.html
http://www.johnshillidays.co.uk/rdf/j-v-p-drtta03.html
http://www.johnshillidays.co.uk/rdf/j-v-p-drtta02.html
http://www.johnshillidays.co.uk/rdf/j-v-p-drtta01.html
http://dci-dsa.com/fgt/j-v-p-drtta04.html
http://dci-dsa.com/fgt/j-v-p-drtta03.html
http://dci-dsa.com/fgt/j-v-p-drtta02.html
http://dci-dsa.com/fgt/j-v-p-drtta01.html
https://igps.ru/xin/j-v-p-drtta04.html
https://igps.ru/xin/j-v-p-drtta03.html
https://igps.ru/xin/j-v-p-drtta02.html
https://igps.ru/xin/j-v-p-drtta01.html
https://et.water.ca.gov/ciz/j-v-p-drtta04.html
https://et.water.ca.gov/ciz/j-v-p-drtta03.html
https://et.water.ca.gov/ciz/j-v-p-drtta02.html
https://et.water.ca.gov/ciz/j-v-p-drtta01.html
http://www.wellspring.edu.lb/rok/j-v-p-drtta04.html
http://www.wellspring.edu.lb/rok/j-v-p-drtta03.html
http://www.wellspring.edu.lb/rok/j-v-p-drtta02.html
http://www.wellspring.edu.lb/rok/j-v-p-drtta01.html
https://www.cbre-ea.com/ecl/j-v-p-drtta04.html
https://www.cbre-ea.com/ecl/j-v-p-drtta03.html
https://www.cbre-ea.com/ecl/j-v-p-drtta02.html
https://www.cbre-ea.com/ecl/j-v-p-drtta01.html
https://www.cbre-ea.com/ecl/uc-cc-es-cl04.html
https://www.cbre-ea.com/ecl/uc-cc-es-cl03.html
https://www.cbre-ea.com/ecl/uc-cc-es-cl02.html
https://www.cbre-ea.com/ecl/uc-cc-es-cl01.html
https://igps.ru/dkr/G-7.html
https://igps.ru/dkr/G-7-bb.html
https://igps.ru/dkr/Glory-ba-be.html
https://igps.ru/dkr/Glory-ba-be1.html
https://igps.ru/dkr/Glory-ba-be2.html
https://et.water.ca.gov/wev/canelo-vs-smith-en-viv-0yt1.html
https://et.water.ca.gov/wev/canelo-vs-smith-en-viv-03.html
https://igps.ru/ogw/canelo-vs-smith-en-viv-03.html
https://igps.ru/ogw/canelo-vs-smith-en-viv-0yt1.html
https://igps.ru/ogw/canelo-vs-smith-0yt1.html
https://igps.ru/ogw/canelo-vs-smith-051.html
https://igps.ru/ogw/canelo-vs-smith-ftg.html
https://igps.ru/ogw/canelo-vs-smith-df5.html
https://igps.ru/ogw/canelo-vs-smith-601.html
https://igps.ru/ogw/Videos-canelo-vs-smith-6la.html
http://www.wellspring.edu.lb/rtx/Videos-C-v-S-tv-f1.html
http://www.wellspring.edu.lb/rtx/Videos-C-v-S-tv-ygtdr114.html
http://www.wellspring.edu.lb/rtx/Videos-C-v-S-tv-tr1.html
http://www.wellspring.edu.lb/rtx/Videos-C-v-S-tv-501.html
https://et.water.ca.gov/wev/Videos-C-v-S-tv-501.html
https://et.water.ca.gov/wev/Videos-C-v-S-tv-tr1.html
https://et.water.ca.gov/wev/Videos-C-v-S-tv-ygtdr114.html
https://et.water.ca.gov/wev/Videos-C-v-S-tv-f1.html
https://igps.ru/dkr/ba-v-b.html
https://igps.ru/dkr/ba-v-be76.html
https://igps.ru/dkr/g-ba-v-be1.html
https://igps.ru/dkr/glory-76.html
https://igps.ru/dkr/n-f1-glory-76.html
https://et.water.ca.gov/wev/ba-v-b.html
https://et.water.ca.gov/wev/ba-v-be76.html
https://et.water.ca.gov/wev/g-ba-v-be1.html
https://et.water.ca.gov/wev/glory-76.html
https://et.water.ca.gov/wev/n-f1-glory-76.html
http://www.wellspring.edu.lb/ton/ba-v-b.html
http://www.wellspring.edu.lb/ton/ba-v-be76.html
http://www.wellspring.edu.lb/ton/g-ba-v-be1.html
http://www.wellspring.edu.lb/ton/glory-76.html
http://www.wellspring.edu.lb/ton/n-f1-glory-76.html
https://et.water.ca.gov/wev/dirett-live-197.html
https://et.water.ca.gov/wev/dirett-live-a-as.html
https://et.water.ca.gov/wev/Indirett-live-a-as.html
https://et.water.ca.gov/wev/dirett-li-a-a5s.html
https://et.water.ca.gov/wev/dirett-Juventus-a5s.html
https://igps.ru/jio/ba-v-be.html
https://igps.ru/jio/g-76-l.html
https://igps.ru/jio/glory-76-l.html
https://igps.ru/jio/Kijk-GLORY-76-live.html
https://igps.ru/dkr/ba-v-be420.html
https://igps.ru/dkr/ufc-ba-v-be420.html
https://et.water.ca.gov/wev/f4-direct-live-tv-19-dec.html
https://et.water.ca.gov/wev/f1-direct-live-tv-19-dec.html
https://et.water.ca.gov/wev/f1f4-direct-live-tv-19-dec.html
https://et.water.ca.gov/wev/eC10-direct-live-tv-19-dec.html
https://et.water.ca.gov/wev/enO-direct-live-tv-19-dec.html
https://et.water.ca.gov/wev/en-direct-live-tv-19-dec.html
https://igps.ru/vne/dirett-live-197.html
https://igps.ru/vne/dirett-live-a-as.html
https://igps.ru/vne/Indirett-live-a-as.html
https://igps.ru/vne/dirett-li-a-a5s.html
https://igps.ru/vne/dirett-Juventus-a5s.html
https://www.cbre-ea.com/ecl/cl-Colo-Colo-v-Catlica-En-viv-Tv4.html
https://www.cbre-ea.com/ecl/cl-Colo-Colo-v-Catlica-En-viv-Tv3.html
https://www.cbre-ea.com/ecl/cl-Colo-Colo-v-Catlica-En-viv-Tv2.html
https://www.cbre-ea.com/ecl/cl-Colo-Colo-v-Catlica-En-viv-Tv1.html
https://et.water.ca.gov/wev/Kijk-GLORY-79.html
https://et.water.ca.gov/wev/Kijk-GLORY-78.html
https://et.water.ca.gov/wev/Kijk-GLORY-77.html
https://et.water.ca.gov/wev/Kijk-GLORY-76.html
https://igps.ru/vnc/Kijk-GLORY-79.html
https://igps.ru/vnc/Kijk-GLORY-78.html
https://igps.ru/vnc/Kijk-GLORY-77.html
https://igps.ru/vnc/Kijk-GLORY-76.html
http://www.wellspring.edu.lb/rtx/Kijk-GLORY-79.html
http://www.wellspring.edu.lb/rtx/Kijk-GLORY-78.html
http://www.wellspring.edu.lb/rtx/Kijk-GLORY-77.html
http://www.wellspring.edu.lb/rtx/Kijk-GLORY-76.html
http://www.wellspring.edu.lb/ton/vdo-Glory-76-L1.html
http://www.wellspring.edu.lb/ton/vdo-Glory-76-L2.html
http://www.wellspring.edu.lb/ton/vdo-Glory-76-L3.html
http://www.wellspring.edu.lb/ton/vdo-Glory-76-L4.html
http://www.wellspring.edu.lb/ton/vdo-Glory-76-L5.html
https://igps.ru/xin/vdo-Glory-76-L6.html
https://igps.ru/xin/vdo-Glory-76-L7.html
https://igps.ru/xin/vdo-Glory-76-L8.html
https://igps.ru/xin/vdo-Glory-76-L9.html
https://igps.ru/xin/vdo-Glory-76-Li0.html
https://igps.ru/xin/vdo-Glory-76-Li-Ki.html
https://igps.ru/xin/vo-Glory-76-c0.html
https://igps.ru/xin/vo-Glory-76-c1.html
https://igps.ru/xin/vo-Glory-76-c2.html
https://igps.ru/xin/vo-Glory-76-c3.html
https://igps.ru/xin/vo-Glory-76-c4.html
https://et.water.ca.gov/wev/video-w-v-i31.html
https://et.water.ca.gov/wev/video-w-v-i30.html
https://et.water.ca.gov/wev/video-w-v-i3.html
https://et.water.ca.gov/wev/video-w-v-i2.html
https://et.water.ca.gov/wev/video-w-v-i1.html
https://igps.ru/xin/Gl-76-ppv.html
https://igps.ru/xin/Gl-76-bro.html
http://www.wellspring.edu.lb/nar/Gl-76-ppv.html
http://www.wellspring.edu.lb/nar/Gl-76-bro.html
https://et.water.ca.gov/wev/video-w-v-i3dgfd5.html
https://et.water.ca.gov/wev/video-w-v-i3dgdxg.html
https://et.water.ca.gov/wev/video-w-v-i3.html
https://igps.ru/ogw/video-w-v-i3.html
https://igps.ru/ogw/video-w-v-i3dgdxg.html
https://igps.ru/ogw/video-w-v-i3dgfd5.html
https://igps.ru/dkr/Glory-76-Hari-vs-Benjamin.html

Below is a screenshot of the Crypto Fear and Greed index highlighting the manner in which it has hovered around 90 for close to two months now.

Bitcoin Regains $23k as Crypto Fear & Greed Index Plateaus Above 90 12

Bitcoin Traders Remain Optimistic
The crypto fear and greed index remaining high echos a similar observation by the team at Santiment in which traders continue being bullish despite Bitcoin being in uncharted territory. According to the team at Santiment, the discussions surrounding Bitcoin are high despite BTC suffering the aforementioned pullback below $23k.