1. TODO string in wallet balances and public keys:

2. CYBERD Tokens in ETH wallet

Includes a lot of stuff:

• ipfs link for every app
• kind of lib or convention for urls inside apps
• back button from left side of search bar

• pdf
• image
• video
• audio

redesign process of page loading
add loading status on navigation bar
do not block page when it is not fully loaded

Found best and useful case of app that we can check against operability of our browser for random app which interacts with web3 id provider: https://github.com/ensdomains/ens-app

This app:

1. Is actively developed by EF
2. Liteweight and serverless
3. Can be useful right now under .ens name

Manage opening dev tools in views (frames)

the bug appears when you get on the page link ".help/#/". When you click the back button you simply get on ".help/" page (which is not a previous state).

We need bright and useful case for third party app. Dragonzzzzzz

Create library of components like here https://ui.decentraland.org/

• from field
• to field
• amount
• automatic fee calculation (with ability to change manual)

User Story

Currently agent switch ethereum networks depending on apps. Sometimes it happens hundred times a day. Such experience is frustrating to agents.

Why Is this Needed?

Web3 must be more convenient than web2. Without automatic network detection it will never be.

Solution

1. Search for existing protocol that allow for developers to markup networks. If non existent => define specs
2. Implement detection, request routing and highlighting in signer.

Definition of Done

Agent don't think about about network switching. It happens like a magic.

new version of cyb can not be opened on mac (security blocks launch)

There must live a forward button from right side of search bar that will predict next link

Possible improvements:

• Graph explorer. Watch incoming and outcoming links.
• Stats monitor. Like steemdb.com
• Blocks
• Txs
• validator stats

Current Behavior

First thing I saw in Cyb was fucking long chunk of text that nobody will every read. It is not web3 is all about.

Expected Behavior

On first open of Cyb user have to feel like sparks shot out and cannons blared and the mountains crumbled and the seas roared.

Solution

I hope we will able to do something prettier, more clear and shorter than MEW did (like explaining the whole shit about interface and private keys and all that stuff)

Definition of Done

Users will remember how she first met Cyb.

She will forget her first computer, first kiss, first fuck, be she will always remember first time with Cyb

Configure custom webpack for cyb

User Story

As web3 user I want to click to cyb:// or dura:// link in any app such that Cyb browser can open it.

Solution

cyb:// and dura:// handler must be registered during installation of Cyb.

favorites button - asadovka/cyb-parity#56
navigation for queries - asadovka/cyb-parity#46
app bar - asadovka/cyb-parity#28

Current Behavior

Balance of active account is not updating

Reproduction

You need at least two ethereum account. Try to send from one to another.

• create separate repo with components like here https://github.com/decentraland/ui

Appstore gets data from Chaingear

There should be all apps, divided by groups (built-in and, all and users').

sources are here:

https://github.com/cybercongress/cyberdesign/tree/concept-cyb_20/cyb/apps/appstore/

Agent Story

As a user I want to interact with more than 1 ethereum networks such as ethereum foundation, kovan, poa, etc.

Why Is this Needed?

1. A lot of apps right now in testnets
2. Sidechains are the next big thing and we see thousands of them

In both cases agents will not be happy to setup a network every time she wants to interact with apps on different chains. Parallel use of networks is mandatory feature for web3

Solution

Make possible to add networks in cyb://settings.cyb

make code more readable

Behaviour:

currently ETH addresses in wallet.cyb are generated and then transform to uppercase.

Solution:

generate addresses as is

The purpose is to create universal look of tx confirmation:

1. split process on 2 parts: signing (can be offline) and broadcasting (can be delayed)

2. add message (purpose of tx) in window

3. display "fee" for all gas fields (fee should be calculated efficiently, but there will be an opportunity to enter custom values)

4. confirmation button to the right, reject - to the left.

There is a need of building custom web3 provider for ETH operation

by default there is a RR from Chaingear, but user can create his own profiles for RR.

sources:

https://github.com/cybercongress/cyberdesign/tree/concept-cyb_19/cyb/apps/Root%20Registry

• analyse mist wallet
• fork needed features

• rename app repos according to cyb whitepaper
• add readme in each repo for issue management

I see some inconvenience for users if they will use the same keystore with parity-shell. Main reason is security. Lets start a discussion on how that is better to be done