Hi, i'm a comp sci student and have been a part of the monero community for nearly a year now. I would like to volunteer with any GUI tasks.

My technical skills are entry level, having experience in C++, object oriented design, algorithm and data structures, and web development

Although i'm new to this, i'm eager to learn new things!

welcome

main gui people are likely asleep right now

all good

so i think this repeater thing will work. [W]allet connects to [RPC] node for refresh. [W] then begins to craft a TX, requires data for outputs [1-11]. Requests [1-11] from node [A]. [A] sends data to [W]. [A] sends request to node [B] for same outputs [1-11]. Node [B] sends data to [A] and requests same data from [C]. etc etc

an asshole in the chain doesn't know where he is in the chain

and if the AH doesn't perform the function, it doesn't help him know his place in the chain, and [W] still gets their data

if the AH owns >50% of nodes, and excludes their nodes from repeating, then ... (don't think that would do anything?)

the AH could flood their peerlist with the repeated tx. all those peers would repeat and send repeat waves through the network

nodes could mitigate this by dropping requests that are duplicates, because thats an attack

gah whats wrong with this.

i guess it'll put more bandwidth burden on the p2p network

but, only small chains of nodes at a time. no idea how many nodes would need to repeat for it to be considered good enough.

i assume it would use the same dandelion approach for random stem lengths

would a puff at the end be useful? no.... don't think so

someones gotta pour some statistics in this beaker

mebbe i'll learn latex so i can make a fancy PDF