Problem:

Need to simplify initial workflow for group managers. Managers may use addresses to assign scores. When bots wants to explode they just create an Upala ID, create delegate and explode.

Solutions:

• Deterministic Upala ID (generated deterministically from address)
• Let bots validate scores by address (and let managers store scores by address)

Also see bots-first go-to-market strategy

Validate by address

Pros.

Simple score assignment

Score assignment before Upala ID exists.

"Aggregating" scores from multiple address (could be useful on early stages)

Cons

A bit more complex logic.

Maybe problems with delegates and creating sponsored Upala IDs (creating an Upala ID for be a third party to an arbitrary owner address).

Deterministic Upala IDs

UIP-26. Deterministic Upala IDs + UpalaID for scores, delegates for control

Decision:

• Make Upala IDs explicitly non-deterministic