boomcrypto / boom-contracts Goto Github PK

Boomboxes should use the same listing and selling as boom-300.

• set max mint at 10000 in addition to time limit
• mint time limit: #720350

This option provides some more flexibility compared to hard coding the uri yet still makes it immutable after you've checked everything is in order.

Just like in the SP3D6PV2ACBPEKYJTCMH7HEN02KP87QSP8KTEH335.megapont-ape-club-nft (see from line 142 and 150 (and line 019, 037))

Add error
(define-constant ERR-METADATA-FROZEN (err u505))

Add variable
(define-data-var metadata-frozen bool false)
assumes:
(define-data-var base-uri (string-ascii 80) "ipfs://Qmad43sssgNbG9TpC6NfeiTi9X6f9vPYuzgW2S19BEi49m/{id}")

add set base uri
;; Set base uri (define-public (set-base-uri (new-base-uri (string-ascii 80))) (begin (asserts! (is-eq tx-sender CONTRACT-OWNER) ERR-NOT-AUTHORIZED) (asserts! (not (var-get metadata-frozen)) ERR-METADATA-FROZEN) (var-set base-uri new-base-uri) (ok true)))

add Freeze metadata
;; Freeze metadata (define-public (freeze-metadata) (begin (asserts! (is-eq tx-sender CONTRACT-OWNER) ERR-NOT-AUTHORIZED) (var-set metadata-frozen true) (ok true)))

make categories an optional parameter for the mint-series function

• Create a new admin contract using a list instead of a map for storing custom boombox contracts
• add function for getting all boomboxes (get-boombox-list)
• update all functions ( get-boombox-by-contract, get-boombox-by-id, halt-boombox, etc) to lookup from list
• add tests

I tried the new template for b-32, and the deploy failed.

https://explorer.stacks.co/txid/0x8d15b0657394c0f41247d5ed95d7144776121ec12d73ee2b8645b4938a0644f1?chain=mainnet

cc @amrro

We need tests to validate the boombox functions when we update.

Owners of boomboxes should have the option to burn the nft, if they wish.

Owners of boombox-28 should get 4 moonboxes airdropped to them. ID/Serial number of the moonboxes should be randomly assigned.

We need to get @friedger's distribution list and drop to those addresses. I'll add Moonbox details to this issue.

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

We're collaborating with Zero Authority DAO to celebrate Bitcoin Pizza day with Boombox 34. ZA will provide assets, traits, metadata for the collection.