Decay Constant

[thebeanogamer]

What do we do about the decay constant? It should be =<1, but you could technically want a bigger number (if you wanted the value of a challenge to increase as it is solved).

Is that too obscure of a use case? Should we just cap it at 1? If not, we should add a pre-event check because you almost certainly don't want to do that.

I like the idea of previewing the decay in shell, although we'd need to decide where the logic for that happens.

[thebeanogamer]

Conclusion is that we should limit it to 0 < constant < 1 in the DB and shell. Will raise a seperate issue on shell.

[0xAda]

This is possible to do as a DB constraint, however out database design in this area is quite questionable. The decay constant is stored in flag_metadata which is a JSON field, which was intended to mean its entirely frontend's responsibility to manage, however thats not how this has been used in practice. If we're going to do this as a database constraint, postgres will allow us to do it, I'm unsure if django or sqlite will, but I would question if this should be a slightly bigger refactor of pulling things out of flag_metadata