---
# System prepended metadata

title: Untitled

---

Alt-Clients Road Map

Team:

- Alexis;
- Sebastian;
- Odis (sp?);
- David;
- Ryan;


- Sophia
- Alex Good

---

- Client Services
    - Infrastructure for clients;
    - Have docker files / dockercompose;
        - Good enough, but needs to be user friendly;
        - Oriented around orgs;
    - Org nodes
        - git push / pull;
        - peer tracking;
        - deploy org nodes;
        - Make deployment easier
            - helm charts / Kubernetes ?
                - minikube?
            - Fully automated;
        - Org Node as a Service;
            - Premium / pay per seat model;
            - Ease of deploy to datacenter for self hosting if desired;
                - AWS, GCP, Azure ?
            - Pay using Eth
                - service providers can accept Eth/crypto for hosting
            - Use CLI to update the org node to watch seeds, peers, etc.
                - deployment;
                - adding authorization keys;
                - etc.
            - GitLab approach, but not centrally managed (monopoly on service hosting);
            - Managed by anyone;
        - Identity Service (within the org-node itself)
            - Keep a link between signing keys and identities
                - GPG, radicle identities (ed25519), EIP155
            - Add a flag within the org-node
            - Extend HTTP API to query keys
                - User centric
                    - Able to query additional org memberships a user may be a part of;
            - Used for automated payments
            - Add authorship trailer
    - Backlog
        - Layer 2 / optimizations for reducing costs
            - zkSTARKS / zkSNARKS (is it really a gas optimization? verification can be costly)
            - Anchoring is too expensive (should be free) on Ethereum
                - orgs should be anchoring;
                - org creation should be free / cheap;
                    - Alternative would be to re-coup the costs;
                - Where should org anchors live?
                    - should be determined by the org;
            - Needs ENS / Gnosis Safe
                - Deployed on Arbitrum
                - Optimism
        - Support for additional networks? (support for ENS / Gnosis Safe?)
            - ETH 2.0;
            - Solana?
                - Live separately;
            - Substrate?
                - Solidity compatibility?
                - EVM Pallet => enable solidity
            - Dfinity?
                - not interested, seems too hyped and may be limiting for external network writes (read only)
            - IPFS
                - Keep decentralized read-only data (previous work)
            - Would need to look into other
- Client Tools
    - CLI Tooling;
        - anchor orgs;
        - create proofs;
        - read accounts;
    - Need to be able to:
        - edit radicle identity;
        - generally update radicle projects;
            - edit project metadata;
            - edit profiles;
    - Radicle link has 'plumbing' CLI tooling;
        - need to add 'porcelain' CLI tooling;
            - User friendly commands (take GH CLI UX as reference)
    - Issues and patches CRDT (Sophia, Alex Good)
        - exploring models for managing issues and patches within git, while reducing conflicts among collaborators;
            - Merging issues and patches,
        - Initially CLI interface, later web interface;
- Radicle Orgs Contract
    - NFT Code Contribution Rewards;
        - Which EIP721 Extensions will make sense?
        - Can eventually become its own token per project or organization;
    - OrgV2 Factory;
- Radicle Faucet
- Radicle Interface
    - The services and tools developed will in the end be used here;
    - Make it easier for Orgs to be created (reduce fees, creation wizard);
    - Contributor reward org stream;
        - engaging contributors to participate more;
            - How should a DAO spend money to incentivize collaboration and grow its project?
                - How is the governance model of the DAO supporting this goal?
                - automated funding (receive payment if in the git log)
                - Grants (RFP) and continuous funding
                    - DAO votes to support a particular RFP.
                    - Continuous funding is based on a base rate, similar to employment or consultancy contract.
                        - Long-lived contributors;
            - How am I paid for the work I do? (radicle funding team)
                - How do I value the work I do?
            - Perks, bounties, etc. for contributing;
            - Drips => rewarding dependencies
                - other projects that have enabled the support of the org's projects. Increasing collaboration.
