Spect Network

GM, GA, GE everybody. Welcome to what's going to be another great DevNTell. If you didn't know, DevNTell is a 30-minute window for members of the DAO to showcase something they're passionate about or have been working on. This can be an awesome project you've been working on, demonstrating unit testing best practices, automation goodies, smart contracts, how to structure a project, etc. Basically, if you've got a passion for something, this is your opportunity to share it with the community. And today, I'm happy to introduce to you chakra and team who will be presenting or giving us an overview rather of the Spect Network. Take it away gang.

Awesome. Thanks Narb. So, yeah, I guess we'll get started with a short introduction about ourselves and then a little background on Spect and after that AVP will actually be doing the demo and then we can also help Reshma and I can also help answer questions. So feel free to ask any questions that you have. So yeah, I mean in terms of background I like I am a software engineer I started in Web3 about a year and a half back with AVP here who started around the same time. Like we were just doing hackathons, building cool new stuff and then we started working on Spect about I would say like in March. We went through like a couple iterations. So the main problem we realized over time was that how to sort of help DAOs make sense when they get too big and that's the problem we're currently focused on: on how we can help DAOs like do operations when they're big and how everyone in the DAO doesn't feel like it's too overwhelming.

So that's what we're working on right now. We've been in production for about with this current version for about two weeks and have been sort of stabilizing the product. So this is sort of the first public demo that we're making we haven't really made any announcement yet so yeah we're pretty passionate about it and we're excited to show you guys what we've built. So I think yeah I mean I'll let AVP... yeah so like AVP and Reshma are also like building Spect with me so we'll sort of split the responsibilities we'll pick up questions and the demo all of us together. So yeah I mean AVP and Reshma feel free to go ahead and introduce and then I guess we can get started.

Yeah, so hey everyone. So I'm AVP and basically I co-founded Spect with chakra like almost a year back and have been building the current iteration since March as he mentioned and so I am mostly focused towards the technical side. So I'm like building out the entire frontend stack and yeah that's about me.

So, this is Reshma and yeah so I'm a designer developer mostly focusing on the frontend and yeah I've been in the Web3 space for about six months now yeah five six and yeah we're part of Spect for three months and it's been a great journey so yeah let's get started.

All right. So I will share my screen to share the demo. Please let me know when it's visible.

Yep, I can see the screen.

All right, awesome. So this is our basically our landing page. So if you go to circles.spect.network here we see all the circles, basically this is what we're calling DAOs, we're calling them as circles. And yeah, so let's just get started. I'll start by creating a new circle: Demo Test 1 and I can add some description, add an image.

So yeah, if for the first-time user when they come you'd be guided through this onboarding. So I'll just like you can create a project if you want to start managing tasks right away. If you wish to create like dedicated workstreams within your circle like how Developer DAO has guilds, so for that you can create a separate workstream and just invite people.

So the first thing which you can do is go to the settings and basically set up the integrations for the circle. So first what we can do we can set up the Discord integration which is basically adding this our Discord bot to your server. So what this does what this allows us to do is like multiple things. So the first thing is that you can map like your Discord roles to the roles on site.

So like currently we have these default roles: steward, member, and applicant. So you can basically add the Discord roles which should map to the site roles and you can add multiple roles to these. Let's just go ahead and save it. So this is the Discord integration. Then you can configure your GitHub. So basically you can add the bot to the repo and this is also for this also comes in handy when you're managing tasks. I have already added so I will not add.

So the next integration is the Gnosis, basically you can add your safe from which you want to pay out for bounties and tasks and stuff. So I'll just I've created the safe on Polygon we'll just add this. So these were the integrations. Then in the payment side you can like add your custom token so just add the token address here and then you can use that token for anything, payment and stuff.

So if you go here to the contributors tab you can see like the three default roles and the members. So here one interesting thing to note is like this add role, so basically you can create your own role and you can do like granular permission like for each and every permission you can set like if this role is allowed to do that or not. So like I can have like a role called developer and I can set for each action if the developer role can do it or not. So you have full control like we offer full customizability in this aspect. So I'll just save it. And yeah, so you can see like another role has been created and this role again you can map it to the Discord role similar to what we did previously. And like you can also like if you don't want to use the Discord role mapping you can manually invite, select the role and then just generate a link and then you just need to send the link to just share it share the link.

So now like over here we can as we discussed like the workstream so we can create like a separate guild. So let's say we want to create a separate developer guild and this basically is the same as the circle we saw. Like this guild can have will have its own integrations so with like this guild can be connected to its own Discord server, this guild can have its own GitHub link, this guild can have its own Gnosis safe and everything is separate like you can this guild will have you can create custom roles for this guild. Like each of the workstreams are independent and you can customize them as you see fit. And this can go n-levels deep. Like you can create another workstream within this workstream and you can go on and on. So with this like you have like proper scalability. Like and like especially which in Developer DAO like the different guilds we have and how deep they go like this can be very handy.

So yeah like I'll just go back to the our main circle and here like I can start by like just creating a basic Kanban project. So I'll just call it Test Project Demo 1. So here basically we can actually start with a template so we have we have currently three templates and we we will plan on adding more templates. So the basic Kanban is just the basic template with those four columns: To Do, In Progress, In Review, Done. Then we have the Outreach template which is customized to for outreach functions. Then the Onboarding template which which again will be like different set of columns and different set of automations. So whatever whatever works best for you you can choose. So I'm just going to go with the basic Kanban for now. And yeah once you create your first project you will be again guided through the project onboarding.

So I'll just... okay. So basically it opens like the access to the entire process of opening the task, creating the task. So this is like the card model. So here you can like I'll just create like Task 1 and you can set... so the first thing is like the card type. So either you can set it as a task or a bounty. So bounty would be like basically it can be claimed by anyone and it it can have basically a reward and you can pay it out and it basically you need to sort of apply for it. Like tasks can be picked up by anyone but bounties can only be like you the whoever is the creator or whoever is a steward needs to approve someone to take up that bounty. Then the column, you can set the assignee, reviewer, deadline, priority and here you can set like the labels and you can have a sub-task and the description field is like a like it's like Notion like you can do anything here: images, heading, list anything is possible. So I'll just create it, maybe I can add some labels.

So yeah, the task is created and let me invite another member to pick up this task. So I'll just go here and invite let's say this this role which we created right let's invite a developer. So I have to logout and login from another account. I'll paste the invite link. So yeah you can see that I've been assigned this developer role. So I can go to the project and I can like I can just claim it claim a task if I see if it's unassigned I can just click on claim and I get assigned this task. So let's see what's in the task so this is basically the task page and here you can add comments.

So this is like you can have a full on discussion going on here and like another thing I forgot to add is that... okay I'm not in the steward account but I can show it later but yeah here you can you can add comments you can discuss here and you can create submissions. So there are two ways to create submission either you can just create a submission like this just free flowing text or we added like the GitHub bot right? So the what that GitHub bot allows us to allows us to do is that you can sort of create a PR pull request and mention this task ID and this will automatically link it to that PR. So I can just quickly show that. Let's create a new pull request. So what we need to do is we need to use the keyword spect and then in brackets we can specify any task IDs multiple task IDs. Test PR, create the pull request.

Uh yeah so then we get the notification from the bot that your submission was successful. So I'll go back and we see that the task automatically moves to In Review since we linked the PR. So then like even in the submissions the PR link is seen.

So I can now basically I'll just switch my account. So then as a as a card reviewer I can add revision instructions or comments here only in the in this sort of we call it submission thread so you can have discussions here you can you can keep on like sending revisions or other submissions here or like you know the PR link is there so I can just like directly go to the PR and then review it. So this was about the task. Then basically another thing what we want to point out is the the customizability of this board. You can rename the columns as you wish and everything is customizable like you can drag around the columns, you can delete a column like I can just delete this column and I can just create a new column. So it's fully customizable. This board we have made it such that that you can use it not only for project management but for anything like we we wanted to provide that customizability.

So next would be like and yeah like the just I'll just briefly mention the for for bounties like if you create a bounty basically then you can we have created this sort of batch pay mechanism where you can select you can pay for all the tasks or bounties which have a reward and you can basically select from which column and then you can decide to pay either from your wallet or through your safe that integration is there. And basic and another thing is this this what we call as the task wallet here you can see all your assigned tasks as assignee or all the tasks which you want you which you have to review just quickly like you don't really have to do anything just have to click on your profile and you can see all the task and go directly to that task.

Then yeah this was about the Kanban board like managing the task and stuff. Another feature which we have is retro. So for this I have to invite one more member. So I'll just invite another account let me logout. I have joined as a member. I'll go back to the steward account. Sorry the steward account is like the admin account for the for the project. Yeah the person who person who created the circle. Gotcha. They are assigned the steward role by default and you can you can change roles for these so you can add multiple roles to each member so I can make this account which joined I can make this account as steward. So only only the person who has this steward role can do that and each member can have various roles so you saw like this member can have both steward and member role and yeah you can assign multiple roles. Gotcha.

So here now yeah let's go to the retro. So retro is basically if you're familiar with Coordinate which is a similar mechanism but we also have like you can use actual tokens for payment and another thing is that we allow both like normal voting and quadratic voting. So let's create a test retro. We can add like a description let's say voting for this like for the month of August. We we can do quadratic voting we can decide like the duration I'll keep it for two days.

And here we can set like the the token which we want to distribute and the members who who will be part of the retro. So you can decide exactly like which member can receive votes and which member can give votes. So this this is useful when you know when you have a retro and stewards are also part of it and they wouldn't probably want to receive votes they would only want to give votes. So we have provided that customizability aspect like so that you can decide which member actually can receive votes and you can also decide like the allocation of each member. So I'll just keep it like this and I'll create a retro.

So this opens up the retro model and here you can you can actually give feedback you know just anything. So this can be used as like a retrospective sort of feedback to you know for for this month. Just give feedback and then I can give the votes and if you see like in the bottom corner like I've just given seven votes but my remaining votes is only 51 this is because of the quadratic voting mechanism. So the max votes I can only give 10 even though my allocation was 100. So I'll just do something like this and I'll save the votes.

Now I'll switch account and vote again. Feedback also like each member can give feedback to everyone and I'll just add some votes. So I'll just go back to the steward account to end the retro manually like instead of waiting out the entire two days. Ah yeah I'll end the retro.

Now once the retro is ended like you can see the feedback which you have received so I can see okay this is the feedback which I received and and then you can you can pay out based on the votes given and the budget which I had set the two MATIC budget. So based on the distribution of the votes that will be you will get like based on the distribution of votes it will distribute the budget which you set initially. Now here so either you can pay using your your MetaMask wallet or you can pay using Gnosis since we have added our Gnosis safe I will do this.

So we just need to sign. It says transaction has been sent to the safe so we can actually take a look. And sorry I might have missed it but can you set it to pay with any token or is it just set to MATIC? Yeah so basically if you go under this payments in your circle you can add any custom token you want. Right now it's only MATIC and wrapped MATIC but you can just paste a token address which you want to use and yeah you can use it everywhere for task payments, for retro payments, anything. Cool.

Okay yeah this I already done. So I was on this... so if we see yeah we've got this transaction. So I can execute it and this will pay out the you see these values which which we got in the actual distribution so it will pay out to the addresses. Yeah I guess this will execute. I think that's it I think I've finished just in time for any questions and Q&A.

Yeah this this is amazing gang. This is like quite feature filled and basically a one-stop shop from what I've seen for for DAOs to come and basically set up their workstreams, their their projects and reward contributors. So how does it kind of play with like a token gated community like Developer DAO for example? Like who is it up to the budget or sorry not the budget the steward rather to invite people into the the project or is there some magic between the Collab.Land bot basically to allow only those holding the specific token to enter the project? Or is it like a manual thing now?

So there is no token gate right now but it's definitely something we're working on but you can use Discord role. So you can set which Discord role gets exactly what permission so I added the Discord bot to the server right then I can select like which role should be allocated like this member on I mean this role on the site. So what happens is like when you get that when someone from the Discord server with that role comes to this this sort of page then they can there'll be this option to join the thing and once you do that you are automatically assigned the role. So the steward doesn't need to do anything like the members can join without any supervision like since you've set these roles. Gotcha.

Yeah awesome awesome. Any any questions from the crowd? Also if you can't speak feel free to type your question I can read it up to the crowd here. I guess if no questions another one for me so is is the Spect Network open source and if so how can Developer DAO members here help you continue to build this build this out?

So this current version is actually not yet open source. We our previous one that we built it's it's open source but this one I mean if someone wants to help out we can like like access is pretty like like we can give access it's not a big deal. We've just not yet open sourced it because there yeah like want to get to stable version and then sort of open source it before yeah. Like if someone wants to contribute definitely we're looking for like to add members to the team as well so if you are looking to work on a project definitely reach out we will give you access.

Yeah awesome awesome. And I guess what what was your what was your inspiration behind starting this starting this project? Like what what was a gap that you saw that made you inspired to kind of get this going?

Man like I think the biggest inspiration for us was we really just wanted to like work in Web3 full time and especially like in DAOs but right now the thing with working in DAOs is that it's like a lot of things like the compensation itself and also like what what exactly your role is what sort of stuff you'll be working on it's I mean we're still figuring all of this out right like as a DAO like it's it's not as clear as the traditional organization you know so basically what we were trying to do is like get it to a place get DAOs to a place where all of these questions are like answered like very clearly for like new contributors coming in and like what sort of stuff they can like do in terms of like like even starting their own project all of this stuff you know so yeah that that was the main motivation I would say is sort of to like yeah start work start doing that ourselves and and help others also to to be able to do that easily.

Gotcha. Yeah yeah fantastic work here gang. We're pretty much closing in on time but are there any questions any final questions here from the crowd? Going once, going twice, sold. So what's the best way for people to to follow the progress here? Do you have a a Twitter Twitter account or any other way maybe a Discord for Spect Network that people can join to follow?

Yeah we actually have a Twitter and a Discord maybe we can share it on the chat.

Yeah for sure. Yeah that would be awesome. All right if there are no further questions I want to thank AVP, chakra and Reshma again for coming on thank you so much for taking the time to share your awesome project with all of us really looking forward to seeing Spect Network grow here. And with that I want to wish everybody a very happy Friday, happy weekend and that will see you back here next week. And I will be dropping a link in the chat as well as the DevNTell channel itself to claim POAPs for attendance today. And Spect Network team I will be sharing a special mint kudos with all of you shortly. But with that I will stop the recording.