This is where the UX gets a bit confusing navigating to the NFT component and not actually seeing the wallet's unlited NFTs shown here. As part of MVP I think you should either:
a) distinguish NFTs from SLP1 tokens in the eTokens component;
b) move the NFTs to the NFT component; or
c) make it clear the NFT component is actually a marketplace (i.e. Trade NFTs)

This should be a Red button to alert the user this is a final click before finalizing the action. It would apply to both cancellation of listing and buying of an NFT so don't need to change the conditional rendering logic here.
The 'Never mind' should be labelled as 'Cancel' for consistency.

use appConfig.derivationPath

IIUC, both myListings and offeredListings are only ever stored as state variables? If so, every load of this nfts component will always trigger getAllTxHistoryByLokadId which traverses through the entire agora lokad history which will cause scalability issues later on. Since myListings and offeredListings are only state vars you'll always get that delay every time you navigate to this page while it retrieves every single lokad history page from chronik, which is already 1.5 seconds with 3 NFTs list and half a dozen associated lokad history txs.

I would suggest storing listedNfts const into localforage and then preload it in useEffect(), and THEN kick off the above to refresh the listings in the background, similar how cashtab tx history loads the last cached history and then updates to the latest.

If you go down the route of directly using chronik response numPages prop to derive frontend pagination pages then keep in mind the scenario where one chronik page might have txs which aren't meant for frontend listings display (e.g. cancel action, buy actions) and you end up with some pages with only 1-2 NFT listings whilst other pages contain 25 NFT listings. On the other hand if you intend to retrieve all lokad history pages and then paginate from within the app then just keep in mind the increasing processing time.

Needs a loading spinner of some sort here. The underlying lokad id lookup call will increase loading time very quickly once this launches.

Presumably this will always be shown upon app startup right? I haven't seen this even on new wallet on a fresh browser. I just see an empty render for 1-2 seconds and then the listing below shows up.

no -- I will mark this "changes planned," I still have some more clean-up to do here.

Also need to implement the new agora tx building functions -- but mb that can wait until this is in prod. that is more an optimization, while the migration to agora plugin queries gets us over the lokad query scaling issue.