Tokens

Specification of the NFT tokens issued for the assets

The NFT tokens that are issued on the platform are the single source of truth about the asset that is being sold. Thus it is important to specify the different metadata carried by this token. Currently there is no specific standard for this, hence we define what we feel as adequate for value representation of the asset on chain.

NFT: House ownership Token

Index	Key	Type	Description
1	Name	String	The name of the NFT
2	Street Name	String	Name of the Street
3	Postcode	String	Postal code
4	HouseNum	String	Number of the house
5	City	String	City where it is located
6	Country	String	Country code following ISO 3166-1 standard
7	OwnershipType	String	Type of ownership Individual / Corporate
8	AssetType	String	Should represent the type of asset. For example Bungalow, Apartment, Condominium and so on.
9	Latitude	String	Latitude on 2d Map
10	Longitude	String	Longitude on 2d Map
11	KYC-PolicyID	String	PolicyID of the NFT minted to store the KYC ID of the user.
12	Owner_Documents	[{doctype:"", docUrl:"", signature:""}]	House documents verifying ownership, combined with signature using private key of owner wallet
13	Legal_disclaimers	[String of Urls]	Urls holding the legal disclaimers for this NFT.
15	ConstructionYear	String	Year of the construction and first registration of the asset
16	Metadata	JSON	Off-chain metadata hash
17	PolicyID_lastversion	string	PolicyID NFT last version
18	issuanceDate	string	Date and time string in ISO 8601 format
19	issuancePlatform	string	In this case "Reitcircles" and can be adjusted for other platforms

The protocol does not define some of the bad weather scenario that may happen and changes adaptations may be needed to fix them. Some of the bad weather scenario's that can arise is:

1. NFT of the house being a high value asset needs to be protected against scenario where they are lost or misplaced, either by chance or due to unfortunate hack happening of the wallets. Just like credit cards needs to be blocked or re-issued in case of theft, the high value tokens should also have the possibility to be the same.

2. Some of the data related to the NFT needs to be updated like legal disclaimers, ownership type etc.

NFT: HOUSE PROXY TOKEN

This token needs no specification. It can contain the reference to the House token or replica of the data as the house token and an extra field qualifying it as a "Proxy" token.

Index	Title	Type	Description
1	Proxy	Boolean	This is by default set to True for this token
...	...	...	All other fields can be the same as House Token

NFT: KYC ID token

Index	Title	Type	Description
1	KYCId	string	ID of the person as registered within the KYC platform
2	issuanceDate	string	Date and time string in ISO 8601 format

The KYC token is issued to the persons registered via KYC on the platform, and will be used to identify this person during token transactions on the platform.

Also the policyID of this token is embedded in the House Token and hence real world identity is tied to ownership of the house.

The information provided above will be used to communicate with a verification server that will close the loop and allow much greater security for house owners on this platform.

The reason we have kept this as a separate token, is because as the platform evolves and becomes more decentralised, this decoupling becomes helpful in scaling the platform.

NFT: DAO ROLES token

Index	Title	Type	Description
1	RoleName	enumString	Can be Admin, Manager, Member etc.
2	allowedTasks	string	Keeping this for extension. Currently it can include string "roleBased".
3	ExpiryDate	DateAndTime	ISO8601 Standard