Hi,
I would like my thesis to discuss and provide a solution to the following problem
“Bringing physical value to nft’s in the real world”
Problem statement : Currently NFT’s do not have any physical usage or value in the real world.
This thesis should provide academic detailed research on blockchains, metaverses, NFT’s and smart contracts, explaining how they each currently run and how they all come together.
It should then show how currently NFT’s are being sold for ridiculous prices, yet they dont have any physical use or value in the real world.
The thesis should then describe in detail the solution
The solution to this is being able to attach NFT’s to already existing “Real world objects” like fashion items, cars , houses, clothes . In other words , taking existing physical products and turning them into 3D NFT’s.
After attaching 3D NFTS to these physical products (using smart contracts), they will then be placed on a marketplace created by me , which will allow users to buy, sell and exchange their NFTS. Only NFT’s which have a physical product behind them will be allowed on the marketplace.
1 possible problem with this solution : we have to design a process that is able to verify the physical item is authentic
These NFTS will also be made avaialble to use in the different metaverses(decentraland, sanbox, axie infity).
The thesis structure requirements
Report Format
As a general rule, the body of the dissertation should be between 12,000-15,000 words this will normally corresponds to about 40-60 pages if you include some diagrams. We don’t have prescriptive style/format, but students should choose a font that is easy to read (normally 10 or 12) and are encouraged to use one and a half line spacing. You should include appendices for additional material not central to the report (e.g. questionnaires, screenshots) and these will be in addition to 12,000-15,000 pages for the main body.
Content and Structure
Student’s projects will be assessed primarily from the report and it is therefore essential that it is full account of your work and clearly presented. The detailed structure will depend on the type and nature of the project and students should obtain advice from their supervisors. Supervisors are also expected to comment on outlines and drafts. When writing the report students should make sure to pitch it at the right level. They should not assume that the reader is an expert in a specialist topic that they are reporting, but should assume that they have a good knowledge of the general discipline. If a good fellow student would understand it then that is about right.
· Title page
· Abstract: a summary of the project highlighting major points and describing the project’s scope and conclusions.
· Acknowledgement: any one student wish to thank.
· Table of contents: detailed breakdown with chapter headings, section headings and may be subsection headings, each with page numbers.
· Table of figures: location, number and legend of all figures in the report
· References
· Bibliography (optional)
· Appendices
Chapter1
Should normally start with a short introduction to the problem you are addressing and your aims and objectivws, give a short review of the context and describe what follows in the main body of the report.
Chapter 2
should normally include a critical review of the pertinent literature review so the reader would understand what you are building on. You may also describe techniques, guidelines and even existing products if relevant to what you will be presenting later. It is important that this review is written in your words throughout, reads as a coherent and connected piece of writing, shows the relevance of the material presented to the problem being addressed and provide some critique / analysis of the material and its applicability to the problem. In essence it is your analysis and understanding that we are interested in, how you build on existing work, understand its limitations and gaps, select from available methods/tools with some justifications, and present that coherently.
It is important you select your references carefully in your review. It is not sufficient to find 15 web sites which seem to have something relevant to say. Sources should be authoritative, accurate and preferably should still be around in five years’ time. Academic papers and books usually meet these criteria but also some web sources are acceptable.
The structure of the middle section of the report will vary according to the type of the project.
Middle Section(Rest of the Chapters)
The structure of the middle section of the report will vary according to the type of the project. Many possible structures are possible but two typical structures are presented here:
A) Software development project: the goal is to develop some software to solve some problem. The chapters should cover requirements, design, prototyping and redesign, implementation, testing, evaluation and conclusion. This structure is appropriate where you have a customer (external or supervisor) who wants some software for a real life problem. A successful project is one where you elicit the customer’s needs, develop a reliable and functional solution, and test/evaluate the software and demonstrate that in deed meet the customer’s needs. A simple set of web pages might satisfy some customers but would not result in you getting the MSc.
B) Research oriented project: the goal is to advance understanding by carrying out an investigation which may include prototyping a system. The chapters will present the problem (sometimes as a hypothesis), review existing work, describe the research undertaken (including design of any experiments), present the results of any experiments, present any conclusions, relate to these to past work and suggesting further work.
The final chapter
will present conclusions and discuss further work. It should also mention Evidence of Legal, Social, Ethical and Professional issues. Also it must be clear just what has been achieved against the original objectives/problem description set out in chapter 1.
Project Evaluation
It is not enough to achieve something in doing your MSc project by way of software development or by conducting some experiments. You also need to demonstrate the worth of what you have achieved by some kind of independent standard other than your own satisfaction with what you have done. With a software development you can do this by conducting an evaluation with the help of some third parties. Evaluation is different from testing your software. The aim of testing is to verify that your software does what is designed to do. The aim of the evaluation is to validate that your software fulfils the project’s requirements. A minimum evaluation might be a checklist comparison of what the original requirements were and what/how you succeeded in implementing them.
Your evaluation should be written up and presented in your report after you describe what you have achieved. Usually you would present this in a special chapter by itself. No software is perfect so the evaluation is likely to reveal some shortcomings. You should not try to hide or disguise them. You are unlikely to convince your markers that your success was one big success story if your evaluation just presents a bland picture of a successful outcome. You should turn around the shortcomings by being honest and realistic about them and even take the opportunity to say how they might be improved. This self-critique is often the most interesting part of a project. Finally, part of your evaluation should consider the potential commercial risks that your project outcome may be susceptible to and how any such risks can be mitigated. In some cases this aims to investigate and develop practical and universal approach to assess and rate large-scale commercial risks.
Report References
Your report may cite a wide range of sources (e.g. papers or web sites that you have used) as background and context of the work. Sources are cited at the relevant point in the text and full source information is given in the references section. There are a variety of acceptable citation and referencing style but the most commonly used styles are the Harvard style and the IEEE style which are recommended in the MSc projects.
Assessment criteria includes
Thorough definition and understanding of the investigated problem
Evidence of appropriate literature review and a thorough reference list
Detailed explanation and justification of the methodology and approach
Demonstration of an understanding of the key concepts involved
Demonstration of the skills necessary to carry out the work, including problem analysis, application design and development, testing and evaluation and other relevant aspects.
Evidence of Legal, Social, Ethical and Professional issues
Comprehensive nature and depth of the materials
Critical analysis with strong grasp of conceptual context and a solid design
Originality and use of innovative ideas and techniques
Discussion, evaluation and assessment of risk of own results
Quality of the written report
1 Plan, schedule, monitor and control his/her own work
2 Produce a clear set of specifications for the project from its initial stage
3 Defend ideas in discussions with the supervisor
4 Critically analyse previous relevant work and set of data in its widest context; according to the subject area and topic of the project, data may be interpreted as: raw data publically available, data experimentally produced, data generated theoretically or even data as a set of various approaches and methodologies to problem solving.
5 Use effectively libraries and other information sources
6 Understand ethical, legal and professional issues and apply them to a project
7 Apply tools, skills and techniques he/she developed in taught modules
8 Communicate effectively findings in a variety of ways
9 Understand the role of the deliverables at the various stages of the project cycle
10 Write a comprehensive and concise report, justify the project implementation, discuss and explain findings at the viva
11 Critically evaluate the project outcomes and evidence of commercial risks
