Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
Aloha, Gitcoiners! How do you feel about Data Dignity, Quadratic Voting, Quadratic Finance and Decentralized Identity?
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
### User Story
As a gitcoin user, I want to easily sign transactions (e.g. claim a bounty) from any device (mobile, desktop), without installing anything, so that I can focus on coding instead of on the complicated process of opening and safeguarding a wallet.
### Why Is this Needed?
Plenty of users are not blockchain-savvy, which means using MetaMask and acquiring Ethereum in order to sign transactions could pose a major hurdle. For developers who do happen to be blockchain-savvy, using MetaMask is simply inconvenient since it requires installing a plugin, it's coupled to the device where it is used and does not support mobile (which means they need to install a separate wallet app). By eliminating this bottle neck, using gitcoin could be frictionless (in regards to web3 actions), allowing them to interact with the system in a simple yet secure manner.
[comment]: # (Feature or Bug? i.e Type: Bug)
### Current Behavior
[comment]: # (Describe what actually happened.)
When interacting with web3 methods, users have to install MetaMask or use the Brave/Mist browser.
### Expected Behavior
[comment]: # (Describe what you expected to happen.)
When interacting with web3 methods, users will be able to sign transactions using Portis, making the flow much more simple and user friendly.
[comment]: # (Describe how we can replicate the bug step by step.)
To replicate, claim an issue.
[comment]: # (Provide a summary of the solution and a task list on what needs to be fixed.)
As described on the [Portis github page](https://github.com/portis-project/portis-sdk), integrating Portis is pretty simply. After installing the package from npm, it should be defined as an additional web3.currentProvider, and adding to the current error message that asks the user to install MetaMask, instead also offering the user to "click here" to use Portis instead (no installation required!).
Since Portis is a standard web3 provider, there is no need to change any of the business logic related to web3 methods.
### Definition of Done
[comment]: # (Any other information that would be useful, bullets are helpful.)
Gitcoin users will be able to interact with web3 methods (e.g. claim issue) using Portis.
### Additional Information
[comment]: # (Any other information that would be useful, content, screenshots, etc.)
Related to issues: