Sergi Delgado

A solution based on tokens and not reusing the same subscription may align with the subscription rotation idea we discussed a while ago @ZmnSCPxj, even though we still don't have...

Hey @bjarnemagnussen, I was thinking on picking this up where you left it. Would you mind creating a draft PR with the current version?

The only place in the `Responder` where the locator is needed is when the appointment is completed so the `locator_uuid_map` cap be properly updated in the db. Keeping locators in...

Welcome @cedric-audy, feel free to take it, no one is working on this atm.

Hi @ritikramuka, happy to see you're showing interest to contribute to teos. The only instances of `OrderedDict` in the codebase should be in the `LocatorCache` located in the `Watcher`. I...

> The main problem would be errors that prevent the real transaction getting delivered. i.e. if the attacker can give our watchers a transaction that double-spends it, but that double-spend...

> > I feel that, in order to avoid this kind of problems, the appointment should acknowledge wether the transaction is standard or not, in the same way it should...

Continue digging into this, we can rule out all the non-transitory errors before reaching the `Responder` by using `testmempoolaccept`. That means that all errors regarding the transaction breaking a consensus...

> > Relevant (once we can fee bump) > > Doesn't `mempool min fee not met` and `mempool full` belong here too ? They do, but they can also be...