Summary
Following recent updates, Tally has ceased operations. As a result, we are proposing to formally deactivate Tally from the RootstockCollective dApp and opt them out of the Collective Rewards program.
Context
Tally has been a key governance infrastructure provider in the ecosystem, supporting onchain proposal creation, voting, and delegation. RootstockCollective itself has leveraged Tally as part of its governance stack.
Deactivate Tally as an active builder in the RootstockCollective dApp
Next Steps
If approved, the team will proceed with the deactivation on the dApp
No further action is required from Tally
*Acknowledgment
We want to acknowledge and thank the Tally team for their huge contribution to onchain governance and their support of RootstockCollective during their time in the ecosystem. They will be missed!
*
It makes perfect sense to remove Tally from service providers, since they will no longer be active.
That said, the ScopeLift team, integrated by Tally’s smart contract engineering partner, will take over Tally’s operations. Do you think it would be valuable to contact them so they can continue the backup operations for the Collective’s voting app?
I’m specially thinking about a very important feature of Tally: tracking and publicizing how each member votes (whether they delegate or not), which I believe is helpful for @Raphael_Anode and for anyone who wants to know how each delegate and community member votes.
The proposal seems to refer both to Tally’s role as a service provider and its role as an active Collective Builder participating in the Rewards program.
@SEEDGov and @Raphael_Anode have commented on the service provider functionality potentially being incorporated into the dApp.
It would be helpful to clarify whether the transition to Scopelift also includes taking over the active builder role within the Collective Rewards program, or if that role is being sunset.
As Tally is no longer active, we agree to remove Tally from the Collective Reward program.
There is no major concern, as Rootstock already has a voting interface in the dApp. We just want to echo @SEEDGov that the feature showing who voted is important for transparency and it also makes @Raphael_Anode work easier, as delegate compensation currently relies on Tally to track voting activity. This feature should be included in the dApp. From our understanding @tobyj is already working on it, so it’s great to see this being addressed.
It would be better to have visibility into who voted on proposals. But I’ve already switched to our own voting platform since Tally has ceased operations, so no issues on my side.
It also makes sense to standardize on a single platform, especially since our own stack can already support. Looking forward to delegate tracking being added to the app.app.rootstockcollective.xyz
I agree with the rationale to deactivate Tally from Builder Rewards.
On a related note, maintaining optionality across governance front ends is still important for decentralization. As delegates are aware, ScopeLift is taking over stewardship of the Tally platform and plans to continue maintaining and improving it.
ScopeLift has already started proactively engaging DAOs and is encouraging teams currently using Tally to reach out directly. They’ve also shared an intake form for that purpose. @tamlerner
I think it would be worthwhile for The Collective to speak with the ScopeLift team. There may be opportunities for alignment or synergies that are not yet obvious. If that conversation surfaces a meaningful path forward, it could make sense to consider ScopeLift for the Builder Rewards Program.
Thanks, @Axia, @SEEDGov and DAOstar for the mentions.
We understand the RootstockCollective is focused on using its dApp as much as possible.
Given the other remarks about the important of having multiple front-ends, we’re very much happy to help in our new role as operators of Tally’s governance platform.
We’re also keen to understand if we can continue contributing towards your Rewards program.
If that makes sense, it would be great if we can have a quick call with the community to get the full context.
Please fill in the form @Axia mentioned so we can arrange one at your convenience.
It will be great to put this proposal on chain as soon as possible, because it totally makes sense that if the team is no longer active and working in ecosystem, we should remove them from Activited Builders. So that resources will be distributed among other teams who are actively contributing and are active towards working.
We fully support moving this deactivation to an on-chain vote as soon as possible and agree with @Axia on maintaining optionality across governance front ends is still important with respect to decentralization.
@tobyj could you please confirm if the team are working on the Rootstock Collective native voting dApp to include a feature that shows who voted on each proposal (in fact, which wallet), and how they voted? This is a very important feature that Tally currently offers, and it would be very important not to lose it by incorporating it into the official dApp. Thanks in advance!
https://x.com/tallyxyz/status/2033917127304814802
