Spec

Using vue-polkadot just like metamask.

1. vue-polkadot/apps's functions are duplicate to polkadot/apps, just different implementation in some way, and we can do it better.
2. apps has wallet functions, this makes vue-polkadot has the potential to be a metamask in substrate ecologies
3. Chrome extensions are better than web pages...(you know, I input the link to my browser every time I'm trying to open the apps...)
4. A nice wallet will reach every chain which is built by substrate, once we develop Kota into chrome, things will change, and substrate will be stronger because of Kota

Nowadays to implement Parity Signer Android, we require [add via qr] https://polkadot.js.org/apps/#/accounts

After click on Seconds it appears slide down

• chain info
  • summary
  • recent blocks
  • recent events
• block details
  • single block detail
  • extrinsics details
  • events details
  • system events
  • logs
• node info
  • node info summary
  • connected peers

KodaDot or DotKoda 🤔

We would like to exactly know which version you are running, so that's why we are looking to have version stamps somewhere.

Right now we are using own API for Vue Instance
yarn info @vue-polkadot/vue-api

Inspiration from polkadot.js.org/apps

• storage
• constants
• raw storage

User can go to settings, upload their preferences.json file with previously saved settings and then will have preferences set.

Take it as key/value storage, sync-settings for KodaDot.

It could be latter extended like ipfs hash, submitted on-chain as storage string, whatever fits.

Price could be latter determined. Thanks to Jam to point me on this

"and then each extrinsic has weights, fees, deposits etc."

Verbose https://github.com/paritytech/substrate/blob/18f0be7c780568a046afab89404de72cd12b708d/frame/transaction-payment/src/lib.rs#L74

Easy way https://polkadot.js.org/api/start/api.tx.subs.html#payment-information
Also https://polkadot.js.org/api/substrate/rpc.html#payment

Looks like https://ipfs.io/ipfs/QmaK78kCLNcPg1bUSbkwvS5gd4WzM7HXxyQT6xpDkqv1UC/ is broken in every way.

Found vue+ipfs deployment, so let's inspire there and take key ideas and adapt in our project.

https://github.com/Ideea-inc/vipfs

Before we pass props to components, would be good to have formatted values.

So we can avoid using .toString() or parseInt() frequently.

Hence we want to keep up, it would be great to have support for Substrate 2.x
Check release log https://github.com/polkadot-js/common/releases

Looks like container is broken right now on mobile.
Best fix would to have fixed sidebar and scrolling content on the right.

• Staking overview
• Account actions
• Payouts
• Targets
• Waiting
• Validator stats - not sure in scope

Definition of Progressive Web App https://web.dev/progressive-web-apps/

The goal is to have application installable on Android phones.
Working offline on account and address book would be optional.

Create PR to the develop branch.

• service worker for offline.
• manifest.json - changed to site.webmanifest
• custom offline page
• wcag - fully accessible

Hit our favourite friends https://github.com/js-org/js.org

We are missing this at actions

change pass - wrong password
backup - wrong password
transfer - wrong password/insufficient funds

For now travis CI is looking for package json in root of the repository
It should have change directory to dashboard and then run yarn (see #15 )

Just had idea after Substrate Seminar that we could integrate into settings API nodes from Polkahub 🤔

We have a lot of components since m1. At m2 we created a lot of functional components which could break anytime soon.
Follow https://vuejs.org/v2/guide/unit-testing.html

We should have tests.

• What doesn't require Vue -> Move to TS
• use Mocha or Jest

Unit tests for these components

• accounts

• addressbook

• transfer

• explorer

• extrinsics

• settings

• shared - now consists of a lot of helper short-lived components, nice to have.

We are thinking that having a desktop app could be a cool thing.

Anyone want to jump in?

Match link to explorer by TokenSymbol from chainProperties

i.e. tokenSymbol = 'KSM' will have prefix https://polkascan.io/pre/kusama/transaction/

We found that original identicon made for Polkadot and Substrate eco is too noisy, this looks much nicer https://github.com/urbit/sigil-js
Also, we would like to keep original identicon

Used this for buefy/buefy#1768 (comment)

We are missing contribution guidelines.
Family repo got https://github.com/polkadot-js/apps#development

https://help.github.com/en/github/building-a-strong-community/setting-guidelines-for-repository-contributors

We would like to have a docker image with UI running, for easier infrastructure setup.

• Send PR against develop branch, beware, it breaks often, you might keep it up to date, till we merge it
• Include working Kusama network
• Working up-to-date image, prefer one we are using here
• Working with local node, inspiration
• Send screenshot with working local node & Kusama
• It should be open to the local network as we are testing it from the mobile on the same WiFi.

Looking forward to contributing from outside. 🙌

We are often looking at various packages updates

yarn info @polkadot/api time

We are also happy to receive webhooks from Netlify from deployments if they're successful tho, bc we are too lazy run build at local. Sometimes at yarn serve are no errors 😅

Format could be telegram bot :)

• transfer could have SignAndSubmit
• review transfer is not working
• tags on create account doesn't work
• filter is broke on accounts

Right now @vue-polkadot/[email protected] returns -1 on connected node

Would be nice to fetch chain properties upon connecting and store it to Vuex.

Also, there are new types like Centrifuge.

Then we can stop querying from balance component for chain properties like token Symbol, decimals and ss58format

Would be good to have SFC component which will generate a link for the particular network where the transaction happened.

Subscan
https://kusama.subscan.io/extrinsic/0xd02e7f94448d6968b18fcc97cbdf4a2e0f2d15d92e6c10583e363f1c8d9e7128
Polkascan
https://polkascan.io/pre/kusama/extrinsic/0xd02e7f94448d6968b18fcc97cbdf4a2e0f2d15d92e6c10583e363f1c8d9e7128

Map links based on prefix of network?

Just had idea to have a mass backup in some case of danger :)

I've been updating packages and found new cli-plugin-babel breaks builds.

New @vue/cli-plugin-babel@^4.2.3 breaks build.
Now using @vue/cli-plugin-babel@^3.12.1.

Feel free to open PR

Transfer module was updated recently so we should mirror new functionalities

• tip for block author
• Sign transaction without submission
  

• We are thinking to use https://buefy.org/#/ for UI components

During referenda, the wrong value is displayed. The current value must be multiplied by 10 ^(-12).

screen in attach. Right value there is 18215 KSM

Our state is

Address prefix

for default connected it's -1, should fetch api.registry.getChainProperties()

Also, to have compatible chains would be nice to include at least this
from recent upstream settings

Remote endpoints

we cover

Live networks

Kusama (Parity)
Kusama (Web3 Foundation)
Kulupu

Test networks

Westend
Edgeware Testnet
Flaming Fir

• rpc calls - @vikiival
• hash data
• sign message
• verify signature

Commented Identicon in

src/components/shared/Keypair:vue:5
src/components/shared/Keypair:vue:80
src/components/shared/Keypair:vue:85

Verbose problem https://stackoverflow.com/a/50932919

After adding through add node URL, it won't show in list

We've got formatBalance.ts which does some small amount of magic.

Inspiration could be found here https://github.com/polkadot-js/common/blob/master/packages/util/src/format/formatBalance.ts

Right now we are struggling to allocate time on this and rather make this as bounty.

• fix all the use cases in code right now which are using the denomination
• repair components which are not using the denomination or not using denomination at all

Would be nice to follow and cover cases like this

reported by @vikiival

Running local Kusama node.

kusama_node | 2020-03-30 09:23:21 Idle (50 peers), best: #1669886 (0x7bbe…1554), finalized #1669882 (0x0f16…f2fd), ⬇ 96.4kiB/s ⬆ 33.6kiB/s

You can notice from node logs best is 1669886 which is fine but finalized should be 1669882