Description
Project Submission
- PROJECT NAME
The Badge - DESCRIPTION OF THE PROJECT (2 lines)
We implemented a proof of concept of the new platform "The Badge", which allows to create an untransferable NFT (Badge) as certificate of ownership of a Github account. - DISCORD USER NAME (team contact to share the judging details)
After submission, this person should be constantly checking discord for updates
- ramabit#4994
- Agup#6624 - REPOSITORY WITH PROJECT'S CODE
https://github.com/thebadge/thebadge-poc-ethlisbon22 - VIDEO DEMO (5 min max)/PRESENTATION (10 slides max)
https://drive.google.com/file/d/1sJCjSKTQ3nmk0CBaU52A2mlTGmDM9kfl/view?usp=sharing - The contract address(es) or website URLs of your deployed application, either on a testnet of your choice or mainnet of a platform of choice. 📂📂 (NOT mandatory)
Contract address: 0xD24b0847747F334c3634BAD3C5CF76a76A384f7A
https://blockscout.com/xdai/mainnet/address/0xD24b0847747F334c3634BAD3C5CF76a76A384f7A/contracts#address-tabs
Bounties
---- WalletConnect Bounty Web3Modal V2 ----
We applied for the Best Mobile UX and the Best Public Good bounties but we found issues with the integration with Web3Modal V2, when we want to send a transaction we got the following error:
----
Error: underlying network changed (event="changed", network={"name":"unspecified","chainId":0,"ensAddress":null,"_defaultProvider":null}, detectedNetwork={"name":"xdai","chainId":100,"ensAddress":null,"_defaultProvider":null}, code=NETWORK_ERROR, version=providers/5.7.2)
at Logger.makeError (index.js?dd68:224:1)
at Web3Provider.eval (base-provider.js?4ba1:998:1)
----
The read-only features work well, account reading, network switch, etc. We found a trick to make the transactions work partially using refetch(). Seems that the preconfigured network inside the library is 0 and does not get updated until we call that function. Once we do that, if the user tries to send again the transaction it works, we tried awaiting the promise of refetch() but seems not working.
This mean that the app is functional, but if you want to send a transaction for creating a badge, you need to press the submit two times in order to dispatch the transaction:
You can check the fix here:
Please note that the solution with web3modal v2 is in another branch called web3modal
Just in case we upload a screenshot with the web3modalv2: