# JuiceboxDAO Town Hall July 5, 2022
### ENS name as project handle by @peri
**peri**: Thank you. Yeah, I wanted to talk about the new project handles that we now have for v2 projects. Folks have been talking about this for a long time, it's definitely been kind of a shortcoming for projects so far. Now it is fixed, this is awesome. So for anyone who doesn't know what I'm talking about, for V1 projects, for all projects before the V2 launch, projects have handles which means you can search for them when you go to the projects page and you search for a project. That's the keyword that you can search for and they show up in the search results. For v2 projects, We decided not to handle handles on the Juicebox side of things. We were kind of waiting to implement another solution later, which has been taking some time, but that's finally done. And so the benefit now is that for projects that add a handle (people can add handles change handles whenever they want), you can now search for those projects. Those projects will show up with a handle on the Juicebox page in various places where we show labels identifying projects. And and you also have a cool URL. So instead of going to like /V2 /p or slash some number you'll be able to go to slash @ your projects handle so it'll be something like [juicebox.money/#/@jango](https://juicebox.money/#/@jango)
If you own a V2 project, you should be able to go to that project, and have your wallet connected and see a button that'll just ask you if you want to add a handle right at the top, or you can go to the project settings and do it from there. The way that it works is very cool, We're using ENS names to manage the project handles.
Part of the reason we didn't implement a Juicebox handle solution right off the bat for v2 projects, is there's a lot of complexity that goes into making sure that handles stay unique and they can be transferred. With V1 projects. There's some strategy built into the contracts to allow handles to be exchanged and just add some extra complexity. Since ENS names already manage this really well we decided to build around ENS names.
The way that it will work for V2 projects is that if you own an ENS name, I'll use Peel for an example, we don't have a V2 project but let's say we do and we own peel.eth. So we would in the form to set a handle for your V2 project. Step one is to just set which ENS name you want to use. So we would use peel.eth which would translate to @peel on Juicebox. And then the second transaction would be to set a text record in that ENS name pointing back to that V2 project ID. In the Juicebox UI we make it really simple, you just type in the ENS name for step 1, for step 2 you can just click a button and we set the text record for you automatically. It should make sense to everybody right off the bat if you check out the form. If you got any questions we can keep improving it of course. If you've got a V2 project go setting handle for it, it'll be really fun and awesome.
**filipv**: Is there any reason why we can't also do searching for project titles, like the the metadata titles?
**peri**: Yes, and it's kind of technical and just comes down to the fact that all the the project titles, project names along with things like the description or the Twitter handle, we store those in a JSON file on IPFS, and we don't have access to the data. They get stored in that JSON file in the Graph, which is what we use to index projects to be searched for. So it's just kind of a technicality that we can't get that data over there. And so doing it this way allows us to effectively store the handle on chain. There's a Juicebox project handles contract and you can go to look up the handle for a project. If both of those two steps match, basically if you're pointing to NES name that has a text record matching your project ID, then that is effectively your handle as far as that smart contract is concerned. Since we can put it on chain, then we have access to it in the Graph and then we can search for it.
**nicholas**: What happens if you go to an ENS that isn’t associated with a project? Would be cool if it had a primary wallet associated, it shows what projects that address owns tokens in.
**peri**: If you go to an ENS that isn't associated with the project, it would basically just be that this project doesn't exist. You'll get a 404 page. Yeah, there's not really any need to think of. You do have to own the ens name in order to use that handle on Juicebox. That means only one project could ever have a handle matching that ENS name. There's no other real integration of ENS name into Juicebox right now. So it's not like there's any lookup for just any arbitrary ENS name.
**0xSTVG**: Is this also available on testnet?
**peri**: Yes, you can do this on your Rinkeby site. You can go to ENS domains, connect your wallet to the Rinkeby network, buy ens names on rinkby and you can go through the setting-a-handle flow on Rinkeby.
**Mieos**: What happens if your ENS expires?
**peri**: Good question. If your ensname expires nothing will happen if your ENS name expires. Basically, your handle is yours, so long as the text record on that ENS name is still pointing back to your project ID and your project is set to use that ENS name. So these two records have to match. If at any point one of those records doesn't match then that will no longer be your handle. So if you're ENS name expires and someone else buys it and they remove that text record, then you will no longer have that handle To that extent you can also have an ENS name owned by somebody else, you could ask them to set a text record to point to your Juicebox project, then you can use their ENS name as your project handle. I don't know if anyone would do that, but you could technically.
### NFT rewards with @jango
**jango**: All right. From one dope project push through the finish line to another project well on its way going through similar processes to project handles did maybe a week and a half ago. What the current status is that we have a sweet contract that was originally written by Mike and @tankbottoms DS integrated that handle, and it's adapted now to be hyperspecific to StudioDAO's needs which is basically what was originally written. Originally we had three different adapters you could plug into a base contract that would give you different types of sales and auctions. Instead of doing the full formalization process for all of them with tests, we adapted the one with similar to what StudioDAO needed to solve that specific problem. In so doing, we'll create pretty easy process to do subsequent versions if anyone is interested in not having the exact same NFT delivery method as written in this contract but with slightly adapted rules, that should be easy to put together. I think tests are well on their way. I understand it's like pretty much good to go except for some slight details.
**0xBA5ED**: Yeah, so I think it works pretty far, except coverage isn't working for me. So I don't have the exact numbers on how many lines we haven't tested yet, but I think the majority of functionalites we have tested. we just need to do the deployer and maybe some end-to-end tests.
**jango**: Sweet. So the depolyer being the last bit that was written this morning, it basically allows the user or someone to launch a project via proxy. They'll just send all the data from the regular deploy plus all the data to create this NFT tier distribution system and tie them together into one depoly transaction, which is very convenient from the performance perspective. And we've got to wrap up test for that. I think the front end is chilling. I don't have JohnnyD in the call to do an update. I think for the most part it's good to go. He is waiting on a testnet version of this. So we'll look to have a version of that up to him in the next little bit of time hopefully. Timelines are weird, but thenI still have to write the the documentations to make sure there's nothing leap in just one more path through but on the finish line here.
So @kentbot thanks again for patience waiting forever for this. I think everyone here is very very excited and stood for StudioDAO and enabling those initial use cases and scaling from there. And I think at the very least like we'll put a system in motion here that can fulfill the vision and support it without a lot of consistent baseline dev work.
**kentbot**: Totally thank you all we're super excited and this is gonna be great. So just let me know what we can do to help test or other stuff. We're here for that. We can take that offline, but definitely with folks here who are ready to get involved.
**jango**: Cool, perfect. Yeah, I think that's the only update there. Anyone have questions about that project.
**nicholas**: Kenny do you want to give like a one or two minute description of how you're going to use this feature and what you're doing?
**kentbot**: Absolutely. Yeah, there's two different things that we want to do with this at first. I'll just drop this [link](https://www.awn.com/news/nft-financed-unlikely-love-stories-anthology-moves-forward-studiodao).

We made this announcement of the first film that we're working with the first filmmakers, and so we have a couple of mint passes essentially that we will be selling if you donate. I've to work out the final tiering here, but we're talking this through with @dropnerd, and actually @peri has gotten involved also, just kind of helping us think through this stuff. It's like 0.01 to 0.1 given the market, you'll get one tier of NFT, and then there'll be a second higher tier for people who want to participate at a greater level. Those things will become mint passes to then get you access to a bunch of other things including additional NFT drops associated with the film, access to the film itself and some other stuff that we'll figure out. So we're going to start one Juicebox project for the film, and then I think we're going to start a second Juicebox project for StudioDAO itself as essentially like a maker token to come in and support the overall initiative. I think those are the first two and then we'll be building essentially a governance stack around those NFTs. There's stuff that we want to do with the ticket generation capabilities as well, I'll kind of put a pin in that if anyone wants to go deeper on how we want to use tokens and tickets in combination as a governance game. I'll be happy to have that conversation and have that debate. I know there's a lot of good thinking around that on this call, so I'll leave it there.
### Governance changes with @filipv
So I think many of you saw the the proposal I'll put a [link](https://www.notion.so/juicebox/Governance-Process-Amendment-5-5bbdea67ef664862b3e2b2d066b0612f) to that on recent governance changes.
- The temperature check freeze no longer takes place so you can edit proposals for the whole temperature check.
- The emergency governance process has been removed.
- There are some language changes which specify that proposals must clearly state multisig actions to be deemed executable.
- There's another important change that the quorum on Snapshot has been updated so you now need 80 million affirmative JBX for a proposal to pass.
**nicholas**: Would there have been many recent snapshot proposals that we have failed this new quorum requirement?
**filipv**: Up until the funding cycle in which I submitted that proposal, there isn't any, but a few of the more recent proposals would have failed under the new quorum. So I think actually the proposal to change the governance process would not have passed under the new governance process, which is kind of funny. It shouldn't affect too many proposals just to kind of keep the quorum at a point where only proposals that the DAO is more enthusiastic about will pass.
**jango**: So kind of creates the bias of being a little bit more conservative unless there's active people voting. right so it's incentive for folks, too.
**filipv**: yeah exactly. There have been a few proposals in the past where you know people maybe are not as enthusiastic about it or it's kind of controversial. So not many people vote and then a pretty small majority ends up being able to swing the vote on those so it's kind of a resilience and natural resistance against those proposals which happened pretty infrequently, but good to have for when they do happen.
**tankbottoms**: I have one question. So quorum means minimum number of affirmative. It's not the total. Vote number, right? like For and Against.
**filipv**: Quorum might not be the best term for it, but it's the minimum number of affirmative votes you need for a proposal to actually be deemed as passing. So even if you get the 66.6% threshold if you don't get 80 million JBX voting yes on your proposal it won't be considered passing from now on.
### Updates on BuidlGuidl and Code4rena by @nicholas
**nicholas**: I have two quick updates.
One is about **BuildGuild**. We decided today to extend the hackathon, Austin from BuildGuild thought maybe we could get more participation if we had a few more days not over the long weekend, for many people in North America. I kind of agreed and we decided we would extend the hackathon till July 14th rather than July 7th which was the original end date.
We did a little Twitter spaces today, and we're going to do some kind of live build on YouTube. I'll meet up with Austin tomorrow afternoon at one o'clock Eastern time to do something on top of scaffold-eth, maybe some NFT thing. And everybody's welcome to join that. I think it's intended to be two people, but I think he just does Zoom calls, So if anyone from here and wants to hang out for an hour to building something that'll be tomorrow 1:00PM.
And there's already two or three projects that are active so you can check out the [link](https://info.juicebox.money/dev/hackathon/) that @filipvs shared in Town Hall to see more information. There's an active [Telegram group](https://t.me/+3tlE2ae0475hMDcx) if you want to join. 10,000 bucks at stake and we'll be voting through the JokeDAO token vote next week on July 15th. So do participate check it out.
**Kmac**: 17th would be better than 14. Get another weekend.
**nicholas**: Yeah, I think we didn't want to make it so much longer than originally intended. So anyway, we're gonna stick with probably what we changed today. In any case it's not like a huge grant that we gave to support this like ten or twenty thousand dollars depending how you look at it. So in a way, we're kind of learning about how to run these hackathons. I think it has been successful so far in leading a bunch of BuildGuild people into thinking about Juicebox at the very least.
Second update, [**Code4rena audit contest**](https://code4rena.com/contests/2022-07-juicebox-v2-contest) is underway. We've got one report today of something that sounded like it's an interesting one. It's privately reported and we won't get public disclosure of the majority of the bugs until after the contest is over in three days time, so that we don't accidentally share information that allow other people to file the same security vulnerability reports, which would then cause them to split the cash, so sort of secret until the end of the competition in three days.
It's been interesting but very annoying to run from my personal perspective, a lot of duplicated documentation over our docs and handholding of them not so much the wardens but more the sort of administrative process. But I think it's going to be valuable for turning up at least some vulnerabilities. It seems to have already turned up one one minor vulnerability that would be relevant and could cost people money. So that's pretty cool.
Also spreading the good word about Juicebox protocol was actually part of the rationale in the [Code4rena proposal](https://juicebox.notion.site/Sponsor-Code4rena-Audit-d254baa7d6e24c0d83997a8ca0f31dfa).
**jango**: Also it's cool in that case the volunteer or the warden volunteered to help out after the fact doing one-off reviews of the extension work since they seem to understand the protocol the base pretty well. Instead of going through separate orgs were definitely has its advantages of going to code4rena and instead of continuing with the same people reviewing stuff over and over again, which is kind of what we do internally for contract reviews. I kind of like the process we're converging on which is like folks tend to have their own area of focus, but everyone comes in and lends their time as a project is leaning towards the finish line and maybe we'll do one of those at a time.
But it is also nice to have a third party reviewer just for sanity sake. It would probably be unwieldy to run one of these competitions every time we want to ship new contract extension codes, which tend to just be bite-sized but definitely have vulnerabilities and definitely depend on how the basis is organized.
I think this effort is going to have a couple of interesting side effects like this that might turn out to be more valuable than the thing itself. Although who knows, any vulnerability caught is incredibly important. I bet if we like poll people in general how they'd want Juicebox to spend the funds in its treasury, the majority would say risk aversion and safety and stuff. That's largely what we offload for people.
And thanks @nicholas for organizing and dealing with the bullshit and pulling it off.
### Update on Immunefi, Legal opinion letter, etc. by @filipv
**nicholas**: Oh, yeah, at least I hope that's what they would say. I don't know if there's people would probably vote for us. It's good market on centralized exchanges or something. @filips can talk a little bit about [immunefi](https://immunefi.com). For people who aren't familiar with the order of operations of these audits, we've learned it's kind of best practices. To do like traditional audits, you pay somebody, as we've paid Certik, a bunch of cash to just review the contracts; then you do something like the code4rena, where a bunch of people look at a big amount of money that they will be split according to the judges voting system that they have inside code4rena. So lots of people can independently and permissionlessly come in and just look at the code, try to find vulnerabilities and win some of that cash. Once the protocol is up and you feel like you've got most of vulnerabilities caught, then the final step is to do an immunefi, which is bug Bounty where you have essentially an alternative path if somebody finds a bug that they could exploit the protocol for cash. They have an alternative way they can get cash immediately without a negotiation, according to some predefined security criteria. And it's a nice way to turn black hats into white hats. And @filip has an update on that.
**filipv**: Minor update just to make sure people understood where we were in the process. So we've been going through with the immunefi people trying to put all the docs together, shout out to @nicholas for doing a ton of that work. Right now we're just dealing with getting some of the contracts for v2 fully verified on Etherscan. So right now there're what's called similar match contract verified, which means basically that the byte code matches but the constructor arguments haven't been verified. For a few reasons, which I don't want to get into, you need to actually like reach out to Etherscan and then get someone approve to verify these types of contracts. @jango's been going through that since he deployed those contracts, but hopefully we should be able to get that done and then get **immunifi** up and running soon.
DAO-lawfirm stuff is moving ahead slowly, @Aeolian asked about this, so I just wanted to share a brief update. Right now, we're kind of going through drafts of the contributor opinion letters. A few opinion letters were already put together regarding like intellectual property law, which has been distributed to some WAGMI people. The opinion letter we're working on now is mostly focusing on securities law that applies to JBX and Juicebox tokens. It should be coming out fully sometime soon. In general we're working on that.
Last brief update is on user docs. I put out [a brief guide on how to configure Juicebox projects](https://info.juicebox.money/user/project/) and there will be some more docs coming out soon over the next week. If people ask for how to configure projects you can send them here and I'll be rolling out a few over the next week or so. They are about very simple stuff like how to get Ethereum if you've never used crypto before, how to set up a wallet, as well as docs on like how to set up a Discord server, how to make a Notion workspace with templates for those things.
### Marfa Giant by @ONNI
**Onni**: First of all, Thanks for giving the time. I'll try to be real fast because I know the meeting is super packed today and thanks for all the support that I've got from this community to date. I just want to talk a little bit about our two projects out here in Martha.
I know some of you are familiar with Martha and some of you are not. We are a very very small town about 1,700-1,800 people on the Texas-Mexico border. About two years ago, I started the idea of starting a publication based DAO here for a variety reasons that we can discuss in-depth of different time. So I set up [**Martha Giant**](https://juicebox.money/#/v2/p/26) DAO, which is a Gayo concerned with putting out a monthly magazine along with a very very robust web presence so on and so forth. In the process of doing that, we needed an office space. So we wound up renting sort of a derelict Adobe Casita pretty close to the center town. Anyway, that sort of spiraled and I became aware that about a year ago some people in this group were looking at starting an art space DAO run operated in Martha themselves. I thought that idea was really cool. I don't personally have the ability to execute that entirely, but I thought our office can be kind of like a cool data test for that. So I set up [**Marfa Mini**](https://juicebox.money/#/v2/p/63), which is a second DAO which is now an LLC. It's insured. We have a building with Wi-Fi running here. It's pretty cheap. It's about 800 hours a month in cash of rent. And DAO's first tenant is Martha Giant, our publication. The idea is to go from there and keep it very simple, maybe like five workstations around the place go to different software packages for different kind of building creating type enterprises, and take this very small project and use it serve as a sandbox. So the idea is to use this to test our running community space, and we can use this to test how operating as a DAO legally works in the state of Texas, which is something that I learned a lot more like here to about over the last three weeks. It's opportunity. So our contracts with tenants is something I think can really grow organically into a project that's much larger. That's my very short elevator pitch.
**jango**: So what's the time frame of the publications that we're after. Can you talk a little bit more about the content and the process for that?
**ONNI**: Yeah on the publication side, it's kind of extensive background in this. I'm an incrementalist by nature, I like small steps. That's kind of become our team philosophy. So the first step for us is putting out a weekly one-sheet printed listing of events and art shows going on about Martha. That's kind of gives us a Shakedown Cruise as far as design gathering content and distribution. We are very deep into that Shakedown Cruise currently working on printing that. We're putting that on a recent graph machine, which is this kind of funky replicator that doesn't work with toner but works with ink so it's somewhere between a printer and a printing press. So that's going on right now. The next step after that is going to be launching a website where the content will update daily. We are looking at the third week of July for that, and we are on pace with the web design right now. We just have kind of a holder page up that actually has all these go to the marfagiant.com. We'll have all these dates outlined and then we are looking at playing the first issue out in September. I believe originally we were looking at doing a September 23rd. I now realize that there's a large festival down here called the Trans-Pecos Festival of Music + Love it's large for Marfa which is a few thousand people and I think that would be a better day to launch the print publication, via just a national influx in the place so we can get the word out.
**jango**: But are you talking about the the physical distribution of the publication?
**ONNI**: It's two angles to that right. So in town it's gonna be very very simple in town. We're gonna you know drive around with a pickup truck and drop them off at a series of locations that we have, as agreed to carry them that's something you know, we're kind of working out with these one sheets is providing us a much smaller run of talking to the business owners getting okay for distribution and actual delivery, nationally and internationally gets a little bit trickier. I've applied for a second class mail license, which is the appropriate USPS item for shipping them. And again, we're talking about the hard copies. Obviously the web distribution is different. I think we're gonna wind up subcontracting that out to our printer, we get the license number and give it to them and then they do the actual order fulfillment.
Likewise, we need to be able to take orders over the web and some of this is why I'm talking to y'all today, I need help with that stuff. I can figure out a way to run it through zappy or whatever, but I probably talked most efficient way of taking web orders. So that's why I'm talking right now.
**jango**: So a little bit of my my involvement into Martha a few times, fascinating place. I really like the idea of figuring out how to leverage a Juicebox treasury and build the community that's centered around a very small and scoped physical experiment, like managing his physical space, a community oriented space, and what are the pitfalls you tend to run into, or in like which opportunities exist that otherwise won't exist running such a project in a more traditional way.
What can we learn from from how co-ops have been organizing for the past while, Martha's super out there. So it's interesting to consider how how we might experiment with some of these stuffs and kind of the fringes of how regulation works and what we can sturdy up in so doing as we practice some of these things and learn while doing.
**ONNI**: Yeah, I think the other thing to add and it's kind of Machiavellian, but someone important is yeah Martha is very very out here and very isolated. we want to send out a press release, you know, we do want to market and publicize it's easier to get stuff picked up coming out of here. You know, it's a little bit of a moral fine line and I think we have to be careful not to be exploitative of the town, but the name definitely does carry some weight.
**jango**: Sure. Yeah, if we're tending towards a community operated version of this to an extent, can you involve the town's people and it's it's like an contributing in part ownership and in the journey I suppose. Yeah, we the anal from an and a few perspective art blocks has their first Gallery like in our life Gallery there, which is the reason I was there last year with a few others. I think we're on the call @mieos, @peri and @nicholas. So it's an interesting spot. Who knows, but thanks for sharing @ONNI. Thank you for wrapping your head around all these tools and being excited about them and trying to put them to work in a very unexplored domain.
**ONNI**: Thank you again. I really appreciate the support from everyone for me. It gives me a little faith in humanity also. Thanks guys.
### Marketing by @Felixander
**Felixander**: Yeah, so I actually just wanted to get some opinions. So at info.juicebox.money, there's the [blog](http://info.juicebox.money/blog). I have been trying to kind of teach myself a crash course in like basic SEO stuff, and I guess one thing that's important is having these kind of little ecosystem articles. So it's a five article series that they all kind of link to one another and if you go to the blog and look at it, they're there. So the most recent thing was my interview with @Mieos. I was thinking @mieos by the way you were terrific interviewee and then under that there're these five articles. So I wrote them with kind of SEO in mind and did you know kind of keyword research and things like that? And I guess the idea is slowly organically they should eventually hit on Google and things like that. The question is if this is a worthwhile endeavor to kind of keep doing? And with SEO stuff, apparently you don't know that very quickly and it takes time.
Also my other question was with Juicebox High. @nicholas and I, we chat about this a little bit. I don't feel like the goal is for us to go up against like ethereum.org and produce the same content. But at the same time it seems, for onboarding, itt would be really nice to have content like the infographs @sage and I have worked on articles like this. And so I was thinking Juicebox High could really be something for people who want to make a project and it's just like a buffet of all the information they could want. Maybe there's an article like, "do you have a traditional nonprofit? Well, here's how you could turn that into a Juicebox project", questions like that are answered with articles or with explainer videos by WAGMI. I know @Mieos and @turtula thought about that, too.

My question is whether we should collate all that data into like a landing page that could be stylized like the markups we had for the Juicebox High. If people think that's a way to go or if I should just keep doing the blog stuff this way. Right now in the blog, as you can see, there's just a long list on the left with a lot of titles. It's not really the organized by subject. It's like a wall, right?
**nicholas**: Yeah, I like the idea of like an information hub. I think the visuals of the blog could be improved and possibly there is some SEO stuff that needs to be improved for it to actually get picked up on Google. But because I imagine it's not a docs or not index the same way actual CMS (Content Management System) blogs are indexed, but I think something visual would be great. I think the general idea makes sense that there be information hub full of resources content to help people understand Juicebox. I think we could be a little sharper not relative to your recent work, but just in general about making sure that it's actually reaching the people we think it should reach and we're not just doing for ourselves. So yeah, I think visual experience and using the ethereum.org as a model makes a lot of sense.
**Felixander**: Follow-up question because we were talking about marketing practices and @filipv used to feel strongly about not using paper clip strategy. Right now it doesn seem like people hardly find Juicebox through Google. The question is whether we are we okay with that. And if not, do we want to really start marketing toward that direction, or do we have thoughts in general of what direction to go there to reach more people?
**filipv**: I think it's very difficult, especially with something like Juicebox. If you get in like an Instagram I had for juicebox.money and you don't know anything about Ethereum or crypto and you open up the website, I find it a bit of a long shot to imagine that people would figure everything out and go through that. Maybe that's something can be worked on, but just in general I think that the best way for achieving growth is just having really great projects and helping people set up cool projects on the platform, because when people are passionate about something that tends to be the first motivating thing at least for for onboarding. So my perspective on this question is that I don't think paying for Facebook Ads or whatever would be very effective or effective at all for juicebox.money, but I'm open to other people's perspectives on that.
**Felixander**: Yeah, I don't know either about paying for ads. I think this will be a question when we really start having more payment terminals, and when the bar is so low that you don't only have to contribute with Ethereum. You can take Visa payment and so on. At that point, I think there's a logical argument to say we want to blast it out to people, because it's much more the hump is easier to get into it. I know we're not there yet, it's just a question of whether we should build in that direction. I'm pretty ambivalent quite honestly, but I think once that bar is lower, there's an argument to be made. That might be a good way to go at least to get outreach.
**flipvs**: Very true. Yeah, I think that's fair. But I will also say, I think that pursuing project creators will always be the best thing. If you have a platform where people can set up treasuries and accept payments you kind of have the ultimate affiliate marketing, because people want to promote their own projects. So if you can get people who are creating really great compelling projects on the platform, I think a lot of that stuff will end up taking care of itself. So if we were to go for some sort of more traditional style of "marketing", I think aiming towards project creators and making that process as easy as possible would probably be the most effective way to do that.
**Felixander**: I agree completely. In terms of the articles I've been writing, the goal has been for potential project creators. It's just a matter of hoping that that somebody sees it. But I agree with you and that's where I think we could diverge from something like ethereum.org. We don't need articles like "What is a wallet?" or "What does a blockchain mean?" I don't think we're gonna get anywhere doing that, but questions about different ways to use a project, use cases and maybe even videos that show those differences, I think those could be really powerful. When we get somebody in, they could see, "Oh I can really enact my vision on this platform and here's a really great guide that lets me do that."
**nicholas**: Yeah, I definitely don't think we need to replicate what's-a-wallet type of content. It's really just about Juicebox protocol, right? I'm a little wary of how short people's attention span is in creating content. I feel we need to measure what content actually engages people, both the quantity of people and duration of engagement. I think people don't like to read things, and we're not a big corporate thing, we don't need to just produce content. We needed to succeed. So I feel like measuring some of that stuff. I'm a little uncomfortable with how relatively bad our Google rankings are and actually want that. I think probably the DAO's vibe is not to pay for marketing and I agree with that overall, but one thing to note is if you look up any NFT collection's name right now on Google, Opensea has the sponsored keyword for every NFT collection and it's gonna do work for them. So keywords like "crypto crowdfund" may not be the stupidest thing to actually pay marketing for. Essentially, I think it would not be stupid because our exposure is to a very small part of crypto Twitter and there's really lots of people who are going to be considering crypto fundraises will never have met any of us, so it might not be silly to think about actual marketing. I think that we talked a little bit about SEO now and then but I do think it would be good if we rose in the Google. I think there is value in it.
**Felixander**: I agree with you. I think one way to do that is with a PPC strategy, even though I agree that doesn't seem to be with the vibe. At the same time, I mean if you look at the [fathom link](https://app.usefathom.com/share/umyovgdg/info.juicebox.money#/?filters=%5B%7B%22property%22%3A%22Path%22%2C%22operator%22%3A%22is%22%2C%22value%22%3A%22%2Fblog%22%7D%5D&range=last_7_days&site=2251799829001774), we're just not really getting a lot of presence in Google. I think we should and also I think it's kind of dichotomous because on one hand Juicebox. When you look at the biggest fundraisers like ConstitutionDAO, AssangeDAO, those were so huge, so I feel like it doesn't make sense that we wouldn't have more of a stake in Google search results. I think that is something we can try to address. I also want to make clear that I don't think there's a need until actually we have multiple payment terminals where we can accept Visa and so on. I think once we can accept those things just from a point of view of getting more business, then it makes sense to aggressively market and get project creators that previously might say "I don't want to mess with ethereum or whatever" now they can immediately start their project and run with it. I think that that's a very powerful thing that we should get out there in the world.
**nicholas**: The analytics link that you shared the fathom. Is there a version of that for info.juicebox.money. Is it all under one link? Is possible to differentiate?
**filipv**: https://app.usefathom.com/share/umyovgdg/info.juicebox.money
**Felixander**: I'll see if I can mess with the Juicebox High a little bit and maybe we'll try to get something started there. That would be fun just to maybe collate some information we have.
**neodaoist**: One side that I had as we were chatting about this is in the interest of getting more project creators. I imagine that there probably are some things that people are searching with an active intent. @nicholas, you mentioned "crypto crowdfund" and things like that could be valuable over the time to build up some SEO rankings for. One hard part about SEO is that it does take so long like mentioned by @Felixander. You don't know if those are good keywords until a long while later and you've been ranking.
And you see what that traffic is doing if it's measurably having an impact.
So I just share one thing that's worth for me in the past, which is maybe something that could be an idea to try. You basically run PPC for a short amount of time on very generic keywords, and you track which keywords drive the impact. So you could bid on crowdfunding, and then watch which long tail keywords convert like maybe filling out a form or creating a project. So it's something like we bid on "crowdfunding" and "fundraising" and then we noticed well, nobody converted on crypto crowdfunding, but people really converted on ethereum crowdfunding as an example. So you kind of watch which keywords in a data-informed way actually convert and then you stop PPC because that might not be the strategy and then you try an SEO for those keywords.
So it's kind of like a PPC as a means to an end to get a little bit more data from the marketplace of which keywords may be valuable for us, before we invest in the content marketing three to six month lead time to actually rank and hopefully get measurable impact of onboarding project creators through organic, right?
**Felixander**: Oh, just throw out there also that PPC campaign is not very expensive. So I also do feel if we're just talking about a couple hundred bucks every month or two months. It's almost like why not just try it. That's kind of where I'm at with it.
**neodaoist**: It all depends, right? I'm sure I could bid on death metal keywords for cents, but if I bid on like mesothelioma keywords, they're like a thousand dollars a click or whatever. Because crowfunding keywords are financially related, typically they're on the more expensive. But it's been a long time since I ran ads, I just want to share that thought. It's an interesting conversation to be sure.
### Quizz time
Two truths and one lie

The answer is ...
$$Felixaner$$
Basically the above are all true, except that he defaced a 250 year old painting.
### Juicebox necklace with @jango
**jango**: So we have these sweet necklaces that @Sage's sister makes and she reached out to see if anyone else will like one because she's got two pending orders and she's gonna make a bunch. So I tweeted it out this morning, info can be found in [this tweet](https://twitter.com/me_jango/status/1544369856912424961?s=20&t=lhJfTjFioc6yFyEBUD6Gsw).

I don't really know the best way to get if you want one, @0xSTVG suggested maybe putting up a slice store for these that'd be tight.
I suppose if you want one of these sweet handmade metal work Juicebox chains, you should definitely reach out to me or @sage and we'll make sure to get you in that batch. I've got a silver one right now. It's tight. And the gold ones would also be sick.
**filipv**: I think the best place to reach her is at [@mesa.teal on Instagram](https://www.instagram.com/mesa.teal/). So send her a message.
### Lexicon Devils' new project
**jango**: We should do another hangout Town Hall session in the voxels room sometime. They're also working on a project that I want to hear more about, which is called [Forming](http://forming.lexicondevils.xyz/), they have [a Juicebox project](https://juicebox.money/#/v2/p/66) for it. Maybe next time we could nudge them to talk about it or something.




Sweet sweet. Well submission will be close exactly a week. It sounds like something we should pay attention to.
**brileigh**: I'm really looking forward to what they'll make out of this. We were talking about it a little bit at the end of the podcast that we did with Lexicon Devils which should be coming out soon. They said it was kind of like coming full circle on their learning experience of Juicebox to have this music event in which they have live performers. They set up a Juicebox project, they fund and pay out those music artists that are playing at the Juicebox event in cryptovoxels. So I think it's really sweet of them. I'm really looking forward to seeing how it all turns out.
**jango**: That's super cool. Yeah, this TLDR on their site is also very nice.

I bet they would use the NFT reward stuff for sure. Also, I'm so excited for that feature to be out there. And I am very much looking forward to that podcast, too.
They're definitely **unsung heroes** of Juicebox and they carry a lot of attitude. They destroyed the month of June that was so well done. They threw some pretty great events.
***
:bulb: Archives of JuiceboxDAO Town Hall can be found [here](https://hackmd.io/@zhape/jbx_town_hall_archive)
###### tags: `JuiceboxDAO Town Hall`