celo-org / celo-composer Goto Github PK

Add option to use Truffle with Composer.

Create example demonstrating utils.

Create example using upgradeable smart contracts.

Composer currently uses use-contractkit. Update code to use latest version - react-celo.

import { useContractKit } from "@celo-tools/use-contractkit";

Create example using Crosschain.

Create example with Wormhole Integration.

Make Java SDK available in composer with basic directions on usage.

Create example using Access Control.

Create example with Moss Integration.

Add basic ERC20 token functionality

Add integration with Figment DataHub and directions on usage.

Add ERC721 token example

Create example using interfaces.

Create a way to aggregate Celo Composer examples for the community.

Make ODIS accessible from composer with basic directions on usage.

Implement Angular framework in composer with basic directions on usage.

Make it easy for developers to integrate with dApps in the Celo ecosystem. Choose 3 examples from Valora dApp explorer and directions for how to add more.

This is an open issue for the Celo Composer Gitcoin Bounty.

The Bounty works as follows:

• If you improve the user interface or create new components that you think might be useful for other developers you may be eligible for a bounty.
• Meaningful and novel contributions from the community to improve or extend the project will receive a bounty ranging from 5 to 50 cUSD (or more) depending on the work.
• To claim a bounty, register for the open Gitcoin bounty as a worker and link to your PR.
• If you are working on something that is in heavy demand from the Celo Developer Community, be sure to get the community excited and commenting on your PR. Although PRs are welcome gitcoin bounty awards will be selected at the discretion of the Celo Foundation team.

Some starter ideas include:

• improved or new documentation
• improved functionality
• extension of current functionality to do something novel or useful
• improving readability of the project code or file structure
• improved design or better support for design changes
• localization of documentation into a new language

If you are unsure whether your idea is a good improvement for Celo Composer, feel free to comment below and ask for additional guidance.

Create example using Security best practices.

Port in Celo ABIs (and other methods) to integrate with Celo Dapps.

Create example with AllBridge Integration.

Make Javascript available for composer with basic directions on usage.

Add example using ERC1155.

Add option to use Composer for React Native without Expo.

Create example using Finance (Payment Splitter/Vesting Wallet).

Create example using Proxies.

Add use case with ERC777.

Add documentation section in docs.celo.org/composer that takes it's own page similar to celocli. Reference scaffoldeth docs for ideas.

Make iOS SDK available within composer with basic directions on usage.

To limit excessive hits to data services per keystroke, implement debounce for the useInput hook for string input components used in GreeterContract.tsx and StorageContract.tsx.

Create example with Witnet Oracle Integration.

Create example using Meta Transactions.

Create example with Band Protocol Integration.

Make Hardhat Verification available programmatically inn composer with basic directions on usage.

This is an open issue for the Celo Composer Gitcoin Bounty.

The Bounty works as follows:

• If you improve the user interface or create new components that you think might be useful for other developers you may be eligible for a bounty.
• Meaningful and novel contributions from the community to improve or extend the project will receive a bounty ranging from 5 to 50 cUSD (or more) depending on the work.
• To claim a bounty, register for the open Gitcoin bounty as a worker and link to your PR.
• If you are working on something that is in heavy demand from the Celo Developer Community, be sure to get the community excited and commenting on your PR. Although PRs are welcome gitcoin bounty awards will be selected at the discretion of the Celo Foundation team.

Some starter ideas include:

• improved or new documentation
• improved functionality
• extension of current functionality to do something novel or useful
• improving readability of the project code or file structure
• improved design or better support for design changes
• localization of documentation into a new language

If you are unsure whether your idea is a good improvement for Celo Composer, feel free to comment below and ask for additional guidance.

Create example with Optics integration.

Make Mento available from within composer with basic directions on usage.

Create example with Governance.

Integrate Hyperverse to give smart module access to developers.

Make Python SDK available in composer with documentation on usage.

Make Ethers easily accessible within Composer and create basic directions on how to use it.

This is an open issue for the Celo Progressive dApp Starter project Gitcoin Bounty.

The Bounty works as follows:

• If you improve the user interface or create new components that you think might be useful for other developers you may be eligible for a bounty.
• Meaningful and novel contributions from the community to improve or extend the project will receive a bounty ranging from 5 to 50 cUSD (or more) depending on the work.
• To claim a bounty, register for the open Gitcoin bounty as a worker and link to your PR.
• If you are working on something that is in heavy demand from the Celo Developer Community, be sure to get the community excited and commenting on your PR. Although PRs are welcome gitcoin bounty awards will be selected at the discretion of the Celo Foundation team.

Some starter ideas include:

• improved or new documentation
• improved functionality
• extension of current functionality to do something novel or useful
• improving readability of the project code or file structure
• improved design or better support for design changes
• localization of documentation into a new language

Create a list of scaffold-eth examples (from branches) to add to Celo Composer. Create issues for new features.

Create documentation to support Celo Composer.

Make Web3js accessible from composer and give basic directions on usage.

This is a bit confusing, I think switching to "modules" or something else would be less confusing when troubleshooting npm/yarn issues.

Make Superfluid available within composer with basic directions on usage.

Create example with RedStone Oracle integration.