Secured connectivity between Meta Chain and Native Chain

[fuxingloh]

What would you like to be added:

Secured communication between Meta and Native Chain. Ideally a symmetrical JWT secret.

Similarly, on Ethereum PoS design it uses a combination of a consensus layer and an execution layer which are separate processes. The separate processes communicate over an authenticated port using JSON RPC with a JWT secret.

Why is this needed:

Secure processes to prevent hijacking.

[defichain-bot]

@fuxingloh: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

[defichain-bot]

@fuxingloh: There are no 'area' labels on this issue. Adding an appropriate label will greatly expedite the process for us. You can add as many area as you see fit. If you are unsure what to do you can ignore this!

You can add area labels by leaving a /area comment.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

[fuxingloh]

/area meta
/meta node

[fuxingloh]

Alternatively, we could validate transactions coming from the native side for transaction validation and vice-versa.