Oleg Andreev submitted by
on Apr 13 2017:
(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 bandwidth concerns (3-4Kb per output,
50x more signature checks), how would we deploy that feature on Bitcoin network
in the most compatible manner?
I'll try to present a sketch of the proposal. I apologize if this discussion already
happened somewhere, although I couldn't find anything on this subject, apart from Elements
sidechain proposal, of course.
At first glance we could create a new extblock and transaction format, add a protocol to
"convert" money into and from such extblock, and commit to that extblock from the
outer block's coinbase transaction. Unfortunately, this opens gates to a flood of
debates such as what should be the block size limit in such block, should we
take opportunity to fix over 9000 of pet-peeve issues with existing transactions
and blocks, should we adjust inflation schedule, insert additional PoW, what would
Satoshi say etc. Federated sidechain suffers from the same issues, plus adds
concerns regarding governance, although it would be more decoupled, which is useful.
I tried to look at a possibility to make the change as compatible as possible,
sticking confidential values right into the existing transaction structure and
see how that would look like. As a nice bonus, confidential transactions would have
to fit into the hard-coded 1 Mb limit, preserving the drama around it :-P
We start with a segwit-enabled script versioning and introduce 2 new script versions:
version A has an actual program concatenated with the commitment, while version B
has only the commitment and allows mimblewimble usage (no signatures, non-interactive
cut-through etc). Legacy cleartext amount can nicely act as "min value" to minimize
the range proof size, and range proofs themselves are provided separately in the
segregated witness payload.
Then, we soft fork additional rules:
- In non-coinbase tx, sum of commitments on inputs must balance with sum of commitments
on the outputs plus the cleartext mining fee in the witness.
- Range proof can be confidential, based on borromean ring signature.
- Range proof can be non-confidential, consisting of an amount and raw blinding factor.
- Tx witness can have an excess value (cf. MW) and cleartext amount for a miner's fee.
- In coinbase tx, total plaintext reward + commitments must balance with subsidy,
legacy fees and new fees in the witness.
- Extra fees in the witness must be signed with the excess value's key.
The confidential transactions use the same UTXO set, can be co-authored with plaintext inputs/outputs
using legacy software and maybe even improve scalability by compressing on-chain transactions
using mimblewimble cut-through.
The rules above could have been made more complicated with export/import logic to allow users
converting their coins to and from confidential ones, but that would require
more complex support from miners to respect and merge outputs representing "plaintext value bank",
mutate export transactions, which in turn requires introduction of a non-malleable TxID
that excludes miner-adjustable export/import outputs.
The rules above have a nice side effect that miners, being the minters of confidential coins,
can sell them at a premium, which creates an incentive for them to actually support
that feature and work on improving performance of rangeproof validation (e.g. in GPUs).
Would love to hear comments and criticism of that approach.
Oleg. original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014144.html
Oleg Andreev . Software designer with focus on user experience and security. New blog is here: oleganza.com. about @oleganza [email protected] reddit archive rss. November 23. How to launder bitcoins perfectly. People often talk about privacy problems with Bitcoin: all transactions are public and every move is watched by millions of eyes. Where’s a problem, there’s a solution. Lets first ... Bitcoin allows you to trade with anyone on the entire planet with near-zero costs. More businesses would bypass Banks and as a side effect, more businesses would be able to withhold their taxes from the state. Competition would force other businesses to drive their costs down the same way. Bitcoin will become a black hole that grows and attracts more and more people in it. Chain architect and entrepreneur Oleg Andreev has said that in spite of “FUD,” markets have accepted Bitcoin is “not going away.” In a series of tweets outlining the short-term prospects for the BTC chain, Andreev demonstrated recent price action was to an extent due to various industry actors’ decisions. “At this point (2016-2017) it’s pretty […] Bitcoin News. Bitcoin Not Going Away, Forks Are FUD Projects: Oleg Andreev. August 21, 2017 August 21, 2017 - by Bitcoin FYI. Chain architect and entrepreneur Oleg Andreev has said that in spite of “FUD,” markets have accepted Bitcoin is “not going away.” In a series of tweets outlining the short-term prospects for the BTC chain, Andreev demonstrated recent price action was to an ... Chain’s protocol architect has likened Bitcoin Cash and SegWit2x to “FUD” in a forecast on Bitcoin’s price. Bitcoin Not Going Away, Forks Are FUD Projects: Oleg Andreev
Oleg Andreev Videos; Playlists; Channels; Discussion; About; Home Trending History Get YouTube Premium ... News Live Fashion Spotlight 360° Video Browse channels Sign in to like videos, comment ... E779: Brian Armstrong Coinbase &Tim Draper: crypto matures, ICO v VC, fiat end, bitcoin resiliency - Duration: 53:12. This Week In Startups 15,092 views Бизнес - это, прежде всего, продажи! Пожалуй, это два важнейших фактора - навыки маркетинга и продаж, которые ... Skip navigation Sign in. Search Oleg Andreev Videos; Playlists; Channels; Discussion; About; Home Trending History Get YouTube Premium Get YouTube TV Best of YouTube Music ...