Costing + Breakdown* (outdated)

ㅤ	High-level Task	Breakdown	Effort (Hours)
1	In sandbox now, button that connects to Metamask	use what is already built	0
2	Price conversion from fiat to (USDC, ETH, BANK).	after price conversion, transaction confirmation would trigger discount generation with all the items added to cart - (will need discount generation)	3 , p , 5, b
3	Generating Shopify coupon: generate discount on the fly and specify which items the discount can be used for, to make sure that the discount can only be used for the items in the cart	after adding items to cart- 1- use shopify API, 2- needs step add to cart and check out that stores collection of items chosen by the user, (PBear - fine with adding a page) - AUTO-APPLY, metdata needs to be added to several shopify entities	5 hrs, b
4	Check user balance in the selected wallet	small task :)	1, p
5	Admin dashboard	allowing the user to check unused discount codes, customer user dashboard they should probably know what the discount is applied for, which items ??	2, b
6	AML : anti-money laundering	during price conversion,	10h??, after meeting with genx
7	set up panel: set there receiving eth address, tokens they accept, etc	(look up store settings, Shopify-specific settings) Store settings in Shop’s metafield https://shopify.dev/api/admin-rest/2021-10/resources/metafield#top	3, b
9	Shopify crypto order tags (not external db to store the order or user information and rely on meta data that can be stored in the shopify entities, this would cut down costs because we wouldn't need an external db to maintain)	during checkout when the order created, doc to be checked when tags can be added to order,	2, b
10	customer dashboard	displaying data, what if the checkout flow didn't go through and there's an unused discount? what happens in this case — discount codes generated can be added to the customer metadata, and once it is used it can be removed from the meta data),	1, b
11	Amount base issue - security issue (solved by number 2)	keep for now though covered	5, b
12	wireframe	visual to communicate to USM team, not final UI, just communication tool	2 , p
13	polygon sidechain integration	the transaction will occur on Polygon instead of Eth main net, no effort	0
14	NFT Receipt	Receipt for each user includes asset (image) and metadata detailed below.	10, p
ㅤ	ㅤ	Total	49
ㅤ	ㅤ	$BANK	49,000

1) Admin Set Up Panel

 

14) NFT Receipt

Each POAP could have an image reflecting either the generic USM logo or be specific to a merchant using the site/tool. This would depend on our stage of development and merchant preferences. To be a receipt it would need the following in plain English both visible and incorporated into the POAP... list for convenience:

• the transaction hash

• the chain in use (for dummies)

• the value of the transaction in the coin/token it was transacted

• the sending address of the transaction

• the receiving address of the transaction

• the UMT date/time of the transaction Also, if possible:

• an identifier for the merchant (to limit capability to review to one merchant)

• an invoice or order number for reference (accounting, etc.)

• a three word item description (T-shirt Red Medium - or - Pendant Gold Round)

• a merchant provided item number (specific to the item type) Receipt to be produced and available for both the send, receive, and system addresses to claim

All of the elements above need to be encoded so each element can be detected on the block (taxes, accounting, etc.), detectable by a smart contract (customer ability to review the purchase), and/or visible to a human eye (collector interest, pride, etc.).

(more metadata more expensive, but with polygon it should be manageable in terms of transaction price (open zeppelin defender to absorb cost of minting NFT do they want users to pay for the transaction fees)

 

1. In sandbox now, button that connects to Metamask

2. Generating Shopify coupon: generate discount on the fly and specify which items the discount can be used for, to make sure that the discount can only be used for the items in the cart

3. Price conversion from fiat to (USDC, ETH, BANK).

4. Check user balance in the selected wallet

5. User dashboard (when plugin selected to be added on the store, their receiving address, erc-20 tokens they want to accept should be part of the setup)

6. Admin dashboard

7. set up panel: set there receiving eth address, tokens they accept, etc

8. Shopify crypto order tags (not external db to store the order or user information and rely on meta data that can be stored in the shopify entities, this would cut down costs because we wouldn't need an external db to maintain)

9. what if the checkout flow didn't go through and there's an unused discount? what happens in this case — discount codes generated can be added to the customer metadata, and once it is used it can be removed from the meta data),

10. Index page of discount codes that customer hasn't used yet (per customer), they can check to see which discount codes they can still use

11. Amount base issue - security issue (solved by number 2)

 

**polygon sidechain?