Disable Weeks right chevron if we are mid month once we reach the end of the data.

Look at the Receive / Invest pages to see how it was done there

The default active page is the wallet page. Reloading the page does not check for the current page. A bit of logic checking the page path can set the active tab correctly on the sidebar.

No functional impact is needed, just a user visual change.

Branch from master to strip down for public demo

If/when we have the time to optimize, common card components for Wallets reside in

WalletCards.jsx

Custom Icons reside in

Wallets/icons

Need to add mobile version based on this design: https://app.zeplin.io/project/5e344439655f2da46f4b16ab/screen/5e5423640f4a1b773a935006

Wallet Details: Pagination for transactions list

Possible, Your Wallets, fetching the wallets depending on how many we have (more than 20?)

Transactions Page. There will be many!

Endpoint: http://api.etherscan.io/api?module=account&action=txlistinternal&address=0x61ace53098d226e77cd26ae26e2c377fb9cb7657#internaltx&startblock=0&endblock=9999999999999&sort=asc#internaltx

Appears the be same format/form except for the first tx. Maybe the factory function? That'll take a little review but it should be OK

The readme should contain clear, step by step instructions on how to run the application on various platforms. It should be written such that someone following the README instructions step by step will be successful in running the app without the need to ask for help, look for other documents, or click through links to get things working.

Also, descriptions on how to run and test should be on the README file not on comments or pull requests.

After adding a wallet, add a spinner to let the user know we're processing the wallet. Latency from the third party or a very large wallet could make the app appear to hang or stop responding.

Take a look at https://material-ui.com/components/grid/ and the Receive and Invest pages to learn more about how to make this dynamically scalable for different browsers / mobile

Invite a user, view existing users. Date user was invited is off on the day

"web3-utils": "^1.2.8" should be removed from client-admin package.json

Passportjs supports using our UNICEF accounts to login to applications through Office365. This is similar to logging in using Google in other applications.

http://www.passportjs.org/packages/passport-office365-oauth2/

To use this, we would need to have the team that manages our Sharepoint/Active Directory register the app and give us the clientID and clientSecret that SP/AD will create when the app is registered.

To register an app:

https://portal.azure.com/#home

Search: App Registrations

My account does not have access, if an admin can approve it we can add this to all of our apps, reducing the time spent on login screens/security across all apps

Adding a new wallet that already exists will overwrite the wallet data as if it were being added for the first time.

If wallet data is already tagged/published/archived then this will overwrite the historic work. Sometimes this may be desirable (unsure since we cannot delete/remove wallets yet). I suggest a warning when adding a wallet that already exists. Perhaps a choice between resetting the data, updating new transactions (in case the wallet is stale), and cancelling the op.

Account pages are currently functional components. There is no reason to re-render every section when the app state changes. This could happen even when the accounts section is not shown.

However, state is currently managed in each respective component class and this is a minor issue that will not affect development or performance for the time being.

Will need a business decision - What value to use and do we still want to pull the tx information?

Do we care about showing these on the transactions screen? I can automatically archive them.

I dun goofed on the indexes and every transaction ever pulled is forever saved. Adding the same wallet multiple times dupes the transactions.

Easy fix, funny problem

Possibly scrape on user login as well

Lol:

existing user list in settings, resend button needs wiring up

How do I Restful/Http standards? =)

Inviting a deactivated user should reactivate the existing user's profile. The app will create a new user. When that user is reinvited a new password is set but the app will reference the deactivated account.

The calculations and values are becoming complex enough that it probably makes sense to setup unit testing for the DB aggregates to help explain how numbers are calculated.

When wallet data is updating show the status/progress somewhere (topbar?)

Set a reasonable limit to how frequently the app will automatically trigger an update.

Give the user a manual way of refreshing/updating wallet data.

https://etherscan.io/address/0x61ace53098d226e77cd26ae26e2c377fb9cb7657#code

This data lives in the event log and will need to be parsed out.

https://web3js.readthedocs.io/en/v1.2.7/web3-eth-contract.html