selsta

[selsta @selsta541]

@sethforprivacy @GBKS @bitcoin_design he also designed monero-gui :)

[selsta @selsta541]

@janowitz @CameronRuggles @WatchFund @binaryFate I don't have (never had) access to any wallets.

[selsta @selsta541]

@binaryFate @janowitz @calciferciccio @fluffypony FWIW we have a history of adding backlinks to the people and companies involved in an audit, like for example

https://t.co/4Q9AUcmCrD

[selsta @selsta541]

@calciferciccio @janowitz @fluffypony @binaryFate because i'm not interested in potentially spending my day defending myself on twitter?

[selsta @selsta541]

@calciferciccio @janowitz @fluffypony @binaryFate because i don't want people to use this as evidence that there was some kind of "secret deal" when no such thing existed.

[selsta @selsta541]

@janowitz @calciferciccio @fluffypony @binaryFate we were only in contact with sarang. if diego was involved in the background that's possible, but out of my knowledge. regarding credits, i would have loved to credit him, that's why I mentioned him in the PR description but that's the blog post he sent so I assume he is ok with

[selsta @selsta541]

@calciferciccio @janowitz @fluffypony @binaryFate what I mean with that is that I saw the backlinks, but since Zano paid for the audit and Sarang / Cypher Stack found them I thought it was fair to keep them in. It wasn't some kind of requirement to get the blog post published

[selsta @selsta541]

@calciferciccio @fluffypony @janowitz @binaryFate i meant fluffy

[selsta @selsta541]

@fluffypony @calciferciccio @janowitz @binaryFate we wanted something prepared in case someone asks "they found issues in clsag, is monero broken?!!"

[selsta @selsta541]

@fluffypony @calciferciccio @janowitz @binaryFate you are in the channel where this was discussed, this wasn't some rushed blog post merge. but i don't know how active you use irc these days.

the reason it didn't get opened earlier is because it was part of a responsible disclosure process.

[selsta @selsta541]

@calciferciccio @fluffypony @janowitz @binaryFate he was the most qualified for it so we said yes. he asked for feedback and we were free to edit it as we want. diego had no involvement. i knew this would end up in drama but i prefer an accurate blog post on how these issues affect monero over some personal issues

[selsta @selsta541]

@calciferciccio @fluffypony @janowitz @binaryFate sarang disclosed issues in CLSAG security proofs and asked if we want to be included in the responsible disclosure. after half a day later we didn't have anything written and sarang offered to write a blog post for us. since he created clsag, and he worked monero's implementation

[selsta @selsta541]

@fluffypony @calciferciccio @janowitz @binaryFate i don't have repo write permission how am i responsible for what ends up on the website?

[selsta @selsta541]

@tannerdsilva @DontTraceMeBruh @hundehausen we have been looking into improving performance during heavy rpc load (together with large txpool) but that's not something we will have ready with the next release

[selsta @selsta541]

@tannerdsilva @DontTraceMeBruh @hundehausen does restarting temporarily improve the performance of the node?

[selsta @selsta541]

@tannerdsilva @DontTraceMeBruh @hundehausen can cake temporarily spin up a couple more nodes until tx volume slows down again?

[selsta @selsta541]

@tannerdsilva @DontTraceMeBruh @hundehausen just to confirm: are all cake nodes running v0.18.3.1?

[selsta @selsta541]

@cold_hanshan @crypto_0ptimist @CryptoTweetie With the second t in my example being this new t-address for exchanges.

[selsta @selsta541]

@cold_hanshan @crypto_0ptimist @CryptoTweetie They want a new t-address that can only receive funds from t-addresses. Basically you would have to send from z->t->t instead of directly z->t.