🎾🌎 ↝ [STA-19 STA-30 SGV2-141]: Articles & off-chain accounts #139
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We've got some 3d planets being rendered in javascript, these are based on the initial C# algorithms in Signal-K/starsailors#4, Signal-K/starsailors-boilerplate#1 We've got some plans to generate nfts from this: Signal-K/sytizen#18. The models here are based on the C# model, we'll have an API call setup later so that they're both equivalent to each other directly. Next step is setting up some image exports and saving user data, providing a way for users to export the 3JS graphic to their Supabase storage row. That will be commenced later on tonight. All the fields will be set to be callable via an API & we will compare the output of different Deepnote graphs generated from `lightkurve` to provide further adjustments to either end. One issue is that on the frontend for the generator, some of the components aren't selectable. This is because the original example components were built for a much older version of React>Next. Since these will be callable via a custom API, and the editor will be changed to be a form, that won't be an issue. Docs available at the central issues on signal-k org Signal-K/marketplace#19 Signal-K/marketplace#3 Signal-K/marketplace#7 Signal-K/Silfur#26 -> These will be added to posts on the image/comment sharing part of the site (and later on Lens -> team members can refer to the roadmap) so that will be routed internally.
…-parameters-from 🥶🦀 ↝ Adding initial off-chain authentication via Supabase to the Lens client
Also updated header component to provide links to the section Signal-K/sytizen#16 Temporarily had to remove the `Threads` hooks because being unfinished, they were causing build errors. They will be re-added later. Vercel has now been updated with a new test link -> check out the generator https://starprotocol-gizmotronn.vercel.app/generator/planet-editor Documentation on the gallery is available here: https://skinetics.notion.site/Supabase-Primer-6cf6c0e31fe6421b9fe0f084d8bad0e5
Changelog: Moved the gallery components into the offchain account section. Added new feature where users can take a screenshot of the planet they've created Currently, the screenshot is saved as an image URI string (see bottom of commit for e.g.), which is a problem as it is then uploaded to Supabase as a URI. What we need to do is convert the URI to an image inside the app (without saving it as a file on the app (as in a png file being saved next to the jsx file). This could be done before it's uploaded to Supabase, or when it's retrieved... Signal-K/sytizen#18 Signal-K/sytizen#16
…contract This is the first step of our new attempt at fixing Signal-K/Silfur#25 I've started merging the CSS into a new `styles/Proposals` directory in the next client, converted the calculater functions to typescript, and adding the context as a wrapper around the rest of the app (inside Thirdweb -> Moralis [providers]). We'll take the `<Sidebar />` component from https://github.com/Signal-K/sytizen/tree/main/client and have that be a persistent component on all pages INSIDE the `pages/Proposals` directory. We can remove the usage of `react-router-dom` by just putting a page inside that directory, and then creating a `[...id].tsx` file for the proposals dynamic routes, thus making it Next compatible. The context provider seems to be working fine. So we'll see how this goes.
Also fixed profile styling issue on my Lens profile (#7 #8 #9 #10 #11 #12): https://www.notion.so/skinetics/Threaded-Comments-2nd-iteration-flow-475d8a2328be4be8a1403256f094790e#61f363eddac74572b243ebb0c9c6513a Signal-K/sytizen#16
…ta for offchain auth
…-commenting-post 👜🦺 ↝ Adding planet editor, profile hooks
…ing to social graph
…management added There's an issue with loading the Avatars in the PostCard component -> we need to match them to the post id & the user who created the post [id] however it seems there's an endless loop that's been established where the client is constantly trying to communicate with the server (Supabase). The key to fixing this issue is getting the Avatar data to be passed in the same way as it is in the PostFormCard component (which is not experiencing any problems) Signal-K/sytizen#16
1. Completed authentication header for web client. To the end user it is 100% offchain, with user profiles being stored on a postgresql database. However, I've taken a dive into the Magic sdk to create wallet addresses for each user, as well as a Flask-based authentication handler for future metamask/wallet interaction. I've made this decision for a few reasons (like simplicity), but the main reason is for the client to seem like a regular journal platform and not be confusing, as well as follow the 'web3-agnostic' design language I favour for projects like this due to confusion and/or distrust of web3 products/teams. However, since each user will have a wallet address, they'll be able to interact with smart contracts and IPFS just fine. Further discussion will need to take place to discuss long-term suitability of this model, including things like gas fees (currently everything regarding transactions is occurring on Goerli [testnet] and gas fees will be processed by a "superuser" so that there's no restrictions or huge expenses) and how we go about getting users to trust the web3 nature (which I've got a lot of experience with). However, I don't fully know the exact demographics we'll be targeting & also I understand that that's quite a while away, so I'll raise it now but won't spend any time thinking about it until the time comes
2. I've continued with the contracts for proposals/publications & updating the metadata standards. I favour a lazy minting approach with data processing being handled by a Flask blueprint (which is a formula my team have developed on signal-k/sytizen). Right now I'm using Thirdweb & Moralis for the contract interactions and I have also, with much difficulty, succeeded in getting Moralis to self-host on my Postgres server. Finally, I've begun the process of optimising the base layer contracts so that the gas fees (which are already reduced post-merge) are essentially negligible at this time.
3. File upload for posts/articles feature on the web client is complete, and the smart contracts now receive all file upload metadata from this.
4. Begun a new flask blueprint (forked from point #2) to generate dataset previews based on which modules (e.g. lightkurve) are used and to add interactive nature to the 'sandbox' feature discussed earlier
5. Reluctantly continued some documentation
(above message from the Desci discord, see Signal-K/sytizen#16 for more info)
…h-to-usesession-from 🥎🔎 ↝ Fixing thirdweb module issue, update avatar export function
… some issues with rendering the planet-editor state. Also added contract info for staking
…s, updating how profile state is used
…t & integration, styling, just missing a few assets. Signal-K/Silfur#28 && Signal-K/Silfur#31
…ent-to-offchain 🥇🐧 ↝ WB3-12 add lens graphql client to offchain client, and staking back
Users can now navigate to `/planets/{$planetID}` to see information relating to their planet, including datasets, articles, a sandbox, basic stats/info, a gallery, and a generator.
Generator:
Signal-K/sytizen#18
Right now it's just the same generator script, but eventually it will take in the fields like radius from the table the page itself is generated from. We'll update the frontend fields to use a UI based on the <Card /> component we've designed for the Profile pages. users will be able to edit these fields and create a fork of the anomaly in its dataset sandbox for use in their own projects, and this can be part of the "XP" demo for "citizen science points" to mimic the behaviour of the reputation erc20 token:
Now that staking has been re-added, time to close #18
Signal-K/sytizen#16 Profile pages
Signal-K/sytizen#13
Signal-K/sytizen#6 -> Generator & staking
Signal-K/sytizen#1 -> sandbox & generator
Signal-K/Unity-Demo#28
Signal-K/Unity-Demo#5
Signal-K/starsailors#4 -> user input on anomalies
Signal-K/Silfur#26
Signal-K/Silfur#25 -> Some small changes with the Thirdweb module behaviour, still yet to commence full re-integration now though
Signal-K/Silfur#24
Signal-K/Silfur#22 -> Replacing "mint" FOR NOW with just a "claim" button that sends the planet to your supabase table inventory (array/foreign key in 'profiles' table
Signal-K/Silfur#21
Signal-K/Silfur#12 -> Keep an eye on this, but for now this is deprecated
Signal-K/Silfur#3 -> Again keep an eye on the original card game contract, but until we commence the full re-integration of the smart contracts, this is not needed
Signal-K/Silfur#30 -> This is working a treat
Signal-K/Silfur#29 -> Now need to add true threaded comments & integrate it with sandbox items
Full notes available here: https://www.notion.so/skinetics/February-Flow-Planets-8c864b66147c447f82136772336e9bc6?pvs=4#09b8260b2360412683ef5935309fd011
…ent-to-offchain 🚀🎨 ↝ Staking soft re-integration & profile page index/boilerplate completed
…worlds. Confirmed to be compatible with react-renderer-
…oading/rendering unity builds on local dev engines with poor connection. | https://www.notion.so/skinetics/June-Week-1-report-f3272b493996416fb2384acfd473b24a?pvs=4#b03c0fd2de9e43f59bf941c09f8ea928
🧠🗿 ↝ Unity LOD build for planet paint function, fresh dir for undefined error
…-posts-be-generated 🧉🧠 ↝ Planet/anomaly object pages generated based on entities in db, claiming & Unity integration added
🐦🧉 ↝ Addition of Unity build
…rn-stats 🐏🩳 ↝ Claiming method created (just hidden for now), stats & graphs for anomalies are returned to the frontend
…commenting-post 🪖👜 ↝ Off-chain threads & discussion board now implemented
…ent-to-offchain 🧛🏻♂️🍢 ↝ Lens client still there, just hidden
…wb3-11-migrate-offchain-auth-to-usesession-from 🛻🧩 ↝ [STA-30 WB3-11 SGV2-141]: Offchain-accounts integrated into article comp.
Gizmotronn
added
documentation
|
…0-create-article-component-in-client
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's just get this over with
Huly®: STAR_-93