Open ori-near opened 5 hours ago
TLDR; the dao policy is not correclty set.
To see the policy run;
near contract call-function as-read-only infinex.sputnik-dao.near get_policy json-args {} network-config mainnet now
.
The group called "Create Request" has permissions to do anything and the threshold to add members is 20 percent. Right now there are 5 members added to this group so it will not be more than 20 percent using this group.
"name": "Create Requests",
"permissions": [
"*:*" <====== SHOULD BE MORE STRICT
],
"vote_policy": {
"add_member_to_role": {
"quorum": "0",
"threshold": [
20, <========== IS TOO HIGH
100
],
"weight_kind": "RoleWeight"
}
The Create Request
group should only be limited to Creating Requests. That way when a user is added by adding/acting on a proposal the permission check will check the correct group. Which is Manage Members
. And the threshold should be low enough that it will always be 1 vote.
Affected Portal: Infinex
Description: Our customer (Infinex) has tried adding users to their treasury, but run into the infinite loading screen every time.
User Type: User with Manage Members permission.
Reproduction Steps
Expected behavior User with Manage Members should be able to add multiple users without running into the error message.
Visual Reference
Priority Critical (P0) – Cannot complete critical action
Environment Details
Additional Context I spoke with @Tguntenaar, who will add his findings below.