Hindi translation

.eslintrc.json

@@ -0,0 +1,18 @@
+{
+    "env": { "browser": true, "es2021": true, "jquery": true },
+    "ignorePatterns": ["tests/", "dist/", "node_modules/", "coverage/"],
+    "extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended"],
+    "overrides": [],
+    "parser": "@typescript-eslint/parser",
+    "parserOptions": { "ecmaVersion": "latest", "sourceType": "module" },
+    "plugins": ["@typescript-eslint"],
+    "rules": {
+        "@typescript-eslint/no-unused-vars": [
+            "warn",
+            { "argsIgnorePattern": "^_" }
+        ],
+        "no-empty": ["error", { "allowEmptyCatch": true }],
+        "no-constant-condition": "off",
+        "@typescript-eslint/no-empty-function": "off"
+    }
+}

.gitattributes

@@ -0,0 +1 @@
+*.toml merge=union

.github/pull_request_template.md

@@ -0,0 +1,36 @@
+## Abstract
+
+<!--- Add any useful and detailed information for other Labs developers and reviewers to consume, this will help get your PR merged faster, as we won't need to reverse-engineer the changes as much.
+--->
+
+---
+
+## Testing
+To test this PR, it's suggested to attempt these user flows, or variations of these:
+- Step 1
+- Step 2
+- Step 3
+
+If any errors are found, the PR works unexpectedly, or you have viable suggestions to improve the UX or functionality of the PR, let me know!
+
+---
+
+<!---
+Below is for LMP (Labs Micro Proposals), how your PR is rewarded PIVX: this'll help your PR be rewarded faster by the DAO!
+--->
+
+## What does this PR address?
+<!---
+Here, describe the problem (or lack of a feature) which this PR aims to address, in as simple terms/concepts as possible to the reader.
+--->
+
+## What features or improvements were added?
+<!---
+Here, describe the new improvement; what it does, and how it does it, in as simple terms/concepts as possible to the reader.
+--->
+
+## How does this benefit users?
+<!---
+Here, describe how the user will benefit from the change, if at all; it may not be noticable to the user (i.e: code cleanup), in that case you may simply state so.
+--->
+

.github/workflows/build.yaml

@@ -0,0 +1,68 @@
+name: Build and release container image
+
+on:
+  push:
+    branches:
+      - "master"
+    paths-ignore:
+      - "*.md"
+      - LICENSE
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository }}
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Install npm/nodejs
+        uses: actions/setup-node@v4
+      - name: Install packages
+        run: npm install
+      - name: Build 
+        run: npm run build
+
+      - name: Set up Docker Buildx
+        id: buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Login to Github Packages
+        uses: docker/login-action@v1
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@v3
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+
+      - name: Set tag date-SHA
+        id: tag
+        run: echo "tag=$(date +'%Y-%m-%d')-$(git rev-parse --short "$GITHUB_SHA")" >> $GITHUB_ENV
+
+      - name: Build image and push to GitHub Container Registry
+        uses: docker/build-push-action@v2
+        with:
+          context: .
+          file: docker/Dockerfile
+          platforms: linux/amd64
+          tags: |
+            ghcr.io/pivx-labs/mypivxwallet:latest
+            ghcr.io/pivx-labs/mypivxwallet:${{ env.tag }}
+            ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          build-args: release=1
+          push: true
+
+      - name: Image digest
+        run: echo ${{ steps.docker_build.outputs.digest }}

.github/workflows/lint.yaml

@@ -0,0 +1,44 @@
+name: Lint
+
+on:
+  # Trigger the workflow on push or pull request,
+  # but only for the main branch
+  push:
+    branches:
+      - master
+    paths-ignore:
+    - "*.md"
+    - LICENSE
+    - "*.yaml"
+  pull_request:
+    branches:
+      - master
+    paths-ignore:
+    - "*.md"
+    - LICENSE
+    - "*.yaml"
+
+
+jobs:
+  run-linters:
+    name: Run linters
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out Git repository
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+
+      - name: Install Node.js dependencies
+        run: npm ci
+
+      - name: Run ESlint
+        run: npm run lint
+
+      - name: Run prettier
+        run: npx prettier -l .
+
+      - name: Run tests
+        run: npm test

.gitignore

@@ -0,0 +1,7 @@
+dist/
+node_modules/
+locale/lang-tools/env
+__pycache__
+coverage/
+coverage.data
+chain_params.json

.prettierignore

@@ -0,0 +1,9 @@
+node_modules/
+index.template.html
+*.css
+*.yaml
+LICENSE
+*.md
+package-lock.json
+dist/
+coverage/

.prettierrc.json

@@ -0,0 +1,5 @@
+{
+    "trailingComma": "es5",
+    "tabWidth": 4,
+    "singleQuote": true
+}

LICENSE

@@ -2,7 +2,8 @@ MIT License
 
 Copyright (c) 2020 Luke Larsen
 Copyright (c) 2020 DogeCash
-Copyright (c) 2021 StakeCube
+Copyright (c) 2021 ZENZO Ecosystem
+Copyright (c) 2021 JSKitty
 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

README.md

@@ -1,42 +1,60 @@
-# StakeCube Web3
-## JS-based web 3.0 wallet for SCC
+<h2 align="center">
+  Send, Stake and Receive with PIVX's most universal wallet.
+</h2>
 
-### Installation
-To use this web wallet locally click the clone or download button, then chose download as a zip. Unzip the file. Once it is unzipped, open the index.html file in your favorite **_MODERN_** browser. In order to generate new address you must change the debug setting to false, This will generate secure keys by way of window.crypto. There are some cases where this may not work properly make sure you are using a modern browser and that window.crypto works with your browser. Otherwise the generation may not be secure.
-### USE
+<p align="center">
+  <a href="https://mypivxwallet.org/">Production</a> (Stable) | <a href="https://pivx-labs.github.io/MyPIVXWallet/">Bleeding-Edge</a> (Unstable)
+</p>
 
-#### Key Generation
-**_IF YOU ARE IN DEBUG MODE (top right it will say DEBUG) MAKE SURE TO DEACTIVATE DEBUG BEFORE GENERATING KEYS AS IT WILL GENERATE THE SAME KEY OVER AND OVER AND IT IS NOT SECURE._**
+---
 
-The current setup allows for users to generate one private key and one public key. This is not a HD Wallet (Hierarchical deterministic Wallet) and because of that you must remember to back up every private key you generate. There is no one master. Losing any of the private keys you generate could result in the loss of funds.
+<br>
 
-#### Transaction
-##### Simple Transactions
-**Warning** _in the current state do not use this if you have to have more then 1000 input transactions. In that case it would be better to import your wallet to a software wallet or wait for an update. A small transaction was recently sent using this so it does work, but be cautious as this is still in beta_
+<img align="left" src="https://pivx.org/build/images/content/img_governance.png" width="150">
 
-Simple transactions require you to have networking enabled (cycle the toggle if its not on) in order to connect to a explorer. This is required because simple transactions do all of the heavy lifting for you.
-To run a simple transaction go to the transaction tab, then click load transactions (make sure that you have imported or generated a wallet otherwise it won't work.). Then simple put in the wallet address you want to send the coins to and the amount, everything else will be calculated for you (for example, the change address and fees). You will then see the whole signed transaction displayed. You can check that this transaction is what you want by taking the signed transaction and putting in into a software wallet with the command decoderawtransaction. If you feel comfortable with it feel free to send it via explorer or by pressing the button on the site.
+## Be your own Bank
 
-##### Advanced Transaction
-*The current setup only allows one input transaction and two output transactions if you need more inputs use the simple transaction for now. This will be changed in future updates.*
+MPW is a completely [non-custodial](https://www.bitcoin.com/get-started/custodial-non-custodial-bitcoin-wallets/), client-side system, giving you absolute control over your funds, data, bandwidth and privacy... all of which are essential to easily-attainable **self-sovereignty**.
 
-Advanced transactions do not require network access you can create the whole transaction then send the signed transaction on any node/wallet/explorer it takes a little knowledge of how transactions work in bitcoin to understand how to use the create transaction page. I will briefly go over what needs to be done, if you are unsure I recommend doing more research and testing with small amounts in order to not lose funds. How this works is it takes the inputs from the previous transaction (the one that funded the wallet.) and it make a new transaction that funds other wallets instead. Here is how you do this. We are going to be using one of my transaction in order to understand how this works. You can follow along here: https://explorer.dogec.io/tx/f52fad9c89a5a71532632679dc6cef84e6f7be949925d9190d054457052a61ef Under the raw transactions section you to put the top Transaction ID (txid) where it says Trx Hash, In our example it would be "f52fad9c89a5a71532632679dc6cef84e6f7be949925d9190d054457052a61ef". The next step would be to figure out which part of the transaction funded your public key, this is put into the index field. you can find this based on the vout under the vin section. In this example it would be 1. For the script field you need to put in the hex scriptPubKey of that VOUT with the same value under the VOUT section in Raw Transaction. In our example that would be 76a9142a8248f72e7ca9250f837b6cec46aedd6cf1edb288ac . Now the easy part under outputs you need to put in the address you want to send coins to and a change address. The change address is used for any extra coins currently associated with the account that you don't want to go to fees in most cases this would be your public key. In our example I have 1 DOGEC in my public address I wish to send 0.99 DOGEC to my friend at the address of DQJ24v6oFsobif8MQ6JFuFk6vefGAUQ6f2 . Then I set the change address( which is just my public address) D91rzgEmTyUcPEMPBLLPHVoKjSzwUreeoy with the amount 0.009 (Any money in this transaction not allocated will be used as fees and lost!) which means that the fee for this transaction is 0.001 . Under WIF key you put you private key in WIF (Wallet Import Format)  which if you used the keypair generator it already is. You can see the end result of my transaction here https://explorer.dogec.io/tx/c445a56c5236a6665f88d3fda012e84778588b9a923f3e13d77927313070b14e
+<br>
 
-#### NETWORK DATA TAB
-This show users what the explorer see in association with the public key
+---
 
-#### SETTINGS TAB
-##### Explorer
-_Note for devs if you want this to connect to your explorer you must set the CORS header to all, otherwise local users won't be able to connect to your explorer_
+<br>
 
-This is where you can change the explorer this currently is only set up for explorer.dogec.io which is the main current explorer. It is best to currently not mess with this setting as it will be developed more in the future.
+<img align="left" src="https://pivx.org/build/images/content/img_pos.png" width="150">
 
-##### Toggles
-###### Debug Mode
-Debug mode sets some things mainly for testing do not use this if you are using this as a user. It will make wallet generation insecure and some other problems if you are meaning to use the site normally.
+## Universal and Portable
 
-###### Networking mode
-This turns on and off the networking functions of the script. If you truly want privacy and security run this on a offline computer but this should be reasonably secure. With this turned off the script doesn't have access to any networking parts meaning anything that connects to a explorer or outside server doesn't work.
+MPW is completely universal and portable, at both a user-experience level & protocol-level, MPW is interopable with much of the functionality within PIVX, while also being portable enough to run on almost **any device in the world**.
 
-#### BETA **_PROCEED WITH CAUTION, DO STORE LARGE AMOUNTS OF FUNDS_**
+<br>
 
+---
+
+<br>
+
+<img align="left" src="https://pivx.org/build/images/content/img_privacy.png" width="150">
+
+## Don't trust, Verify!
+
+MPW is completely free, open-source software ([FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software)), with absolute transparency in security, features, down to every letter of code.<br>
+Alongside total codebase availability, MPW allows you to totally bunker-down, with the ability to customize your experience in accordance to your [principles](https://en.wikipedia.org/wiki/Free_and_open-source_software#Four_essential_freedoms_of_Free_Software) & security desires.
+
+<br>
+
+---
+
+<br>
+
+<img align="left" src="https://pivx.org/build/images/content/img_slider_bars.png" width="150">
+
+## By the Community, for the Community
+
+MPW is built with love by [PIVX Labs](https://github.com/PIVX-Labs), a micro-DAO of [awesome people](https://github.com/PIVX-Labs/MyPIVXWallet/graphs/contributors) that build both FOSS and Proprietary software for the PIVX community to enjoy.
+
+The mission of PIVX Labs is to accelerate the adoption & growth of PIVX as a currency, using awesomeness. Join the [PIVX Labs Discord](https://discord.gg/v57eCP4MMx) to meet us!
+
+<br>
+
+---