NO. This is an independently developed spec that serves as an extension to the official RMRK spec. This is not endorsed by RMRK, though their endorsement would be appreciated. Please note that the interactions in this spec do not change the state of any NFT in the RMRK extrinsic-based ecosystem, so this is not a fork of the standard.
The RMRKDAO spec allows for complex proposal configuration. It also requires trust in whoever is submitting the RESULT entity. If there were no financial incentive for anyone to count votes, or if it were up to the proposer to count the votes, the integrity of the results would be questionable. For example, a lazy counter might just make up the results or completely ghost, or a proposer might submit whatever outcome they see fit. That is why the count needs to be delegated to a third party custodian who has a financial incentive to provide accurate results. This spec allows any wallet to REGISTER as a custodian and declare their own fees, thus creating an oracle market. Game theory dictates that the more custodians there are, the more users can trust results. Also, the RECERTIFY interaction allows a result to be confirmed by more than one custodian. This free market will, in theory, flesh out custodian who are not submitting accurate results.
Technically this spec could be adapted for RMRK 1.0.0 NFTs but since it has been deprecated, we recommend migration to at least the 2.0.0 extrinsics standard.
Snapshot.org only facilitates simple majority voting and it only supports EVM-based chains. The RMRK extrinsic-based standards are native to Kusama, a substrate-based chain. Snapshot.org is currently incapable of supporting any kind of voting with RMRK NFTs. This is not the case for RMRK 3.0.0 released on Moonriver (and other EVM chains), but collections that wish to remain canonical on the extrinsics standards will need to use this spec or a similar spec to facilitate voting.
Here is a list of the UI that facilitate RMRKDAO
NO. This spec is open source and everything is submitted on the Kusama blockchain. If users can manage to follow this spec properly by submitting remarks directly on the Kusama blockchain, they are free to do so. However, there are many logical checks that should be implemented to ensure no one wastes their voting and proposal fees by submitting an invalid proposal or an invalid vote. These logical checks are self-evident.
YES. But please do so by submitting an issue here on the RMRKDAO github.
A custodian is responsible for counting votes per this spec and submitting results on-chain. Technically, all you need to do to become a custodian is to submit a REGISTER interaction. However, if you fail to submit results or if you submit faulty results your reputation will be tainted. Custodians should have an intimate understanding of the RMRK specs, have the ability to parse data from the RMRK consolidated dump, be able to track which proposals they are assigned to, and be able to consolidate votes/ proposals per the RMRKDAO spec.
That's an ambitious support request ser. Perhaps one day this will be adapted to a pallets standard but that is a more difficult technical challenge.