[PROJECT] tw3-profile

[TechnicallyWeb3]

Project name

tw3-profile

Problem statement

TW3 contributors are building infrastructure and earning contribution credit tracked by GitHub account, but there is no way to link those accounts to Ethereum wallets for future token distribution. The on-chain identity registry (git-registry) requires smart contract development, validator infrastructure, and a challenge/consensus flow that won't be production-ready for some time. Without a simpler interim solution, we have no mechanism to map GitHub identities to wallet addresses — meaning contributors can't receive token rewards when they launch, and we can't verify wallet ownership for governance participation.

Every day this gap exists, contributions accumulate with no verified destination for rewards.

Proposed solution

Create a tw3-profile repository under the TW3 org that contributors fork and edit with their identity data. The core of the profile is a JSON file containing:

• Ethereum wallet address — where token rewards will be sent
• Wallet signature — cryptographic proof that the profile owner controls the claimed address (prevents unauthorized claims)
• Optional metadata — display name (defaults to GitHub username), profile image (defaults to GitHub avatar), bio (defaults to GitHub bio)

The workflow is:

1. Fork tw3-profile to your GitHub account
2. Run the included signing tool to generate a signature linking your GitHub identity to your wallet
3. Edit the profile JSON with your address, signature, and any optional fields
4. Submit the fork — the signed profile serves as your verifiable identity claim

The repo should include:

• A profile schema (JSON) defining the required and optional fields
• A signing tool (TypeScript CLI) that connects to a hot or cold wallet, signs a message binding the GitHub username to the wallet address, and outputs the signature. Early versions can use local private key or mnemonic input; future versions should support browser-based wallet connections to eliminate key exposure
• A validation script that verifies a profile's signature is correct (for use by admins and automated checks)
• Documentation explaining the fork-and-edit flow, how to use the tooling, and how this feeds into the future git-registry migration

This approach requires zero blockchain infrastructure. It works today using only Git and GitHub. Profile data is self-hosted in each contributor's fork, publicly auditable, and cryptographically verifiable.

When the git-registry contract is operational, profile data migrates to the on-chain registry. No contributor loses their history — the JSON profiles serve as the seed data for the registry's initial state.

Alignment with TW3 philosophy

• Postulate 1 (Stakeholder sovereignty): Contributors maintain ownership of their identity data in their own fork — no centralized database, no admin-controlled user table
• Postulate 3 (Open source without exception): The entire profile system, signing tools, and validation scripts are open source and forkable
• Postulate 7 (Radical transparency): All identity claims are publicly auditable JSON files in public GitHub repos
• Postulate 8 (DAO governance required): The profile schema and validation rules are governance-adjustable and live in a TW3 repo subject to the standard contribution process
• PHILOSOPHY.md — "building the plane while flying it": This is the practical, no-blockchain bridge that lets the community start operating today while the decentralized infrastructure is built

Estimated scope

• Small — a few contributors, weeks of work

Skills needed

• TypeScript — CLI signing tool and validation script
• Ethereum/Web3 — wallet signature generation and verification (ethers.js or viem)
• JSON Schema — profile schema definition and validation
• Documentation — contributor-facing guides for the fork-and-edit flow

Potential stakeholders

• Users: Every TW3 contributor who wants to receive token rewards now or in the future; future sovereign project contributors who adopt the same identity system
• Contributors: TypeScript/Web3 developers to build the signing and validation tooling; documentation contributors for guides and onboarding
• Investors: Not directly applicable at this stage, though the profile system is a prerequisite for the token distribution infrastructure that investors depend on

Additional context

• The CONTRIBUTING.md in tw3-dao already references tw3-profile as the current identity method and describes the fork-and-edit workflow — see the TW3 profile section
• The long-term evolution is the git-registry project, which implements on-chain social consensus identity verification. tw3-profile is explicitly designed as the bridge to that system
• Profile creation is optional — anonymous contributions are tracked by GitHub account and rewards can be claimed retroactively by creating a profile at any time
• Prior art: GitHub's own verified email system links identities to accounts via signed commits; this approach applies the same principle to wallet addresses using Ethereum signatures

[TechnicallyWeb3]

Since this has been upvoted, we can turn it into its own repo. Once created it will be available at github.com/tw3-dao/tw3-profile

[TechnicallyWeb3]

Oh... sub threads interesting. This could be helpful for creating universal discussions such as creating admin elections, comments can be nominations, nominee can reply, we can vote with reactions still. Best not to focus too much on this as we will be attempting to build a custom UX off GitHub so we're not trying to work within a fixed infrastructure. For now we will simply model our DAO on GitHub, these sub threads may be useful. I wonder if it goes deeper...