Live on GenLayer Testnet Bradbury

A majority is not enough. The bylaws have a vote too.

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.

Riverside Food Co-op3 members
#0 · Shelving for the shoppaid

0.001 GEN · passed 2 to 0 · allowed by 3.1.

#1 · New till systemrejected

Passed 3 to 0, but: “3.2 No single payment may exceed 0.002 GEN.”

–Organisations
–Proposals
–Rejected by the bylaws
–In treasuries (GEN)

How it works

Votes, then rules.

  1. I
    Found

    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.

  2. II
    Fund

    Anyone sends GEN to the treasury.

  3. III
    Propose and vote

    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.

  4. IV
    Execute

    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

For the group

  • Rules you already wrote are enforced, not just quoted at the next meeting.
  • A loud majority cannot pay itself against the bylaws.
  • Every proposal, vote and ruling is on record.

For each member

  • One member, one vote; nobody votes twice.
  • A rejection names the clause, so the next proposal can be fixed.
  • Anyone can execute a passed proposal; no treasurer holds the keys.
Pinned bylawsValidators re-read the page at execution and check it against the hash pinned at founding. If it changed, execution reverts: the rules are the ones members joined under.
Quoted, not guessedA violation counts only with a clause that every validator finds in its own copy of the bylaws.
Honest limitsValidators judge the proposal as written. A recipient's identity or a purpose that lies is for members to catch before they vote.

Organisations

Every treasury, read live from the contract.

Reading the contract…

Found an organisation

Validators read it now and pin its hash. Don't edit it later: execution checks the same bytes.

FAQ

Who decides whether a payment is allowed?

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.

What if we need to change the bylaws?

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.

What if the page is down at execution?

The call reverts and nothing changes; execute it later. Nothing is paid without a reading.

When does a proposal pass?

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.

Spend together, by the book.

Pin your bylaws, fund the treasury, and let consensus hold the rules.

Found an organisation