---
# System prepended metadata

title: 'Sign in With Ethereum Community Call #15'

---

# Sign in With Ethereum Community Call #15

### Date: 2022/06/16
### Agenda:

- [General] Reader Notes & Updates
- [General] Introductions 
- [Show & Tell] General Updates
- [Q&A] 

## Reader Notes and Updates

- SIWE TypeScript library is out and can be found [here](https://github.com/spruceid/siwe).
- The [Discord](http://discord.gg/WjvuYqvm5Y) server is always open for questions and those that wish to participate.
- We're working on support for different templates, languages, and more - please reach out if you're interested in a SIWE integration.
- Documentation: if you're about to embark, let us know what you think would be best to include! All feedback is welcome.

## Introductions 
- [CPerezz] - I am at the Ethereum Foundation on the privacy and scaling team. Saw the EIP and initiative and wanted to sync up and help and be in touch with that. 
- [Jay Frank] - A community manager at MeTokens - a DeFi enabled personal token app. I would love to join these community calls and meet as many new people as possible.
- [Yash Zanwar] - I am new to this community and just came across the website and really like the idea. I joined the Discord channel as well and wanted to join the community call.
- [Alisha.eth] - Hey I'm alisha.eth and do community and governance at ENS. Excited to listen in to today's updates. 

## General Updates
- [Wayne] - We have a recap on the 2.0 release, we've created some backwards compatible changes that are technically breaking because people should use the new functions but have added some flexibility. You can now control more aspects of it without the verification process. We have `VerifyParams` which is "what are we verifying" and `VerifyOpts` which allows you to configure providers. You can now have different control flows for the code now as well. 
    - We now also have standardized the SIWE response in this case. Fortunately, we have also stubbed out the function `validate` to become `verify` and throws exceptions as expected. We're grateful for the MetaMask team for the feedback here. We also have a react-js template coming.
    -  Sign-In with Ethereum is also now part of the official passport.js library. A lot of people use passport.js to handle the authentication part of their app and now you can slot it in. The server directly integrates it and there's no middle party here. 
    -  Updates on wallets - we have an in-progress PR to MetaMask to enable Sign-In with Ethereum to enable a great interface to be displayed to users. Still a lot of discussions but we are getting very close to something everyone can agree on. 
    -  Having it look a lot more ergonomic to the end user and checking for domain binding. Knowing that you're actually on the domain you're being asked to authenticate on. We're really excited that as soon as this is merged, a bunch of users will be able to enjoy better security and be protected by MITM attacks.
-  [Wayne] - Other updates, Lens Protocol, Coordinape, and more have integrated with Sign-In with Ethereum, and usage is a great success metric here. Standards are based on network effects - people see this as a community effort. We've been very clear on the specification scope. We'll always be writing posts and updates as we keep seeing the integration sides. 
    -  Finally, updates on the community OIDC. The server has been launched on `oidc.signinwithethereum.org`. During the deployment there were witnesses and witnesses have access to CloudFlare to see it. We wouldn't recommend it just yet for high-assurance cases, but are quickly going to upgrade the plan to make sure it can handle it.
    -  This is based on EP-10 which was a proposal to launch a community-identity-server to handle a number of web2 infrastructure based workflows. The problem is that someone _has_ to run a server and it's difficult to integrate direct authentication for relying parties. We proposed having the community run one and get rid of misaligned incentives. Basically we proposed that with this and it's what we shipped.
-  [Wayne] - We can move to the Q&A section. 

## Q&A 
- [Yash Zanwar] - Just wanted to know if you have any resources to help me get started with the project.
    - [Wayne] - Everything can be found at login.xyz. 
- [CPerezz] - How can I contribute to the Rust codebase? Are there any issues that are suitable for external contributors? Not due to the difficulty in Rust but just for the codebase itself. If I can help it would be nice.
    - [Wayne] - We don't have an EIP-1271 implementation but we would welcome a contributor to handle that to take ethers.rs but that would be a fantastic opportunity. 
    - [CPerezz] - Is there an issue for this task?
    - [Wayne] - No but I can do that now! Can I tag your GitHub? 
    - [CPerezz] - Yes, great.
- [Wayne] - Okay well if there are no more questions, we can keep this a short sync! We've been building and wanted to share some progress. On the next call, we can share some progress on DAO-login, like how do you authenticate on behalf of a DAO. 
    - Great, see you on the next community call. 