\r\n\r\nFinally, we have an endpoint we can start to integrate multi-chain components.\r\n\r\nAt some point would be nice to have some component which would wrap and abstract the current endpoint in case we find Supabase is not sufficient for our case. \r\n\r\n\r\n## Endpoint\r\nFollow up what can be done with new endpoint\r\nIf anyone wants to play with that here is the URL\r\n\r\n```\r\nhttps://xtnvtbdyvpbbnonbbcif.supabase.co/graphql/v1\r\n```\r\n\r\nYou need to add `apiKey` header into your request. You can find the key in the discord group.\r\n\r\n\r\nSample Query\r\n```graphql\r\nquery findCollections {\r\n\tcollectionsCollection(first: 10) {\r\n\t\tedges {\r\n\t\t\tnode {\r\n\t\t\t\tname\r\n\t\t\t}\r\n\t\t}\r\n\t}\r\n}\r\n```\r\n\r\n\r\n## Tasks \r\n- https://github.com/kodadot/nft-gallery/issues/4865\r\n- https://github.com/kodadot/nft-gallery/issues/4617\r\n- https://github.com/kodadot/nft-gallery/issues/4380\r\n- https://github.com/kodadot/nft-gallery/issues/4618\r\n- https://github.com/kodadot/nft-gallery/issues/4073\r\n- https://github.com/kodadot/nft-gallery/issues/4275\r\n- https://github.com/kodadot/nft-gallery/issues/4753\r\n\r\nOnce all the above done \r\n- https://github.com/kodadot/nft-gallery/issues/4379\r\n\r\n## Ref\r\n- https://developers.cloudflare.com/d1/platform/client-api/\r\n- https://github.com/kodadot/nft-gallery/issues/1824",[1984,1987,1990,1993,1996],{"name":1985,"color":1986},"$$","0E8A16",{"name":1988,"color":1989},"p2","D4C5F9",{"name":1991,"color":1992},"A-search","FBCA04",{"name":1994,"color":1995},"chief","67EA1F",{"name":1997,"color":1992},"A-multi-chain",4257,"kodadot","nft-gallery","open","Enable Multi-chain capabilities in KodaDot","2023-03-15T14:49:24Z","https://github.com/kodadot/nft-gallery/issues/4257",0.7385855,{"description":2007,"labels":2008,"number":2018,"owner":1999,"repository":2000,"state":2001,"title":2019,"updated_at":2020,"url":2021,"score":2022},"Right now, KodaDot was built mostly to be an on-chain data explorer and being a thin layer. Hence we would like to enhance comfort and are not sure if we should put these numbers like views on-chain as it might get expensive; we would like to provide users/artists some off-chain metrics and close to real-time.\r\n\r\nMaking a serverless function (worker?) which will be storing this stuff in KV in some efficient way. \r\nProbably each 1k, or 10k we can offload some stores to some remark to store these numbers on-chain to having only small increments off-chain. \r\n\r\nThis would be helpful for artists, creators and game item designers to have approximate estimation of which item is in demand. Similiar you have plays in Spotify, this would help estimate general audience likeliness of particular artifact \r\n\r\nWe could collect \r\n- load times of item (we should put some filter/captcha to account it was human viewing and not programmatically made or bumping some views)\r\n- if it's video play times\r\n- if it's 3d, time user has played with item?\r\n- if it's downloadable, times user/owner has downloaded it \r\n\r\nwyt?\r\n\r\n\r\nWe can then incorporate this into the new v1.1 Gallery item detail\r\n- #4403 \r\n\r\n\r\nTo start iterating on this, we would like to start showing this views per visit from logged persons. \r\nI think we can still trigger workers somehow and I guess we should split it to counting with logged vs not logged persons with wallet\r\nWe can trigger worker from which item was it visited and take it from there? \r\n\r\nUsing Workers/CF infrastructure would be probably easiest \r\n\r\n",[2009,2012,2014,2016],{"name":2010,"color":2011},"enhancement","a2eeef",{"name":2013,"color":1992},"A-research",{"name":2015,"color":1989},"p3",{"name":2017,"color":1992},"A-worker",4593,"Views counter/ranking","2023-04-11T20:04:33Z","https://github.com/kodadot/nft-gallery/issues/4593",0.75460774,{"description":2024,"labels":2025,"number":2034,"owner":1999,"repository":2000,"state":2035,"title":2036,"updated_at":2037,"url":2038,"score":2039},"We would need to have a search of artist creators names as well \r\n\r\n- To make this you would need to index the whole identities from the chain\r\n- Requires to write schema to the https://github.com/kodadot/rubick \r\n- Add to search box in the gallery and in collections view\r\n\r\n\r\n### Ref\r\n- https://github.com/kodadot/rubick/issues/31\r\n- https://github.com/kodadot/rubick/issues/52\r\n- https://github.com/kodadot/rubick/issues/56\r\n- https://github.com/kodadot/rubick/issues/83",[2026,2027,2028,2030,2031],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":2029,"color":1992},"A-subsquid",{"name":1991,"color":1992},{"name":2032,"color":2033},"creator","DCD7A0",2112,"closed","Add results of artist creators names to the search","2023-01-24T10:46:40Z","https://github.com/kodadot/nft-gallery/issues/2112",0.6711781,{"description":2041,"labels":2042,"number":2048,"owner":1999,"repository":2000,"state":2035,"title":2049,"updated_at":2050,"url":2051,"score":2052},"We still need essential parts to be more multi-chain robust, like search.\r\nI briefly chatted with Viki that we will have a cheap hack to aggregate results from other chains for search, for example. \r\n\r\nCurrent results show only one chain.\r\n\r\nI guess we would leverage this on top collections too.\r\n\r\n\r\n## Continue\r\n- https://github.com/kodadot/nft-gallery/issues/4380\r\n\r\n---\r\nFirst draft of schema\r\n\r\nCollection\r\n\r\n```sql\r\n-- create table collection_entities with following columns\r\n-- id (uuid, primary key, auto increment)\r\n-- animation_url (text)\r\n-- block_number (bigint)\r\n-- chain (enum, default 'rmrk')\r\n-- collection_id (text)\r\n-- count (integer, default 0)\r\n-- created_at (timestamp, default now())\r\n-- floor_price (bigint, default 0)\r\n-- hash (text)\r\n-- image (text)\r\n-- issuer (text, foreign key to creators table)\r\n-- max (integer)\r\n-- metadata (text)\r\n-- name (text)\r\n-- supply (integer, default 0)\r\n-- updated_at (timestamp, default now())\r\n-- version (integer, default 0)\r\n```\r\n\r\nNFT: \r\n```sql\r\n-- create table nft_entities with following columns\r\n-- block_number (bigint)\r\n-- chain (enum, default 'rmrk')\r\n-- collection_id (text, foreign key to collection_entities table)\r\n-- issuer (text, foreign key to creators table)\r\n-- id (uuid, primary key, auto increment)\r\n-- metadata (text)\r\n-- name (text)\r\n-- image (text)\r\n-- animation_url (text)\r\n-- created_at (timestamp, default now())\r\n-- updated_at (timestamp, default now())\r\n-- hash (text)\r\n-- serial_number (integer)\r\n-- version (integer, default 0)\r\n```\r\n\r\n--- \r\nFollow up what can be done with new endpoint\r\n\r\nSo I managed to pushed the data into `Supabase`\r\nIf anyone wants to play with that here is the URL\r\n\r\n```\r\nhttps://xtnvtbdyvpbbnonbbcif.supabase.co/graphql/v1\r\n```\r\n\r\nYou need to add `apiKey` header into your request. You can find the key in the discord group.\r\n\r\n\r\nSample Query\r\n```graphql\r\nquery findCollections {\r\n\tcollectionsCollection(first: 10) {\r\n\t\tedges {\r\n\t\t\tnode {\r\n\t\t\t\tname\r\n\t\t\t}\r\n\t\t}\r\n\t}\r\n}\r\n```\r\n\r\n## Ref\r\n- https://github.com/kodadot/nft-gallery/discussions/4457#discussioncomment-4555921\r\n- https://developers.cloudflare.com/d1/platform/client-api/\r\n- https://github.com/kodadot/nft-gallery/issues/1824\r\n- https://github.com/kodadot/nft-gallery/issues/4257",[2043,2045,2046,2047],{"name":2044,"color":1986},"$",{"name":2015,"color":1989},{"name":1991,"color":1992},{"name":1997,"color":1992},4617,"Add multi-chain support to the search ","2024-07-31T13:56:48Z","https://github.com/kodadot/nft-gallery/issues/4617",0.68735766,{"description":2054,"labels":2055,"number":2069,"owner":1999,"repository":2000,"state":2035,"title":2070,"updated_at":2071,"url":2072,"score":2073},"backlogging for redesign as it's among onboarding popular field for users \r\n\r\n> onchain identity supports picture this would be nice we could include on user profile their pictures\r\n\r\n- we will probably putting there IPFS hash which will point on our gateway, best way we can do it right now, need confirm if IPFS is not too long as I've seen u32 there\r\n- we can also show some thumb of uploaded picture\r\n- \r\n\r\n- https://github.com/kodadot/nft-gallery/issues/4466\r\n\r\n\u003Cimg width=\"1116\" alt=\"image\" src=\"https://user-images.githubusercontent.com/104380776/213158601-571ee80e-db20-4b88-9037-4237546e11c8.png\">\r\n\r\n_Originally posted by @JustLuuuu in https://github.com/kodadot/nft-gallery/issues/4466#issuecomment-1386895690_\r\n ",[2056,2057,2060,2063,2066],{"name":1988,"color":1989},{"name":2058,"color":2059},"onboarding","715318",{"name":2061,"color":2062},"redesign","227120",{"name":2064,"color":2065},"on-chain","95EB87",{"name":2067,"color":2068},"Ready for dev","12F4BE",4751,"Redesign Identity dialog","2023-09-30T12:35:37Z","https://github.com/kodadot/nft-gallery/issues/4751",0.7114316,{"description":2075,"labels":2076,"number":2086,"owner":1999,"repository":2000,"state":2035,"title":2087,"updated_at":2088,"url":2089,"score":2090},"Till we implement RMRK::BANNER or our own version of banners, we would be happy for users to by default repeat on x and y with nfts on random basis from recent NFTs \r\n- by particular aritst\r\n- inside particular collection\r\n\r\nPreferably show only static pictures, not moving stuff like gif,SVG,mp4 and 3d objects. \r\n\r\nPut it as background with some light grey scale filter to make other components hover over it.\r\nProbably put behind tabs as well if would not be complicated and won't harm readability \r\n\r\nThinking let's try with one or two rows, how it would looks like?\r\n\r\n\r\n\r\ninspiration from singular\r\n\r\n\r\n\r\nHow to implement: \r\n1. From the identity call fetch field `additional` where you find md5 hash for profile pic and background\r\n2. Create new query for Subsquid `nftMetaByHash` where you query \r\n\r\n```graphql\r\nquery nftMetaByHash($hashes: [String!]!) {\r\n nftEntities(where: {hash_in: $hashes}) {\r\n id\r\n hash\r\n meta {\r\n id\r\n image\r\n animationUrl\r\n }\r\n }\r\n}\r\n```\r\n\r\nThis query should you return `zero`, `one` or `two` results :)\r\n\r\n3. properly handle the image using Cloudflare image cache\r\n4. ???\r\n5. Profit\r\n\r\nThere is an edge case where we cache identities so having another button in settings for clearing identity cache would be perfect!\r\n\r\n### Ref\r\n- https://github.com/kodadot/nft-gallery/issues/2180",[2077,2078,2079,2081,2083],{"name":2044,"color":1986},{"name":1988,"color":1989},{"name":2080,"color":1992},"A-collection",{"name":2082,"color":1992},"A-profile",{"name":2084,"color":2085},"banner","EF1F8C",2329,"wallpaper users artist profile and collections","2023-05-25T14:50:26Z","https://github.com/kodadot/nft-gallery/issues/2329",0.72863084,{"description":2092,"labels":2093,"number":2096,"owner":1999,"repository":2000,"state":2035,"title":2097,"updated_at":2098,"url":2099,"score":2100},"Right now we are showing accounts that have at least some RMRK went through their account. \r\nWould be good to add a toggle to show only accounts with identity in /spotlight to filter no-names and scammers.",[2094,2095],{"name":2010,"color":2011},{"name":2015,"color":1989},603,"Show users with on-chain identity in spotlight","2021-08-23T10:35:47Z","https://github.com/kodadot/nft-gallery/issues/603",0.72950876,{"description":2102,"labels":2103,"number":2107,"owner":1999,"repository":2000,"state":2035,"title":2108,"updated_at":2109,"url":2110,"score":2111},"on-chain identity from Kusama, other chains\r\n\r\n- show Twitter if has it an on-chain id next to author?\r\n\r\n",[2104],{"name":2105,"color":2106},"good first issue","5319e7",13,"Add Twitter from on-chain Identity to NFT detail","2021-07-07T09:56:37Z","https://github.com/kodadot/nft-gallery/issues/13",0.7377001,{"description":2113,"labels":2114,"number":2123,"owner":1999,"repository":2000,"state":2035,"title":2124,"updated_at":2125,"url":2126,"score":2127},"This switch will be added to spotlight and series \r\n\r\n- Add new resolver to https://github.com/kodadot/rubick \r\n- add a switch to show passion \u003C> all \r\n- query\r\n-- where a collector is a current owner but not the issuer\r\n-- all nfts where the issuer is in the array from list 1\r\n\r\n### Ref\r\n- query could be find in previous issue\r\n- #2222 \r\n- https://github.com/kodadot/rubick/issues/27",[2115,2116,2117,2118,2121],{"name":2044,"color":1986},{"name":1988,"color":1989},{"name":2029,"color":1992},{"name":2119,"color":2120},"series","B68E24",{"name":2122,"color":1992},"A-spotlight",2223,"Passion feed for spotlight & series","2022-06-23T18:50:58Z","https://github.com/kodadot/nft-gallery/issues/2223",0.74076974,{"description":2129,"labels":2130,"number":2134,"owner":1999,"repository":2000,"state":2035,"title":2135,"updated_at":2136,"url":2137,"score":2138},"We could actually migrate/adapt/point to the existing reputation of recognized artists elsewhere i.e. deviantart https://www.deviantart.com/twoclicks/shop",[2131],{"name":2132,"color":2133},"stale","ededed",119,"On-chain identity for foreign markets","2024-07-31T11:10:52Z","https://github.com/kodadot/nft-gallery/issues/119",0.7410848,["Reactive",2140],{},["Set"],["ShallowReactive",2143],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"GIE48BrhfNyKVvroQ8v9HogCb1paHsfjnpU9XvF8HKY":-1},"/kodadot/nft-gallery/4753"]