> For the complete documentation index, see [llms.txt](https://lynqyo.gitbook.io/lynqyo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lynqyo.gitbook.io/lynqyo/product-architecture/approach.md).

# Approach

1. Entities

There are three main entities in lynqyo: creators, fans and content. Creators are able to supplement with value and entertain their fans easily using CUBE infrastructure on the lynqyo ecosystem. Each eligible creator can be uniquely identified by a public key constructed through a derivation of the address that staked the necessary amount and the node ID. Relations between entities in the lynqyo ecosystem are shown in Fig.2.

![](https://lh4.googleusercontent.com/a8GqY_X9_Xjtr4aBHWOo6WFAldnP2jBbqYniw3NjdHqvoALwcKYgFIC1sS6fLRWZpxmWHpLjprNm3VVj1hJ1y7d9ST5DJ5fy1bVF48oRUq0pBeRcXls6vOe7ipDvelQKU8KdNFVFtbFAd1ujwAi-4Q)**Fig.2 Entities Structure**

Furthermore, our infrastructure is divided into smaller units called CUBES. An eligible validator is assigned to a shard based on an algorithm that keeps the nodes evenly distributed across shards, depending on the tree level. Each shard contains a randomly selected consensus group. Any block proposer is responsible to aggregate transactions into a new block. The validators are responsible to either reject, or approve the proposed block, thereby validating it and committing it to the blockchain.