12 篇博文 含有标签「update」

New website just dropped for the Juicebox Protocol

After countless workshops, discussions, and pull requests, the website for juicebox.money is now live featuring the new homepage, About page, and Success Stories, as well as some exciting new features like improved search and project tags. The new website was made possible by PeelDAO, the front end team building and maintaining juicebox.money, and WAGMI Studios, whose juicy artwork is featured throughout.

You can follow along in the video below or in this article.

The Homepage​

Let’s get started with the homepage. At the top we’ve got a call-to-action: create a project and Fund your thing. And right below you can see a few trending projects built on Juicebox, so you can browse what creators are building and find some projects that align with your values and interests.

Hero: Fund your thing, trending projects

You’ll also notice some categories at the top like DAO, NFT, and Fundraising. Those are a new feature: Project Tags! So for example, if you click on DAO you’ll be able to find projects that have added that tag. You can also use tags to filter your searches. Keep in mind that this is a new feature and not too many projects have added tags yet. Give it a try next time you’re browsing projects.

Explore Projects​

Once you’re on the Explore page, you’ll also notice that search has been completely revamped so it’s now way easier to find specific projects or browse to find new ones. Looking for projects by Krause House? Try searching terms like “NBA”. If you’re feeling nounish you can search “nouns” and find projects in the Nouns ecosystem like SharkDAO.

Explore page

Mental Models for Juicebox​

So going back to the homepage, you’ll see a few examples of the different types of projects that you can build with Juicebox. Whether you’re starting a DAO, crowdfunding for a cause, launching an NFT project, or building something else, you can manage the funds transparently with your community.

Mental models for Juicebox

Introducing Success Stories​

If you’d like to know more about past projects that have been successful, we’ve created a new Success Stories section which tells the story behind projects like ConstitutionDAO, MoonDAO, SharkDAO, and StudioDAO. Each case study will tell you how the project got started, how they set-up their project on Juicebox, and how they found success.

Success Stories

How, What, and Why you should Juicebox​

Back to the homepage, next we have a quick summary of how Juicebox works, including setting up your project with rules to build trust, managing your treasury onchain, and building your community with token and NFT issuance. You can also find a link to the docs if you want to learn more. Next we have a section highlighting some of Juicebox’s core strengths. Juicebox is:

• Community owned
• Reliable and transparent
• Trust minimized
• Flexible
• Extensible

What is Juicy Picks?​

After that we have the Juicy Picks section, which is a new section of curated projects on Juicebox that really stand out from the crowd. These projects will rotate on a monthly basis and will be chosen by the Juicebox community. Below this section you’ll find a number of categories you choose to find a project that’s right for you.

Juicy Picks for May 2023

New FAQ​

If you still have some questions, make sure to check out the FAQ section near the bottom of the homepage.

How to get in touch​

Last but not least, you’ll see a button at the bottom to contact onboarding. So if you’d like more personalized assistance while setting up your project, reach out via the contact form or join the Discord.

Shoutout to Sage Kellyn from WAGMI Studios for the amazing art and illustrations throughout the website. Juicebox really wouldn’t be the same without it.

New hero illustration for juicebox.money by Sage Kellyn

Banny, along with a fruity assortment of new characters have been reimagined to embrace Juicebox’s new brand identity. Paired with a slick sans serif Agrandir, a font that “celebrates the beauty of being imperfect,” the Juicebox brand update keeps the protocol fresh while acknowledging its punk origins.

New About Page​

Under Resources in the top navigation bar you’ll find a new About page for Juicebox. Here you can read about our mission statement, goals, learn about about the protocol and Juicebox DAO, the contributors at Juicebox, as well as our values.

Sections of the new About page on juicebox.money

The Juicebox protocol has grown a lot since its launch in July 2021. From contract versioning and audits to feature developments like tiered NFTs, to metaverse concerts at the Juice Lounge, countless members of Juicebox DAO have shaped what it is today through its active governance. Juicebox doesn’t drink from the kool-aid, it leverages the power of collective action through its community to help passionate creators and builders successfully launch and scale projects, openly on the Ethereum blockchain.

Screenshot of old version of juicebox.money

What are you waiting for, anon? Come explore the world of community-owned DAOs, fundraisers, non-profits, and other projects running on Juicebox today.

🐦 Follow Juicebox on Twitter: @JuiceboxETH

💬 Join the Juicebox Discord

🚀 Trending projects on Juicebox

📚 Project Creator Docs

📹 YouTube Tutorials

背景介绍​

目前大家持有的 JBX 代币是 JuiceboxDAO V1 金库的项目代币。Juicebox 协议从最开始的 V1版本，到 V2，再到目前的 V3，经历了几次迭代升级。为了方便管理协议及收取平台费用，JuiceboxDAO 在每个协议版本都创建了 DAO 的项目金库，也就相应有了 V1 JBX、V2 和 V3 JBX 三个代币版本。其中 V1 和 V3 代币都是 ERC-20 标准代币，V2 则由于是过渡性质，并没有签发 ERC-20 标准代币。我们持有的绝大部分都是 V1 JBX 代币。

目前 V3 的版本控制工作已接近尾声，协议经过几次审计之后也渐趋稳定，相比前几个版本也增加了很多功能和提高了安全性。现在我们平台上的新项目已经全部是基于 V3 协议来创建的了。出于协议的日常管理工作的考虑、JuiceboxDAO 治理的需要以及 JBX 代币赎回价值的正确体现，就需要把 V1 JBX 代币和 V2 代币迁移到 V3 JBX 代币。

相关链接​

JuiceboxDAO V1 项目金库：https://juicebox.money/p/juicebox

JuiceboxDAO V2 项目金库：https://juicebox.money/@juicebox?cv=2

JuiceboxDAO V3 项目金库：https://juicebox.money/@juicebox

旧的 V1 JBX 代币地址：0x3abF2A4f8452cCC2CF7b4C1e4663147600646f66

新的 V3 JBX 代币地址：0x4554CC10898f92D45378b98D6D6c2dD54c687Fb2

迁移须知​

以下是迁移前一些大概的情况：

1. 可以在语言菜单选择中文，翻译目前基本都同步上了；
2. 会有三至四个交易需要确认（如果你有 V2 代币，会多一个交易），分别是授权迁移、批准使用旧代币和确认迁移；
3. 整个迁移大概耗时五分钟左右。
4. 迁移暂时没有时间限制，可以挑选 gas 比较低的时间或者其他自己合适的时机来操作。
5. 迁移指引的视频中文版也已经完成，不想看文字版本的，请直接去到本页面最下方。

迁移步骤​

1. 操作页面​

迁移操作在 JuiceboxDAO 的 V3 项目页面进行：https://juicebox.money/@juicebox.

在右上角的语言菜单栏选择“中文”，并点击连接钱包。

2. 代币标签​

点击页面红圈处的 代币 标签，在最下方可以看到你的待迁移代币总余额。（请注意，如果你持有 V2 的未领取代币，这里会显示你 V1 JBX 和 V2 代币的总数量。） 然后点击 迁移代币 。

3. 授权迁移 V1 代币​

接下来，会弹出一个窗口，提示我们要进行迁移授权，授权 V3 JBX 合约迁移你的 V1 JBX。点击 授予权限 并在钱包弹窗确认交易。

4. 授权迁移 V2 代币​

继续授权 V2 代币，同样是点击 授予权限 并在钱包弹窗确认交易。

5. 批准使用​

授权完成之后，还需要批准 V3 JBX 合约使用你的旧代币。因为迁移其实就是把旧代币发送到新代币合约地址，再由新代币合约相应地发行出来新代币，因此就需要批准新代币合约使用旧代币。点击 “批准”。

设置批准使用的限额，这里可以点击 “Max”，也就是你持有旧代币的最大数量。如果要分批迁移，这里填入具体迁移的数量就可以了。然后点击 “NEXT（下一步）” ，再在下一步点击 “ Approve（批准）”。

6. 迁移批准的代币​

弹窗会变成这个样子，分别是显示的是 ”授权迁移 V1 代币“、”授权迁移 V2 代币“ 和 ”批准使用 V1 ERC-20 代币“ 都已经完成。然后就是迁移的最后一步，点击 迁移所有批准的代币，并在钱包的弹窗确认交易。

7. 迁移完成​

然后会出现 ”交易进行中“ 的界面，再稍等片刻，弹窗消失回到项目页面。再点击代币 标签，可以看到，待迁移代币余额变成 0， 而你的余额中已经正确显示出 V3 JBX 代币的余额。

恭喜你！现在 JBX 代币的迁移工作就完成了。

8. 其他​

你现在点击上图的红框处 ” 添加至 METAMASK 钱包“ 把 V3 JBX 的合约地址添加到 Metamask 钱包，这样在钱包内就可以正常显示我们的代币余额了。

JBX 代币迁移流程的中文视频：

Defifa.net upends how we think about NFT trading​

The Juicebox protocol has its eyes set on the FIFA World Cup this year. A new project called Defifa is set to launch on November 5th, and will allow players to purchase NFT flags of any of the 32 World Cup teams set to play this year.

(example of the Argentina flag NFT)

Where it gets it exciting is when the World Cup starts. From the first kick-off, all NFTs become non redeemable. The treasury that has amassed all the ETH for the NFTs will become locked, as well. As each phase of the World Cup takes place, the NFTs claim on the treasury will change proportional to their finalist ranking. Midway through the World Cup, the NFTs will also become non-transferable, meaning holders will be locked into waiting for the outcome of the games. At the end of the competition, all participants must ratify a scorecard to attest to the accurate results of the World Cup, at which point the NFTs will be come unlocked and can make their claim on the treasury. So if you purchased an NFT of a team that ended up winning, redeeming that NFT at the end of the World Cup could give you back more than you paid for it. For a short video breakdown, check out this explainer on twitter.

A protocol more flexible than an olympic gymnast​

The entire defifa.net is run on the very same protocol that ran ConstitutionDAO last year, and that is currently home to a variety of projects including, including MoonDAO and JuiceboxDAO. But for Defifa, there were some important tweaks.

The protocol has no idea who will win or lose in the world cup, and who will get knocked out. While one obvious solution is to appeal to an off-chain oracle, a much more interesting one was to have the NFT holders participate themselves. When a new game has happened, anybody can submit a scorecard which NFT holders must then vote on to ratify. Doing this allows the protocol to run more purely, but it also introduces some interesting dynamics.

A game of chance or cooperation?​

Anybody working on defifa will tell you that this is a grand experiment, the outcome of which can’t be predicted. In theory, the game should run smoothly— NFTs are minted, held, participants vote and at the end the NFTs can be redeemed against the treasury with their new (adjusted by the game’s outcomes) value. But what if that doesn’t happen?

What if some people refuse to vote, or vote in bad faith? Or what if so many people purchase the NFT of a favored team, that the claim on the treasury between all those holders is actually quite small? Statistically speaking, what is the expected value of purchasing a highly favored versus a long-shot team, and when does it make sense to trade your NFT and when doesn’t it? The beauty is that nobody knows, and those that play will all find out in real-time.

Where to learn more?​

Head over to defifa.net to learn some of the details of each game phase and to see the NFTs offered. To hear a short podcast episode with the defifa.net creator, jango, head on over to spotify. And if you’d just like to hang out and say hi, come to the Juicebox discord and feel free to ask any questions there.

On Tuesday, May 3rd (Wednesday May 4th local Chinese time), some Juicebox members (including jango, Zeugh, peri, filipv and your favorite author, to name just a few) engaged in an open discord call with Chinese-speaking JB community members and contributors. This article recaps some of the main points discussed. Also a huge shout-out to Zhape for his excellent on-the-fly translations!

Translation needs​

The translation efforts are coming back underway as JB has overhauled its documents over the past few weeks. One area of concern was in how to best achieve accurate translations that can be written engagingly. The need for accurate translators, particularly who are comfortable working from English to Chinese, was underscored by Zhape. If you are comfortable translating into Chinese fluently and would like to contribute to translation efforts, reach out to Zotico in the #translation channel.

Guerilla Marketing Campaign and Community Building​

Zeugh gave a brief highlight of some intended efforts at marketing and community building. Currently, there have been discussions to send some Juicebox contributors to Crypto or NFT conferences where they can network and spread the word about Juicebox. Possible eventual speaking opportunities at conferences, or sponsorships of conferences, are also being discussed, but at the moment the goal is to start small and see if we can spread the word about Juicebox and make meaningful connections between communities, or create opportunities for people to open projects on the Juicebox platform.

Translating outreach/community content​

One area discussed was the importance of trying to make it a priority to translate into Chinese blog posts, interviews, or other materials that will help bridge the gap between our Chinese-speaking and English-speaking communities. For instance, an article such as this one that simply updates the community at large on a recent discord call, or an article that announces major changes coming with V2, would be excellent opportunities to inform our Chinese-speaking readers and to open the opportunity to gain feedback from them.

The state of V2​

jango gave some insights on how the V2 protocol is coming along. Front-end of the protocol is still under development and coming along nicely, and in the mean time fine-tuning measures in the back-end continue to ensure a smooth rollout. The V2 protocol will allow many creative opportunities to build extensions, and offer more tools to project creation. So far early reception has been very good.

Tokenomics strategies​

The question of how tokens should be disbursed, traded and valued also came up. The goal of ensuring that a project received the best rate of JBX per ETH is being discussed and worked on. Practically, this would mean that if a better JBX rate existed from an AMM, a project creator would receive that rate JBX at the AMM exchange rate. While JBX currently has low liquidity, one line of thinking is that such a system, which would necessarily drive traffic to such AMM’s, would serve as a mechanism to build those liquidity pools. Importantly, the impetus for such a process starting will likely come as Juicebox incentivizes these opportunities.

Voting equity​

Another core topic of discussion was around voting equity in the current DAO governance. The question centered around how to strike a balance between early contributing members, such as jango, who have very large sums of JBX and thus have tremendous voting power, and members who may be contributing heavily but are newer, and thus have far lower voting power. This is a catch-22, but it is important to note that this imbalance is certainly aware to early contributors such as peri, jango and others. In the case of per and jango, they do not engage in voting for this reason (both were quick to point out). One solution is to continue issuing JBX, which will give more voting power to more individuals, but this also flies squarely against certain opinions to completely stop JBX issuance. It is a complex situation that has a lot of moving parts, and is inextricably linked to the JBX issuance/AMM situation mentioned above. Ultimately the thinking is that with these new changes, solutions may present themselves and we will see growth and directions in these domains.

Main Takeaways​

This call provided important information and helped streamline communication between the English-speaking and Chinese-speaking Juicebox member communities. The nature of questions remained substantive throughout and finding a cadence to have such calls seems like a good strategy moving forward. A huge thank-you to our members, both English- and Chinese-speakers, for taking the time to hop on this call and for having such open and transparent discussions. And again a huge thank-you to Zhape, who translated and managed the discussion and kept a good flow going!

If you held JBX before 2022-02-23 and have not done so already, claim your JBX!

We've seen some super interesting results from the Juicebox Benefits Airdrop which launched last month. ARCx has worked with us to collate and summarise some preliminary findings from the airdrop. Results below!

Definitions​

To fully comprehend the findings, it helps to quickly define the terminology used in our analysis.

Most of these findings centralise around a concept called the "Retention Rate". The retention rate is defined as the lowest JBX balance for an address after the airdrop. To better understand this, let's use an example:

0x123 claims 100 JBX tokens from the airdrop. They then go on to sell 30 of their tokens immediately after claiming. This address then waits a week, and buys back the originally sold 30 tokens. In this scenario 0x123 would have a retention rate of 70%, even after buying back the tokens, as it is the greatest amount of tokens sold after the claim.

This logic ensures that per address the retention rate can only go down over time.

The second concept to understand is the "Average Retention Rate". Many of these graphs aggregate the retention rates across all claimers in the airdrop. The average retention rate is defined as the average of all the retention rates for all addresses whom have claimed already. So, again using an example, if 10 addresses claimed the airdrop each day, then the average retention rate on day 1 would only consider the first 10 address and not any of the addresses who claimed on day 2, day 3, etc.

Findings​

The first graph shows retention rates 28 days after several major airdrops. The Juicebox Benefits Airdrop had unprecedented levels of hodling!

The next graph also shows retention rates, but instead shows them over time. After a brief selloff, retention was remarkably stable.

Next, we consider this same retention rate over time broken down across the 3 different score chorts (see JBP-114). Interestingly, the cohort with scores between 53-200 had the second highest retention rate, beating out the 201-300 cohort by ~15% at times.

Finally, we looked at how quickly each cohort claimed their JBX. Interestingly, the 53-200 tier fared better than the 201-300 tier in this metric as well.

Thank you to everybody who helped make this airdrop happen. More information and analysis will be coming soon!

Juicebox v2​

Jango's proposal to Deploy v2 passed by overwhelming majority. You can learn more about v2 on the docs.

Currently, v2 is scheduled to deploy on April 16th.

Frontend efforts are already well underway: as of 2022-04-07, the V2 feature parity milestone is 64% complete. Feature parity is Phase 1 of PeelDAO's roadmap for v2.

veBanny Frontend​

VeBanny has pushed into a new stage. We have completed all the Layers, Backgrounds and token spreads. The Ui for the VeBanny voting token minting site has been fully drafted. All contracts are written and nearly finalized. Next steps are to tighten up some front end pieces and start the build out.
―Mieos

For realtime progress updates, take a look at the Figma.

Juicebox High​

Juicebox High is live (and you are on it right now)! Join the Discord and send a message in #documentation if you're interested in contributing or have ideas for improvements.

You can use the new blog with your RSS reader by adding https://docs.juicebox.money/blog/rss.xml or https://docs.juicebox.money/blog/atom.xml.

Metaverse Festivities​

Lexicon Devils has some amazing plans for April! Here's the schedule:

Head to the Juicebox Lounge to join!

Juicebox in the words of​

Felixander has launched a new interview series called "Juicebox in the words of".

In his words: “Juicebox in the words of” is a series that highlights JB community members in interview form. Learn about members’ roles at JB and what makes them tick.

Interviews with zom, filipv, jango, and peri have already been published. You can find the latest interviews (and more) on the blog.

Vote!​

FC#20 temperature checks are live now. Head to the Discord and vote! Snapshot voting opens at 00:00 UTC on 2022-04-12.

You can claim your JBX here! For more information, read on.​

Background​

Juicebox's legitimacy as a DAO is built upon sufficient decentralization of power, access, and ownership. To accomplish this ideal, Juicebox must attract and retain an active community that has Juicebox's long-term interests in mind.

One of the most direct methods for improving decentralization is the airdrop. Several airdrop proposals were made to this effect in FC#15, all of which were rejected.

• JBP-103 - Distribute JBX to JBX Holders

• JBP-102 - Distribute JBX to Juicebox Projects

• JBP-101 - Distribute JBX to v1.1 Party Attendees

• JBP-100 - Distribute JBX to Nicholas’ List

• JBP-99 - Distribute JBX to Extended Community

As part of a new airdrop proposal, ARCx has crafted a Juicebox Benefits Score which identifies Juicebox community members based on their token holding behaviour and governance participation.

See JBP-114: Juicebox Benefits Airdrop

Score Methodology​

The Juicebox Benefits Program identifies and rewards active community members who hold Juicebox DAO’s long-term interests at heart. The score rewards active contributors by measuring governance participation, and rewards long-term support by measuring how long a wallet has held JBX.

Governance Factor (60%)​

The Governance Factor measures the number of Juicebox Snapshot proposals that a wallet has voted in. The wallet with the highest Governance score is given 600 points, and the wallet with the lowest score is given zero. All other wallets are linearly scored within those bounds—for example, a wallet that voted in half as many snapshot proposals would be given 300 points.

HODL Factor (40%)​

The HODL Factor measures the number of UTC dates that a wallet has held at least 1 JBX (either claimed or unclaimed). The wallet with the highest HODL score is given 400 points, and the wallet with the lowest score is given zero. All other wallets are linearly scored within those bounds—for example, a wallet that held JBX for half as many dates would be given 200 points.

How to Claim​

Visit airdrop.juicebox.money and connect your wallet to see if you are eligible. You can also claim a free passport to view this score (and other scores) on arcx.money.

On 2022-06-07 at 22:00 UTC, any unclaimed JBX which remains in the smart contract will be returned to the multisig for future use.

Your score on arcx.money might not be the same as your score on airdrop.juicebox.money. To prevent sybil attacks, the airdrop scores were measured at Ethereum block 14,263,369.

What's Next?​

Going forward, the community could use the Juicebox Benefits score to make new airdrops, to set up a gated Merch Squad collection, to make gated Discord roles, or even to create exclusive Juicebox-themed ARCx passport skins. These scores are verifiable onchain, meaning they can be permissionlessly used in smart contracts or used through an API.

Some other examples mentioned by ARCx include:

• Distributing airdrops equitably
• Boosting smart contract staking yields
• Verifying social status via Discord roles
• Offering free smart contract insurance to the best users
• Fee & product discounts
• Many more

This score evolves with your behaviour over time! Although the methodology could evolve, Juicebox Benefits projects aim to reward active contributors which support Juicebox's long-term goals. Your participation and support of Juicebox will be reflected in these scores over time.

If you have ideas or suggestions, share them in the ARCx Discord or in #jbx-benefits on the Juicebox Discord.

Verify​

Airdrop contract: 0x518e3CdBcda4f0735399c9F1e03A7aBC7562632f
Merkle root: 0xba0ccda021dd3008d51728ccd530dfe42d6bba07f8118d8a796e26d80e305009
Sweeper: 0xAF28bcB48C40dBC86f52D459A6562F658fc94B1e

Main Repository

Airdrop CSV

Merkle Root(use yarn && yarn generate-list to verify).

Airdrop contract on Etherscan

arcx.money｜ARCx Twitter｜ARCx Discord｜juicebox.money｜Juicebox Twitter｜Juicebox Discord

JuiceboxDAO is running final tests on an updated/forked version of its Terminal contract. Once deployed and approved by JuiceboxDAO, projects will be able to voluntarily migrate their funds and accounting parameters from the V1 terminal that is currently being used to this new V1.1 Terminal with just one transaction.

There are many broader changes being developed in a V2 release scheduled for the coming months. V1.1 is a simpler change that still manages to provide crucial utilities and fixes for projects operating on the protocol.

Here's why a project might want to migrate to V1.1:

Features​

• Pause - Projects will be able to pause contributions to their treasury as well as subsequent token issuance on a per-funding cycle basis. Any new transactions – or pending low-gas transactions in flight – that settle after a paused funding cycle has started will fail.
• Mint - Projects will be able to allow itself to mint more of its own tokens on a per-funding cycle basis. During a funding cycle where minting new tokens is allowed, the project owner can submit a transaction to increase the token supply and send this new supply to a beneficiary of its choice.

Currently projects can only mint new tokens before receiving a first contribution.

• Burn - Anyone will be able to burn their tokens by redeeming them, even when there is no overflow.

Currently tokens are only burnable when there is some amount of overflow that is being reclaimed through the redemption.

• Off-protocol redemption value - Projects will be able to supply a contract to their funding cycles that tell the protocol how much value it is holding off-protocol, like in a multisig wallet or yielding vault. Projects can use oracles in this contract to convert the value of any other asset it owns into ETH for the protocol to use when calculating redemption values.

Currently redemption values are calculated only with the ETH the project has locked in the Juicebox Terminal contract.

• Fee cap - The protocol fee is capped at 5%. JuiceboxDAO can adjust the JBX fee from 0% - 5%.

Currently there is no fee cap.

Bug fixes​

• Fixed bug that prevents a project from updating its reserved token tracker when the reserved rate is set to 0%. This bug prevented the project from reconfiguring from a 0% reserved rate to any other value without inadvertently creating an extra reserved token supply inso-doing. See this postmortem.
• Fixed bug that prevented overflow from being viewed correctly when a funding cycle rolls over before it has had its newly available funds distributed.

Other adjustments​

• The contract is now directly Ownable instead of using an ownable Governance contract proxy. The JuiceboxDAO will own the contract, which allows it to set the fee, and allow other forked Terminal contracts for projects to migrate onto.

Last update: 9/07/2021

Current focus areas are:

• Risk mitigation
• Protocol upgrades
• Web experience
• Analytics
• DAO relations
• Liquidity pools
• NFT marketplace
• Governance
• Materials

Focus areas​

Risk mitigation​

Goal: Make sure things don't go to zero.

Current team: jango (lead), exekias, peri.

Updates:

• nothing to report.

Help needed:

• Reviewing V2 docs and tests.
• Bug bounties now included in the V2 documentation that's underway.

Protocol Updates​

Goal: Evolve the protocol to be more useful.

Current team: jango (lead), peri, exekias, nicholas

Updates:

• Progress on documentation. JBSplitStore, JBOperatorStore, JBPrices, and JBProjects are fully documented. See Protocol section of docs.juicebox.money.
• Bug bounties now included in the V2 documentation

Help needed:

• More eyes on the docs
• Pursue leads for solidity audits in next 4-6 weeks

Web experience​

Goal: Improve the Juicebox experience both for people starting communities and for communities that are growing.

Current team: peri (lead), jango, exekias

Updates:

• Added feature for JB Project owners to update assets listed in the Project UI
• will eventually support 721 assets, too
• 'Pay' button Call to Action can now be customized
• Rinkeby support
• JB Interface now has its own dedicated repo and issue tracking https://github.com/jbx-protocol/juice-interface

Help needed:

• Backlog of todos https://github.com/jbx-protocol/juice-interface/issues
• Would love to bring on a dedicated person to get familiar with the UI codebase

Analytics​

Goal: Give projects rich insights into their community treasury.

Current team: peri (lead)

Updates:

Contribution pipeline being refined. Subgraph now has a dedicated repo with a streamlined deployment flow.

Analytics roadmap being refined as steps for V2 migration become clearer.

Subgraph Deep Dive

Help needed:

• Work/todos being tracked here https://github.com/jbx-protocol/juice-subgraph/issues

DAO relations​

Goal: Work towards making sure JB projects and the JB community have the resources and attention they need to get started and thrive.

Current team: nati (lead), zeugh, mieos, nicholas, jango

Updates:

• Jango and others converting people from DMs into discord members.
• Lots of people coming into the DAO relations channel.
• Pencil DAO created without any interaction with team. BrainDAO and others coming online.
• Idea: Daoification Hackathon to help JuiceboxDAO members feel more comfortable onboarding others.
• Meeting with largest single contributor: Conversation with Tom Schmidt of Dragonfly Capital
• Lots of progress in Notion: Tools section, How to section.
• Meeting notes becoming standardized and recordings much more frequent
• Gitbook docs welcome page and contract addresses added.
• Zeugh bought Sesh pro.

Help needed:

• Project lead on Daoification hackathon where anyone can join in and create a bunch of projects on rinkeby to be more comfortable configuring and reconfiguring a JB.
• Project lead needed to design and implement faster easier way to create "a DAO for your group chat". Can this be done with a Discord bot?Help Needed
• Feedback to Zeugh for discord restructuring.
• Adding info to Tools.
• More people willing to record calls and upload.

Liquidity pools​

Goal: Add support for JB treasury tokens in secondary markets for communities to be able to value their assets better.

Current team: exekias (lead), jango

Updates:

• No updates. Core dev team is focusing on V2 for the time being.
• Might be a good move to fork the BarnBridge rewards contracts instead of the synthetix ones.

Help needed:

• Someone to help test, verify, and deploy the staking contracts.

NFT Marketplace​

Goal: Give JB projects a place to sell digital (and eventually physical) goods which pipe percentages of revenue to any number of addresses or Juicebox treasuries.

Current team: nicholas (lead), jango, peri

Updates:

• Looped in Peri and Mieios for NFTMKT specification feedback meeting.
• Reprioritized NFTMKT, JB devs will do a sprint this coming week, Sept 27, 2021
• Nailed down V1 spec with Peri's help. Updated architecture, replacing submit with list function, which will save on gas.
• Reaffirmed permisionless design of NFTMKT and v2+ roadmap.
• We will also stand up a couple 721 Creator contracts so artists collaborating with JB projects (e.g., Numo with Sharkdao) can create superior NFTs than on the OpenSea creator contract, which is closed source, centrally hosted metadata by default, and a shared contract. We anticipate one 721 contract for closed collections (where token supply is known in advance) and one open minting collection (where artist can add over time). Nico already has a closed collection contract that we can refine. Can also build a simple front-end to make this easy for artist collaborators (and the broader NFT ecosystem).
• We continue to experiment with ideas about spinning NFTMKT off into its own JB project because the opportunity is large, and we believe that small teams working on focused projects are more effective than one overwhelmingly large vertically integrated JB protocol team. Perhaps initially staffed by same dev team as JB. Can focus on NFTMKT and the creator contracts. Could collect a fee for NFTs sold through the marketplace (2.5% like opensea?) or could be free. If it had revenue it would have more opportunity to expand dev team. Also thinking about token-swaps between NFTMKT and JB 📈🤝.
• Increasing belief that NFTMKT will solve the DEX vs JB dilemma facing DEX-traded DAO tokens, where the DEX is always a better price than the JB, by game-theoretic definition. This limits DAOs' ability to fundraise because DEX trades do not affect DAO treasuries. NFTMKT will allow DAOs like Shark to largely replace direct-to-JB appeals. DEX purchases may still offer cheaper DAO tokens than the NFTMKT, but buyers will not get access to limited edition NFTs via the DEXes. NFTMKT will also be more fun and easy to use for NFT acclimated, compared to JB or DEXes which are unfamiliar to many in that space.
• The team is very excited about the promising design specification and roadmap for the NFTMKT.
• Nicholas also discussed with Mieos affordances in the 721 contracts that will enable WAGMI to create NFTs on behalf of client DAOs. Achievable design requirements even within the V1 spec.

Help needed:

• Review read methods & TheGraph events with Exekias or Peri this coming week
• Nico x Jango will collab to finalize v1 NFTMKT solidity
• Nico to talk to Pencil DAO

Governance​

Goal: Plan how we make decisions within the community.

Current team: 9birdy9 (lead), zheug, jango, unicornio

Updates:

• New voting process
• Finalized proposal process
• New governance process:

Governance

Includes Proposal Templates for each common type of proposal.

All JBX holders participate in votes that affect big picture JBX variables.

Changes to recurring payouts are voted on by addresses currently receiving payouts as they have greatest insight and are most affected by such changes.

Changes to reserved token allocation voted on by addresses currently receiving reserved tokens as they are most affected.

Addresses receiving payouts are expected to vote.

• Discussion about whether large token holders and people on reserved list should have max voting capacity or some quadratic strategy that limits outsized impact.
• First trial of these new templates in current governance process.
• @9birdy9's trial payout proposal is the first proposal sent to snapshot according to these forms.
• FC5 reserved JBX tokens will be passed without a formal snapshot for lack of sufficient time to complete our governance snapshot process. We will use snapshots for future reserved token proposals.
• Creation of BANNY gov participation incentivisation token — An airdrop is in the works.

Help needed:

• Refining governance process:
• Creating informational foundations to keep people up to date on governance proposals/timelines.

Materials​

Goal: Videos/visuals/memes/stuff that radiates Juicebox vibes.

Current team: WAGMI studios

Updates:

• WAGMI producing cultural content
• Published overflow video

Help needed:

• Feedback on content
• How can WAGMI help juicebox projects launch
• Helping onboard
• Developing visual identity (cultural material)

Co-authored: jango, peri, exekias, nati, nicholas, zeugh

Current focus areas are:

• Risk mitigation
• Web experience
• DAO relations
• Analytics
• Liquidity pools
• NFT marketplace
• Governance
• Protocol upgrades
• Materials

Focus areas​

Risk mitigation​

Goal: Make sure things don't go to zero.

Current team: jango (lead), exekias, peri.

Updates:

• No new bugs/problems discovered in the contracts.
• New repo where security issues are documented here.
• Wallet connection issues in the front end solved. One remaining bug where connecting wallet from the projects page sometimes causes the beneficiary field of payments.
• DefiYield auditors seems to have dropped off. Need to follow up again.
• Focus on security now moved to V2. Documentation, tests, audits, etc.

Help needed:

• It'd be great if more folks could help write tests and review the code and documentation as it gets done. We should collaboratively mold this into its final, secure form.

Web experience​

Goal: Improve the Juicebox experience both for people starting communities and for communities that are growing.

Current team: peri (lead), jango, exekias

Updates:

• New analytics data in project dashboards. Still room to grow, more data sourced into The Graph and ready to use.

• New wallet connection integration. Can now connect with many other wallets with BlockNative integration.
• Progress on Github issues backlog.
• Wording in the interface being reconsidered:  "staking" vs "claiming".
• Researching different UIs for different treasury types.

Help wanted:

• Backlog at https://github.com/jbx-protocol/juice-juicehouse/issues

DAO relations​

Goal: Work towards making sure JB projects and the JB community have the resources and attention they need to get started and thrive.

Current team: nati (lead), jango, nicholas, mieos, zeugh

Updates:

• Gitbook updates underway. Walkthrough, explanation of processes.
• Working with Whiteboard crypto, UltraDao, BeatsDao.
• Focusing on established DAOs. Might refocus to newer DAOs later.
• People should forward questions from #support and from other JB projects to Nati to aggregate into docs.

Analytics​

Goal: Give projects rich insights into their community treasury.

Current team: peri (lead), buradorii

Updates:

• Most updated in the UI under the "Web experience" focus.
• Experimenting with what data can be accessible in the UI.
• No updates on Flipside or Dune analytics.
• People want to see current token holders for each projects.
• People want to see current FC vs upcoming FC.
• People want to see the price the treasury token is being sold at over time.
• People want to see the percent of the tokens that they will own at the time of making payments.
• People want to be able to play out funding cycle scenarios before making reconfigurations.

Open to help:

• Index more Subgraph events.
• Display discount rates (tokens/ETH) of past funding cycles.

Liquidity pools​

Goal: Add support for JB treasury tokens in secondary markets for communities to be able to value their assets better.

Current team: exekias (lead), jango

Updates:

• Experimenting with Synthetix staking rewards contracts: https://github.com/jbx-protocol/staking-rewards.
• Fleshing out UI prototypes:

Help wanted:

• Comms with JBX project owners (e.g., SHARK) to understand their needs from a staking reward/LP perspective.
• Devs with staking rewards expertise.

NFT Marketplace​

Goal: Give JB projects a place to sell digital (and eventually physical) goods which pipe percentages of revenue to any number of addresses or Juicebox treasuries.

Current team: nicholas (lead), jango, peri

Updates:

• Big demand from SharkDAO (and others?).
• Draft of contract looking good.
• Plan for V1 is no UI on juicebox.money, make bare bones JS SDK/library with/for Shark to build a NFT MKT into their forthcoming website.
• Need to finalize what will be included in v1, and what won't.
• Specification draft
• Github repo (private for now)

Goals:

• Finalize spec for v1
• Get a working v0 implementation on Rinkeby by Monday 2021-09-13 EOD
• Get a basic 721 contract together to mint NFTs that we can submit to the marketplace

Help needed:

• Jango will help with contract implementation and testing (thank you –nicholas)
• Next week open to help starting building a JS SDK

Governance​

Goal: Plan out how we will make decisions together.

Current team: zheug (lead), unicornio, 9birdy9

Updates:

• Trying coordinape to test a reputation system. The epoch system feels good, didn't give us the easy integration to voting that we needed after the epoch.
• We're still wroking on our basic model for how to make decisions. Need to balance governance power between token holders and reputation/contributions but we haven't got a way to test it yet.
• We can, at the moment, take the csv of reputation distributed after the Epoch, but are still looking on how to import those in a strategy to snapshot. Need help from more dev oriented folks to communicate coordinape results onto snapshot.

Help needed:

• We need some dev/snapshot help to integrate our new governance system into a snapshot strategy.

Protocol upgrades​

Goal: Evolve the protocol to be more useful.

Current team: jango (lead), peri, exekias, nicholas

Updates:

• V2 has been announced here.
• Reviewed V2 with Peri, Exekias, and Nicholas, got very valuable feedback that is being iterated on.
• Docs for V2 are in progress here.

Help needed:

• Same as in the "Risk mitigation" section.

Materials​

Goal: Videos/visuals/memes/stuff that radiates Juicebox vibes.

Current team: WAGMI studios

This is a new section that will have updates next time