dshulyak

> I would make switching to gomobile a blocker for this taks. When we have gomobile, the implementation will be much nicer. can you clarify why it will be easier?

@adambabik i guess you have different implementation in mind. i assumed that we will have to use signals as a subscription channel. as i understand rpc returns ID when subscription...

> but the problem is that subscriptionID is unknown yet, it's returned by on(). subscriptioID needs to be known anyway. i think it is stored somewhere inside of the ethereum...

Also we should swtich infura urls to newer per project URLs (https://blog.infura.io/infura-dashboard-transition-update-c670945a922a) . they provide faster response and request that use them are prioritized during high network traffic. i tried...

that is certainly possible, however it makes our clients even more reliant on our own infra, which is probably not a good thing (especially for the chain). i would start...

hey @shazow . are you still around? I wanted to discuss a couple of concerns: 1. how to discover vipnodes? and when they are discovered how to understand if the...

@shazow thank you for clarifying design decisions, to repeat some points: 1. vipnode pools will act as a discovery entrypoint, and as long as there are enough capacity in the...

> Indeed. Another option is pools can offer a brief trial per nodeID (maybe something like 10-30 minutes, enough to sign up). there is an additional risk in doing so....

It looks like node-canary sends a history request for a specific chat, waits for response, and verifies that envelope that was sent last, as a part of response, was added...

> Or does it get no response if there is nothing to return? it gets response, but after that it waits for the last envelope to appear in filters, using...