🔍
RnDAO workspace
/
🪪
IDconnector
/
Leads Catch Up

Leads Catch Up

Date
May 20, 2025
Status
Assign
Goal:
  • What are the next steps?
    • Can we pick a tool or two to implement?
  • Why are we doing this?
Agenda:
  • Review synthesis boards
  • Review responses
  • Skim stories
  • Next steps
 
Questions
  • seems too complicated for it’s own good. If you simplified, what’s the fast way to simplify it? Just GoogleID?
    • All are using Web2 providers who work with OAuth2. Just abstracting your reputation from those to our Wallet
    • What’s the problem with just doing this?
      • Relying on centralized systems
      • How do you handle the multiple IDs people have? Is that a problem or not? Aggregation and connection
    • Is there a way to have us do this and also allow other methods (w/o creating vulnerabilities?)
    • GitCoin passport is the essence of connecting multiple IDs (but expire in 90 days)
      • If any of my 3 IDs is compromised, then all of my 10 tools are compromised
      • Are there ways to test IDs for being broken. Or treat IDs as stronger or weaker
  • Where are we with the project?
    • understand the requirements, the space
    • scope out the requirements for a solution
 
Solutions
  • What are the low-hanging fruit for reputation?
    • what are the friction points that we could smooth, for another reason?
      • no aggregation, so the reputation isn’t accurate. Aggregate for other needs
    • Ask Dominik and SNET
      • why did the other tool (P??) not work? What was missing?
      • Data pipelines and ways to integrate
    • Why isn’t it working in Arbitrum?
  • What are small chunks of value before reputation
    • Login
      • Extending the composability of OAuth
      • And consolidating it (unifying the providers) - Disco.xyz but weird business model
      • Required a wallet, which is the scariest thing. Start elsewhere
    • Fluid group creation and access control
      • Groups and lists and tagging
      • composable yet open
 
  • What’s the “solution”
    • Consolidate all of them into one ID (Aggregation)
      • as a user, define each one, but pick one of 2 for sign-in
      • Why do I want to ID all of these? Add each one for each tool I use (MW - google for calendar, Discord, telegram). Reduces UX friction, helps build reputation, gives you more control over who accesses data (like GoogleID access control)
      • Incentivises people for their data
      • Fluidity of permissions
      • Single social graph of individuals and groups
      • Easy access control from groups involved in one tool to another
        •  
         
      Next steps
    • mini demo - aggregation of all my IDs
      • access your data on those systems (like for TC reputation and
      • TC thing failed on UX - can we get a link to where they got to? Video? For each system, had to sign with wallet and pay gas twice (!!)
      • Like MW connections, but just use a small SDK
    • cost it out
    • get a grant
    • Working with DiD providers
      • combine with WorldID, Ontology
 
Jan comments
  • super easy login but enough that we don’t have bot problems
    • just sumsup
  • what’s composable? about a login that bridges pr
    • lot of indicators sprinkled through the internet that you are a real person
      • Bring all the snippets that bring it all together
      • but it’s not really ZK
    • Better use cases (porn, alcohol, proof that you are OK)
  • First idea
    • Already integrated - universal profile in CG
    • Go into app and login with Google, and then logged in to CG because of that
    • Passport .JS, ??, simple sale contract, simple token contract,
    • then simple version of the chat that uses the same thing
  • Book for Friday for a download - or next week?
🔍
RnDAO workspace
/
🪪
IDconnector
/
Leads Catch Up

Leads Catch Up

Date
May 20, 2025
Status
Assign
Goal:
  • What are the next steps?
    • Can we pick a tool or two to implement?
  • Why are we doing this?
Agenda:
  • Review synthesis boards
  • Review responses
  • Skim stories
  • Next steps
 
Questions
  • seems too complicated for it’s own good. If you simplified, what’s the fast way to simplify it? Just GoogleID?
    • All are using Web2 providers who work with OAuth2. Just abstracting your reputation from those to our Wallet
    • What’s the problem with just doing this?
      • Relying on centralized systems
      • How do you handle the multiple IDs people have? Is that a problem or not? Aggregation and connection
    • Is there a way to have us do this and also allow other methods (w/o creating vulnerabilities?)
    • GitCoin passport is the essence of connecting multiple IDs (but expire in 90 days)
      • If any of my 3 IDs is compromised, then all of my 10 tools are compromised
      • Are there ways to test IDs for being broken. Or treat IDs as stronger or weaker
  • Where are we with the project?
    • understand the requirements, the space
    • scope out the requirements for a solution
 
Solutions
  • What are the low-hanging fruit for reputation?
    • what are the friction points that we could smooth, for another reason?
      • no aggregation, so the reputation isn’t accurate. Aggregate for other needs
    • Ask Dominik and SNET
      • why did the other tool (P??) not work? What was missing?
      • Data pipelines and ways to integrate
    • Why isn’t it working in Arbitrum?
  • What are small chunks of value before reputation
    • Login
      • Extending the composability of OAuth
      • And consolidating it (unifying the providers) - Disco.xyz but weird business model
      • Required a wallet, which is the scariest thing. Start elsewhere
    • Fluid group creation and access control
      • Groups and lists and tagging
      • composable yet open
 
  • What’s the “solution”
    • Consolidate all of them into one ID (Aggregation)
      • as a user, define each one, but pick one of 2 for sign-in
      • Why do I want to ID all of these? Add each one for each tool I use (MW - google for calendar, Discord, telegram). Reduces UX friction, helps build reputation, gives you more control over who accesses data (like GoogleID access control)
      • Incentivises people for their data
      • Fluidity of permissions
      • Single social graph of individuals and groups
      • Easy access control from groups involved in one tool to another
        •  
         
      Next steps
    • mini demo - aggregation of all my IDs
      • access your data on those systems (like for TC reputation and
      • TC thing failed on UX - can we get a link to where they got to? Video? For each system, had to sign with wallet and pay gas twice (!!)
      • Like MW connections, but just use a small SDK
    • cost it out
    • get a grant
    • Working with DiD providers
      • combine with WorldID, Ontology
 
Jan comments
  • super easy login but enough that we don’t have bot problems
    • just sumsup
  • what’s composable? about a login that bridges pr
    • lot of indicators sprinkled through the internet that you are a real person
      • Bring all the snippets that bring it all together
      • but it’s not really ZK
    • Better use cases (porn, alcohol, proof that you are OK)
  • First idea
    • Already integrated - universal profile in CG
    • Go into app and login with Google, and then logged in to CG because of that
    • Passport .JS, ??, simple sale contract, simple token contract,
    • then simple version of the chat that uses the same thing
  • Book for Friday for a download - or next week?