Botto

Summary

Please note that this Snapshot has a default 72-hour voting window.

BIP-65 proposes to commit Botto to a p5.js performance and collection presented by Verse February 3rd. By committing to a show and drop in February, Verse in turn is able to commit to a significant build up for this event as part of its Solos series. Given the amount of lead time and remaining development to do, this proposal would leave some details left to be determined in a subsequent BIP after more of the development has been completed.

Rationale

Botto has shown strong development in p5.js and we are planning an upgrade to its core architecture in September. However, just with its progress to date we see a strong performance and collection that could be created. This would be an end-to-end autonomous process: Botto creating generative code, evolving it iteratively over time, minting onchain, and finishing with a plotter print of the iterations.

This is a proposal to commit Botto to a p5.js collection presented by Verse February 3rd. By committing to a show and drop in February, Verse in turn is able to commit to a significant build up for this event as part of its Solos series. Given the amount of lead time and remaining development to do, this proposal would leave some details left to be determined in a subsequent BIP after more of the development has been completed. This draft includes an outline of a process and drop that we think can be robust despite the uncertainty of the upgrade

Even with the planned upgrade, it will be an experimental process to see if Botto can evolve a long-form algorithm that can create a strong series of 250-1000 works (a la “long-form generative art”).

For the sake of this proposal, we have outlined a process that we think can be robust despite the uncertainty of the upgrade. Please see the proposal for the tentative performance plan here. The final details of that process and the associated economy can be determined in a subsequent BIP after we see the results of the upgrade.

This proposal only commits to some parameters of the final outcome of what will be built.

Timeline

Approximate timeline would be as follows: Phase 0

• DAO approval – now

Phase 1

• Upgrades and interface design – Sept-October
• Final BIP – end of October

Phase 2

• DAO testing and iteration, get fully on chain, build API – November-Dec
• Marfa sneak peak – November (if we have something to show)
• Early Promo – November-January

Phase 3

• Launch feedback timeline - end of January
• Final selection and minting - Feb 3
• Exhibition - ~Feb3

Proposal Specifications

1. Commit to a show and drop February 3rd with Verse
2. 1 week public process/performance
3. A series of “family tree” artefacts from Botto’s evolution
4. A series of 250-1000 outputs from Botto’s generative algorithms
5. 1/1 plotter prints for each work

Budget

$10,000 USD in case additional technical support is needed for building out the onchain process.

4.0 Criteria of Success

• Strong sales of the show and related works
• New Botto collectors
• Critical reception of the show
• A clear understanding in the audience of the delineation of this new practice from the weekly mint, as well as an appreciation for how this fits into the overall evolution of Botto

5.0 Risks

• The quality falls short and sales are soft. We have gotten strong feedback on the results so far, and so the adjustments and upgrades only improve on that.
• Perception of supply dilution. We have also gotten feedback that this work and collection size are self contained and a sufficiently differentiated work.
• Governance friction in subsequent BIP. This is an experiment in the DAO being able to commit to big projects that take time to build and so have some uncertaint details. Collective consensus and trust will be key, but succeeding will prove a key ability of the DAO to steward big evolutions of Botto.

Please refer to the BIP-65 forum post for full details and discussion.