link above updated with verification and size numbers

Goood Morning Vietnam! I think everyone here knows that most Monero exchange withdrawals and desposits are traceable (Breaking Monero poisoned outputs). How does it feel to go out and lie to people that they are private and then earn less than holding BTC on your bag?

> blames XMR for shit exchanges do

> promotes BTC

i assume you're simultaneously in #bitcoin saying that BTC is shit because of the gox hack

it's just a troll lol

dEBRUYNE: I think it's unwise to delay BP+ for Triptych. I think you are picturing Tripytch being faster to implement than it actually will be

BP+ is actually quite close, just need the audit. So theoretically <3 mo

Ecosystem can't handle forks in quick succession

It would be unwise to do a fork in say March or April, imo

sure I'm not saying to rush it

I'm just saying, for example, BP+ in June-ish 2020, Triptych in June-ish 2021

I'd personally like to see an upgrade at the end of the year with both Triptych and BP+

I think a full year would be sufficient to get Triptych ready

moneromooo sarang ^

I'm strongly against coding it myself, I'll just screw something up in the crypto. I could do python->C++ like BP though. Either way, it'd need someone who groks the crypto well first.

sgp_ June 2020?

lol oops

:)

2021, 2022

I don't have a good estimate of what it would take for folks to audit and deploy Triptych

My existing Triptych code handles proving and verifying already

There would be additional work on output selection that is nontrivial

as well as the usual upgrade-the-protocol stuff involved whenever consensus rules and transaction formats change

But sgp_ is correct that after an audit, nothing particular is stopping a deployment of BP+ if it's decided to do so

sarang: Multisig for Triptych is a nontrivial effort as well, correct?