<Inge> "check block height against..." <- Thanks. I may do that, but first I wanted to be sure that there the timestamp from _get_last_block_header_ is the more recent timestamp from all the available monerod RPCs ?

> <@Inge:libera.chat> check block height against some other nodes?

* Thanks.

I may do that, but first I wanted to be sure that the timestamp from _get_last_block_header_ is the more recent timestamp from all the available monerod RPCs (?)

Doesn't the node already check against all other nodes via the p2p protocol? But it does so through the block height, not the timestamp

If you really wanted to check timestamps, I'd just grab the latest one from the top block and check that it's no more than 30mins-1h behind the current time

IIRC the max "jitter" is 2 hours.

Thanks for the informations.

I have noticed that the block height returned from get_last_block_header can be easily 4 or 5 blocks behind what status says in monerod.

I wonder what's the reason for this lag (?)

I'll check if the timestamp from the top block is better/more recent.

Does get_info also show this same lag ?

The one thing I can think of is that it might use a longer lived read txn that has a view of an older db state, but in theory it should also apply to status.

I'll check those RPCs and try to evaluate the lags which each.

s/which/for/

I didn't notice, but get_info has :

synchronized - boolean; States if the node is synchronized (true) or not (false).

synchronized nodes are for squares

Yesterday I asked in the monero room how I might send a transfer where the fee is deducted from the amount I want to send, i.e. make it so exactly some amount leaves the wallet. This is what I came up with using the monero-python library, wondering if it looks reasonable:... (full message at libera.ems.host/_matrix/media/r0/do…817a178308048bad05bd387565f937efcee)

I'm also curious under what conditions it could fail - I'm guessing that when I request the 2nd transfer there's a chance that the fee changes and I would have to recalculate everything

.merges

> <@lookaside:matrix.org> Yesterday I asked in the monero room how I might send a transfer where the fee is deducted from the amount I want to send, i.e. make it so exactly some amount leaves the wallet. This is what I came up with using the monero-python library, wondering if it looks reasonable:... (full message at libera.ems.host/_matrix/media/r0/do…390baa519fe711d724ebf511dc99ccb7073)

*

I'm going to presume you want to guarantee sending X monero post fees? If so you would want to add the transaction fee to the amount and not subtract it. That way sending X + T monero results in X monero being sent rather than sending X - T monero.

s/I'm going to presume you want to guarantee sending X monero post fees? If so you would want to add the transaction fee to the amount and not subtract it//

I'm going to presume you want to guarantee sending X monero post fees? If so you would want to add the transaction fee to the amount and not subtract it. That way sending X + T monero results in X monero being sent rather than sending X - T monero.

s/and/rather/, s/not/than/, s/subtract/subtracting/