Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPIKE: Understand Bounty Integrations #10079

Closed
GTChase opened this issue Feb 2, 2022 · 3 comments
Closed

SPIKE: Understand Bounty Integrations #10079

GTChase opened this issue Feb 2, 2022 · 3 comments
Assignees

Comments

@GTChase
Copy link
Contributor

GTChase commented Feb 2, 2022

Action Items:

  • Find and understand any existing branches: https://github.com/gitcoinco/web/tree/feat/cosmos-integration

  • Need to understand in detail the remaining work that is needed for the Cosmos integration. Outcome will be enough information to point and get started on the existing Cosmos tickets.

  • Understand any existing integrations, documentation and process for future integrations

  • Where to do we keep cross-chain integration discovery docs?

  • Do we have a checklist of data we need before we proceed?

  • Do you have an example of a perfect cross-chain integration PR we can checkout to see where work needs to be done/do we have this process documented?

@GTChase GTChase changed the title SPIKE: Determine Remaining Work for Cosmos Integration SPIKE: Understand Bounty Integrations Feb 2, 2022
@chibie
Copy link
Contributor

chibie commented Feb 7, 2022

Do you have an example of a perfect cross-chain integration PR we can checkout to see where work needs to be done/do we have this process documented?

browser extension

manual pasting of txn hash

qr code

Where to do we keep cross-chain integration discovery docs?
Understand any existing integrations, documentation and process for future integrations

drive folder for integration docs -> https://drive.google.com/drive/folders/1Cjw9iUZ3QoV4lAxI6NU6AQEfo-FgD1mF

Do we have a checklist of data we need before we proceed?

check the callout or question section in integration doc template -> https://docs.google.com/document/d/1c4hv9fumrSNkr0b7BHCxzC9YlnWPjEFLN-UaJqi3X68 (it's in same folder as above)

Need to understand in detail the remaining work that is needed for the Cosmos integration. Outcome will be enough information to point and get started on the existing Cosmos tickets.

pending work on the cosmos PR involves fixing cosmos_extension.js which involves processing a payout using keplr wallet browser extension to sign and broadcast the transaction

this doc explains how to sign a transaction using keplr + cosmjs -> https://docs.keplr.app/api/cosmjs.html

however, we have to find a way to access SigningStargateClient object (SigningCosmosClient is for cosmjs/launchpad i.e version 3) by having a browser script of cosmjs/stargate library to be able to sign the transaction with keplr wallet.

here's what i've written for cosmos_extension.js with relevant comments -> 1bd7765

open discussions on browser script for cosmjs -> cosmos/cosmjs#921 and cosmos/cosmjs#998

cc: @gdixon @thelostone-mc

@gitcoinbot
Copy link
Member

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


This issue now has a funding of 0.001 ETH (2.84 USD @ $2843.11/ETH) attached to it.

@gitcoinbot
Copy link
Member

gitcoinbot commented May 3, 2022

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Workers have applied to start work.

These users each claimed they can complete the work by 264 years, 6 months from now.
Please review their action plans below:

1) sdhacker has applied to start work (Funders only: approve worker | reject worker).

I understand the project that I have to look into the given repo and perform a given tasks. I am ready to do it.
2) ashwin2545 has applied to start work (Funders only: approve worker | reject worker).

I need to be an active investor
3) thisispalash has applied to start work (Funders only: approve worker | reject worker).

I really enjoy browsing through repositories and figuring out the best practices in order to more efficiently organize code and docs so it is quite understandable by a repo viewer. I am also intrigued with the number of features Github offers and how they may be leveraged to enhance the developer experience and also accelerate development. Just one question — is this bounty actually for just 0.001 ETH or is that just a placeholder until the approval process is completed?
4) doopadydoo has applied to start work (Funders only: approve worker | reject worker).

Will try. School me. See my grant thing. Im down for whatever.

Cheers

Learn more on the Gitcoin Issue Details page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants