gnolang / gno

Gno: An interpreted, stack-based Go virtual machine to build succinct and composable apps + gno.land: a blockchain for timeless code and fair open-source.
https://gno.land/
Other
896 stars 375 forks source link

Name Space Discussion needed. #401

Closed piux2 closed 1 year ago

piux2 commented 1 year ago

The realm namespace is part of the Package Path, which is internally mapped to a contract account address on the chain. It is also part of the service endpoint for the front-end or off-chain services.

The contract admins control smart contract logic and can upgrade contact and modify the state.

https://github.com/gnolang/gno/blob/76f079df092ea0e3d1c43ed35d6ec9bdb7b34ce8/examples/gno.land/r/system/names/genesis.gno#L5

https://github.com/gnolang/gno/blob/76f079df092ea0e3d1c43ed35d6ec9bdb7b34ce8/examples/gno.land/r/system/names/names.gno#L13

Related to this

384

For other chains out there, using the smart contract to manage (gov) chain parameters is not a design choice but a workaround for VM and chain design limitations. But in Cosmos-SDK-Based GVM, we don't have such constraints.

If we model the Gnoland chain as a github with run time and transparent state transition in the cloud instead of a sudo managed computer, we might want to avoid using realm contract (r/system) to manage the parameters of the chain

moul commented 1 year ago

Can we stay on the existing PR please?

-> #384