Plan

Nota bene: must-haves refers explicitly not to what has to be completed to successfully finish the thesis, but rather to what parts of the system should work before it can be used by the end-users

Must-haves

Step 1

Rewrite anydex-core code to use product URNs rather than coin identifiers

• (see https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml)

Step 2

If trustchain is suitable for indexing and searching through 100m+ semantic entries AND average response time < 1s

• Yes => develop functionality to return a list of all products matching the search query based on their relevance
• No => develop complementary "Toogle" service that anyone can host to index all product URNs and match them with user queries (a Google for transactions) Keep in mind that product elements should be matched against the entire subset (e.g. place names, see https://simplemaps.com/data/world-cities/)

Step 3

If trustchain is suitable for storing massive quantities of data (e.g. videos) AND average response time < 1s

• Yes => check for every ask/bid if the product URN exists in the trustchain
• No => develop complementary "Tikipedia" service that anyone can host to store and send product information (a Wikipedia for transactions)

Extra step

GUI for tweakers

Should-haves

Step 4

Differentiate between digital / physical products in the code

• Digital: stream to stream (I give you a coin, you give me a coin, iterate; OR; I give you a coin, you give me part of the file, iterate)
• Physical: custodian handles the transaction

Step 5

Develop custodian service

• Only a really bare-bones interface: it can become really complex when dealing with payment period, paying in terms, lottery style, refunds, damage claims, etc.

Step 6

• Develop review system for sellers (Toogle providers, Tikipedia providers, and custodians are also included under "Sellers")
• Develop review system for buyers

Step 7

• Add item "Templates" to the Toogle service
• Add review "Templates" to the Toogle service
• Add general terms and conditions "Templates" to the Toogle service

Step 8

• Implement field for manual approval
• Implement field for "infinity" amount bids
• Implement field for "enable bidding" (/ minimum bid / tick size)
• Implement field for "price as quotation upon request"
• Implement field for "notify third party after purchase" (e.g. corporate share register)

Step 9

Evaluate options for age check, Know Your Customer (KYC), Anti-Money Laundering (AML), Counter-Terrorism Financing (CTF), and creditworthiness checks

Could-haves

Step 10

Implement a watchlist that notifies user when certain matching asks/bids are entered into the system (probably add to Toogle)

Step 11

Implement "automatic review system" for Toogle and Tikipedia providers, by checking them at random intervals creating graphs showing their reliability