210 похожих чатов

Basically the ACI amounts to a permissionless ability to build

Metagraphs and public data types at will, correct? and it's up to Metagraphs to broker the logic between themselves which is then executed by the global executor. so "trusting" the Metagraph as a first party oracle is at the discretion of the consumers..whether they are other Metagraphs or end users of that particular Metagraph service

5 ответов

21 просмотр

It is about the interoperability/networking between metagraphs - building metagraphs and data types is already permissionless, there is no ACI needed for that. Once you want to start to use the respective data type between different metagraphs or validate it on the gL0 then you will need the ACI. The specific metagraph data itself is dependent on the metagraph consensus and this is up to each end User to check.

SethV- Автор вопроса
criptix | I WILL NEVER PM FIRST
It is about the interoperability/networking betwee...

yea, I guess what I mean is the ACI permissionless in terms of what data types are published into it's registry of data types. does that make sense?

SethV
yea, I guess what I mean is the ACI permissionless...

Oh you mean supported data types - yes, you will be able to validate completely arbitrary data on the gL0, so the ACI will need to support arbitrary data types imho.

SethV- Автор вопроса
criptix | I WILL NEVER PM FIRST
Oh you mean supported data types - yes, you will b...

yea. like there isn't an approval process that screens data types before being allowed to enter the ACI registry

Похожие вопросы

Обсуждают сегодня

Карта сайта