Tally: Front-end interface to force transaction inclusion during sequencer downtime

I will be voting “For” this proposal on Tally.

As a broad concept, making this functionality more accessible to users will be a useful tool as a backup plan in the event of sequencer downtime. So I am glad to see this being taken on by a team.

Initial concerns I had when reading the post seem to have been asked and addressed by other users. Probably my largest being if this type of risk extends past those who interact with the contract. With that being addressed here & here, I am comfortable with the project as pressent. Things such as ongoing support being factored into the ARB ask are nice additions too - the flexibility of the proposing team is appreciated.

The team looks to have a good technical background and the request amt / the timeline both look reasonable as well. So no issues there.

Probably my only thought for improvement would be if there was a milestone attached to funding. It could be as simple as the initial 35k is paid out now and the 10k service & maintenance fee is paid once the project is completed. Given the relative amount asked I don’t see a huge issue to the point I wouldn’t approve regardless, but I think it’s worth bringing up now at the Snapshot stage as a discussion point.

Edit: Updating (5.21.2024) here to save forum space. My opinion has remained unchanged of the above since the snapshot vote. I have voted “For” Tally, and look forward to seeing the end product.

2 Likes