Lance & Max / Regen Compute Integration — Live Eco-Offset Line Items
Lance demonstrated his integration of Regen Compute into his astrology reading site. Each purchase now includes a $0.25 eco-offset line item visible in the checkout form. The user dashboard tracks cumulative ecological contributions across readings and AI coaching sessions. Currently Lance batches monthly purchases manually using his API key, but discussed the possibility of real-time on-chain offsets using Cosm.js and a prefunded Kepler wallet — the same pattern Regen Compute uses internally with Stripe and ERC-20 payments. Max and Lance discussed packaging this integration pattern into a reusable Next.js component or SDK that other developers could drop into their sites with minimal setup (API keys in .env, a subdirectory with dashboard tooling).
Gregory / Agentic Tokenomics Repo — Architecture Walkthrough
Gregory walked through the current state of the Agentic Tokenomics GitHub repo, which now has 23 open pull requests. The repo is structured as a mono-repo coordination tool for multi-party contribution to Regen Ledger’s token economics upgrade. It includes a contributor navigation guide, dependency mapping between mechanisms, a mechanism index, and agentic instructions for AI-assisted contribution. Gregory emphasized the repo’s value as shared architectural context — contributors can load it into Claude or another AI tool and get oriented on mechanism interdependencies before working on a specific piece. He asked the group to review the overall architecture, particularly the fee-splitting contract design, rather than adding uncoordinated side contributions.
Gregory / Cosmos SDK 0.54 — Proof of Authority for Free
Gregory highlighted that Cosmos SDK 0.54 will include a native proof-of-authority module, built by Aaron Craelius (a Regen co-founder, now at Cosmos Labs). This means Regen’s team only needs to follow a migration checklist from 0.53 to 0.54 rather than building a custom POA module. The work is Apache-licensed open source — not tied to Cosmos Labs’ enterprise offering. Gregory created a migration checklist PR tracking what the upgrade will entail. The POA module handles validator permissioning; combined with the fee-splitting contract, it covers the core infrastructure needed for the new token economics.
Gregory / CosmWasm Fee-Splitting & Burn Contract
Gregory presented the architecture for a CosmWasm smart contract that handles fee routing and automated burning. When eco-credits are purchased, the contract programmatically splits payments — e.g., 75% to the land steward community, 20% to Regen, 5% to a partner organization — with a 2% burn on transactions. The contract parameters are configurable so business logic can be adjusted through governance. Gregory has built out the contract specs locally but still needs testing, test-net deployment, hardening, and audit. This contract also relates to the dynamic mint/burn mechanism and the fixed supply cap — all three are interdependent and must work together.
Mark & Gregory / CoinStore Listing & Marketing Alignment
Mark gave an update on the pending CoinStore token listing. He’s developing a plan to align the listing’s marketing push with Regen Compute’s momentum and the token economics upgrades (POA, buy-and-burn, fee splitting). The group discussed timing: Gregory estimated the full token economics upgrade would take roughly one quarter with two focused contributors (one architect, one engineer) — but the dependency on Cosmos SDK 0.54 shipping and governance processes adds uncertainty. Gregory expressed a preference for getting the protocol upgrades functioning before a major listing push, while Mark argued for coordinated messaging to retain validator confidence during the transition.
Group / Validator Transition Economics & Sell Pressure
Mark raised the question of how current validators will respond to the POA shift, since they’ll lose inflationary staking rewards. Gregory acknowledged the transition will likely cause some sell pressure as validators exit positions, but argued this is preferable at the current micro-cap (~$500K) rather than after momentum builds. The group discussed offering exiting validators optionality — alternative utility for their tokens, off-market exit opportunities, or hybrid staking mechanisms not tied to security. Gregory noted that no validator has objected to the POA direction on the forums so far, and that fee-split revenue replaces inflationary rewards with transaction-based income.
Lance & Gregory / Hard Cap — Grounding in Biophysical Thresholds
Lance raised the idea of choosing a fixed supply cap number. Gregory recommended grounding it in biophysical data rather than picking an arbitrary number: analyze on-chain credit volume, projected credit pipeline, the cadCAD simulation Max built, Mark’s Excel model, and symbolic/biophysical thresholds. Key missing data is R&D’s pipeline of incoming eco-credits — Lance could query the Koi MCP for any public statements, or model growth from historical data. Gregory emphasized that the fixed cap mechanism exists in the repo’s mechanism library and is ready for someone to pick up, but he prioritized fee splitting and POA as architectural prerequisites.
Gregory / Bio-Regional Validator Vision & Software Stack
Gregory shared his vision for a bio-regional validator stack: rather than just running a Regen chain validator, operators would run an integrated system combining the validator, agentic farm operating tools, ecological data commons access (via Koi), and knowledge commoning infrastructure. He estimated this “bio-regional validator and knowledge commons stack” would take him about four months of solo vibe-coding to reach MVP, but cautioned that adding more contributors too early increases complexity through scope creep and coordination overhead. The concept uses Regen Ledger as the data backbone, permissioning, governance, and market infrastructure layer.
Group / AI Tooling & Development Workflows
The group briefly discussed AI development workflows. Gregory recommended terminal-based Claude Code over IDE integrations for complex architectural work, noting superior tool extensions and MCP harness support. Lance shared his recent switch from VS Code GitHub Copilot to terminal Claude Code. The group discussed Gemini’s free code review (via Google Workspace) as useful for automated PR review despite occasional hallucinations about model versions, and proposed scheduling a separate AI skillshare session covering tools like Notebook LM and presentation generators.