Interesting concept. I’m a bit wary of having only one key and no way to ever reset it. If it ever falls into the wrong hands, there would be no way to stop mischief, short of intentionally driving and keeping its voting mana at zero, which I guess would be no different from having sent the tokens to @null to begin with.
With all that said, I’ve often wondered how the @null account is guaranteed to have no keys that can access it. If someone can give the technical overview on that, I’d be interested in hearing it.
That's the thing. There are no keys, so there's no way to authorize a transaction on behalf of @null account. That's for owner, active, and posting authorities. However, @null has a signing key defined, but this key is a NULL key, so there's no corresponding private key that could match it and sign transaction.
This account (defined in
libraries/protocol/include/hive/protocol/config.hpp) is also special,because it has its balance cleared, see:
database::clear_null_account_balance()inlibraries/chain/database.cppThanks!
@gtg probably can. :D