leather-io / extension

Leather browser extension
https://leather.io
MIT License
303 stars 142 forks source link

Ordinals not showing after logging back into the wallet #3358

Closed 314159265359879 closed 1 year ago

314159265359879 commented 1 year ago

User 1 dewan 208694468e41112375626e29247ca8657d980840dba79b6af0d16438469eec23 https://www.blockchain.com/explorer/transactions/btc/208694468e41112375626e29247ca8657d980840dba79b6af0d16438469eec23
Chrome/PC Reloaded many times, reset react cache, didn't help.

Confirmed NFT showing in sparrow wallet.

User 2 heezyMD Hello, I logged back onto my wallet and now the ordinal I previously created disappeared and my ordinal address has changed. It showed up in the wallet before. Is there a way to restore the previous ordinal address or link it back?

User 3 Two accounts with ordinals not being loaded, not seeing any helpful messages in the console. I do see that the taproot address generated to receive the next ordinal inscription is a fresh one. Different from the ones that have already received ordinals.

314159265359879 commented 1 year ago

User 4 camilocuadros Migrated inscription from native segwit address to ordinals address but it is not showing after 67 confirmations.

Restored the wallet from seed to exclude caching issues.

markmhendrickson commented 1 year ago

For those also using Sparrow, can we confirm that the Taproot address provided by Hiro Wallet is also showing up in their Sparrow list of addresses?

314159265359879 commented 1 year ago

I will confirm. I know user 3 is only using their seed with Hiro Wallet.

314159265359879 commented 1 year ago

User 4 is only using their seed with Hiro wallet, another inscription is showing up normally. This is the inscription not showing up: https://mempool.space/tx/e7011ffc97e239e52e030c1cd98d4b8f1747ef63fe5f59edcf879cdee720dc86 ordinal https://ordinals.com/inscription/c9d48c469d832ff1dc558444e2beb202f7f7bf6e6e58a1010dfceb9a6cb8ef20i0

314159265359879 commented 1 year ago

User 5 Lucynator, is only using their seed with Hiro wallet, 15 confirmations so far. Not yet showing up. b1df3a71a61e4f2dc7e8349a9b81de215ec6d69e750c140e9955206443ea8228 https://www.blockchain.com/explorer/transactions/btc/b1df3a71a61e4f2dc7e8349a9b81de215ec6d69e750c140e9955206443ea8228

314159265359879 commented 1 year ago

User 6 Ivan, saw ordinals earlier, but are now not displayed anymore.

314159265359879 commented 1 year ago

User 7: 20470 created inscriptions with gamma and send them from the ordinals wallet to the HIro wallet, about 20 were send to the same Taproot address.

They restored the wallet from seed which yielded no change. Address receiving the 20 inscriptions: bc1pyas6v800xrkqavy3cle2uw9vs8hjdfgltnw7fykqq7v29ad0sesqvv84sk

crypstronomer commented 1 year ago

Yeah just same as everyone reporting my end. Sent ordinal an md received in Hiro generated ordinal address about an hr ago can't display I'm using the chrome extension

https://blockchair.com/bitcoin/address/bc1psv5yjn7exqv6w8y3pjhrve0mgk5vamedwcv255mnm9yyh2kexa0ql4xgmn

Was a Hiro seed generated account, imported into xverse app, sub account created in Xverse fir bns and then also added and married up into Hiro chrome extension.

Sent BTC fine to BTC address yesterday, still shows bns associated with the address, however the collectable refresh is forever scrolling and i think that's the issue also, previously it stopped scrolling and had option to refresh.

The address shown in Xverse to recieve ordinal is different to one showing in Hiro chrome, I was told yesterday that would be the case just adding it in for reference

crypstronomer commented 1 year ago

Also just noticed this under manage extensions in chrome, says a lot of errors

crypstronomer commented 1 year ago

![Uploading Screenshot (96).png…]()

aviwol commented 1 year ago

I saw parts of the code rely on ordapi.xyz, the key structure has changed (keys with " " spaces were replaced with "_") on the return of ordinals from all endpoints including ordapi.xyz/inscription/:inscription might be because of that?

markmhendrickson commented 1 year ago

Thanks everyone for the input here, especially @aviwol for spotting the issue. We've rolled out a client-side fix and have also requested a temporary roll-back to the semantic change from OrdAPI so that viewing functionality is restored faster.