Open alexauroradev opened 3 years ago
@evgenykuzyakov what do you think?
Relevant discussion https://gov.near.org/t/store-protocol-config-in-a-contract/2105
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Some factory contracts (for example, [the bridge FT connector factory](https://github.com/near/rainbow-token-connector/blob/master/bridge-token-factory/src/lib.rs#L238-L266), or mining pool factory) during their lifetime deploy other contracts. At the moment factory contracts have [hardcoded values](https://github.com/near/rainbow-token-connector/blob/master/bridge-token-factory/src/lib.rs#L24-L32) for the required storage deposits. Similar problem is valid for the data storing.
This can be enhanced, by providing in the runtime an environmental variable for yoctoNEAR cost per byte and/or a function(s) that takes as an argument a piece of data to be saved OR a contract to be deployed and returns the amount of yoctoNEAR to be used as a deposit.