---
description: Specification of the NFT tokens issued for the assets
---

# Tokens

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

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

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.

<table><thead><tr><th width="150">Index</th><th>Title</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Proxy</td><td>Boolean</td><td>This is by default set to True for this token</td></tr><tr><td>...</td><td>...</td><td>...</td><td>All other fields can be the same as House Token</td></tr><tr><td></td><td></td><td></td><td></td></tr></tbody></table>

### NFT: KYC ID token

<table><thead><tr><th width="150">Index</th><th>Title</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>KYCId</td><td>string</td><td>ID of the person as registered within the KYC platform </td></tr><tr><td>2</td><td>issuanceDate</td><td>string</td><td>Date and time string in ISO 8601 format</td></tr></tbody></table>

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.&#x20;

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

<table><thead><tr><th width="150">Index</th><th>Title</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>RoleName</td><td>enumString</td><td>Can be Admin, Manager, Member etc.</td></tr><tr><td>2</td><td>allowedTasks</td><td>string</td><td>Keeping this for extension. Currently it can include string "roleBased".</td></tr><tr><td>3</td><td>ExpiryDate</td><td>DateAndTime</td><td>ISO8601 Standard</td></tr></tbody></table>

