--- Day changed Sun Jul 02 2017
00:18 < jonasschnelli> sipa, gmaxwell: thanks
00:20 < jonasschnelli> I'm reviewing a proposal where a DID pubkey is in an OP_RETURN as a recoverable signature that covers the 2nd output of the DID tx where that second output is a revocation puzzle.
00:20 < jonasschnelli> So.. you say it would be better to have a seperate pubkey and a non-recoverable signature?
00:20 < jonasschnelli> (maybe it's the wrong channel)
00:27 < sipa> i don't think you should ever put anything in an op_return...
00:27 < sipa> but i also don't know the goal of what you're trying to do
00:36 < jonasschnelli> sipa: I know that not everyone like the OP_RETURN approach for DID,... but I failed to see other way how to add a proof-of-spend DID backed by the Bitcoin blockchain.
00:36 < jonasschnelli> I guess what the WOT want's to achieve is revokable identity root keys in the Bitcoin blockchain
00:36 < jonasschnelli> (in train, connection is weak)
00:36 < sipa> yeah just don't use thr bitcoin blockchain for that...
00:37 < sipa> and if you need to, you're relying on the hope of censorshio resistant publishing ot offers
00:38 < sipa> at least don't do it in a recognizable way
00:40 < jonasschnelli> Ideally it's not recognisable,.. but that would somehow impossible for public known DID...
00:40 < jonasschnelli> sipa: or do you mean not recognizable during the time of confirming? To avoid miner censorship?
00:41 < sipa> jonasschnelli: yes, if you're going to abuse the blockchain for non-monetary purpose, you're giving every bitcoin user an incentive to censor you
00:41 < jonasschnelli> I see...
00:41 < sipa> since censorship resistance is the reason why you'd want to use the blockchain in the first place, it seems paramount that you do it in an unobservable way
00:42 < jonasschnelli> Yes. It should be P2WSH wrapped and only revealed after the +100 depth has been reached (or so)
00:43 < jonasschnelli> revealed = DID used in non Bitcoin blockchain aspects
00:44 < sipa> getting offtopic here
00:44 < jonasschnelli> yes. Sry
00:46 < sipa> but if you can 'reveal' something through a means that is not the Bitcoin blockchain, then why do you need the chain?
00:46 < sipa> the whole point is that it's a censorship free channel; if you have another censorship free channel, you clearly don't need it
00:50 < jonasschnelli> sipa: I mean if someone start using (public) the DID (wich may be hidden in P2WSH) before it gets mined...
00:57 < sipa> i have no idea what DID is or what 'using' it means,  but this should probably move to #bitcoin-wizards or so
00:57 < jonasschnelli> Yes     
04:08 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #secp256k1     
06:06 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
06:07 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1     
07:17 -!- echonaut [~echonaut@46.101.192.134] has quit [Remote host closed the connection]     
07:17 -!- echonaut [~echonaut@46.101.192.134] has joined #secp256k1     
12:36 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]     
13:04 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
13:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1     
15:39 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds]     
15:42 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1     
17:00 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds]     
17:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1     
20:38 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
20:38 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1     
20:43 -!- adiabat [~adiabat@45.63.20.152] has joined #secp256k1     
23:18 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
23:18 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1     
23:47 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #secp256k1