You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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.
gno/examples/gno.land/r/system/names/genesis.gno
Line 5 in 76f079d
gno/examples/gno.land/r/system/names/names.gno
Line 13 in 76f079d
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
The text was updated successfully, but these errors were encountered: