Reward requests become specific while the draft remains unfinished
Rupesh said 6 weeks had elapsed since the proposal passed and challenged repeated references to a few more weeks. The holder put forward concrete delivery alternatives: transfer rewards directly to wallets, reopen the existing claim interface with updated allocations, or announce a fixed claiming date. Alongside those options was an accusation of repeated unfulfilled promises. The demand had moved beyond reassurance to a distribution mechanism or a deadline that participants could actually track.
Rupesh said 6 weeks had elapsed since the proposal passed and challenged repeated references to a few more weeks. The holder put forward concrete delivery alternatives: transfer rewards directly to wallets, reopen the existing claim interface with updated allocations, or announce a fixed claiming date. Alongside those options was an accusation of repeated unfulfilled promises. The demand had moved beyond reassurance to a distribution mechanism or a deadline that participants could actually track.
Earlier that day, administrator Diablo had said the team also worked at weekends and would share the draft once finalized. In response to the draft comment, seven asked whether publication would activate the proposal immediately or whether implementation would require more time. Those earlier exchanges did not answer the later demand with a claiming date. They identified the unresolved distinction between publishing a document and making its reward provisions operational.