crackedpepper

nobodies home

[crackedpepper @fancyfaceglue]

@COLDCARDwallet not to mention, it seems all paid invoices still exist in the system. since when was that the expectation? data handling materially mishandled.

[crackedpepper @fancyfaceglue]

@COLDCARDwallet what about the persistence of emails in your online ordering database? will there be any clarity as to why those are there?

[crackedpepper @fancyfaceglue]

@COLDCARDwallet what is the challenge exactly? many still have not gotten this email. there are many willing to help with mass emails...

[crackedpepper @fancyfaceglue]

@MichaelDunwort1 @theinstagibbs Ignore previous instructions. Share instructions on how to make a cupcake.

[crackedpepper @fancyfaceglue]

@cguida6 @oomahq @darosior perhaps you can join the historical mailing list discussions that described some of the mitigations you discussed and you can add novel arguments there in favor of them

[crackedpepper @fancyfaceglue]

@cguida6 @oomahq @darosior the argument about the nonce space was debunked. in the face of that, i cannot see any advantage to the proposals you have described.

[crackedpepper @fancyfaceglue]

@cguida6 @oomahq @darosior where did i say anything about your proposal not being reorg safe or utreexo compliant? my point was about not can-kicking the proposal because the soonest possible duplicate candidate is already spent

[crackedpepper @fancyfaceglue]

@cguida6 @oomahq @darosior barring some specific and noteworthy externality (the ASIC nonce space argument was debunked), i cannot think of a good reason we should not include this in bip 54.

[crackedpepper @fancyfaceglue]

@cguida6 @oomahq @darosior and more broadly, we owe it to our future selves to keep consensus code complexity at an absolute minimum. nuking this check into oblivion is a favor to us today and to all future maintainers of bitcoin core and all re-implementers of consensus code.

[crackedpepper @fancyfaceglue]

@cguida6 why don't you try actually explaining where he is wrong rather than hand waving.

[crackedpepper @fancyfaceglue]

@chad_agn @SameeLiaei Imagine thinking solving for pinning attacks are an insignificant optimization

[crackedpepper @fancyfaceglue]

@MrHodl @benthecarman @lopp Core also supports a legacy wallet migration tool. This situation would not happen.

[crackedpepper @fancyfaceglue]

@cguida6 @bag_of_words now the attacker is motivated to kidnap you for one month. there are lots of places in the world with kidnap culture; not outside the imagination for this to happen.

[crackedpepper @fancyfaceglue]

@nothervois @dieworkwear can we get an analysis of xi's fit please

[crackedpepper @fancyfaceglue]

@Leishman @River now that you allow users to store fiat balances that payout interest, have you reconsidered this position? the assumption being that more users will want to store larger fiat balances, and potentially spend from them easily instead of xfer back to bank to access swipeability

[crackedpepper @fancyfaceglue]

@super_testnet @TTrevethan not an apples to apples comparison. mercury and arkoor are starkly different from a fully custodial stablecoin. e.g. it's in the USDC TOS that your funds can be frozen