How to add modifier to public state variable?

Question

I have a contract that looks like this

pragma solidity >=0.7.0 <0.9.0;

contract SomeContract {

    uint256 public id;
    address public creator;

    enum Status {ACTIVE, INACTIVE}

    Status contractStatus;

    modifier checkStatus {

        require(contractStatus == Status.ACTIVE);

        _;

    }

    modifier onlyCreator {
    
        require(msg.sender == creator);

        _;

    }

    constructor() {

        contractStatus = Status.ACTIVE;
        creator = msg.sender;

    }

    function doSomething() external checkStatus {

        // do something here

    }

    function changeStatus(bool _isActive) external onlyCreator {

        if (_isActive) {
            contractStatus = Status.ACTIVE;
        } else {
            contractStatus = Status.INACTIVE;
        }
        
    }}

}

This contract works fine. The problem is after I deactivate the contract, people still can access public state variables like id and creator because solidity automatically creates a getter for each of these variables. Is there any faster way besides making it internal and creating my own getter and adding a modifier to it?

Answer 1

By default public variables have already built-in getter, you can stop that by changing the variable type to private or internal. But don't get confused with the word "private", because nothing is really private on the blockchain. Even if you change id and creator to private type this will remove the automatic getters that you see in Remix, but this data is not hidden and everyone can still access it.

On top of my head the first ideas I have to save sensitive data in smart contracts are via asymmetric encryption ( the contract is saving encrypted format of the data and the data is being decrypted on the front end ) or keep the sensitive data offchain and make connection to it with the smart contract.

Answer 2

No.

The creation of the public getter is automatic and you can't influence that.

I think you can override the getter in an inheriting function, but that certainly isn't easier than writing it in the same function.

And in any sense, there is no way to "hide" information in a contract. Even if users can't access it directly, knowledgeable users will be able to get the data (for example getting it from the block before the data was restricted).