Andrey Petrov

> Even if we can't get great perf it is probably worth it to have as an option What kind of perf goals are you looking for? I'm working on...

> Another thing is data volume needed to be synced. Right. IIRC that initial sync data is on the order of ~200mb? In the grand scheme of things, that's on...

> 3.1. as it was pointed out it is impractical to use discovery v5 for les peers, as it can take long time, which is obviously won't work for mobile....

> Which brings us to reserving LES server slots. If you're already running your own full nodes, you could whitelist all Status client node IDs on your cluster. I have...

@dshulyak > 1. how to discover vipnodes? and when they are discovered how to understand if the given vipnode requires a payment? Your understanding is correct. Quick distinction: Let's call...

> currently payment, that includes client identity, must be committed before initiating a connection. it is even bigger problem if mobile device is used. one way to solve it is...

> there is an additional risk in doing so. any client (status included) will be able to abuse this property, and create new identity every 10-30 minutes. Indeed but I...

@dshulyak Hey there, quick update: vipnode v2 is close to getting finalized. Bulk of the work is complete, just the payment mechanism is still missing. I have a binary pre-release...

+1 to @auryn-macmillan, feels best to avoids treating an existing incremental counter as a scarce resource. ENS for EIPs makes a lot of sense to me. Either implemented as ENS...

Worth noting that this doesn't need to be a shell-specific situation. For example, pasting the wrong multi-line buffer into IRC can be equally embarrassing.