10:53:10 <br-m> <routingerror:metropolis.nexus> how does monero prevent amount of txns, in those time periods, with these amount of funds kinda attack
10:55:53 <sech1> Monero transactions don't expose the "amount of funds", it's private
10:56:21 <sech1> Sender, receiver wallets are also hidden
10:56:35 <sech1> Which outputs are spent - also hidden
10:56:38 <sech1> It's not Bitcoin
10:56:52 <br-m> <routingerror:metropolis.nexus> Timestamps are also private, also how does monero nodes agree on time > <sech1> Monero transactions don't expose the "amount of funds", it's private
10:56:53 <sech1> the only thing not hidden cryptographically is sender's IP, but this is where Dandelion++ comes in
10:57:25 <DataHoarder> "also how does monero nodes agree on time" by median chain time
10:57:26 <sech1> Timestamps? Irrelevant
10:57:36 <DataHoarder> not relevant for txs, these only care for block heights
10:58:06 <sech1> Well, chainanal can track "time of first seen, first seen IP" meta data, but it's of little use
10:58:08 <sech1> and they do
10:58:24 <DataHoarder> yeah, not relevant for monero nodes, as it's someone else keeping track of time
10:58:32 <sech1> unless someone connects to their honeypot node and exposes their IP :)
10:58:40 <br-m> <ofrnxmr:xmr.mx> like me
10:59:24 <br-m> <routingerror:metropolis.nexus> DataHoarder: Median chain time?
10:59:31 <br-m> <routingerror:metropolis.nexus> DataHoarder: Who?
10:59:47 <br-m> <ofrnxmr:xmr.mx> chainanalysis, or me
10:59:56 <DataHoarder> who what? whoever the attacker part is probably has a way to measure time in the world
11:00:10 <br-m> <ofrnxmr:xmr.mx> ^
11:00:46 <br-m> <ofrnxmr:xmr.mx> the time each tx is first seen is known by your node, and the time it is commited into a block is known by every node. this is.. real basic
11:01:16 <DataHoarder> the median timestamp is the aggregation of the last N blocks, with top high/bottom low 10% removed, and median is done on these
11:02:19 <br-m> <routingerror:metropolis.nexus> Got it thanks