-
br-m<routingerror:metropolis.nexus> how does monero prevent amount of txns, in those time periods, with these amount of funds kinda attack
-
sech1Monero transactions don't expose the "amount of funds", it's private
-
sech1Sender, receiver wallets are also hidden
-
sech1Which outputs are spent - also hidden
-
sech1It's not Bitcoin
-
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
-
sech1the only thing not hidden cryptographically is sender's IP, but this is where Dandelion++ comes in
-
DataHoarder"also how does monero nodes agree on time" by median chain time
-
sech1Timestamps? Irrelevant
-
DataHoardernot relevant for txs, these only care for block heights
-
sech1Well, chainanal can track "time of first seen, first seen IP" meta data, but it's of little use
-
sech1and they do
-
DataHoarderyeah, not relevant for monero nodes, as it's someone else keeping track of time
-
sech1unless someone connects to their honeypot node and exposes their IP :)
-
br-m<ofrnxmr:xmr.mx> like me
-
br-m<routingerror:metropolis.nexus> DataHoarder: Median chain time?
-
br-m<routingerror:metropolis.nexus> DataHoarder: Who?
-
br-m<ofrnxmr:xmr.mx> chainanalysis, or me
-
DataHoarderwho what? whoever the attacker part is probably has a way to measure time in the world
-
br-m<ofrnxmr:xmr.mx> ^
-
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
-
DataHoarderthe median timestamp is the aggregation of the last N blocks, with top high/bottom low 10% removed, and median is done on these
-
br-m<routingerror:metropolis.nexus> Got it thanks