Not sure if this is the wrong place

But regarding the 10 block unlock time

I noticed fixedfloat does 2 blocks. If it is of any consequence, I may ask them if theyve ever lost any monero due to the low confirmations.

I dont remember how many changenow, kraken etc use, but kucoin is 12

10 block unlock time is enforced by consensus, it's the amount of time after receiving monero before you can spend it and there are no exceptions.

The other numbers you're seeing are simply third parties saying "after X confirmations, well mark the transaction as complete". It doesn't mean they can spend it after 2 blocks, it just means they consider the transaction complete.

This channel is intended for devs, so questions like this are best asked in channels like #monero:monero.social

Hey I've got a couple questions about Levin. Upon receiving a levin handshake request, does monerod always send back peer information in the payload?

Second: the Bender's nightmare signature must proceed both the bucket and the payload, correct?

> <@busyboredom:monero.social> 10 block unlock time is enforced by consensus, it's the amount of time after receiving monero before you can spend it and there are no exceptions.... (full message at libera.ems.host/_matrix/media/r0/do…45f2dc1b20c02f9f9cbf50e87218f0912f4)

s/My question was misunderstood, was more wondering thebimplications of lowering the unlock time in the protocol, as if a company like ff accepts 2 conf tx id wonder how necessary 10 is / would it be worth looking into - but ill cont. in #monero:monero.social/My question was misunderstood, was more wondering thebimplications of lowering the unlock time in the protocol, as if a company like ff accepts/ is able to trust 2 conf tx, id wonder how

necessary 10 is / would it be worth looking into changing - but ill cont. in #monero:monero.social /

w[m]: you are still mixing up two different things

.merge+ 8222

Added

@selsta So my PR (monero-project/monero #8211) has a merge conflict with PR #8186 (monero-project/monero #8186). Luckily, It can be trivially resolved. Should I put that merge commit in my PR or let Luigi handle it?

luigi1112 ^

rebase please

Then you can ping me to re-review.

mj-xmr[m] Okay I rebased! I put a comment in the PR how I did it so you can easily replicate and check it

I just did git rebase --master and then deleted the 3 files that conflicted (they were deleted anyways in my PR)

Is there a reason that boost::interprocess::ipcdetail::atomic_(read/write/inc/sec)32 is used instead of boost::atomic or std::atomic in abstract_tcp_server2, levin_protocol_handler_async, etc?