--- Log opened Sat Apr 10 00:00:21 2021
00:16 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 265 seconds]
00:32 -!- fkinglag [~fkinglag@unaffiliated/fkinglag] has quit [Ping timeout: 260 seconds]
00:34 -!- smartineng [~Icedove@88.135.18.171] has joined #bitcoin-wizards
00:34 -!- smartineng [~Icedove@88.135.18.171] has quit [Excess Flood]
00:36 -!- smartineng [~Icedove@88.135.18.171] has joined #bitcoin-wizards
00:36 -!- smartineng [~Icedove@88.135.18.171] has quit [Excess Flood]
00:36 -!- smartineng [~Icedove@88.135.18.171] has joined #bitcoin-wizards
00:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-wizards
00:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
00:46 -!- fkinglag [~fkinglag@unaffiliated/fkinglag] has joined #bitcoin-wizards
01:12 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:13 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
01:13 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-wizards
01:14 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:15 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:16 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:29 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:30 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:31 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:32 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:36 -!- true-asset [~true-asse@178.239.168.171] has quit [Remote host closed the connection]
01:37 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:37 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:37 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:38 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:39 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:39 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:41 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:42 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
01:44 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
01:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-wizards
02:24 -!- smartineng [~Icedove@88.135.18.171] has quit [Ping timeout: 268 seconds]
02:49 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 265 seconds]
02:53 -!- spake [~spake@139.28.218.148] has joined #bitcoin-wizards
03:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
03:25 -!- jadi [~jadi@93.119.217.23] has quit [Ping timeout: 260 seconds]
03:34 -!- kabaum [~kabaum@host-217-213-87-160.mobileonline.telia.com] has joined #bitcoin-wizards
03:50 -!- kabaum [~kabaum@host-217-213-87-160.mobileonline.telia.com] has quit [Ping timeout: 265 seconds]
03:52 -!- TheoStorm [~TheoStorm@ptr-g0z44tueo4uds013342.18120a2.ip6.access.telenet.be] has joined #bitcoin-wizards
04:19 -!- fkinglag [~fkinglag@unaffiliated/fkinglag] has quit [Read error: Connection reset by peer]
04:19 -!- fkinglag [~fkinglag@unaffiliated/fkinglag] has joined #bitcoin-wizards
04:23 -!- jadi [~jadi@93.119.217.23] has joined #bitcoin-wizards
04:46 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-wizards
04:52 -!- spake [~spake@139.28.218.148] has quit [Remote host closed the connection]
05:19 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
05:39 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-wizards
05:45 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
06:20 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 240 seconds]
06:26 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-wizards
06:37 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection]
06:39 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has joined #bitcoin-wizards
06:58 -!- proofofkeags [~proofofke@97-118-239-55.hlrn.qwest.net] has joined #bitcoin-wizards
07:21 -!- jadi [~jadi@93.119.217.23] has quit [Remote host closed the connection]
07:22 -!- jadi [~jadi@93.119.217.23] has joined #bitcoin-wizards
07:26 -!- proofofkeags [~proofofke@97-118-239-55.hlrn.qwest.net] has quit [Ping timeout: 246 seconds]
07:31 -!- laptop_ [~laptop@ppp-3-130.leed-a-1.dynamic.dsl.as9105.com] has joined #bitcoin-wizards
07:33 -!- _whitelogger [~whitelogg@uruz.whitequark.org] has quit [Remote host closed the connection]
07:34 -!- slewis [~slewis@185.169.233.10] has joined #bitcoin-wizards
07:34 -!- _whitelogger [~whitelogg@uruz.whitequark.org] has joined #bitcoin-wizards
07:40 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has joined #bitcoin-wizards
07:50 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
07:51 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
08:16 -!- IGHOR [~quassel@176.121.4.135] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.]
08:24 -!- belcher_ is now known as belcher
08:34 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Remote host closed the connection]
08:45 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-wizards
08:52 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Quit: Bye!]
08:52 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined #bitcoin-wizards
09:04 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
09:05 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
09:17 -!- IGHOR [~quassel@176.121.4.135] has joined #bitcoin-wizards
09:20 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
09:20 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
09:55 -!- nick_fre_ [~nick_free@port-92-194-254-232.dynamic.as20676.net] has quit []
10:16 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
10:17 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
10:25 < copumpkin> can someone help me understand what the meaning of the input to CLTV means, vs. the nLockTime field? I see the conditions in the BIP, but am not really following why that relationship between the two exists. Trying to understand if it could be used to validate that some externally provided "timestamp" falls within a range
10:28 < copumpkin> the rules seem to force it to be effectively a constant, right?
10:50 < copumpkin> I guess that's not right, I misread a statement about the type to be about the value. But it's still comparing against a constant for the lifetime of the transaction, which doesn't give me the now()-like semantics I was hoping for
10:55 -!- Netsplit *.net <-> *.split quits: wxss, isis_, cdecker, treyzania, AaronvanW, nanotube, EmmyNoether, niftynei, qawap, avrdude
10:56 -!- Netsplit over, joins: AaronvanW, nanotube, cdecker, niftynei, wxss, EmmyNoether, treyzania, isis_, qawap, avrdude
10:57 -!- bitjedi [bitjedi@gateway/web/irccloud.com/x-gbhgoiafktgbdlnw] has quit [Ping timeout: 240 seconds]
10:59 -!- bitjedi [bitjedi@gateway/web/irccloud.com/x-bnmlxtdzuspshbah] has joined #bitcoin-wizards
11:18 < andytoshi> copumpkin: the input is the "target" locktime
11:21 -!- roconnor [~roconnor@host-45-78-241-236.dyn.295.ca] has joined #bitcoin-wizards
11:23 < copumpkin> "Thanks goes to Gregory Maxwell for suggesting that the argument be compared against the per-transaction nLockTime, rather than the current block height and time." <- I guess what I'm not following is why that's more desirable
11:24 < roconnor> It makes script evaluation self-contained and cachable.  I.e. whether a script fails or not is only a function of the transaction, and not any other context.
11:26 < copumpkin> fair enough. Are constructs that don't meet that generally considered non-starters?
11:26 < roconnor> Probably.  For example, Simplicity is designed to uphold this priniciple.
11:27 < roconnor> And with taproot annex, anything else other contexts you care about would be passed through there.
11:29 < roconnor> I don't know. I might be overstating this.
11:29 < andytoshi> no i think you're right, it'd be a non-starter if you needed external data to validate a transaction
11:29 < copumpkin> yeah, but it seems like that principle would also vastly limit any sort of actually flexible "smart contract" possibilities you might think up in the system
11:29 < copumpkin> smart as long as it's statically knowable, which is basically a very narrow family of contracts
11:29 < andytoshi> copumpkin: it would limit the possibilities to things that were well-defined before transcations were in blocks
11:30 < andytoshi> i'm not sure what you mean by "statically knowable"
11:30 < andytoshi> do you mean computable? ;)
11:30 < roconnor> Taking BIP-115 for example, I think we'd rather do it with an annex item that contains a height/blockhash (fragment) pair, and maybe no script operation at all.
11:31 < andytoshi> copumpkin: so, locktimes actually do look at external data (the current block height). but they do it outside of Script
11:31 < andytoshi> and this is considered ok/within the bitcoin ethos
11:31 < andytoshi> so you can do similar things with the taproot annex, as roconnor is hinting at
11:31 < copumpkin> well, the context was "what if I had an oracle that two parties trusted, that every day publishes a signed and timestamped blob of data asserting some fact that those two parties want to refer to in their contract. How can I refer to such blobs in script?" and I think I can verify the signatures, but I can't meaningfully link those assertions to the timestamp
11:31 < copumpkin> (assume the timestamp is in blockheight or something sensible)
11:32 < andytoshi> copumpkin: so, we actually would like to do this in liquid, and if you try to do it in the "obvious" way where the blockchain checks the timestamp you quickly run into really nasty problems
11:32 < andytoshi> regarding reorg safety and miner censorship incentives
11:32 < andytoshi> copumpkin: but we have an interesting solution to this
11:32 < copumpkin> ooo
11:32 < andytoshi> which is that somebody *cough*blockstream*cough* runs a server that'll sign any hash you give it alongside a current timestamp
11:32 < andytoshi> then in your transaction
11:33 < andytoshi> you get two signatures: one of the current txid+"current time", and another with your meaningful timestamped data
11:33 < andytoshi> and within the script, you check that the timestamps match
11:33 < andytoshi> so the timestamp oracle is (unknowingly) asserting "this transaction was created at this time"
11:33 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 240 seconds]
11:33 < andytoshi> and so then you have a transaction which is statically verifiable but whose validity is unaffected by reorgs/miner censorship/whatever
11:34 < copumpkin> andytoshi: does the somebody need to be predetermined or can it be specified on a per-transaction basis?
11:34 < andytoshi> if you then want the transaction to _expire_ somehow, then you need to do a LN-type system with backout transactions
11:34 < copumpkin> I guess it could be per-transaction if it's just a signature
11:34 < andytoshi> copumpkin: hmmmm, i suppose you could make it "signed by somebody whose pubkey is signed by the parties to the transaction" and get a dynamic system that way
11:35 < andytoshi> but in the scheme i was thinking of it'd be fixed in the scriptpubkey, i.e. fixed at setup time
11:35 < andytoshi> so it is "per transaction"
11:35 < copumpkin> that seems fine
11:35 < copumpkin> my issue is that baking the TTP into the system is a lot more controversial than baking it into the transaction :)
11:35 < andytoshi> ah yes :)
11:35 < andytoshi> we are definitely not proposing to bake any (other) TTP into liquid :)
11:35 < copumpkin> :D
11:36 < copumpkin> what is this scheme you're describing called?
11:36 < copumpkin> can I read more somewhere?
11:36 < andytoshi> and actually ideally the TTP is really unaware of what it is doing here, it's just signing "whatever 32 bytes you give me + current time"
11:36 < andytoshi> copumpkin: uh, it doesn't have a name, i think the first time i've talked abuot it outside of blockstream is right now
11:36 < copumpkin> hah okay
11:36 < andytoshi> but if you think of a catchy name i'm all ears :)
11:37 < andytoshi> and if you can find somebody willing to run this timestamp server that'd be pretty dope
11:37 < andytoshi> it would be nice if we could get somebody who'll be around forever to do it. like a central bank or something ;)
11:37 < roconnor> opentimestamps?
11:38 < andytoshi> ohhh lol i totally forgot that OTS does exactly this
11:38 < roconnor> Actually, I suppose opentimestamp somewhat needs a full node to operate to compare block headers to.
11:38 -!- jadi [~jadi@93.119.217.23] has quit [Ping timeout: 252 seconds]
11:39 < roconnor> otherwise backdating is trivial.
11:39 < andytoshi> roconnor: well it's trivial for the server to backdate
11:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-wizards
11:39 < andytoshi> this is a risk inherent to the scheme i've been thinking of
11:39 < roconnor> sure, that's why it such a server is trusted.
11:39 < roconnor> but opentimestamps itself is not trustworthy without a full node behind it.
11:40 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
11:40 < roconnor> something that you probably don't want to implement with script (yet).
11:40 < andytoshi> roconnor: OTS supports several pluggable timestamp schemes. one is blockheaders
11:40 < andytoshi> but another is just a trusted sig
11:40 < andytoshi> and i _think_ that trusted sig does exactly what we want it to
11:40 < roconnor> Oh.
11:40 < roconnor> That's probably true.
11:41 < andytoshi> normally when you use it you run `ots stamp` and then it gives you a trusted sig ... and the server meanwhile is accumulating a pile of them that it can commit in a transaction
11:41 < andytoshi> then later you run `ots upgrade` to download a proof from the server
11:41 < andytoshi> and the server will say "here, forget my sig, now you can have a merkle proof leading to a blockheader"
11:41 < andytoshi> i mean, you don't actually forget the sig, both of them remain in the OTS proof
11:42 < andytoshi> (I may be forgetting the exact commands here. kanzure may know off the top of his head. but that is the workflow)
11:45 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 240 seconds]
11:46 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
11:48 < copumpkin> andytoshi: so I'm just trying to think through your scheme. Imagine coinbase puts out a stream of signed and timestamped blobs every so often saying "the btcusd price on our exchange is X at time T". Now I make an output that says you can spend it if you provide an andytoshi signature and can provide a coinbase-signed blob saying the price is above $X in the month of July. We implement that by asking for both the coinbase-signed
11:48 < copumpkin>  blob and for an OTS-stamped signature of that blob and compare the OTS TS value and the coinbase TS value to see if they're in the same range. What stops you from holding onto the OTS stamp for a year and submitting it a year later?
11:49 < copumpkin> oh, both parties need to be involved in submitting to OTS?
11:50 < copumpkin> I guess OTS would be timestamping some nonce or hash preimage (depending on the rest of the contract presumably) to stop one party from doing that?
11:51 < andytoshi> copumpkin: the OTS timestamp covers the tx
11:51 < copumpkin> oh, okay
11:51 < andytoshi> so you can pre-create a tx, sure .... but then you have to hold onto the UTXOs forever etc
11:51 < andytoshi> also yeah you could strengthen it by having the OTS timestamp cover signatures from both parties, say
11:51 < andytoshi> this all depends on having OP_CAT and OP_CHECKSIGFROMSTACK and then the sky's the limit
11:52 < copumpkin> yeah, feels very checksigfromstack :)
11:52 < copumpkin> even the base assertion ignoring timestamps
11:52 < roconnor> andytoshi says OP_CAT is OP_CHECKSIGFROMSTACK.
11:52 < andytoshi> i think in the specific blockstream application i was working on recently, we decided to only have the OTS timestamp cover the tx inputs
11:52 < andytoshi> lol roconnor not quite, i don't _think_ i can abuse CAT to sign external data
11:53 < andytoshi> i can just use it to enforce tx data
11:53 < roconnor> oh oops right. *lol* I went too far.
11:53 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 240 seconds]
11:53 < copumpkin> in another example I was distinguishing between "semantically monotonic" external oracle events (like "Prince Philip has died") vs. others like "btcusd on coinbase is $30 at time T". The former seems doable with just checksigfromstack
11:54 < copumpkin> (though some might say $30 is also monotonic :P
11:54 < copumpkin> sorry, no pricetalk in -wizards :)
11:55 < andytoshi> :P
11:56 < copumpkin> so when can I do all this in bitcoin? :) :) :)
11:56 < roconnor> *lol* assasination markets.
11:57 < copumpkin> hey you said it, not me :P
11:57 < copumpkin> it just was top of mind
11:57 < roconnor> no price talk, but "life insurance" is okay. :P
11:58 < copumpkin> anyway, my point was just that some flavors of external oracle assertions once signed will be true forever so you don't really need any timestamp shenanigans around them, and those still seem potentially useful
11:58 < roconnor> Isn't "The bitcoin price was X value sometime in July" a forever true statement?
12:00 < copumpkin> it's more about the flavor of assertions someone wants to make about the underlying truth of it, I guess. If all you want to say is that bitcoin price has hit X on coinbase, then you don't need timestamp shenanigans there either. If you want your contract to specify when Philip dies, then you need timestamps there
12:00 < copumpkin> "If you want your contract to specify when Philip dies" <- man, I'm starting to sound really shady, aren't I
12:03 < copumpkin> anyway, I just want trusted sources of signed+timestamped statements to become commonplace, and then to start integrating them into fun stuff like this :)
12:04 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
12:10 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 240 seconds]
12:11 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
12:23 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 260 seconds]
12:34 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
12:38 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 246 seconds]
12:39 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
12:41 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Quit: Lost terminal]
12:44 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-wizards
12:44 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 240 seconds]
12:44 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
12:45 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection]
12:49 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-wizards
13:18 -!- slewis [~slewis@185.169.233.10] has quit [Remote host closed the connection]
13:24 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
13:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
13:40 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-wizards
13:55 < jeremyrubin> i have some code that helps with this somewhere
13:57 < jeremyrubin> you can make oracles where you don't just have a fixed key, but you have a publicly derivable PK per question you want to ask for signing
13:57 < jeremyrubin> This makes it easier to make semi-stateless oracles
14:23 -!- stian_ [~stian@cm-84.212.218.202.getinternet.no] has joined #bitcoin-wizards
14:24 -!- fkinglag [~fkinglag@unaffiliated/fkinglag] has quit [Read error: Connection reset by peer]
14:24 -!- fkinglag [~fkinglag@unaffiliated/fkinglag] has joined #bitcoin-wizards
14:29 -!- stian_ is now known as fuzz23
14:38 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
14:38 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
14:47 -!- fuzz23 [~stian@cm-84.212.218.202.getinternet.no] has quit [Ping timeout: 252 seconds]
14:53 -!- fuzz23 [~stian@cm-84.212.218.202.getinternet.no] has joined #bitcoin-wizards
15:05 -!- fuzz23 [~stian@cm-84.212.218.202.getinternet.no] has quit [Ping timeout: 240 seconds]
15:12 -!- TheoStorm [~TheoStorm@ptr-g0z44tueo4uds013342.18120a2.ip6.access.telenet.be] has quit [Quit: Leaving]
15:29 -!- lgedeon [~lgedeon@185.169.233.10] has joined #bitcoin-wizards
15:43 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
15:43 -!- IGHOR [~quassel@176.121.4.135] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.]
15:44 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
15:47 -!- IGHOR [~quassel@176.121.4.135] has joined #bitcoin-wizards
15:56 -!- IGHOR [~quassel@176.121.4.135] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.]
16:00 -!- IGHOR [~quassel@176.121.4.135] has joined #bitcoin-wizards
16:04 -!- IGHOR [~quassel@176.121.4.135] has quit [Client Quit]
16:09 -!- IGHOR [~quassel@176.121.4.135] has joined #bitcoin-wizards
16:14 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:15 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:19 < copumpkin> jeremyrubin: interesting, not following the stateless part, can you elaborate a bit? or if the code is up I'd be curious to take a look
16:30 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:30 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:30 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:31 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:34 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:35 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:37 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:37 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:39 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:40 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:41 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:41 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:42 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:43 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:43 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
16:43 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
16:48 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
16:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-wizards
16:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 258 seconds]
17:00 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 265 seconds]
17:00 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
17:00 < kanzure> andytoshi: opentimestamps doesn't give a signature just a partial set of hashes that it can use to find the rest of the commitment tree later once it has actually committed
17:11 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 240 seconds]
17:12 < jeremyrubin> you can look at related code in https://github.com/sapio-lang/sapio
17:13 < jeremyrubin> the ctv_emulator crate implements a stateless signing module for CTV oracles
17:14 < jeremyrubin> you can use the same sort of trick for a oracle by making a deriv path based on H(question) and concatenating that with another path for the answer.
17:14 < jeremyrubin> Well formed questions are things like "price of gold in bitcoin is >= X" and not "price of gold = X", and then you can do a BST
17:15 < jeremyrubin> You then just need to impl the oracle trait for it to work with the relevent sapio contracts https://github.com/sapio-lang/sapio/blob/master/sapio-contrib/src/contracts/derivatives/oracle.rs
17:16 < jeremyrubin> https://github.com/sapio-lang/sapio/tree/master/ctv_emulators
17:17 < jeremyrubin> The "statelessness" is that the oracle doesn't need to pre-register or pre-generate anything
17:17 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
17:18 < jeremyrubin> And at resolution time they can just blindly sign anything with either key A or key B (but only pick once)
17:21 < jeremyrubin> Discrete log contract oracles are a bit different
17:27 < copumpkin> thanks! will take a look
17:27 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 265 seconds]
17:28 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
17:35 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 240 seconds]
17:35 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
18:03 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 268 seconds]
18:14 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #bitcoin-wizards
18:18 -!- kenshi84 [~kenshi84@49.135.41.195] has joined #bitcoin-wizards
18:19 -!- kenshi84_ [~kenshi84@w0109049135047178.uqwimax.jp] has quit [Ping timeout: 260 seconds]
18:40 -!- roconnor [~roconnor@host-45-78-241-236.dyn.295.ca] has quit [Quit: Konversation terminated!]
19:20 -!- IGHOR [~quassel@176.121.4.135] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.]
19:24 -!- IGHOR [~quassel@176.121.4.135] has joined #bitcoin-wizards
19:36 -!- laptop_ [~laptop@ppp-3-130.leed-a-1.dynamic.dsl.as9105.com] has quit [Ping timeout: 252 seconds]
20:22 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #bitcoin-wizards
20:25 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
20:44 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-wizards
21:02 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection]
21:07 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-wizards
23:13 -!- wk057 [~wk@unaffiliated/wizkid057] has quit [Read error: Connection reset by peer]
23:19 -!- wk057 [~wk@unaffiliated/wizkid057] has joined #bitcoin-wizards
23:22 -!- jadi [~jadi@81.91.148.242] has joined #bitcoin-wizards
23:30 -!- jadi [~jadi@81.91.148.242] has quit [Read error: Connection reset by peer]
23:54 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
23:55 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-wizards
--- Log closed Sun Apr 11 00:00:22 2021