use bulma css
group links

https://cyber.fund/system/Alloy

There are no single container for each backend component that we need to reach from frontend API, and maintaining list of container dependencies for every backend component in multiple places is too much of a hassle.

We've already got up.sh script, so let's make it handle dependencies and leave in docker-compose.yml only containers for cyber-ui itself.

Conventions needed for staging server setup:

• repos for all components are cloned into $HOME on staging
• component compose file is located in /devops/staging/docker-compose.yml

up.sh then pulls all repos and runs docker-compose.yml up for every component.

CI loop is too long for Web UI. Too much time is wasted waiting for new version to appear at staging.

In this CircleCI job - https://circleci.com/gh/cyberFund/cyber-ui/17#tests/containers/0 - fetching dependencies takes 30 seconds.

added 1173 packages in 28.084s

• cache npm dependencies during container build

It looks brilliant here

make ethereum block and transaction items
change pager to load more
show system it item
make api call for items type(blocks transaction address)

Token Page FAQ v1.0

https://docs.google.com/document/d/1ybiEyiaks15mQ1g1lnJcVeoBYwKgdtsRvrP2echTYic/edit?usp=sharing

Code and UX

• crowdsale => ico
• crowdsales => icos
• Crowdsale => ICO
• Crowdsales => ICOs

Reason: significantly more popular semantics according to Google Trends

use bulma table
change diagram => just line

Now we have two docker images for frontend and chaingear api. Need public stage server for testing configuration. Need script to build containers, and run container configuration on staging server.

As a potential repository contributor I need to find out the source that builds cui-browser. See also https://github.com/cyberFund/cyber-ui/commit/2ae7e74cb6f0989705ec69e4bf9cadc73086d06e why having different names for software repo and its image is inconvenient.

Until we have our frontend split into several containers, there is no need in convention like in cyber-markets that is used to split market components into pieces. "Foolish consistency is the hobgoblin of little minds".

https://www.python.org/dev/peps/pep-0008/#a-foolish-consistency-is-the-hobgoblin-of-little-minds

cyber.Search main page concept

https://drive.google.com/file/d/1_tSxHHBz5v3M1RQzxe8CzA_TDZjmIht8/view

As analyst I want to get all transactions for specific address (ETH). By @Snedashkovsky.

We've discussed that downloading CSV is way better than clicking through pages and gathering data through them. We may even just expose CSV export to API. The link for to download that CSV from API would still be useful in UI.

One of the most important objects has been forgotten 🥇
Should be on the main menu

To keep our frontend independent from backend(s), which are:

• search-api
• chaingear
• markets-api
  we need to make these endpoints configurable.

We've discussed with @Pechalka and @litvintech that we will not proxy requests to API from client through frontend container, because that means that requests from client application in browser will go to the frontend server first and then to backend. It creates unnecessary bottleneck and increases moving parts for API management (access control, throttling, etc.).

So, we agreed to configure endpoints in config.json file for web application, which will be generated from environment variables:

• CYBER_SEARCH_API
• CYBER_CHAINGEAR_API
• CYBER_MARKETS_API

@litvintech as a staging user, can not connect to our staging server, because he uses HTTPSEverywhere extension.

https://insight.bitpay.com/
make base html => tabs 2 tables
use search api for update

in current spring we can not search by address

Use bulma cards

As a user I want to know price change (or better % dynamics) in USD of 5 tokens from my portfolio for certain period (week). I want to see tokens, current price is not obligatory, but period is good. @SiarheiSadau

Tokens page is for price monitoring, comparing between tokens (selected actual ones).

• I don't understand what price is, how is it calculated
• I don't get where the price comes from (which markets)
• I don't understand why it is sorted like this

An order should be the following:

• Blockchains
• Tokens
• Exchanges
• ICOs
• Labels (should be renamed from Funds)
• Analytics
• Cybernode

make button back
use table from bulma
if transaction page show status as bulma tag

api should return supply and volume

show big chart
group links like cyber.fund
use bulma tables
do not show statistic yet
https://blockchain.info/

https://cyber.fund/system/Bitcoin

1 api
get data by transaction

api should return price and change in btc usd eth, supply and volume

Comments from @mguryeva about mobile design:

/tokens

• not mobile-optimized
• no sorting by column names (up and down)

/crowdsales

• no column sorting
• data column meaning is not clear - is it start of sale or end of sale?

/cybernode

• there is an urge to click API and get explanation
  • what's that?
  • how to use it?
  • or follow to appropriate GitHub

More comments from Marina - mobile functionality should match desktop:

• links to detail pages
• setup column ordering (capitalization first, then diagrams, then reverse, ...)

We need a quick status indicator that show that API URL are offline or misconfigured. This may grow up into separate Cybernode tab on UI interface, but right now anything on the main page would do.

As a wish, it would be nice to get this panel extendable, so that anybody could easily add more indicators or checks against backend API there. By modifying code and sending PR, or in other convenient way.

use this lib https://vx-demo.now.sh/axis
use rest market api

Ideally should install yarn automatically

@Pechalka asked to rebuild latest container on DockerHub on every commit. This means CircleCI config should be updated for the project.

2 api

• transaction by address with pagination
• csv list of transaction by adreess

in current sprint we do not integrate api for address

Several groups of work blockers were detected:

1. Web version design
2. Mobile version design
3. Chaingear data validation (affects of supply, cap calculations)
4. Trades, price calculation on backend.
5. Graphs (7d change)

This is th basic concept of main token monitor page:

Updates for first release:

1. The page consists of 2 sections: static header with coin basic info, market stats and detailed section with switchable tabs, including historical graph, orderbooks, market depth graphs, coin specifications.
2. Market tab shows combined graph of market depth for all exchanges. There will be a function of selecting of displayed exhchanges.
3. Market tab shows order book for 1 selecting exchange for certain trading pair.
4. Market tab shows trades for all selected exchanges.
5. Specs tab displays etailed coin data from chaingear.
6. Links tab displays helpful links, grouped by categories.

Further development:

1. Add USD, Cap and BTC price graphs with zoom functions to historical graph.
2. Add zoom in/zoom out funtcion for market depth graph.

Work blockers:

1. Invalid (?) orders (with > 1million USD price). Should be clarified.
2. Problems with step calculation for orderbook price values.
3. No valid data from chaingear (links, specs etc.)

• Check and update .gitignore
• Add .editorconfig
• Update LICENSE
• Setup project description
• Update README (+ setup, FAQ, wiki, dockerhub)
• Describe Semantic Versioning of cyber-markets
• Setup CHANGELOG
• Add Travis CI bage
• Add current version bage (and other bages)
• Describe Code Style
• Add CONTRIBUTING
• Add CONTRIBUTORS
• Add ISSUE_TEMPLATE
• Add PULL_REQUEST_TEMPLATE
• Setup donation addresses
• Organize labels
• Describe labels
• Describe GitFlow (branches and issues)
• Describe cyber•Search board on organization level (milestones flow)
• Add CMIP (cyber-markets improvement proposal)
• Describe CMIP (cyber-markets improvement proposal)

This is th basic concept of main token monitor page:

https://drive.google.com/file/d/1ImT4HTkLOQyH9BZTyLFVOGEqmFhyXAbD/view?usp=sharing

Updates for first release:

1. Two loadings are used for page: first - to get all pairs, second - to update prices.
2. The price of the token is calculated as the last value of 1H ticker (close price). Price updates every 3 seconds.
3. Price change value (24H) is calculated using open and close price of 24H ticker for tradeable currencies. For example: if the token can be bought for USD, the price change will be calculated for USD, for BTC - traded pairs price change is calculated for BTC and so on.
4. Volume is calculated as volume of trades per 1H for one pair in all included axchanges.
5. Small price graph for 7D price change will be implemented.
6. All coins are displayed in a single page.

Further development:

1. Sorting function (by volume, price, cap etc) will be implemented
2. Price will be displayed in several currencies (USD, BTC, ETH) with correct caltulation

Work blockers:

1. No correct token supply information. Do we need a chaingear info source, or it wil be calculated using cyber.Search resources.
2. Cross calculations of coin price. Needs a backend improvement.
3. Volume should be calculated using full trading data (all pairs with certain coin, exchanges)
4. Market cap should be calculated using correct token supply data. Type of supplyused is an open question (number of existing coins, number of available coins etc)

In #9 we've made a quick manual deploy of our staging server. Now that mars came down again we need to repeat the setup.

And then automate it.

3 api:
data fro block
transaction by block with pagination
csv list of transactions by block

hide procents
coming soon coinmarketcap
make api cal for search api
coming soon for profile block