Create Boombox Admin

[friedger]

Create a contract that manage the minting of Boomboxes.

The contract should

• register one or more boombox contract for one or more locking cycles
• handle all pox related calls

The contract does not handle payout

The boombox contract must implement the boombox trait and can define

• a split of payout/a payout function
• locking period
• reward address

[dantrevino]

Some of these may be obvious, but want to add:

• admin contract should save the boombox owner in addition the items above
• should allow admin to stop registration/minting, separate from "time limit"
• should require "allow-contract-caller" for each separate owner (ie allowing a Freidger pool Boombox does not mean I allow a Dan Pool boombox)
• have 1 accessor function to to allow getting all boomboxes (current and expired, expectation that filtering is client-side)

[friedger]

v3 deployed at https://explorer.stacks.co/txid/SP1QK1AZ24R132C0D84EEQ8Y2JDHARDR58R72E1ZW.boombox-admin-v3?chain=mainnet

should require "allow-contract-caller" for each separate owner (ie allowing a Freidger pool Boombox does not mean I allow a Dan Pool boombox)

My understanding was that we want to remove friction. v3 does not implement this. allow-contract-caller for the admin contract is sufficient. v3 does not allow stacking through a different pool than defined by the user.

have 1 accessor function to to allow getting all boomboxes (current and expired, expectation that filtering is client-side)

We can only have pages of the list, is this required by other contracts?

[dantrevino]

My understanding was that we want to remove friction. v3 does not implement this. allow- contract-caller for the admin contract is sufficient. v3 does not allow stacking through a different pool than defined by the user.

Absolutely remove friction. Not allowing the pool to change has two consequences, afaict:

1. safer for creators, since people are not allowed to set incorrect pool addresses
2. assumes that all work will be thrown into Friedger Pool, which is more work for you (@friedger )

What do you need so that the process scales, when one custom boombox sets rewards to 30/70 split and another set rewards to 100/0, etc, etc?