Sign on Forum via Your Conflux Address. Web3 Authentication on Conflux Forum. Sign in with Conflux(SIWC) Web3 Conflux Community Forum.

Technical Grant Application:
Sign In With Conflux on Conflux Community Forum. Web3 Authentication for Open Source Community Forum. - Funding Tier1

Application Introduction

Conflux Network it’s a open source permissionless blockchain, that aimed to bring decentralise, innovative products, build Conflux Ecosystem with DeFi Stack and managed under community backed DAO architecture.
In that case, first important thing, it’s to implement innovations in Conflux Community and Project at all official sources.
Im want to propose Conflux Community SIWC Plug-in Development, for update main official Community Forum to Web3 Authentication. For increase usage of SIWC and up community experience with Web3 and Conflux blockchain technology.

After plug-in would be done and implement to Forum Source. For login would be required only your Conflux addresses.

Team

  1. That task required only my own work.
    My contact email: [email protected]

Total budget and funding tier

The estimated budget is 100$ x 50h = 5 000$ (TIER 1)

ROADMAP

Init projet (Github, fork and init project) : 5H
Developpment and unit tests : 40H
Publish and testing (publish on npm) : 3H
Documentation and sharing git : 2H

Current Functionality

Web3 Sigh in With Conflux Authentication on Conflux Community Forum. Sign with Conflux addresses. No emails And passwords would be needs.

Technical proporsal

Overview: Conflux Community Forum based on Discourse, is an open-source discussion platform used for most crypto governances and projects to discuss proposals, updates, and research. This tech proporsal aimed to add Sign in With Conflux to Conflux Community Forum;

The existing Sign In With Conflux stack should be used: https://github.com/MPoulhazan/siwc and discourse siwe plug-in should be forked adjusted with all needs modifications, so it works with Conflux.
Also provide an easy-to-follow documentation for projects wishing to use this SDK.
The implementation should adhere to EIP-4361 as much as possible.
The implementation should be open-sourced.
Specifications:
This project requires no smart contracts.
Previous art: https://login.xyz, https://eips.ethereum.org/EIPS/eip-4361
Known challenges: Understanding typed signatures (https://medium.com/metamask/eip712-is-coming-what-to-expect-and-how-to-use-it-bb92fd1a7a26) and deeply understanding EIP-4361

Specifications:
This project requires no smart contracts.
Previous art: https://login.xyz, https://eips.ethereum.org/EIPS/eip-4361

Known challenges: Understanding typed signatures (https://medium.com/metamask/eip712-is-coming-what-to-expect-and-how-to-use-it-bb92fd1a7a26) and deeply understanding EIP-4361;

Specification of the software

SDK (JS)
Typescript
Jest
Ruby

Strong linter conditions for easy maintenance and clear code.
Comments and units tests

MAINTENANCE CONSIDERATIONS

I can maintain or give the privileges on git to new maintener.

1 Like