Is it normal to fail the functional_rpc_test related to stopping the miner? I figured maybe CI maybe blocking monero mining, but sometimes it works, other times it doesn't.

Yes, unknown reason. Feel free to look at it, but it'll be unrelated to whatever you're changing.

thanks!

hey guys, I am trying to understand how to see how much XMR is sent to a subaddress

but it shows my balance as a whole

how do i see how much each XMR went to each subaddress

hi

type `balance detail` in the cli wallet. also wrong channel, use #monero

ok sorry

yea that works

it shows the first 6

i tired balance detail

i thouught i had to put blance and [x]

instead of detail

what that x was I dunno

again thanks for your help

<moneromooo> "Now I'm wondering whether this..." <- apologies, but what is "cold signing" ? What's the difference with signing ?

Would be very thankful for a link or a small explanation.

Signing a transaction on a computer that is permanently disconnected from the internet

You have a view-only wallet connected to the internet that scans the chain and creates the unsigned transaction, which you then export to the "cold wallet" on the airgapped computer and sign with the spend key. Once you've done that, you export the signed transaction back to the view-only wallet and submit it to the network

<merope> "You have a view-only wallet..." <- gotta pass outputs & key images first ;)

seraphis will make it as simple as you describe IIRC

cryptonote_connection_context has three atomic members: m_callback_request_count, m_new_stripe_notification, and m_idle_peer_notification, which I will call A, B, and C, respectively. Currently, copy assignment and copy construction for cryptonote_connection_context is not thread-safe. For example, when we assign a cryptonote_connection_context to another, ccc1 = ccc2, the value of ccc2.B may change between the assignment of ccc1.A

and ccc1.B. Is this mitigated outside of the class?

Or rather I should say that the three members are of type epee::copyable_atomic, which is std::atomic<uint32_t> but with copy assignment and copy construction defined