klaytn/klaytnwallet

NO LONGER MAINTAINED

Since the launch of Kaia Blockchain this repository has been parked in favour of the new open-source projects in Kaia's Github. Contributors have now moved there continuing with massive open-source contributions to our blockchain ecosystem. A big thank you to everyone who has contributed to this repository. For more information about Klaytn's chain merge with Finschia blockchain please refer to the launching of Kaia blockchain - kaia.io.

---

Klaytn Wallet Project

Klaytn Wallet Project explanation

table of contents

1. Getting started
2. npm package information
3. Directory Structure
4. Web browser support scope
5. Describe how to use the front api
6. Setting up the env file
7. License

1) Getting started

1. Open terminal
2. Clone the repo by running git clone https://github.com/klaytn/klaytnwallet.git
3. Run npm installto install node packages
4. Run npm run start:local
5. App should be running in https://localhost:15000

2) npm package information

dependencies

The wallet project is optimized for Caver-js version "0.8.3-2".
Caver-js needs confirmation before updating.

3) Directory Structure

Folder structure

pm2.config.js           // npm run dev (execution server code )
webpack.config.js       //webpack dev server config
webpack.prod.config.js  // webpack prod config
dist                    // file built with 'npm run build'
static                  // folder with static images and font.
public                  // index.html, favicon, manifest.json existence in folder

1. src
src - actions           // Folder where Redux action are defined
src - components        // Folder where React components are defined(Save as .scss file for components)
src - constants         // Define the .env file
src - enhancers         // Folder where key event are defined
src - klaytn            // klaytn related definition folder
src - reducers          // folder where Redux reducer are defined
src - styles            // stylesheet code file. _mixins.scss
src - utils             // utility file. (contract.js, misc.js, transaction.js, ui.js )
src (root)              // index.js, App.js, store.js(Redux store), reducer.js(Redux reducer) file existence

4) Web browser support scope

Supported browsers.

Chrome	Safari	Firefox	IE Edge*
Supported (Optimized)	Supported	Supported	Not supported

5) Describe how to use the front api

Actual service wallet site

1. Baobab testnet
  - https://baobab.wallet.klaytn.com/
  - Use your wallet with a test klay. The Faucet menu is available.

2. Main Network
  - https://wallet.klaytn.com
  - This site uses real klay. Take care when using your wallet. The Faucet menu is not available.

* Check out the site link below

• Baobab testnet url : https://baobab.wallet.klaytn.com/
• Main Network url : https://wallet.klaytn.com

Api Type

1. api using caver ( Everything except KLAY Faucet )
  - Because it uses caver, it can be used outside.

2. EN Backend api ( KLAY Faucet )
  - Since it is the backend area of ​​klaytn, it can not be used from the outside.

How to use the wallet API

The api with caver is a public API. You can also use the api from the outside.
You can use caver function by using api.
For more information on how to use caver, please visit 'https://docs.klaytn.com/'
You can see how wallet works and how to use caver in the following sites.

• klaytn docs url : https://docs.klaytn.com/
• klaytn docs wallet description url : https://docs.klaytn.com/toolkit/wallet
• klaytn docs caver-js url : https://docs.klaytn.com/sdk/caverjs

6) Setting up the env file

Default values ​​to include in the env file

This is needed when starting based on the project.
add 'API_HOST','KLAYTN_HOST','CRYPO_PASSWORD' in 'config/default.env'
Explanation
'API_HOST' : KLAY Faucet backend API
'KLAYTN_HOST' : klaytn API
ex) 'https://api.baobab.klaytn.net:8651'
'CRYPO_PASSWORD' : The key used to encrypt the private key.
ex) '12345A12345B12345C12345'

License

Wallet service is released under the MIT license.

MIT License

Copyright (c) 2018 Klaytn wallet Authors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Contributing

As an open source project, Klaytnwallet is always welcoming your contribution. Please read our CONTTIBUTING.md for a walk-through of the contribution process.

klaytnwallet's Issues

Validation error in send amount

input error list

1. +, - can be input

2. You can include multiple '.'

3. I can not send all the Klay account except the gas limit.

klaytnwallet need to fix the above three things.

Error when attempting to send quantity with more decimal than decimal of Token

An error occurred when trying to send a quantity in decimal greater than decimal.
If there is an error in the token transmission, a transmission error pop-up should be called.

How to reproduce the error

1. Log in to your account with your token.
2. The decimal number adds the token contract as a number 2.
3. Go to the KLAY & Tokens page.
4. Enter the quantity as 1.123 and send the token.
5. There are no actions on the screen.

Security enhancement required for a vulnerability: CVE-2022-32969

Background
vulnerability explanation: https://halborn.com/disclosures/demonic-vulnerability/
browser restore session feature: https://support.mozilla.org/en-US/kb/restore-previous-session#w_privacy-issues

Mitigation

• To speed up the garbage collector’s removal of the phrase from memory, clear or dereference values of variables which store Mnemonic Phrases in your code

• Avoid displaying the Mnemonic Phrase raw in the browser.

  • A way to do this is to display the Mnemonic in an HTML5 canvas, so that the browser does not load the whole Phrase in memory.
  • Another way is to obfuscate the Mnemonic Phrase as you display it. Each Mnemonic word could be displayed in a span HTML tag. In-between these spans there should be additional “fake” spans with “fake” random words. Each of the “fake” spans should have the following CSS properties: .fake{ position: absolute; left: 0px; top: 0px; z-index: -1; opacity: 0; } . This forces the browser to only display “genuine” Mnemonic words, while loading both the “genuine” and “fake” words into memory – thus obfuscating the Mnemonic Phrase.

• Prevent (and warn) users from directly copying/pasting the Mnemonic Phrase into the browser. The browser’s clipboard is also responsible for leaking data into memory. Therefore, it is important to warn the user not to fill the browser’s clipboard with the Mnemonic Phrase, and to prevent them from doing so using the following method:

  • Use the e.preventDefault() method on the onPaste event handler.
  • It is also important to warn the user to manually enter their Mnemonic Phrase word-by-word. Even by using the e.preventDefault() method, the user is still able to copy/paste their Mnemonic. The only difference when using the aforementioned method is that it will live in memory for a shorter period of time. It is better not to introduce it into memory at all.
  • During recovery of a wallet by entering the Mnemonic Phrase, it is suggested, instead of a text area, to provide to the users one password input for each mnemonic word.

Mainnet faucet

Is your request related to a problem? Please describe.
안녕하세요! Foreigners getting KLAY is a hastle. Multiple swaps & transfers from binance, just so we can unwrap KLAY assets from bridge. So... we usually just ask a Korean friend to solve this. WE also made a mainnet faucet for anyone to use. https://ooju.xyz/en/klay-faucet

Describe the solution you'd like
We'd love if the Klaytn team would support this. Klay is an awesome blockchain with a growing NFT scene. One of the best ways to increase international exposure might be from tools like this.

Describe alternatives you've considered
Give it a look and tell us what you think :)

Additional context
감사합니다.

Error when sending Klay to contract address

Does this error intended because I try sending Klay to a contract address using the caver-js module and it work.