Terra Classic Proposal Seeks to Restrict Smart Contract Code Uploads in Security Move
Terra Classic could introduce an additional security measure that would change who can upload new smart contract code to the blockchain. A new governance proposal seeks to restrict this ability to governance approval, preventing individual accounts from uploading new contract code without authorization.
The proposal is intended to reduce potential security risks while keeping existing smart contracts and decentralized applications operational. It would not remove CosmWasm from Terra Classic or prevent existing contracts from running.
Before the proposal moves to an on chain vote, community members and developers are being asked to provide feedback, particularly those who may need to deploy new smart contracts in the near future.
What Is the Terra Classic Proposal About?
CosmWasm is the technology that allows developers to build and run smart contracts on Terra Classic. These contracts support blockchain applications and services, including decentralized finance platforms and other on chain tools.
Under the current settings, any account can upload new smart contract code to the blockchain. The proposal seeks to change this arrangement so that new code can only be uploaded through governance approval.
In simple terms, the change would add a community approval step before new smart contract code can be introduced to Terra Classic.
The proposal does not give special privileges to a particular developer, company, or wallet address. Instead, it sets the permission to prevent direct code uploads by all individual accounts unless the community later approves a different arrangement.
Why Does Terra Classic Need This Change?
Uploading smart contract code is a sensitive operation because the code is stored on the blockchain and processed by the network’s validators.
Allowing any account to perform this action creates a broader entry point for potential security risks. Restricting uploads through governance is intended to reduce that exposure and give the community greater oversight over new contract code entering the network.
The proposal describes this as a precautionary security measure. It is not presented as a response to a confirmed attack or a claim that existing Terra Classic contracts are unsafe.
The goal is to strengthen safeguards without disrupting applications that are already operating on the network.
Will Existing Smart Contracts Stop Working?
No. According to the proposal, existing smart contracts and their normal operations would remain unaffected.
The proposed change applies specifically to uploading new contract code. It does not change the default permission for creating new contract instances from code that has already been uploaded.
For Terra Classic users, this means the proposal is not intended to interrupt existing decentralized applications or prevent users from interacting with their current smart contracts.
CosmWasm would also remain part of the Terra Classic ecosystem. The change would restrict how new code is introduced, rather than remove the technology itself.
How Would Developers Be Affected?
The biggest impact would be on developers and teams planning to launch new smart contracts.
If the proposal passes in its current form, developers would need to seek governance approval before uploading new contract code. This could introduce an additional step into the deployment process.
The proposal also leaves room for the community to approve a list of specific addresses that can upload code in the future. For example, governance could authorize vetted development teams or a multisignature wallet responsible for managing deployments.
Any such permission would require a separate governance decision. The current proposal does not automatically authorize any developer or organization.
Developers planning upcoming launches are therefore encouraged to share their requirements before the proposal proceeds to an on chain vote. Their feedback could help the community determine whether governance only access is sufficient or whether a controlled list of approved deployers would be more practical.
Can the Decision Be Reversed?
Yes. The proposed change is reversible through a future governance decision.
If the community later decides that certain developers should receive direct upload permissions, another proposal could authorize selected addresses. Governance could also change the setting again if the community determines that a different approach is more appropriate.
This means the proposal does not permanently prevent new smart contracts from being introduced. Instead, it changes the default process for approving new code.
The current proposal deliberately avoids granting immediate upload privileges to any specific address.
What Happens Next?
The proposal is seeking community feedback before moving to an on chain vote. Community members, validators, and developers can discuss the potential security benefits alongside the practical effects on future contract deployments.
The main question is whether Terra Classic should require governance approval for all new smart contract code uploads or adopt a controlled permission system that allows selected developers to deploy contracts directly.
If approved, the change would add another layer of oversight to Terra Classic’s smart contract deployment process while leaving existing contracts and their execution permissions unchanged.
For the Terra Classic community, the decision comes down to balancing security and developer flexibility. Restricting new code uploads could reduce unnecessary exposure, but the community must also consider how to keep future development accessible and efficient.
