This issue is preparation work for the Self-Spawn.
We want SVM to support having an Account in a Pending State (i.e., inactive).
That Account won't have any Template attached to it, and therefore it can't run any code.
That said, it can have a non-negative balance and be part of the Global State.
To stay efficient, looking up an Account should work the same regardless of whether it's active or not.
This issue turns the current Account into ActiveAccount, creates a new PendingAccount, and adds a new enum called Account.
That enum will enforce giving attention throughout the codebase of whether any Account would work or whether we expect it to be active or pending.
I think it's safer than just having a new is_active boolean added to the current Account.
This issue is preparation work for the
Self-Spawn.
We want SVM to support having anAccount
in aPending State
(i.e., inactive).That
Account
won't have anyTemplate
attached to it, and therefore it can't run any code. That said, it can have a non-negative balance and be part of theGlobal State.
To stay efficient, looking up anAccount
should work the same regardless of whether it's active or not.This issue turns the current
Account
intoActiveAccount
, creates a newPendingAccount
, and adds a newenum
calledAccount
.That
enum
will enforce giving attention throughout the codebase of whether anyAccount
would work or whether we expect it to be active or pending.I think it's safer than just having a new
is_active
boolean added to the currentAccount
.Implementation Proposal