\r\n\r\nI'll try to outline, till @vikiival pick this up\r\n- Currently, we will use KSM as currency for buying and selling \r\n- Users can use whatever currency they want for transaction fees, but just KSM to buy/list/sell NFTs. Later there will be available any other currencies on Basilisk (KSM, BSX, aUSD and others)\r\n- Goal is for the user doesn't need to care about the fee payment currency \r\n- If you transfer KSM to Basilisk and it's your new account, it will automatically switch to payment for fees in KSM\r\n",[2892,2895,2897],{"name":2893,"color":2894},"p3","D4C5F9",{"name":2896,"color":2872},"A-basilisk",{"name":2898,"color":2872},"A-writing-✍️",3881,"More comprehensive writing on current Basilisk Rococo implementation","2023-10-16T14:37:38Z","https://github.com/kodadot/nft-gallery/issues/3881",0.74289435,{"description":2905,"labels":2906,"number":2907,"owner":2874,"repository":2875,"state":2876,"title":2908,"updated_at":2909,"url":2910,"score":2911},"Would be amazing to be more web3 native and run at least one instance under handshake domain to give it a try\n\n- explore setup\n- prepare deployment at Netlify if there is extra requirement\n\n",[],1592,"Setup HNS domain","2024-07-31T14:28:07Z","https://github.com/kodadot/nft-gallery/issues/1592",0.74592155,{"description":2913,"labels":2914,"number":2918,"owner":2874,"repository":2875,"state":2876,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Is your feature request related to a problem?\n\nSometimes the artist puts the price too high and it takes a while that someone buys it.\r\n\r\nExample (Art): \r\n- Artists puts it firstly for 1 KSM\r\n- relist it fo 0.75\r\n- relist it 0.5\r\n- someone buys it\r\n\n\n### Describe the solution you would like\n\nThe index should tell the price change from beginning to sale and then average (in this case -50/-50)\n\n### Describe alternatives you have considered\n\nIf you have any ideas how to do it better lmk\n\n### Screeenshots\n\n👀",[2915],{"name":2916,"color":2917},"enhancement","a2eeef",1123,"Percentual price change index for NFT ","2024-07-31T12:03:35Z","https://github.com/kodadot/nft-gallery/issues/1123",0.75735414,{"description":2924,"labels":2925,"number":2935,"owner":2874,"repository":2875,"state":2876,"title":2936,"updated_at":2937,"url":2938,"score":2939},"For particular reason to be aware if we are up or not would be great to have handsome endpoints to see what's needed to have seamless working with users\r\n\r\n### spec\r\nWe should be able monitoring endpoints and route on minute basis, hope that's enough using serverless functions\r\n\r\n- [ ] subquery endpoint (magick)\r\n- [ ] SubSquid endpoint (rubick)\r\n- [ ] snek \r\n- [ ] unique\r\n- [ ] Netlify edge performance points \r\n- [ ] Pinata\r\n- [ ] Estuary\r\n\r\nThen we could measure amount of time to resolve particular queries for routes\r\n- [ ] series-insight\r\n- [ ] spotlight\r\n- [ ] gallery\r\n- [ ] collection\r\n- [ ] random item detail\r\n- [ ] collections\r\n- [ ] random profile artist\r\n- [ ] other upcoming bigger query routed\r\n\r\n### \r\n- [ ] Link \"Status\" to footer at KodaDot \r\n\r\n### stack\r\n@roiLeo suggested https://github.com/juliomrqz/statusfy\r\n\r\nprobably it could be written as serverless function, we have some spare capacity on Netlify but for the reason, later it should be running outside Netlify to verify if there is everything ok",[2926,2927,2930,2932],{"name":2893,"color":2894},{"name":2928,"color":2929},"hackathon","91962A",{"name":2931,"color":2872},"A-nuxt",{"name":2933,"color":2934},"$$$$","F085E8",1492,"Create dashboard status.kodadot","2024-07-31T13:36:35Z","https://github.com/kodadot/nft-gallery/issues/1492",0.7609311,{"description":2941,"labels":2942,"number":2945,"owner":2874,"repository":2875,"state":2876,"title":2946,"updated_at":2947,"url":2948,"score":2949},"we've had some issues with multiple sorting options before, the feature got introduced here:\r\n- https://github.com/kodadot/nft-gallery/pull/3067\r\n\r\nlater was fixed (in a hacky way) to not allow conflicting options at once (such as price high to low and price low to high at once) here:\r\n- https://github.com/kodadot/nft-gallery/pull/3325\r\n\r\nsome questions / things to figure out before this can be properly labeled, picked up, and refined:\r\n\r\n1. Even though, passing multiple search params was allowed, what is the desired outcome? As an example, @roiLeo comment from #3067\r\n\r\n> Tested on /rmrk/explore?page=1&tab=GALLERY&search=&sort=PRICE_DESC&sort=EMOTES_COUNT_DESC&listed=true\r\n\r\nwhat do you actually expect to see there? Maybe it's just me but I'm having hard time imaging the desired result. Is it first sorted by price? (desc) and then sorted by number of emotes...? I actually don't know what should the fetched data look like. Do we really want this? I think I'm not alone in this confusion, but please, provide your feedback. Right now, to me it seems, that the first param is the one which is sorting and the second one is not taken into consideration.\r\n\r\n2. thanks to @cryptodamsky comment from #3507: \r\n> Ok, i’m just saying that the term \"serial number ascending\" doesn’t make sense to end user AND it doesn’t work when I click it.\r\n\r\nseems that Serial Number Ascending, indeed, isn't working correctly, although it is sorted in some way, it's not an intuitive one + I'm not really sure on which basis are the serial numbers attached to the NFTs and why would that be interesting to anybody. I don't think more is necessarily better in this case, the filter has too many options already.\r\n\r\n\r\nI'm not saying we have to do it like this, but some inspiration, with many less options, and in my opinion, cleaner UI (I've cut out filtering which we don't provide):\r\n\r\nOpenSea search | LooksRare search\r\n:-------------------------:|:-------------------------:\r\n | \r\n\r\n\r\n\r\n\r\n\r\n\r\n",[2943],{"name":2944,"color":2872},"A-research",3523,"Sorting in Gallery/Collections - revisited","2023-12-22T10:55:09Z","https://github.com/kodadot/nft-gallery/issues/3523",0.76665086,{"description":2951,"labels":2952,"number":2957,"owner":2874,"repository":2875,"state":2876,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Is your feature request related to a problem?\n\nWhen someone creates a collection and will not add NFT right after into it, this collection is not visible in his profile. I just chatted with a confused artist who wanted to report an issue because he could not find his (empty) collection. This is probably not an essential change, but it would make our platform a bit more user-friendly. \r\n\r\nArtists can see their empty collection only in the process of creating new NFTs.\n\n### Describe the solution you would like\n\nMaybe it will be nice to have something like drafts or empty collections that would be visible only to the artist. \n\n### Describe alternatives you have considered\n\nAdd a folder or option where people can see their empty collections.\n\n### Screenshots\n\n_No response_\n\n### Are there opened related issues?\n\n_No response_",[2953,2954],{"name":2916,"color":2917},{"name":2955,"color":2956},"profile-redesign","fbca04",4420,"Making empty collections visible to creator","2023-11-06T14:08:37Z","https://github.com/kodadot/nft-gallery/issues/4420",0.7717779,{"description":2963,"labels":2964,"number":2974,"owner":2874,"repository":2875,"state":2876,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Is your feature request related to a problem?\r\n\r\nCurrently we have a bit ugly error page for missing collections\r\n\r\n### Describe the solution you would like\r\n\r\nI would like to see a universal page for errors like `/404` where you add can add the query params like `?type=collection&reason=error.notfound&id=dasdas` so we can reuse it also for missing nfts or other pages :)\r\n\r\n### Describe alternatives you have considered\r\n\r\nIt can be built on top of the `Error.vue` component :)\r\n\r\n### Screeenshots\r\n\r\n`errorcollection`\r\n\r\n\u003Cimg width=\"1101\" alt=\"Screenshot 2022-05-06 at 11 54 53\" src=\"https://user-images.githubusercontent.com/22471030/167110400-24bb41aa-cc65-4bdf-8f87-c72bb9751995.png\">\r\n\r\n`current 404`\r\n\r\n\u003Cimg width=\"1104\" alt=\"Screenshot 2022-05-06 at 12 00 22\" src=\"https://user-images.githubusercontent.com/22471030/167110884-5ff96685-e53d-440b-9a66-dfa4fa42fc99.png\">\r\n\r\n`Error.vue`\r\n\r\n\u003Cimg width=\"1105\" alt=\"Screenshot 2022-05-06 at 12 00 45\" src=\"https://user-images.githubusercontent.com/22471030/167110916-57fa45b4-fec1-48ad-877a-352422e29db2.png\">\r\n\r\n\r\n\r\n",[2965,2966,2969,2972],{"name":2916,"color":2917},{"name":2967,"color":2968},"good first issue","5319e7",{"name":2970,"color":2971},"$","0E8A16",{"name":2973,"color":2894},"p2",2958,"unified error page","2022-05-10T11:22:08Z","https://github.com/kodadot/nft-gallery/issues/2958",0.7725401,{"description":2980,"labels":2981,"number":2983,"owner":2874,"repository":2875,"state":2876,"title":2984,"updated_at":2985,"url":2986,"score":2987},"Probably we will need setup how we collect fees\r\n\r\n- chain agnostic - like Statemine, Basilisk, MoonRiver, &c\r\n- setup multisig on other chains\r\n- fall back address collect fee to other chains? But user needs approval or balances there so meh\r\n\r\n_Originally posted by @yangwao in https://github.com/kodadot/nft-gallery/issues/2129#issuecomment-1025538908_",[2982],{"name":2893,"color":2894},2130,"Reengineer sustainability program","2024-07-31T13:37:49Z","https://github.com/kodadot/nft-gallery/issues/2130",0.7752355,["Reactive",2989],{},["Set"],["ShallowReactive",2992],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fe2ZlzjpiJh27vhHbaYL6sZDTuhqK06cNTsQDze-m7Mc":-1},"/kodadot/nft-gallery/2756"]