Skip to main content

Product History

Green Goods has changed substantially as the team learned from communities and from running the protocol. This page records the broad milestones without presenting old specifications as current implementation guidance. For current behavior, follow the builder guides and their linked code, configuration, ontology, and deployment sources.

The complete historical documents remain available in the repository's Git history.

v0.1​

The first product specification established the Garden, work-submission, attestation, and account-abstraction direction. It explored Privy, Ethereum Attestation Service, Pimlico, and token-bound accounts as the initial stack.

v0.4​

The next specification shifted authentication toward passkeys and added Karma-based impact reporting to the proposed product shape. It also refined the user journeys around creating a Garden, submitting work, reviewing evidence, and making attestations.

v1.0​

The v1.0 planning cycle broadened Green Goods into a fuller impact-and-funding protocol. It explored Hypercerts, Octant vaults, Gardens conviction voting, Cookie Jar payouts, and a wider set of roles and action domains. Those ideas have since landed, changed, or been deferred independently; current code and the machine-readable ontology now own implementation and role claims.

DID-ETHR modernization research​

A March 2026 proposal explored an updated did:ethr profile for account abstraction, interoperability, privacy, and conformance. It was research, not an adopted Green Goods implementation plan, and no active Plan Hub owns it.

GreenWill research​

A March 2026 proposal set explored reputation badges and Greenpill Impact Framework-aligned measurement. Durable reputation choices are tracked in the reputation-badging Plan Hub; yield-to-impact framing is tracked in yield-to-impact-codification. The proposal documents themselves are historical research, not current protocol authority.

OpenCred credential login research​

A March 2026 proposal explored using verifiable credentials for geographic Garden access and account linking. It was not adopted as an active implementation plan, so the proposal remains available only through Git history.

Passkey recovery hardening​

A March 2026 proposal explored production passkey-server topology, relying-party and origin rules, account-first recovery, and second-device access. The durable release constraints were carried into the account-recovery-hardening Plan Hub; the original proposal is retained through Git history.

v1.2.2 - September 2026​

Passkey sign-in can approve actions again

  • Passkey accounts — if you sign in with a passkey, approving an action (joining a garden, submitting work) no longer fails with a prompt that appears to time out. Sign-in itself was always working; it was the approval step that could not find your saved passkey. Once the app updates, your existing passkey and your account work as before — there is nothing to re-register.

Full notes: GitHub Releases.