I just noticed something in the TokenTable technical specifications that raises a practical operational question —
the whitepaper lists scheduled distributions as a core feature —
“recurring payments such as pensions and regular subsidies” with “second-level granularity and calendar months” for precision.
“Second-level granularity” means the payment for a pension can be scheduled to the exact second.
Technically impressive.
The part of the whitepaper that surprises me:
“Second-level precision on recurring government payments is sophisticated infrastructure.”
The whitepaper describes the scheduling feature without describing the failure feature.
After tracking the ETHEREUM smart contract scheduled payment systems and the failure of keepers to trigger transactions on time, a well-known problem in the ETHEREUM smart contract scheduled payment systems —
I came back to the SIGN section. What happens when the scheduled payment is not executed at the defined second?
If the scheduled payment for a pension is missed, the citizen might not receive his or her monthly income on time. In populations where precision is required in the timing of payments, such as rent, medication for purchase, and payment of bills, a payment missed by a day might have consequences.
Still figuring out if…
the whitepaper refers to "user-initiated batch processing" as one of the modes of processing. this implies that there might be some triggering mechanism involved for the distribution. thus, if the distributions are user-initiated, then the second-level scheduling is not a guarantee, i.e., the distribution will happen at the scheduled second only if the user initiates it.
if the distributions are autonomous, i.e., the smart contract execution does not require any triggering mechanism and happens at the scheduled second, then the failure modes are chain congestion, gas availability, or contract state. none of the failure modes were described.
#SignDigitalSovereignInfra @SignOfficial $SIGN
