paid0.001 GEN · passed 2 to 0 · allowed by 3.1.
rejectedPassed 3 to 0, but: “3.2 No single payment may exceed 0.002 GEN.”
Co-ops, clubs and small DAOs hold a shared treasury. Members propose and vote on payments; when one passes, GenLayer validators read the group's own bylaws, pinned when it was founded, and pay it only if it breaks no rule. If it does, it is rejected with the clause quoted.
paid0.001 GEN · passed 2 to 0 · allowed by 3.1.
rejectedPassed 3 to 0, but: “3.2 No single payment may exceed 0.002 GEN.”
How it works
Name the organisation, its 2 to 20 members, a quorum, how long voting lasts and the https page of your bylaws. Validators read the page now and pin its hash: a later edit can't change the rules.
Anyone sends GEN to the treasury.
A member proposes a payment: recipient, amount, purpose. Each member votes once. A majority of all members passes it at once; at the end of the period, more yes than no with the quorum met passes it.
Anyone executes a passed proposal. Validators judge it against the pinned bylaws: allowed pays the recipient; a violation rejects it with the clause it breaks, quoted from the bylaws.
Built for members
Organisations
Reading the contract…
FAQ
GenLayer validators. Each one reads the bylaws page itself, checks it is the pinned version, and answers: does this payment break any rule? A result counts only when they agree, and a violation also needs a clause that every validator finds.
Found a new organisation with the new text and move the treasury by proposal. Pinned rules can't be changed by whoever controls the web page.
The call reverts and nothing changes; execute it later. Nothing is paid without a reading.
At once, when more than half of all members vote yes. Otherwise at the end of the voting period, with at least the quorum voting and more yes than no. Half or more voting no fails it at once.
Pin your bylaws, fund the treasury, and let consensus hold the rules.