🛠️ [TASK] : MVE2 enabler: post temporary account info to backend

[mike-mcnulty]

Summary

post temporary account info to backend

Description

As a user, I need to post my account details directly to the backend after I submit them to chain, so that I can access the application without waiting for my transaction to be indexed

Use case:
#1139

GIVEN a valid role0 key in the header
WHEN post to backend
THEN record role0 key + staking key + timestamp, with label = temporary

Authorization: must be signed by a valid role0 key.

• Note - this role0 key will not exist anywhere else besides the application at this point. We are just now posting to backend, and the transaction has not yet been finalized on chain.
• Consider DDOS risks and mitigations. Could someone just generate a bunch of valid role0 keys from CLI and hammer the backend?

This temporary account information should be overwritten once a matching role registration has been indexed from chain. We should keep timestamps for when temp access recorded, initial chain registration recorded, and final chain registration recorded.

We need to consider what happens to records that do not get a matching on chain registration within X time frame. This could indicate a rollback, which we’d want to notify the user about. What other scenarios could lead to this situation? Should we consider any kind of “auto re-register” if we identify a rollback?