# BBB Sync 11/02

## Action Items

* **RG Josh**
* Send new background in tg
* **Bill**
* Ping John/Justin about current stack
* **Damu**
* Check out Saimano's Test NFT Contract

## Documents Referenced

[Project Proposal ](https://hackmd.io/dH7umlMIT2uCsIMc504BAA?view)
[Kanban](https://airtable.com/invite/l?inviteId=invowI6rbkpUSjGMu&inviteToken=79d8ef5c47016a3eb3e971d7dbf19e44fcb4e555b034d70d23e9730b8d212609&utm_medium=email&utm_source=product_team&utm_content=transactional-alerts)
[Architecture](https://hackmd.io/fTNdNUUMR6yJbFfW6zNq4Q?view)
[Saimano's Test NFT Contract](https://goerli.etherscan.io/address/0xa3afe17b63a8917ef77062b99061da7e0707c550)

## Lightly Edited Meeting Notes

Overview:

JD: bg later/ dev now/ lore q’s / product q’s

### Development

SM: shows off demo. Start of function to end - 20/30 seconds. Running script locally - but for testing. Schema not finalized yet (tiny changes based off flow chart)

If executor is on another active swap, will check if can’t be done. 2 traits restricted from swapping - swap record. Previous swapIDs were empty - last swap is required to check if swap had been made.

Pass swapID
Maybe second buffi corn made swap between
-if send buff gets involved, want it to be checked
Want to prevent behavior - need a check so that swap creator/executor. You create eye swap, need to check that you haven’t changed

Executor’s bufficorn will be locked

BW: Don’t think we need to lock anything. Just need to check that hasn’t changed traits since.

DM: Need to add in db, not only trait to swap but also which trait are we swapping. Then check if doesn’t change

JD: stack swaps? Or just diff traits?

BW: check on complexity

JD: yeah, see world where happens

DM: maybe check just on finished side. User can swap eyes to another buffi corn. Can create swap with three buffi corns - then 1st user accepts, it’s done.

BW: can check on executor’s side. Initial check is that the user owns the bufficorn

JD: also scalable for marketplace

BW: agreed

SM: swap script, just want to rearchitect additional validations. Not a big deal

DM: can copy image layers locally.

SM: layer files along with backend deployment. layer is 150mb or something - fine to deploy with backend API?

SM: don’t know where we will deploy, actually including files in codebase. Currently heroku, may digital ocean

DM: deploy to repository

BW: from UX perspective, other thing to do - if takes 5/30 seconds. Could have fun loading screen come in handy. Share a tidbit of lore to distract from we

JD: agree, think we can have some fun with how to do it

JD: storage, thinking digital ocean?

Saimano - layers, on AWS. For actual API - digital ocean is pretty neat. Mongoldb atlas for db. Probably can
For frontend - chakra for styling elements,

JD: should ask Bill

BW: used amazon s3 for bufficorn stuff. Did food truck stuff - either fleek or vercel for frontend, airtable for backend. Check with Justin/John on AWS credits/digital ocean/if strong preference. Guess would be that they really don’t care, that level of traffic/size of db wouldn’t be significant. Need to be cost conscious

Will check and see who’s going to maintain

SM: one more thing to ask, when testing UX db. Deploy dummy buff on testnet? S3 bucket? See trait swap happening in realtime

DM: def deploy contract

SM: for buff contract on testnet, made tweaks

JD: circling back - adding array into db?

SM: where second table comes in. Contains all swap records. current/new DNA. IPFS hash on buffs, can refer to that for history

BW: damu, assuming took a look at, makes sense. Will defer mostly to damu - with having table track

DM: will track table. Can save image in s3 bucket

SM: Up to them - store on S3

DM: image in s3, can save there.

BW: cool, save IPFS for later iterations

SM: processing info, doing validation on executed buff. If come up with any q’s/blockers

### Design

[JD shows off background]

BW: John has strong opinions, tag John

### Lore

CK: John wants trait swapping to be buff being more of themselves. How to portray that?

Want to think of any feedback onto why the bufficorn would want to trade?

DA: IRL moments were people trade, maybe a sign of respect? In some rowing races, teams swap shirts. Don’t think we need a competition between buffi corns. Maybe if 2 buffs swap a trait, it implies that they’re closer, they’re friends? Maybe prompted to meet IRL?

CK: sign of respect is a good idea

DA: adding value to action of swapping will dilute the marketplace feel. May be too complex - but if located in same georadius, spork fee is less?

CK: can do this in the lore without adding technical stuff to it. Add more connecting to each other - more like you and I see each other & interrelating - how does that translate into showing up at ethdenver?

DA: Likes buff world, people identify with look and feel. Items aren’t boring, people use imagination. Doesn’t know if it’ll lead to affinity group - people with similar traits - but also leading to diversity. Also rarity aspect. Likes how sponsored shirts also break the seal. The tiered system - top X may get greater spork airdrop

Daniel: setting target - desired goal is to create a bufficorn that looks like specific collection. If trait swap successfully, achieve goal.

DA: likes that, encourages people to go through training. Encourages people to level up - training - participate in rigs. Level up not in grinding way, but take course and execute tutorial. People should be proud. Setting goals - threshold to be difficult? How to get to next level? How to keep going?

JD: some way to keep trading

DA: motivating people to swap. Kind of a bonus

JD: connect to buffalo/unicorn lore?

BW: user motivation, has a buff close to perfect and swap 1 trait. 1) build a specific bufficorn 2) trying to play game of rarity. One is game, one is emotional. One of Opolis guys - will