Native GGT voting

Native Grape governance uses active locked GGT. Creating a proposal requires at least 2,700,000 active locked GGT. Voting lasts seven days, with for, against, and abstain choices. Each address casts one final ballot, using weight snapshotted at the block before proposal creation.

New locks after that snapshot do not add weight to the proposal. Under the reviewed contract, a proposal passes when for exceeds against, with no minimum turnout. Recording a passed result does not automatically execute a protocol change.

Circle proposals

Circle has a separate application workflow for discussion, proposals, voting, and tracked implementation. Its configurable GGT snapshot, quorum, minimum voters, and voting duration are not interchangeable with the native contract’s rules.

Circle’s implementation mode is tracked delivery: an accepted proposal can be followed through ownership, milestones, and evidence. Records and social discussions use the application database. Availability of binding voting depends on the current configuration shown in Circle.

Protocol authority

Protocol upgrades have a separate authorized-signing and delay process. A holder ballot is not itself an upgrade signature. This separation should be visible whenever a proposal promises a network change: who approved the idea, who can execute it, and what evidence shows delivery?

Check the proposal’s mechanism, asset network, snapshot, deadline, and effect before voting. Holding GRP alone is not the same as holding or locking GGT.