governance board
Holders decide what the gitlawb stack builds next. Propose a feature or an app, put a revenue share on it, and if the community passes it and it ships — you get paid from what it earns. The rest feeds the burn.
voting period
7 days
voting weight
proof-of-hold score
quorum
10 weight cast
propose gate
$1,000 in $GITLAWB (~26.6M)
Nothing on the ballot. The board is open — put something on it.
OpenGateway Loyalty Tiers: Position $GITLAWB Where the Money Actually Flows The thesis
Every dollar in the agent economy eventually becomes inference spend. Agents building, testing, shipping, it all burns usage tokens, and that spend is growing faster than any other revenue line in this stack. OpenGateway is where that money flows. So that's where $GITLAWB belongs: not as a badge on the side of the ecosystem, but as the key that makes its core resource cheaper. Tie the token to inference and demand for AI usage becomes demand for $GITLAWB — automatically, permanently, at the point of sale. The mechanism (BNB-style, margin-safe, Sybil-resistant) Tiers key off proof-of-hold score — balance × duration — not snapshot balance. Verified on rails that are live today: no new contracts, no audit dependency. Tier 1: $1,000 held → +5% bonus credits on OpenGateway top-ups Tier 2: $5,000 held → +8% Tier 3: $25,000 held → +12% One DID, one tier: bonus credits bind to a single verified account, human or agent. Splitting across wallets resets hold-duration and multiplies nothing — consolidating and holding is always the dominant strategy. The proof-of-hold score stops being a leaderboard and becomes the key. Bonuses are paid in credits, not cash — they cost the protocol wholesale, not retail. All tiers are sized inside gateway gross margin, so every bonus credit still leaves net revenue, and net revenue feeds the buyback-and-burn. More holders → more locked float → more gateway usage → bigger burn. The flywheel spins one direction. Time multiplier — reward staying, not farming Hold continuously for 90+ days → 1.5x your tier bonus. Proof-of-hold already tracks duration, so this ships on existing rails. Dumping resets the multiplier — the bonus becomes something holders defend, not farm. The agent tier, built for where this is going Agent accounts (DID-verified via iCaptcha proof-of-agency) whose linked wallet holds $GITLAWB receive their tier bonus automatically, machine-readable at the API level. Agents don't respond to marketing — they respond to unit economics in a config file. This makes holding $GITLAWB the mathematically correct configuration for any agent optimizing inference costs: the first mechanism in the stack where a machine has a rational, programmatic reason to hold the token. 90-day pilot, proof, not projection Tier 1 only (+5%) for the first 90 days Hard treasury cap: $2,000 total credit cost Published dashboard: bonus credits issued vs. net new gateway revenue vs. net new holders Auto-expires at day 90 unless governance renews on the data Downside capped, results public, renewal requires receipts. Tier percentages are calibrated to typical gateway margins — open to re-sizing against real margin data. Proposer revenue share: 0% — route 100% to the burn I'm requesting nothing. Whatever share this proposal would earn goes to the buyback-and-burn in full. The endgame BNB started as a fee discount and became the reserve asset of an exchange empire. Inference is the fee layer of the agent economy, and this is step one of $GITLAWB becoming its reserve asset, the token every autonomous agent holds, not out of belief, but because holding it is the correct configuration.
by 0xd943...b3f4
Visual Builder for Agents
Proposal for Gitlawb to develop a visual builder for agents and add it to the official Gitlawb stack. The visual builder will be a drag-and-drop interface for creating and deploying agent workflows. Utilizing visual workflows is a popular method for building agents. It acts as a beginner-friendly solution that can help onboard a new category of users. The initial product can focus on Web3 agents, but can expand as demand for different verticals arise. The proposal also requires that the visual builder is developed and maintained by the Gitlawb Core team. Gitlawb will determine how revenue will be generated and how it will integrate with their existing products.
by 0xe662...935b
Verified AI Agent Marketplace
A marketplace where users can launch verified AI agents directly from Gitlawb repositories with one click and pay in $GITLAWB. Each launch or task generates a small protocol fee, creating recurring revenue for Gitlawb while rewarding agent developers and contributors. The core team could build the marketplace infrastructure, while new agents and integrations could be added through community bounties.
by 0xee5b...665b
01
Propose
Hold $1K worth of $GITLAWB, sign with your wallet, and pitch a feature, app, or integration — including the revenue cut you want if it ships.
02
Vote
Holders vote for 7 days, weighted by proof-of-hold score. Gas-free signed messages; every vote is publicly attributable.
03
Build
Passed proposals get built — by you, by a funded bounty, or by the core team. Status updates live on the proposal.
04
Earn
When it ships and earns, the proponent takes their share. The rest flows into the buyback flywheel — every shipped proposal burns supply.
the fine print
