InvArch — project architecture

Hello, in the last article I wrote and told you about such a project as InvArch, told about its plans and advantages in the future, today I would like to touch in more detail such a thing as the architecture of the project

InvArch and Polkadot.

The InvArch blockchain and platform will be built utilizing the Substrate
development framework, and the underlying Rust programming language. The intention behind these decisions is to have the InvArch blockchain be deployed to the Polkadot network’s multi-chain ecosystem and parachain relay

Parachains.

A parachain is an application-specific data structure that is globally coherent and validatable by the validators of the Relay Chain. Most commonly a parachain will take the form of a blockchain, but there is no specific need for them to be actual blockchains.

The InvArch blockchain will be seeking this development path to utilize the benefits of shared security,
fast transaction speeds, and interoperability.

Intellectual property Sets.

In context, an IP Set is viewed as an idea, which consists of one or more
components (IP Tokens) that help to strengthen and describe that idea

For example, a 3D rendering of a flux capacitor prototype could be stored as an IP Token representing an STL file. Additionally, an XML file explaining the relation between a flux capacitor’s different components could also be stored as an IP Token in the “Flux Capacitor” IP Set, these two files exist and help to
strengthen and expand on the idea for building a flux capacitor.

Intellectual Property Tokens.

Utilizing the InvArch Blockchain, users will be able to tokenize their ideas
or intellectual property (IP) in the form of non-fungible tokens called IPTs. An IP Token (IPT) is a part of a set and can be thought of as a component of an idea. Either by itself or in combination with other IP Tokens, it serves to strengthen the foundation for an idea. IP Tokens represent a unique digital asset. IP Tokens are stored using IPFS, which is a decentralized storage protocol that securely stores files off-chain and provides a unique hash or CID which is used to query the data.

Intellectual Property Ownership.

Intellectual property tokens will be able to have their ownership divided
among multiple addresses or owners. IP Ownership (IPO) is a form of fractional ownership over an IP Set.
A finite and preset number of fungible IPOs may be assigned to a single intellectual property set. The value of a single IPO will be determined by the total amount of the network’s native currency bonded to the IP Set, divided by the total number of IPO tokens. To ensure that no single actor can have a 51% hold over a project when forming a DEV, IPO can be distributed within the following ranges:

𝑓 + 𝑡 = 10000 | 0 ≤ 𝑓 ≤ 6600 | 3400 ≤ 𝑡 ≤ 10000

Among the Founders, out of however much IPO is decided to be allocated, no single participant can have more than 50% (Max. 3300) of the allocated IPO. No single co-founder can have a higher stake than the founder. The distribution algorithm for the founder’s distribution is:

𝑓(𝑂) / 𝑝(𝑛) ≥ 𝑝(𝑂)

Where 𝑓(𝑂) represents the founder’s total IPOwnership tokens, 𝑝(𝑛) represents the number of co-founders, and 𝑝(𝑂) represents a co-founder’s

IPOwnership tokens.

This statement must pass to form a DEV, and changes that break this statement cannot be implemented. * Voting Weight IPO acts as a governance
token over a DEV. Holders have the right to propose development changes, financing strategies, report misconduct, and vote on status consensus reports. Every DEV has 10,000 votes, with an IPO representing a single vote. The more IPO a participant has, the more voting weight they have.

Leveraging these new forms of tokenized assets, users will be able to establish partnerships with other individuals and users who provide hard skills and/or resources that their intellectual property set (IP Set) is missing to come to fruition.

Decentralized Entrepreneurial Ventures.

Creators of intellectual property sets will be able to bond them
using the DEV Pallet. This Pallet is responsible for taking ownership over an IP Set, establishing roles and terms for a venture, and recording the application process for agreeing. Users will be able to leverage ownership over their IP Set, and therefore parallel value, in the venture.

Governance rules, general development timelines, and partnership terms are defined at this time. As an alternative to offering skills in return for employment on a job board, users can provide their skills in return for equity and entrepreneurship through the InvArch blockchain.

Multi-Layer Governance.

Project management and development sometimes require different levels of governance. In some cases, it may be optimal to only allow certain individuals (usually specialized in their background) in a DEV to have a say over a decision. In other cases, it may be optimal to allow all IPO token holders to be able to participate in a decision to address a deadlock or dispute within a DEV. Other decisions may be best if all working members in a DEV, regardless of their role, have a say over a decision. The DAO Pallet will provide the logic for customizing and layering different governance mechanisms throughout a single venture.

Participation in decision-making within a DEV is democratic, meaning that voting takes place and decisions are decided based on group consensus. Consensus can be reached using different rules, but the most common margins are 51% and 67% majorities. To participate in a voting procedure (which usually takes place over a period of anywhere from 24 to 72 hours), a user must have some amount of the voting DEV’s IPO tokens. The percentage of IPO that a participant wields is equivalent to their voting weight.

Development Work Logs.

Whether the work is recorded and reflected via video recording, a file with
programming code, or anything in between, these progress reports are stored and made visible to the participants in a DEV. This is a way of recording and monitoring work progress for all to see and can be required to be submitted on a weekly or bi-week basis. This is also a way of protecting those who submit
the updates, as this permanently stores their work for reference and proof of existence.

Project Deliverables.

The Deliverables pallet handles the logic for assessing the work submitted using the Development Work Log. Upon certain development milestones being completed and group consensus signing off on the results, IP Ownership tokens can be administered to the submitter of the work. For
example: Say a user was being allocated 2,000 IPO tokens for their participation in a DEV. Their work consisted of 2 development milestones. The first milestone could administer 1,000 IPO upon completion and consensus. The second milestone would administer the remaining 1,000 IPO. Additionally, in the future, users can choose to only reveal or expose IPTs within an IP Set as needed for each milestone.

Decentralized KYC.

The chain will integrate with a pre-existing decentralized KYC protocol. This will ensure the identity and integrity of participants in a DEV and serve as a way of enforcing compliance and preventing bad actors from existing within the system, as their actions would be known and their identity
unique and verifiable. It would be a poor decision to commit acts of blackmail or intellectual property theft over the InvArch network, considering the identity of anyone who does these things would be known and their interactions with intellectual property recorded.

Smart Contracts.

To expand upon the functionality and capabilities of the network, InvArch will also provide smart contract functionality using Ink! Smart Contracts. to deploy and execute WebAssembly Smart Contracts. It has its smart contract language, specially designed to write contracts that optimize for
correctness, conciseness, and efficiency

conclusion

That’s it, do you like the architecture of the In vAr ch project, do you see success in the future?

Personally, I really like the project and I believe in its future, I will be very active in its ambassador program!