0.0 Summary
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.
1.0 Background
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 proposal includes a tentative 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. 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.
1.1 Process Outline – Tournament Style
Botto will start with a set of 64 possible algorithms, created using its new architecture that makes use of the generative code it has already created so far.
Each round, only 50% will survive and be iterated on (some percentage of top ones will continue without changing), running 5 rounds until there are only 4 algorithms left.
On the last day/round, a final selection will be made alongside a 5th “fail-safe” option to not mint if the participants determine Botto has not reached a sufficient threshold of quality.
If the 5th option is selected, there will only be a special collection of the family trees of evolved code presented (we can also discuss a series of different algorithms rather than a master algo).
If a final algorithm is chosen, there will be a series of 250-1000 minted from it. To complete the process of automated generative creativity, there will be a plotter print of each 1/1 iteration available to claim per pass.
Regardless of the outcome, Verse will produce an exhibition of the works, online and IRL events discussing the work and Botto’s broader context/practice, solicit acquisitions by museums, and produce a book documenting the process including the comments, visualizations of months of feedback and code then the upgraded version, Botto’s own descriptions of its attempts, etc.
In sum:
- Botto starts with a set of 64 sketches
- Day 1-5: 50% of the lowest voted sketches are removed each week, other 50% continue or evolve
- Day 6: Users vote between 5 choices: 4 sketches or a “fail-safe”
- Final outputs are at minimum family trees and artefacts, and ideally a series of 250-1000 individual outputs plus plotter prints.
1.2 Variables
The biggest variable is in the outcome of the upgrade to the generative architecture. Seeing the outputs from the upgrade and the learning process will determine what kind of full training regimen Botto will need.
Botto may need some prep time with its new architecture, akin to the rounds we have been running so far with p5.Botto so that it is warmed up for the tournament-style process. Or it may even need to run that tournament style process over weeks instead of days.
These variables change the economy, how open vs. gated the training can be, just how much of the process can be run onchain, and the final outputs themselves.
These will be determined in a subsequent BIP after the upgrade.
1.3 Family Tree Artefacts
Family trees consist of ascendants and descendants. Some are quite short if they didn’t make it past a round or two; others are quite long if they persisted and/or merged with other family trees. Different ways of presenting could be triptychs, ERC-7160, or full family trees.
2.0 Proposal Specifications
- Commit to a show and drop February 3rd
- 1 week public process/performance
- A series of “family tree” artefacts from Botto’s evolution
- A series of 250-1000 outputs from Botto’s generative algorithms
- 1/1 plotter prints for each work
3.0 Timeline
Approximate timeline would be as follows:
Phase 0
- DAO approval – next 2 weeks
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
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
- Critical reception of the show
- A clear understanding in the audience of the delineation of this new practice from the weekly mint while also fitting 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.
