Developers Forum for XinFin XDC Network

Cover image for BlocksScan Contributed towards XDCPay 2.0 and It's ready for Beta Testing.
BlocksScan
BlocksScan

Posted on

BlocksScan Contributed towards XDCPay 2.0 and It's ready for Beta Testing.

Hello,

Greetings from BlocksScan ! ! !

We are glad to inform you that BlocksScan is adding contributions towards XDC Network Ecosystem and we have successfully upgraded XDCPay 2.0 with the latest code of Metamask (before its license applied).

XDCPay browser extension wallet Beta version is now available for testing within the XDC Community.

Image description

Github Link: https://github.com/XinFinOrg/XDCPay/pull/11

Issues which is Fixed:

  • Fixed UI broken after submitting incorrect password on reveal seed phrase screen
  • Fixed verifies password on requesting seed phrase
  • Fixed timing-reliant network controller test
  • Fixed connection removal bug
  • Fix no-case-declarations issues
  • Fixed import/extensions issues
  • Fixed import/order issues
  • Fixed radix issues

Download Link: https://download.blocksscan.io/XDCPay2.0_Beta/

Now, you can download the XDCPay2.0_Beta browser extension for Brave Browser, Chrome, FireFox Browser and Opera.

Image description

Steps to Follow:

  • Unzip the downloaded file.
  • Open your chrome → Visit “Manage Extensions” setting(Find Puzzle icon, on the right side of the URL bar) → On the “Developer Mode”
  • Now click on the “Load Unpacked” option to import your XDCPay file, By clicking on Load Unpacked, the user needs to select the unzipped file from the folder.
  • Once done, Users will be able to see the XDCPay symbol on their URL bar.

Suggestion Form: https://forms.gle/eEcEtCJEeLNnBxA56

Please provide us with your feedback on the list of issues and your suggestion in the discussion box or update the same in the above suggestion form to implement the same before going live.

Also, we will look forward to your suggestion or guidance on our below Roadmap 2023.

BlocksScan, need your suggestion: https://www.xdc.dev/blocksscan/blocksscan-needs-your-suggestion-554k

Thank you and Wishing you a Happy New Year.

Discussion (20)

Collapse
coincow_art_a9fac6bf88081 profile image
CoinCow Art

Hi, Thanks for the great works.
Let me ask you a question.
Is there any way to check if a user I have created a web page and connected XDCPay to owns the NFT I have created, using javascript, php, etc.?

Collapse
s4njk4n profile image
s4njk4n

Can we backup/restore wallet address labels? (I know of many people using a lot of addresses in XDCpay). Anytime they change browser and/or computer it is challenging to relabel tens (and in some cases hundreds) of wallets.

The ability to backup and restore them would be amazing

Collapse
ivan_blocksscan profile image
Ivan_BlocksScan

Hello @s4njk4n

The team is exploring how we can add the accounts automatically with a seed phrase.

For now, If you are importing your old account with a seed phrase, all your accounts will be recovered. For this, you need to click the "Create Account" button, to recover your account related to that seed phrase.

In XDCPay 1.0, if you have imported some accounts with Private Key or with Keystore file, then make sure you are doing the same thing in XDCPay 2.0 so that it will restore the imported accounts.

You can download the stats log to know the Account Names(Address labels), To download the "stats log": Visit Settings -> Advanced setting -> "Download Stats Log".

Collapse
s4njk4n profile image
s4njk4n • Edited on

Thank Ivan. For the users I'm referring to, the wallet addresses themselves wont be a problem as they're all imported from Trezor so they can just reimport them all as normal whenever setting up a new instance of XDCpay. Its more the actual labels that are ascribed to each wallet address to describe its purpose. Its great to be able to download them in the Stats Log. I guess what I'm getting at is that when setting up a new instance of XDCpay it would be great to be able to just import all the Address labels instead of having to manually type them all every time a new instance of XDCpay is installed/setup. In a situation where one would have 50 or even 400 wallet addresses, this process becomes very cumbersome at present (and yes I do know several people who have and actively use this many wallet addresses so I'm not just theorising). How do we get this functionality added?

Collapse
xdcdomains profile image
XDC Web3 Domains

Can you consider integrating xdc domain so that users can send and receive using their .xdc.

We already have libraries for integration, looking forward to your review. Thanks

github.com/XDCWeb3Domains/xdcdomainjs

github.com/XDCWeb3Domains/restfulAPI

Collapse
blocksscan profile image
BlocksScan Author

Yes definitely, We would go for vote from community to get it integrated in XDCPay.

Collapse
mrblockchain22 profile image
Salomon Morales

Hello team,

I have submitted another suggestion. Currently XDCPay 2.0 is not able to interact with StorX (site: farmer.storx.io/staking) as it does not recognize the wallet being unlocked. I have removed the previous version of the wallet and I dont have MM installed on this browser. I have tried clearing cache and relaunching the Brave browser with no success. Thank you!

Collapse
ivan_blocksscan profile image
Ivan_BlocksScan

Hello @mrblockchain22

Refer these steps to connect StorX Farmer site: xdc.dev/ivan_blocksscan/steps-to-c...

Hope this will help you...

Collapse
mrblockchain22 profile image
Salomon Morales

@ivan_blocksscan I have been beta testing XDCPay across several layer 2 dapps and dapps that we currently manage. I noticed that XDCPay 2.0 does not work with Origin (origin.xdc.org/). Please see image attached. I have spoken with the person in charge of Origin and he mentioned that the new version of XDCPay does not work with Web3Modal.

Collapse
mrblockchain22 profile image
Salomon Morales

Thank you @ivan_blocksscan! This worked really well.

Collapse
xzavix profile image
XH

Hello,

Issue: I sent 1000 Test XDC
to the Test wallet 1, then
created another wallet
Test wallet 2 to sent 500
test XDC tokens. It never
arrived on the Test wallet 2.
I see only the gas transaction
taken from Test wallet 1 despite
transaction being conifrmed
as a success.

Idea: When you view the value
on Blockscan explorer, it would
be great if you can click the
the value number to show what
the value on the day of tx was.
Not sure if that's in the works

Collapse
ivan_blocksscan profile image
Ivan_BlocksScan

I have tried your scenario, and I have received the tokens on another wallet.

Please check once again. If you still face any issues, you can share the screen recording for the same.

BlocksScan team trying to create a "BlocksScan - Etherscan compatible API", which will be integrated with XDCPay soon. So that user can able to see the "Received" transaction history too.

Collapse
global_citizen_37ac0334d6 profile image
Global Citizen

Please enable “max” withdraw. Incase I want to withdraw all my xdc from a wallet i no longer want to use this would come handy. Otherwise there’s lots of wallets with small amounts of xdc abandoned

Thread Thread
anilchinchawale profile image
AnilChinchawale

Hello,

Kindly note that MAX button is enable and you can use it to send all fund from specific account.

Collapse
sudeep profile image
Sudeep Ravindran

Hi,

XDC Pay 2.0 seems to break our existing integration with the web3-onboard library(formerly bnc-onboard) that we use for detecting network change.

At the root of this issue seems to be the problem that web3.currentProvider now gives chainId as "0xNaN" (with XDCPay 2.0).

We think this code below is responsible for the issue

github.com/XinFinOrg/XDCPay/blob/b...

Firstly, the list of standard selectors in the file do not contain XDC Networks (neither apothem nor mainnet).

So, the "OR" condition is triggered which has its own set of problems. Most likely, the chainId configured elsewhere is not int & hence the parseInt fails with NaN. The whole outcome triggers the "0xNaN" which messes up the onboard library as the value is non-null but unintelligible.

For reference, we are using v 1.34.1 of onboard and our dapp has otherwise been stable for a while now. This is the line where XDC Pay 2.0 fails for us.

github.com/blocknative/web3-onboar...

Collapse
ivan_blocksscan profile image
Ivan_BlocksScan

Hello @sudeep,

BlocksScan team have already fixed the issue, Kindly check the updated build (latest version) of XDCPay 2.0

Collapse
sudeep profile image
Sudeep Ravindran

Thanks. The issue has been resolved

Collapse
mrblockchain22 profile image
Salomon Morales

Hello BlocksScan team, I have submitted my review of the XDCPay 2.0. There are some bugs which I addressed in the feedback form. I do love the UI and the buttons, as it has a smooth feel. Keep up the excellent work!

Collapse
blocksscan profile image
BlocksScan Author

Thanks for the feedback, we will definitely try to deliver best with users suggestions and feedback.

Collapse
cryptosandtokens profile image
Robert Aronovici

I was having issues with the beta extension and Metamask not behaving properly. Loading other web 3.0 content from other sites were blocked. I had to remove the extension to load them properly.