post-boole cleanup

[shane-moore]

after boole fork hits production, deprecate logic that's no longer needed, ideally the logic to deprecate would already be marked with a todo(post-boole) as to make it easier to find

[PoulavBhowmick03]

Can I take this up?

[shane-moore]

@PoulavBhowmick03, this is a cleanup task for a month or so from now after a network upgrade hits production. let's hold off for now

[PoulavBhowmick03]

@PoulavBhowmick03, this is a cleanup task for a month or so from now after a network upgrade hits production. let's hold off for now

Alright!

[diegomrsantos]

@shane-moore wdyt about creating just one issue to remove all legacy Alan code?

[shane-moore]

@diegomrsantos, nice, yah, let's start with that approach. and if we think later that we need to break it down into sub-tasks to distribute work, we can do that then. updating this ticket. In the meantime before the upgrade, if we notice logic in the codebase that we won't need after the fork, we could add a todo(post-boole) as to make it easier to find later. kind of similar to how lighthouse does. wdyt? @petarjuki7 @dknopik for thoughts as well