Assigned person

1) hub.vg works, tested by creation of the links
2.Tested Ultra.exchange on MacOS ecosystem - works good
3) Created instance for Tharanga
4) Set the library for oauth authorisation on localhost for further testing purposes.
5) HubCulture Tickets: if the user hadn't avatar, that broke the styles. Fixed.
6) Added links to our support and zeke to the new pop up on Ultra.exchange
7) Created specific route to login to the Ultra https://ultra.exchange/J8u3EqHne2srRWU6.html

Today's report:
1) Removed Bermudastandard убрать надпись бермудастандарт.
2) Updated the form on Bermudastandard + added customization to displaying errors
3) Updated redirect to the cabinet after login
4) make the button hidden
5) Created repo for Wordpress.

1) Updated login screen on Bermuda Standard
2) Oauth:
- Our SDK shown just one template for all the sites. Once Thranga chnaged it for hubculture.com, it updated on the rest of the sites. We've updated the library to the state when it can receive the site name which will be displaying as well as have separate template for the each site. This functionality added to our API
3) HubCulture
- Updated login screen to display Welcome to HubCulture + linked template which Tharanga created
- Updated the Zeke issues.
4) Bermudastandard
- linked default template (not the one which hubcul;ture uses)

Bermudastandard
- Сreated Purchase page for asset where all info is visible
- made it dynamic, so Available Quantity and You will pay in VEN is counting automatically
- In case there are entering amount of assests more then available, there will be notification
- The same regarding if the user has low amount of Ven then he should pay.
- Asset chart http://i.imgur.com/l6LTVBe.png

Bermudastandard
- made the link to purchase Asests hidden
- Anyway, finished the related code adn commented it for further usage.
- deployed live
HubCulture
- Optimized JS and CSS of assets to avoid duplication on other sites
- Fixed auth issues - it was casued by deployment of beta built on live. REMINDER:
before deploying the code, it should be built with help of the next command: npm run build:prod
HubID API
- Finished the API part of assets and deployed on live
- Working on documentation regarding the deployment processes and so on.

Today's report:
HubCulture
- Resolved the issue with Markets page when it is viewed as a guest.
- deployed to live
Bermuda
- Found the resolved the issue with messages sent from the 'Have a question?' form - http://i.imgur.com/Ftw66g7.png
- deployed live
Ultra
- resolved the issue with charts.
- deployed to live

HubCulture
- Resolved the issue with unsupported currency http://i.imgur.com/9gZpVOB.png
- deployed to live
Zeke training
- worked on optimization of Zeke Knowledga base. All the questions/amnswers were displaying on the one page. Added pagination http://i.imgur.com/CgLz9An.png
- Added feature to select how many answers will be displayed on the page - 5, 10, 15, 20, 25, 30, 50, All
- Updated filtering option so the filter is not dropping settings when you are changing amount of displaying questions
- deployed to live

Today's report:
Oauth auth
- Previously we have implemented the system of notifications when there were suspicious attempts to login to the account. The same implemented for OAUTH authorization.
- This will helps us to track the issue and found if the wrong password is the issue.
- Due to security reasons, only parts of the passwords will be stored in DB so we can find out are they using correct onces, e.g. if the pass is 1234567890, then in DB will be stored********90
- Working on documentation
HubCulture markets
- found the issue with uRSV and applied temporary fix.

Today report:
hubculture auth error API
- Added function to list failed login attempts to the API
- This list is available for admins only
- deployed to live
hubculture auth error
- Added a page to display such list to the hubculture.com admin dashboard
- There are displaying only those failed attempts which hasn't trapped to the 'possible hijack' list yet.
- Such list is available on the 'People' tab http://i.imgur.com/MrMa7ic.png
- There are listing: name, part of the used password, ip, user-agent, email, and time stamp of the failed attempt http://i.imgur.com/Tv86IHE.png
- Deployed to live
Deployment instructions:
Posted needed details to https://hubculture.com/hubs/373/projects/1642/wiki/

Auth Error
- optimized page with failed auth attempts
- Added pagination
- Added links to the pages http://i.imgur.com/Bm4sKuA.png http://i.imgur.com/BZKBPDh.png
- made it looking more compact http://i.imgur.com/we0XLgp.png
- Updated design for navigation http://i.imgur.com/GDobFRc.png
- Added timestamps http://i.imgur.com/fIVxF44.png
- Made user name clickable to see the info http://i.imgur.com/quYqJNW.png
- deployed live

HubCulture auth errors
- The list of unsuccessfull auth attempts is now grouped. If the user has 100 unsuccessfull login attempts there will be displayed just last one
- Near the user login you can find amount of unsuccessful attempts http://i.imgur.com/eRj9Sqr.png
- The time under email stands for the time since last unsuccessful attmept http://i.imgur.com/e72rQly.png
- Selection of the user provides detailed info regarding his/her unsuccessful attempts http://i.imgur.com/rwvfBqC.png
- Added pagination to speedup loading

HubCulture auth errors
- Update load speed of the failed authed tabs - hubculted now sends requests to DB and get whet it needs in just 1 request.
- Added 'time ago' feaature (date displaying format) and pagination
- deployed to live
- Tested the speed - works like a charm

1) We see actual data on Ven pairs on Ultra as they are equal to https://ven.vc/rates. In the asme turn, the data goes there from our DB where they are updating based on this sites - http://i.imgur.com/Ns1gm6i.png
2) You can not auth on Ultra without URL craeted on your request. Here is output of our attempt to authorise http://i.imgur.com/swjfE0K.png
What is working at the moment:
- Ven rates
- displaying and purchase of UltraAssets.
- pages templates.
3) We've rechecked TopUp Ven. It works correctly.

Today's report:
HubculturePayments
- performed test in testing environment for all payment methods - passed
- used bulk data on payments - passed
- Found the source of your issue (payment method disabled) - it is related to Kalixa part. As we do not have accesses to their logs, we can not find exact details. To resolve it we should contact Kalixa directly to find more details.