# Multi-Dimensional Value

A multi-dimensional value system plays a major role in transforming existing digital "transactions" into "interactions" bearing multiple information vectors and value transfers. This facilitates participants to discover a whole new arena of ways to exchange values that are mutually agreed upon by respective participants. MOI network provides the ability to create, persist and manage all digital assets natively as multi-dimensional values. These values accrued by the participant over time are represented in the form of Total Digital Utility (TDU).

In summary, TDU is a collective measure of disparate behavior of actors in the MOI network across different types of interaction through one or more applications. It offers a multi-dimensional value environment for all MOI users to leverage their respective interests and abilities to avail the digitalservices in exchange for verifiable TDU points. It is further defined by the following dimensions as fields:

type TDU struct {
EconomicPoints AssetBalanceMap json:"tdu_economic_points"
PrivilegePoints AssetBalanceMap json:"tdu_privilege_points"
TimePoints AssetBalanceMap json:"tdu_time_points"
SocialPoints AssetBalanceMap json:"tdu_social_points"
BarterPoints AssetBalanceMap json:"tdu_barter_points"
EmotionPoints AssetBalanceMap json:"tdu_emotion_points"
PossessionPoints AssetBalanceMap json:"tdu_possession_points"
}

The fields in the TDU structure, 𝜚, are described below:

• EconomicPoints: Economic points assigned to the account. This is formally denoted as 𝜚E

• PrivilegePoints: Privilege points assigned to the account. This is formally denoted as 𝜚P

• TimePoints: Time points assigned to the account. This is formally denoted as 𝜚T

• SocialPoints: Social points assigned to the account. This is formally denoted as 𝜚S

• BarterPoints: Barter points assigned to the account. This is formally denoted as 𝜚B

• EmotionPoints: Emotion points assigned to the account. This is formally denoted as 𝜚E

• PossessionPoints: Possession points assigned to the account. This is formally denoted as 𝜚Zt

Where the type AssetBalanceMap is defined as a mapping of a unique asset ID to the number of tokens held by the user. The code snippet is as follows:

type AssetID string
type AssetBalanceMap map[AssetID]uint

This completes the definition of the Balance field of an account.

For each asset in TDU, there must be a representation. We will see that in the following section.