Symverse

SymVerse is a multi-blockchain platform ecosystem with 1-second block Finality that operates based on self-sovereign distributed ID.

With a Symverse-based ID system, independent blockchain platforms can expand blockchain services as a cooperative ecosystem that interacts with one another.

SymID

The SymID information makes it easy to check which blockchain mainnet is being used, and what its purpose is based on account identifiers. By reviewing the contents of the documents possessed by SymID, it is also possible to determine the legitimacy, authenticity, and status of the ID.

SymID is one of the most advanced forms of the DID (Decentralized Identifier) standard recently spotlighted in the blockchain industry.

A document containing different types of information along with the SymID is stored in Citizen Chain.

It is generally accepted that the public key hash used as an ID in the block chain has a length of 20 bytes. Having 10 bytes of data, SymID consists of two network identifiers, six citizen identifiers, and two account identifiers.

With a SymID of 10 bytes, 281 trillion IDs can be generated, and one SymID can contain 2^16 accounts (credentials).

SSII(Self Sovereign identity Information)

Field			Size	Description
SymID	Ver		2b	0: version 1
	Citizen ID	CA ID	14b	0x001 : Master CA 0x002 ~ 0x3FFF : CA
	Citizen ID	Random	6B	0x00...01 : CA Random Number : General users (requires double check)
	SeqNum		2B	1: General Credential 2 or more : Basic Credential

SymID's Basic Credential simplifies complex ID information by storing ID properties, facilitating Dapp development.

Structure of SymID

Credential (Basic)	PubKeyHash	20 B	Hashed Public Key
	Role	2 B	0x0001 : General 0xF0F0 : Master CA 0xF0F1 : CA
	Verification Flag	3 B	Reserved
		1 b	Deposit
		1 b	Face-to-Face
		1 b	National Identity Card
		1 b	Cell phone number
		1 b	E-mail
	State	1 B	0x01 : Active 0x02 : Revoked 0x03 : Locked 0x04 : Holding // holding for credential update 0x05 : Marked // Foundation Settings (Oracle)
	Credit	1 B	Credit Rating (0~15) // Foundation Settings (Oracle)
	Country	2 B	Country code

Example

Owner(Holder)	Description
Master CA’s 1st Account	0x0001 000000000001 0002
Master CA’s 2nd Account	0x0001 000000000001 0003
Oracle	0x0001 000000000002 0002
Reward	0x0001 000000000003 0002
1st CA’s 1st Account	0x0002 000000000001 0002
1st CA’s 2nd Account	0x0002 000000000001 0003
1st CA’s 1st User’s 1st Account	0x0002 XXXXXXXXXXXX 0002
1st CA’s 1st User’s 2nd Account	0x0002 XXXXXXXXXXXX 0003
1st CA’s 2nd User’s 1st Account	0x0002 YYYYYYYYYYYY 0002

Multichain

SymVerse is composed of four different blockchains, and since each block generation time is different, it can realize high data processing speed.

A single blockchain node consists of the Main Chain, Citizen Chain that records ID information, Warrant Chain that records rewards, and Oracle Chain that records blockchain parameters and external information.

The Main Chain has an average creation time of 1.39 seconds and is created using the enhanced BFT (Byzantine Fault Tolerant) method.
Blocks in Citizen Chain that contain DID documents are created when IDs are recorded.
And a Warrant Chain block that records rewards for nodes and users participating in SymVerse is created once a day.
Blocks in Oracle Chain are created when recording governance voting history or data coming from external systems.

main block Chain

Transaction, Contract, Reward Storage

Citizen block Chain

SymID, Information Update

Warrant block Chain

Selection of warrant node, Rewards

Oracle block Chain

Operation policy, token exchange rate

Consensus Process

The block generation method, which agrees on the details of the data stored in the Symverse block, uses the enhanced BFT (Byzantine Fault Tolerant) method with strategic voting applied.

The design of the Symverse Consensus Process is based on game theory. Utilizing the Gibbard-Satterthwaite theorem of social choice theory, made it impossible for block producers to obtain benefits by manipulating the contents of blocks through voting with Veto rights applied.

There are 25 guarantee nodes, 9 of which are called group A and selected by the foundation. Group A nodes do not have the right to generate blocks, they can exert only the right to vote and collectively veto showing the same voting result. If more than 2/3 of all guaranteed nodes agree, the consensus process will be terminated.

Guaranteed nodes of Group B are selected through a 4-step Autonomous Bench Marking Test, which is a decentralized and fair selection process among the job nodes for which candidates have applied. Including the primary node (1) that manages the consensus process of block generation, the front bench node (3), the middle bench node (8), and the back bench node (4) It consists of 16 pieces.

< Augmented BFT >

Block Confirmation

The main chain is created within 1.39 seconds on average, including the block generation time and the time the proposer receives the signature from the nodes participating in the consensus process. Therefore, the details of the main chain can be used after the block contents are confirmed through creation and signature. (Unlike EOS, Cosmos, and Ethereum, the transaction is confirmed at the time of creation)