mydoge-com/mydogemask

Doge wallet chrome extension

MyDogeMask

🚀 Quick start

• Use Node.js version 18
• Use Yarn installed by NPM only: npm install --global yarn
• Install packages with yarn install.
• Create a file named .env at the root of the project and add the following line to the .env file, replacing "YOUR_API_KEY" with your actual NowNodes API key:
  NEXT_PUBLIC_NOWNODES_API_KEY=YOUR_API_KEY
• Run yarn start to start the development server
• Open http://localhost:3000 to view the development build in your browser

Building the extension

• Run yarn build to build the app for production to the build folder.
  It correctly bundles React in production mode and optimizes the build for the best performance.

• Install Extensions Reloader Chrome extension to enable automatic extension reload after every build.

• Run yarn watch to build and reload the extension with every file change.

Integration

• See our integration example for instructions on how to use MyDogeMask to accept Dogecoin payments on your own website.

mydogemask's Issues

multilingual support

it seems that there is no multilingual support, why not?

requestTransaction return unexpected data on 0.1.2 release

I was testing my integration using a self build extension (version 0.1.0) an requestTransaction was returning as expected :

{ "txId": "b9fc04f226b194684fe24c786be89cae26abf8fcebbf90ff7049d5bc7fa003f0" }

I've just installed the chrome store release (version 0.1.2) and requestTransaction is now returning unexpected data :

request transaction result {connected: true, address: 'D8vU6PDQ8DacbqFenVFiqWFrmtez9Q9Aor'}

Use testnet for development

Can be possible use dogecoin testnet some way ? I'm working on mydogemask API integration in a project and have to do real transactions to can test my code is quite frustrating

Window dimensions are broken in latest chrome

Build problem on Debian 11

On debian yarn build fail because of sed syntax in the package.json build line.
Changing sed -i '' -e 's=/_next/=/next/=g' out/**.html to sed -i -e 's=/_next/=/next/=g' out/**.html fix the issue.
I did not a pull request because currently I can't test on other SO.

Error Failed to send transaction

After having upgraded to 2.0 from chrome store, for each transaction i get "Failed to send transaction" error message.
I've try to uninstall and reinstall extension several time but without results. Attached you can find the extension inspector screenshot

Chrome version 103.0.5060.134 (Build ufficiale) (arm64)

.

libdogecoin integration

Several issues preventing us from using libdogecoin via the JavaScript wrapper:

1. Primarily, unable to bundle the exported wasm file via rollupjs. I've attempted several work-arounds without luck.
2. Loading the wasm requires an async call to start the wasm runtime. This pattern doesn't fit in all the sync places we need to use the lib.
3. Specific interfaces for transaction building finalizeTransaction and getRawTransaction are tricky when handling edge-cases such as "sweep address" and "change amount less than minimum output amount".
4. BIP 39 support.

When importing wallet on another device in chrome extension the multiple wallets do not loadin

I added mydoge mask on a second device. the additional wallets that I created do not import and are apparently tied to the same seed phrase from the wallet I generated them on. This may be a big issue if someone loses their device and has to sign in again and has multiple wallets in use.