spike: Tracking the number of accounts a miner has setup

[giovaroma]

Problem

• we do not formally know the capacity of all the miners in the network
• How many logins users do have
  • We can only see that by observing "passively" the events in the network (e.g. errors)
• We currently cannot measure network capacity/efficiency
• We do not know the state of some the nodes this is to be further defined by Chris chatting with Bob.

Acceptance criteria

• We know of an approach that we can use to track how many accounts are set by a peer id
• This information can be used and tracked via API

Notes:

We had a report on the testnet that a miner is taking advantage of the testnet campaign but this cannot be validated. To further understand this we would need to be able to:

Tracking the number of accounts a miner has setup because out performance might just be that they added more accounts recently therefore they have more capacity

Slack conversation for full context here: https://masafinance.slack.com/archives/C028C3D5FD3/p1730827864336509

[theMultitude]

A loom and notebook detailing my findings.

[theMultitude]

Essentially I backed into this information by picking the unique authentication errors by peer_id to get a count of the unique usernames associated with each.

[mudler]

@theMultitude is there anything needed from this card left?

[restevens402]

Notes:

• make sure the uuid is readily available everywhere we send events
• Event service needs a new event LoginEvent with corresponding table
  • PeerId
  • service user id
  • timestamps that are useful
  • success/failure
  • error (optional)
  • service type (Twitter / Discord etc)
• Add to the Nodes event service to call the actual Event Service
• Add sending the event in the workflow for twitter