[bitcoin-dev] Predicate Tree in ZkVM: a variant of Taproot/G'root

2019-02-01 Thread Oleg Andreev via bitcoin-dev
Hi, We've been working for a thing called ZkVM [1] for the last few weeks. It is a "blockchain virtual machine" in the spirit of Bitcoin, with multi-asset transfers and zero-knowledge programmable constraints. As a part of its design, there is a "Predicate Tree" — a variant of Taproot by Greg

Re: [bitcoin-dev] Predicate Tree in ZkVM: a variant of Taproot/G'root

2019-02-01 Thread Oleg Andreev via bitcoin-dev
A follow-up comment: I've have sent this email right before Pieter's talk on miniscript at Stanford yesterday. I want to express my appreciation to the thinking about scripts/contracts that Pieter, Andy, Greg have been promoting for long time. These ideas influenced a lot the design decisions in

Re: [bitcoin-dev] Dealing with OP_IF and OP_NOTIF malleability

2015-11-06 Thread Oleg Andreev via bitcoin-dev
> One and zero should be defined as arrays of length one. Otherwise, it is > still possible to mutate the transaction by changing the length of the array. > > They should also be minimally encoded but that is covered by previous rules. These two lines contradict each other. Minimally-encoded "

Re: [bitcoin-dev] Dealing with OP_IF and OP_NOTIF malleability

2015-11-10 Thread Oleg Andreev via bitcoin-dev
OP_0 gives a zero length byte array because OP_0 == 0x00 which is equivalent to pushdata with zero length. OP_EQUAL compares byte strings as-is. So it will push "false" because empty string is not the same as a single-byte string with 0x00 byte in it. Value "false" in turn is encoded as empty s

[bitcoin-dev] Deploying CT in Bitcoin without extension blocks?

2017-04-12 Thread Oleg Andreev via bitcoin-dev
(This is a sketch, not a fully-formed proposal, just to kick off the discussion.) Confidential Transactions (by GMaxwell & Poelstra) require a new accounting model, new representation of numbers (EC points as Pedersen commitments) and range proofs per number. Setting aside performance and ban

Re: [bitcoin-dev] Răspuns: Personal opinion on the fee market from a worried local trader

2015-07-31 Thread Oleg Andreev via bitcoin-dev
> On 31 Jul 2015, at 11:56, Thomas Zander via bitcoin-dev > wrote: > > On Friday 31. July 2015 03.21.07 Jorge Timón via bitcoin-dev wrote: >> If I was a miner and you want me to include your transaction for free, >> you're asking me to give you money > > What? > > Ask yourself; why do miners

Re: [bitcoin-dev] Removing the Dust Limit

2021-08-08 Thread Oleg Andreev via bitcoin-dev
I agree with Jeremy. Dust limit works due to design accident: that outputs are not encrypted. But outputs are private business and the real issue is only the cost of utxo set storage born by every user. There are two ways to address this: 1) either make ppl pay for renting that storage (which cr

Re: [bitcoin-dev] Is there a tool like Ethereum EVM at present for Bitcoin script?

2021-08-26 Thread Oleg Andreev via bitcoin-dev
It is worth checking out Ivy lang Playground by Dan Robinson, but AFAIK, it's not actively maintained. It compiles contracts to Bitcoin Script: https://www.ivylang.org/bitcoin > On 24. Aug 2021, at 16:08, Andrew Poelstra via bitcoin-dev > wrote: > > > Simplicity does not compile to Bitcoin S