Back to collectionA proposal to count the time between challenges
The intervals between batch submissions had become less steady. The team put a proposal before key holders. The support gave the change a direction, but the rule had not taken effect.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
The intervals between batch submissions had become less steady. Key holders saw challenges arrive in quick succession at times and take much longer at others. For the product team, the question was how to explain and calculate rewards for the gaps, rather than whether the chain itself was functioning.
The team put a proposal before key holders. The chain itself had no problem, it said, but variable submission timing made challenge intervals uneven. A missed challenge remained missed, so reward reliability mattered to the community. The proposal would calculate rewards according to the time since the previous challenge. Replies were almost unanimously supportive; some felt it would at least account for the wait.
The support gave the change a direction, but the rule had not taken effect. Key holders still needed a clear calculation method, especially for machines that went offline or came back online partway through an interval. The team had yet to turn the proposal into details people could check.