MyCrypto VS covidpass

Hardware wallet? https://mycrypto.com will let you retransmit a new transaction with the same nonce. Did it yesterday during the Binance SEC sell-off frenzy.

Have you tried any deprecated MyEtherWallet versions or perhaps MyCrypto - or any other Ethereum wallets that can have Ledgers connect via hardware wallet? Taho (formerly TallyHo) might be a decent option worth trying as well?

Several years ago the core developers of MyEtherWallet split up their team. One part kept on developing MyEtherWallet and the other part was called MyCrypto, which is maintained up to this day: https://github.com/MyCryptoHQ/MyCrypto

You should be able to manage your XDC using your Ledger as a hardware wallet in conjunction with a 3rd party wallet such as MyCrypto.

this is bad. Yes your wallet is forever compromised. You have to take your funds out ASAP. But read this before: https://blog.mycrypto.com/how-to-beat-an-ethereum-based-sweeper-and-recover-your-assets if ever you have that on your MM wallet. I would suggest you get in contact with the support of https://mycrypto.com/ they're a doing good work. Contact them. Metamask support normally isn't that helpful, but can be a way, too. Normally for compromised wallets they'll send you elsewhere, so you can ask them for direction.

Alternatively, you could connect your Trezor to software like MyCrypto (https://mycrypto.com/). From there, you can broadcast a transaction with the following properties:

mycryptowallet (https://github.com/MyCryptoHQ/MyCrypto)

- MyCrypto: (https://mycrypto.com/)

I'm sorry, I just checked and same problem for me. Maybe you should contact the dev? https://github.com/covidpass-org/covidpass

Their code is supposedly open source so you can read their public repo here: https://github.com/covidpass-org/covidpass

Yeah, you'd think so, wouldn't you. Unfortunately, two factors conspire to make that impossible. Firstly, the QR code for the vaccine card is based upon the Smart Health Card standard, which does it's best to generate the smallest payload possible, but it still ends up being ~1.7KB, which is on the large side for a QR code. Secondly, Apple always applies the "medium" error correction level to QR codes on a pass, and only displays them at a fixed size. Both of these combine to make a QR code on the pass that is too small and too dense to be scanned properly (at least by a smartphone when both devices are handheld). More details in this GitHub issue for another service that is trying to achieve this.

I understand your concerns. This is why the code of the web app and the API is publicly available on GitHub for everyone to see how and what data is processed. Please also consider reading the Privacy Policy.

The whole project is openly available on GitHub, so everyone can check how their data is processed. I have no ambitions to make profits of this but there is a donation link on the bottom of the page to cover the server costs :)