add fallback pools with individual user identities

[GitGab19]

Alternative to #119

Closes #45

[pavlenex]

Good direction! Is there a reason why username needs to be asked on 3 places?

Also should we add a vailidation that it needs to be a bitcoin address if text says it's "usually" a bitcoin address?

[GitGab19]

Is there a reason why username needs to be asked on 3 places?

I made it work in that way to have guarantees about users properly setting the usernames they want for each pool they want to configure as fallback.

Also should we add a vailidation that it needs to be a bitcoin address if text says it's "usually" a bitcoin address?

Validation is already in place:

[pavlenex]

I don't mean per pool, check the screenshot, besides username for each pool on this page we ask user 2 more times for the username.

It's also odd that something user needs to submit, such as username now gets below the fold. Can't we have username in a different step?

[pavlenex]

I would also consider having fallback pool as a separate step, optional, this step now is too convoluted imo, we need to think more on the design pattern here. Let me play around a bit to see if we can have better UX here.

[GitGab19]

Squashed @pavlenex commit, now the pool selection looks like this:

[lucasbalieiro]

the input is loosing focus on every char typed

Screen.Recording.2026-07-09.at.00.16.04.mov

[GitGab19]

@lucasbalieiro, I just tackled all your three points.

[lucasbalieiro]

ACK

the upstreams are being correctly ordered and applied in the config file: