-
Notifications
You must be signed in to change notification settings - Fork 117
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
Learn to send CELO and cUSD #1
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 2.0 CELO (5.56 USD @ $2.78/CELO) attached to it.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 2.0 CELO (5.56 USD @ $2.78/CELO) has been submitted by:
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 3.0 CELO (10.08 USD @ $3.36/CELO) attached to this issue has been approved & issued to @fte.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 3.0 CELO (10.08 USD @ $3.36/CELO) attached to this issue has been approved & issued to @fte.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 265 years, 8 months from now. 1) avalonche has started work. Ready to complete the tutorial Follow the instructions in the repo Learn to send CELO and cUSD and submit a address Follow the instructions in the repo Learn To Send CELO And CUSD 1- follow the tutorial. LEarn to send some tokens in Celo Transfer CELO and cUSD on the test network complete the task, learn and earn Will follow the tutorial and submit my address Follow tutorial Learn to send CELO and CUSD - tutorial I am new to this plateform. I will give my best to make sure entire project get up lift. I want to know about the program. going to Learn how to send CELO And CUSD read the docs, complete the task I will solve it as soon as possible for you interested, lets get started with this project I will run through the tutorial and send Celo transactions via the sdk carefully focusing on the learning objective Saya akan memberitahu teman kerabat saya tentang karunia ini I will finish it in every time i work Hi, I'll follow the code tutorial and provide the address used for the activity I will submit a URL to verify the completion of the bounty. The URL will link to a GitHub gist that includes the address that i used in the exercise (to look up activity on the Alfajores block explorer. With this address, you will see token deposits from the faucet and two small transactions out of the account (1 CELO and 1 cUSD). Learn more on the Gitcoin Issue Details page. |
Learn to send CELO and cUSD
Description
This bounty will send bounty hunters through this code example in the Celo docs. The purpose of this bounty is to help developers get acquainted with some of the basic features and tools in the Celo development environment.
This bounty will show developers how to install ContractKit, one of the core components of the Celo SDK, and use it to connect to the Alfajores testnet. From here, we will show how to access some of the core protocol contracts using ContractKit and use the SDK to read from and write to the Celo blockchain.
Time expectation
Expect this bounty to take a web developer familiar with Javascript and Node.js about 30 minutes. A web developer with blockchain experience should be able to complete this in less time.
Requirements
You will need to submit a URL to verify the completion of the bounty. The URL should link to a GitHub gist that includes the address that you used in the exercise (to look up activity on the Alfajores block explorer. With this address, we want to see token deposits from the faucet and two small transactions out of the account (1 CELO and 1 cUSD).
The first 20 submissions will receive 3 CELO. Make sure to submit a Celo address (not an Ethereum address) on the bounty submission page. As Celo is a mobile-first blockchain, we suggest you install Valora to create a new Celo account, but you can also create an account using the command line tool or via a Ledger hardware wallet.
Resources
The text was updated successfully, but these errors were encountered: