Parse multiple orgs for payments

[Keyrxng]

Resolves #106

The numbers should be looking better now (still 5th tho how about it).

• Is there a need to parse user accounts for payments?

0x4007CE2083c7F3E18097aeB3A39bb8eC149a341d,13894.65
0x00868BB3BA2B36316c2fc42E4aFB6D4246b77E46,7226.1500000000015
0x0fC1b909ba9265A846b82CF4CE352fc3e7EeB2ED,7115.0999999999985
0xf76F1ACB66020f893c95371f740549F312DEA3f1,6976.55
0xAe5D1F192013db889b1e2115A370aB133f359765,5600.5

---

I've committed both the unspent and leader board data in this PR as it's needed for the leader board PR and the unspent I plan to use for a new feature request to either search for or automatically display a user's unspent permits when visiting the portal.

Turning the action into a cron job for the leader board data I left for another.

[Keyrxng]

new feature request to either search for or automatically display a user's unspent permits when visiting the portal.

This was discussed previously but maybe a cleaner alternative considering the amount of unclaimed permits there are is to write a script to have the permit signer (ubiquity) invalidate all of them and bundled them into one or two new permits?

[rndquu]

@Keyrxng This PR should be closed in favor of #112 because the latter also solves #106, right?

[Keyrxng]

Indeed it should be @rndquu I didn't want to jump the gun just in case