Stand Up 4/26

Date

Apr 26, 2022

Note Taker

Property 1

Crucial Items:

UI: ‘select your token’ removed from modal in times where it is not pertinent

Token being added to db before checkout is complete?

hardcoded golden glove NFT contract addresses

issue related to token id being hardcoded / customer id

manually updating customer id in published version, currently it is hard-coded : it is ok for now

polish pr approval process - ASYNC

Agenda + notes

Updates:

Prad: -1 week

last week

complete redeem functions

debugging the errors

cors issue no longer and issue

debugging and getting the redeem function working

working on cors issue, cors is still an issue

database persistence

figuring out metafields >> can fetch metafields from product if it is redeemable, then what contract

Next week:

investigate token id being added to redeemed db before checkout process is complete,

cors in chrome is still an issue

work old version without affecting beta, we’re on dev merge, and work on hardcoded contract address and customer-id, merge in pieces

catch up on notion

make sure that all the endpoints work, and testing them

get everything else working locally (can’t write serverside code)

restoring a working version of redeem db, replicating rose’s success on the server side

Touch base on Thursday>> UI/UX, friday>> default gas fees

try to figure out cors issue, it is only not working on chrome

redeem function >> cors

redeem db (server integration)

data verification between product and nft by end of the day

token check against db <challenging>

default gas > after april 8th demo day

add help instructions >> before demo

connect to discord on the modal >> “Need Help? Join our discord and go to customer service channel.” >> after april 8

Challenge:

Questions:

can we host db in the cloud or somewhere public <not the safest>

roseja: -1 week

Last week:

webhooks not working properly>> so spent time into looking into this that wasn’t the issue - manually deleting the shop, some webhooks work, some don’t

tested endpoints with some changes prad implemented after added to same branch and was able to redeem and added to the db, and the db was working, after refreshing db, (two manual, manually delete the shop (webhook not working as bug), whenever a db change proceeding with) (liquibase will automatically keep track and update databases, might be complicated for now and not sure how to set up on heroku)

whenever updating then app, when it is refreshing with updates, the token is no longer valid, and getting an error to provide the url, but when remove the url for the shop manually. (keep in mind and think about solution moving forward) - still issue

discount generation is back to working again (root issues: removing the extra shops on the authentication side, and the endpoint errors, the schema changed some fields to text fields.

current site<configure host not provided>, new branch config error is no longer there, there is something off with graphql, needs debugging, once this is working it should solve a few other issues

database persistence + changes: (not a priority for Friday, this will be a long term issue), added new redeem db token, but have to manually update the code, need long term solution

api endpoints some issues, information not loading properly

discount generation > some questions have cleared up, admin page cannot be changed, we could create a new (orders and settings) another admin there to add to show it was added by NFT) — forget about admin dashboard, for now, add redeemed with NFT with orders

screen record

Next week:

everything in QA is working

modify discount generation>> update the endpoint to make sure the metafield on the order level is updated - manually adding to metafield— manual tagging bankless,

updating shop db correctly

review merge pieces with prad

hide payment: need potential solutions (no shopify plus), maybe there is a way to modify the cart before it gets to checkout > research that, or maybe webhook (webhook for only redeemable for nft, force redirect)

if graphql works >> might help with some of the errors resulting from outdated js libraries

data persistence > challenge

NFT Discount generation

add serverside endpoint to add token id

add serverside endpoint to check if token id exists

Challenge:

getting the correct db URL with docker, locally it works <solved> with add to orders rather than admin

Results of meeting with PBear + Prad

setting up a new customer on heroku: successfully deployed and installed on USM and bankless test store

we would like a demo on the published site (after order tagging is done - 25th demo on published site ) we can also install on preview theme (any order will show up on the real store)

Cost of shipping:

variable shipping costs, not covered with NFT Sale —> v high average, NFT sale covers shipping costs

Use cases other than the FC Red gloves: custom code to estimate shipping based on country and zip code that can calculate price of shipping (ask user information before discount code is applied) shopify theme handles object, shopify API uses a checkout object to send users, we would have to create a custom code to do this - priority lower than nft redemption and nft receipt

setting - payments tab >> add free shipping options / custom functionality

NFT Redemption:

UI Button - connected wallet > connect with wallet and grab address

check again with moralis (tried with moralis, documentation shows it is an API, tested with DAO Punks contract)

get data from the backend what is redeemable and what address

if all the verification have passed, add the token to the db

if not error

Last meeting notes

NFT Receipt

will run on only remix, code doesn’t compile on its own, it would be better if they deployed and send the address on which it is living. This code, is an NFT contract, it is not ready for USM or bankless checkout right now. 1 hr. allow only USM address to create the receipts, not any other nft receipt, so only USM can mint 

spec sheet >> wallet to fund the minting, absorbing minting costs 

NFT Redemption - 2/3 weeks 

check to see if token used to redeem 

use cases:

list of tokens/NFTs

complexity on shopify admin settings >> embed meta data on the product level (this token they can redeem shirt), use that to check if wallet has the token and store token they have redeemed

same product >> check if you have token >> check if you claimed >> in their order/custom attributes the token that the customer holds (on the shopify side, adding the token number to order custom attributes)

Admin interface UI to allow the store to add custom attributes about the contract, search box>> select product to enable token redemption and then once that feature flack is turned on, then you go to the product setting and in the rules for how someone redeem (contract address, # how many they can redeem)

prad would have to do some frontend logic to check

Map out the receipt and the redemption next stand up! 

Info if they hold the NFT:

1- Moralis: all the NFTs that user holds

2- get that array and check if user holds token

3- if so, return 200 status 

Product info:

1- contract address for tshirt

2- deployment address, retrieve token addresses in a dynamic fashion

contract factory address >> but each token will be different, so we want to look into this with moralis not with ether scan

PBear>> admin dashboard >> add contract address (1- settings input contract address per product , 2- db table, 3- API)

Client 

Stand Up 4/26

Date

Apr 26, 2022

Note Taker

Property 1

Crucial Items:

UI: ‘select your token’ removed from modal in times where it is not pertinent

Token being added to db before checkout is complete?

hardcoded golden glove NFT contract addresses

issue related to token id being hardcoded / customer id

manually updating customer id in published version, currently it is hard-coded : it is ok for now

polish pr approval process - ASYNC

Agenda + notes

Updates:

Prad: -1 week

last week

complete redeem functions

debugging the errors

cors issue no longer and issue

debugging and getting the redeem function working

working on cors issue, cors is still an issue

database persistence

figuring out metafields >> can fetch metafields from product if it is redeemable, then what contract

Next week:

investigate token id being added to redeemed db before checkout process is complete,

cors in chrome is still an issue

work old version without affecting beta, we’re on dev merge, and work on hardcoded contract address and customer-id, merge in pieces

catch up on notion

make sure that all the endpoints work, and testing them

get everything else working locally (can’t write serverside code)

restoring a working version of redeem db, replicating rose’s success on the server side

Touch base on Thursday>> UI/UX, friday>> default gas fees

try to figure out cors issue, it is only not working on chrome

redeem function >> cors

redeem db (server integration)

data verification between product and nft by end of the day

token check against db <challenging>

default gas > after april 8th demo day

add help instructions >> before demo

connect to discord on the modal >> “Need Help? Join our discord and go to customer service channel.” >> after april 8

Challenge:

Questions:

can we host db in the cloud or somewhere public <not the safest>

roseja: -1 week

Last week:

webhooks not working properly>> so spent time into looking into this that wasn’t the issue - manually deleting the shop, some webhooks work, some don’t

discount generation is back to working again (root issues: removing the extra shops on the authentication side, and the endpoint errors, the schema changed some fields to text fields.

current site<configure host not provided>, new branch config error is no longer there, there is something off with graphql, needs debugging, once this is working it should solve a few other issues

database persistence + changes: (not a priority for Friday, this will be a long term issue), added new redeem db token, but have to manually update the code, need long term solution

api endpoints some issues, information not loading properly

screen record

Next week:

everything in QA is working

modify discount generation>> update the endpoint to make sure the metafield on the order level is updated - manually adding to metafield— manual tagging bankless,

updating shop db correctly

review merge pieces with prad

if graphql works >> might help with some of the errors resulting from outdated js libraries

data persistence > challenge

NFT Discount generation

add serverside endpoint to add token id

add serverside endpoint to check if token id exists

Challenge:

getting the correct db URL with docker, locally it works <solved> with add to orders rather than admin

Results of meeting with PBear + Prad

setting up a new customer on heroku: successfully deployed and installed on USM and bankless test store

we would like a demo on the published site (after order tagging is done - 25th demo on published site ) we can also install on preview theme (any order will show up on the real store)

Cost of shipping:

variable shipping costs, not covered with NFT Sale —> v high average, NFT sale covers shipping costs

Use cases other than the FC Red gloves: custom code to estimate shipping based on country and zip code that can calculate price of shipping (ask user information before discount code is applied) shopify theme handles object, shopify API uses a checkout object to send users, we would have to create a custom code to do this - priority lower than nft redemption and nft receipt

setting - payments tab >> add free shipping options / custom functionality

NFT Redemption:

UI Button - connected wallet > connect with wallet and grab address

check again with moralis (tried with moralis, documentation shows it is an API, tested with DAO Punks contract)

get data from the backend what is redeemable and what address

if all the verification have passed, add the token to the db

if not error

Last meeting notes

NFT Receipt

will run on only remix, code doesn’t compile on its own, it would be better if they deployed and send the address on which it is living. This code, is an NFT contract, it is not ready for USM or bankless checkout right now. 1 hr. allow only USM address to create the receipts, not any other nft receipt, so only USM can mint 

spec sheet >> wallet to fund the minting, absorbing minting costs 

NFT Redemption - 2/3 weeks 

check to see if token used to redeem 

use cases:

list of tokens/NFTs

complexity on shopify admin settings >> embed meta data on the product level (this token they can redeem shirt), use that to check if wallet has the token and store token they have redeemed

same product >> check if you have token >> check if you claimed >> in their order/custom attributes the token that the customer holds (on the shopify side, adding the token number to order custom attributes)

Admin interface UI to allow the store to add custom attributes about the contract, search box>> select product to enable token redemption and then once that feature flack is turned on, then you go to the product setting and in the rules for how someone redeem (contract address, # how many they can redeem)

prad would have to do some frontend logic to check

Map out the receipt and the redemption next stand up! 

Info if they hold the NFT:

1- Moralis: all the NFTs that user holds

2- get that array and check if user holds token

3- if so, return 200 status 

Product info:

1- contract address for tshirt

2- deployment address, retrieve token addresses in a dynamic fashion

contract factory address >> but each token will be different, so we want to look into this with moralis not with ether scan

PBear>> admin dashboard >> add contract address (1- settings input contract address per product , 2- db table, 3- API)

Client 