Ethereum

Binance Smart Chain

Solana

Celo

Beauty is the spice that flavors life’s experiences. Imagination is the chef that takes transforms it into a feast for the senses. Art is the magic that lets us see beyond the ordinary, explore new worlds, and create new realities. Welcome to Act One of a Three Part Series. Let’s take a journey together through ego and out into infinity. Let’s harness our powers of creation to transform. Self is faced with the constant powerful force splitting all into the duality between seemingly good and seeming bad. But remember not everything is as it seems. Do you believe in the power of blockchain and AI to create a more equal world? Together we can build a new future where everyone has a voice, and no one is left behind. Then join our team of rebels and let's hack the system and decentralize the power! So come one, come all and let's make some revolutionary code!

Web3Genesis

We are a growing NFT collection looking for a skilled graphic designer to create 888 unique generative alien profile pictures for our collection. As a graphic designer, you will have the opportunity to showcase your creativity and skills by designing original, high-quality alien images that will become part of a unique NFT collection.

Responsibilities:

Design and create 888 unique generative alien profile pictures for our NFT collection.
Collaborate with our team to develop concepts and ideas for the alien designs.
Utilize generative art techniques to create unique and dynamic alien images.
Ensure that all designs are original, high-quality, and meet the specifications required for the NFT format.
Deliver completed designs within the specified timeframe.
Requirements:

Experience in graphic design, with a strong portfolio showcasing your skills in digital art and design.
Expertise in generative art techniques and proficiency in the use of generative art software.
Familiarity with the NFT format and the technical specifications required for NFT artwork.
Excellent communication skills and the ability to work collaboratively with a team.
Strong attention to detail and the ability to deliver high-quality work within tight deadlines.
This is a freelance position with a flexible schedule, and compensation will be based on experience and the number of designs completed. If you are a talented graphic designer with a passion for generative art and are excited about the opportunity to contribute to a unique NFT collection, please submit your portfolio and resume for consideration.

Graphic Designer for Generative 888 Alien Profile Pictures for NFT Collection

We are a community of Freelancers who offer unique opportunities through our own eco-system of jobs. Based in Singapore, we are using web3 to connect with a wider audience and solve the demand problem to our supply of jobs.

Freelancer Nation

I need urgent help to create a component for my crypto wallet.

I need a pop up bottom screen (gorhom/bottom-sheets) that appears when you press the middle icon inside my tab navigator. 

Items on the pop up screen must be navigatable to my Stack.Navigator.

The crypto wallet called cypher has the same function if you want to install it. I have attatched a video in my google drive: https://drive.google.com/drive/folders/1bNvNfaDedVbBk977U8TpKpgYfECEY535?usp=sharing

You can reach out to me on discord if you have any questions Sly#2370

React Native Frontend Configuration

Uniswap is an automated liquidity provider for swapping, earning, and building on the leading decentralized crypto trading protocol. Uniswap is governed by its community and enables developers to build third-party solutions on top of the protocol. 

Uniswap

Use TEST_RECIPIENT as taker in Element test

Add ERC20->NFT tests for SeaportV1.4

Add Element ERC1155 support

Offchain Labs

I noticed this when initiating 2 withdrawals one right after the other, the 2nd dialog had both checkboxes already checked. This might be the case on other dialogs, too.

reset state of dialogs after closing

Ethereum Foundation

### Description

The `trin-cli` was previously used to initiate sending a message from one Trin client to another. 
It is no longer actively maintained or used

### Solution

Either:
- Mark the `trin-cli` crate as deprecated
- Remove the `trin-cli` crate


Deprecate `trin-cli`

Currently `yarn run tsc` catch errors from `node_modules` folder:
```
❯ yarn run tsc
yarn run v1.22.19
$ /home/.../.bin/tsc
node_modules/@wagmi/core/dist/contracts-3880ee54.d.ts:144:91 - error TS1005: '?' expected.

144 }, TOptions extends Options = DefaultOptions> = TFunction['inputs'] extends infer TInputs extends readonly AbiParameter[] ? Or<IsNever<TInputs>, NotEqual<TAbi, Abi>> extends true ? {
                                                                                              ~~~~~~~

node_modules/@wagmi/core/dist/contracts-3880ee54.d.ts:144:99 - error TS1005: ':' expected.

144 }, TOptions extends Options = DefaultOptions> = TFunction['inputs'] extends infer TInputs extends readonly AbiParameter[] ? Or<IsNever<TInputs>, NotEqual<TAbi, Abi>> extends true ? {
                                                                                                      ~~~~~~~~
```

It should only catch errors from our own files

Fix tsc not catching typescript errors 

Zharta

### 📃 GOALThe goal of this bounty is to get [Zharta's platform](https://app.zharta.io) listed on [https://defillama.com/protocols/NFT+Lending](https://defillama.com/protocols/NFT+Lending)The prize will be 0.25ETH paid in case of success, after the bounty is fulfilled, to a wallet to be designated by the winner of the bounty.### 🛠️HOWIn order to get Zharta listed there, you must follow the instructions set here: [https://docs.llama.fi/list-your-project/submit-a-project](https://docs.llama.fi/list-your-project/submit-a-project)You may also need to consult Zharta's documentation, present at: [https://zharta.gitbook.io/zharta-welcome-kit/overview/introducing-zharta](https://zharta.gitbook.io/zharta-welcome-kit/overview/introducing-zharta)

zharta

Get Zharta listed on DefiLlama for 0.25ETH

Reserve Protocol

### Prize TitleCollateral Plugin### Prize Bounty- $33k total for [this category across all plugins](https://docs.google.com/spreadsheets/d/1po4UsxqG-3Nn1O3N6lEbpiZszhV4zYw2Qv_ELv3AHvk/edit?usp=sharing).- Award for plugin is $3,000 USD paid 50/50 in USDC and RSR### Challenge DescriptionOur protocol is a platform that allows anyone to permissionlessly define an asset-backed currency. These currencies can be more creative, and potentially more successful, if there are more building blocks from which to choose.An important goal of this hackathon is to create as many safe, usable collateral plugins as possible to cover the entirety of possibilities in the defi landscape. Write a collateral plugin, or collection of plugins, for the defi protocol specified in the title, so that people can use collateral from the protocol as collateral in an RToken.### Submission RequirementsThe submission must include:- Twitter handle (if any)- Telegram handle (if any)- Discord handle (if any)- Source code for your Collateral plugin or plugins- An open source license- Documentation (e.g, a README file), describing the following for each plugin:    - What are the collateral token, reference unit, and target unit for this plugin?    - How does one configure and deploy an instance of the plugin?        - If the deployer should plug in price feeds, what units does your plugin expect those price feeds to be stated in?    - Why should the value (reference units per collateral token) decrease only in exceptional circumstances?    - How does the plugin guarantee that its `status()` becomes `DISABLED` in those circumstances?- Tests demonstrating the behaviors checked by our [example Collateral plugin test][example-test], which we encourage you to use as a starting template for your own testing. Particular behaviors must include:    - Deployment    - Issuance, appreciation, and redemption of an RToken with this Collateral in its basket    - Claiming rewards (or, if no rewards are available for this token, tests demonstrating that the claim-reward functions do nothing and don't revert)    - Correct behavior for `price()` when any price sources return invalid values    - Correctly changing `status()` whenever that's needed in order to flag sudden or impending default[example-test]: https://github.com/reserve-protocol/protocol/blob/master/test/integration/individual-collateral/CTokenFiatCollateral.test.ts### Acceptance CriteriaEach Collateral plugin must:- Fully implement the [ICollateral interface][icoll]- Satisfy the correctness properties given in the [Collateral plugin-writing howto](https://github.com/reserve-protocol/protocol/blob/master/docs/collateral.md)- Be fully permissionless once deployed- Be documented with cogent explanations of its economics.- Be deployable with USD as its [Unit of Account](https://reserve.org/protocol/monetary_units_baskets/#monetary-units)- Not be prone to relatively simple economic attacks or *cough cough* "highly profitable trading strategies"[icoll]: https://github.com/reserve-protocol/protocol/blob/master/contracts/interfaces/IAsset.sol#L75### Judging CriteriaIf there are multiple submissions in this category that meet all acceptance criteria, we will decide the grant winner based on the following judgments:- How clear, clean, and solidly-engineered is the implementation?- How gas-efficient is the implementation? The Reserve protocol makes heavy use of the `refresh()`, `price()`, and `status()` functions, for users' sake these need to be especially efficient.- How easy is it to reason about what these Collateral plugins do?- Do we see technical or economic vulnerabilities in these plugins, and how severe are they?- Could these plugins be deployed and used on mainnet immediately, or are they missing prerequisites? For instance, do they require price feeds or trading mechanisms that don't already exist?- How large is the range of significant, natural use cases covered by this set of Collateral plugins? Example of this further described below.For an illustration of "range of use cases," when we implemented our Compound collateral plugins, we thought it important to implement three different kinds of Collateral contracts to capture three substantially different kinds of Compound-wrapped tokens:- Tokens where the underlying token is a [fiatcoin][comp-fiat], and the Collateral plugin should default if the underlying token's price diverges from the target unit's price. For instance, cUSDC is redeemable for USDC, and the plugin should default if USDC loses its peg to USD.- Tokens where the underlying token is pegged to some [unstable][comp-unstable] asset, and the Collateral plugin should default if the underlying token's price diverges from the target unit's price. For instance, cWBTC has underlying token WBTC, and the plugin should default if WBTC loses its peg to BTC.- Tokens where the underlying token simply *is* the [target][comp-target] asset, and requires no default check. For instance, cETH has underlying token ETH, and so the underlying token itself needs no default check.[comp-fiat]:https://github.com/reserve-protocol/protocol/blob/master/contracts/plugins/assets/CTokenFiatCollateral.sol[comp-unstable]:https://github.com/reserve-protocol/protocol/blob/master/contracts/plugins/assets/CTokenNonFiatCollateral.sol[comp-target]:https://github.com/reserve-protocol/protocol/blob/master/contracts/plugins/assets/CTokenSelfReferentialCollateral.solIf we had implemented only one or two of these, the range of use cases would be notably smaller. The degree to which each Collateral plugin is configurable will also contribute to the range of use cases covered by the set of plugins. Again, we expect the already-existing Collateral plugins should be a good guide here.### Winner Announcement DateApproximately May 15, 2023; one month after the deadline.To accept the prize, winners will need to complete and sign one of the following on Docusign:- W-9 (for US citizen/resident or company)- W-8BEN (for non-US person)- W-8BEN-E (for non-US company/entity)We are quite secure in how we collect KYC information and will never share PII with anyone outside of necessary tax authorities.### Resources- [How to write a collateral plugin](https://github.com/reserve-protocol/protocol/blob/master/docs/collateral.md)- [Reserve's Solidity Style Guide](https://github.com/reserve-protocol/protocol/blob/master/docs/solidity-style.md)- [Example Compound Collateral Plugin](https://github.com/reserve-protocol/protocol/blob/master/contracts/plugins/assets/CTokenFiatCollateral.sol)- [Discord Link](https://discord.gg/jY9dGHKc)- [Github Repo](https://github.com/reserve-protocol/protocol)- [Documentation](https://reserve.org/protocol/)

Reserve Collateral Plugin - Maker Earn - 50x Uni Pools | $3,000

Reserve Collateral Plugin - BendDAO - Supplied ETH | $3,000

Reserve Collateral Plugin - Bancor - v2.1 | $3,000

Reserve Collateral Plugin - Stargate - USDC/USDT/ETH Pools | $3,000

Algorand Foundation

# Algorand Community Champion - Location - Miami**OVERVIEW*** **Short Description**: Algorand Foundation Community Champion* **Bounty**: 3,000 USDCa per quarter (or equivalent ALGO tokens) _(US residents will receive USDCa and have to opt-in to receive the asset in their wallet)_* **Payment Frequency**: Quarterly* **Estimated Time Commitment**: 20-25 hours per month **DESCRIPTION**Alongside our community, the Algorand Foundation is on a mission to build a global, borderless economy. To achieve this, we are empowering the world's most scalable, secure, decentralized, inclusive and green blockchain ecosystem - at scale - on the Algorand blockchain.We now invite you to apply to join us in this mission, and we are excited to announce the expansion of the Community Champions Program. Community Champions will fall into one of three (3) categories: Location Community Champion, Vertical Community Champion, Digital Community Champion.**WHAT IS THIS TASK?****THIS APPLICATION IS FOR: Location Community Champion (Miami).** The Location Community Champion is responsible for growing awareness and community participation in Miami through local events, meetups, and regional social media engagement. Tasks and objectives are coordinated with the Foundation Community Leads.**WHAT ARE THE REQUIREMENTS?**Must be passionate about Algorand's technology and ecosystem, committed to representing Algorand and growing the #algofam in your community. You will be an important part of our community team and in many cases, you will be the first interaction someone will have with the Algorand ecosystem. You must be willing to accurately represent Algorand’s mission and purpose with transparency, integrity and inclusivity. **DELIVERABLES**1. Host one event per quarter (virtual or physical TBD with your Foundation Lead)2. Support virtual events and related community calls in your region3. Attend and represent Algorand at local events regularly4. Management of your regional online community5. Provide post-event and activity reporting with metrics **KPIs**  * Event registrations & attendees  * Wallets Downloaded & Opened  * Regional Social Channel Growth  * Community & Foundation Lead Feedback**SUBMISSION PROCEDURE**1. **Tap “express interest” on the bounty and let us know who you are and why you should be chosen for this role.** 2. **Submit your interest formally via this [Community Champion Application](https://info.algorand.foundation/community-champions) form.**Thank you for applying to the Algorand Foundation Community Champions Program, we're grateful for your dedication and support. Once we've reviewed the applications, we will contact chosen candidates with next steps, no later than February 10th.  **PAYMENT**- **Champions will begin work March 1st (or soon thereafter pending application review).**- **First quarter (Q1) will be pro-rated, payment for March work will be provided 1st week of April.**- **Beginning April 1st, payments will be submitted via quarterly calendar.**## **IMPORTANT*** Do not start work until you have been approved and notified officially by the Algorand Foundation team.* Taking this bounty task means you have agreed to our [Bounty Agreement terms and policies](https://github.com/algorandfoundation/grow-algorand/blob/master/bounty-agreement.md).* Potential Conflict of InterestIn the (rare) event that you, or a business that you’re affiliated with, have received a grant, funding, or investment from Algorand Foundation, you need to disclose to Algorand Foundation at the time of application, and must maintain objectivity in your conduct as a Community Champion. If you find yourself in a situation where there could be a potential Conflict of Interest, you must recuse yourself. Any sign of Conflict of Interest in your duty as Community Champion will be grounds of immediate dismissal from the Champions program.

Algorand Community Champion - Location - Miami

Reserve Collateral Plugin - Morpho - Aave | $3,000

Reserve Collateral Plugin - Maple Finance - Permissionless Pool | $3,000

Reserve Collateral Plugin - Uniswap  - v3 | $3,000

### What was wrong?

Some methods are still unavailable on the `AsyncEth` class.

### How can it be fixed?

Following the pattern already established, add `sign_typed_data` to the `AsyncEth` class, and add corresponding tests. The `AsyncHTTPProvider` docs in `docs/provider.rst` will also need to be updated.



ethereum

Add async eth.sign_typed_data

### What was wrong?

Some methods are still unavailable on the `AsyncEth` class.

### How can it be fixed?

Following the pattern already established, add `sign_transaction` to the `AsyncEth` class, and add corresponding tests. The `AsyncHTTPProvider` docs in `docs/provider.rst` will also need to be updated.


Add async eth.sign_transaction

### What was wrong?

Some methods are still unavailable on the `AsyncEth` class.

### How can it be fixed?

Following the pattern already established, add `modify_transaction` to the AsyncEth class, and add corresponding tests. The `AsyncHTTPProvider` docs in `docs/provider.rst` will also need to be updated.



Add async eth.modify_transaction

### What was wrong?

Some methods are still unavailable on the `AsyncEth` class.

### How can it be fixed?

Following the pattern already established, add `replace_transaction` to the `AsyncEth` class, and add corresponding tests.

Add async eth.replace_transaction

### What was wrong?

Some methods are still unavailable on the `AsyncEth` class.

### How can it be fixed?

Following the pattern already established, add `get_uncle_count` to the AsyncEth class, and add corresponding tests. 


Add async eth.get_uncle_count

DFINITY

## OverviewStatus: OpenProject Type: Traditional: One applicant is selected to work on the task.Time Commitment: DaysExperience Level: IntermediateSize: USD 2'000 in ICP## DescriptionSince the Internet Computer allows canisters to sign Ethereum transactions, there's a need to hash those transactions. This is currently not directly possible in canisters written in Motoko. and a workaround like calling the [EVM utility canister](https://forum.dfinity.org/t/assigned-icdevs-org-bounty-28-evm-utility-canister-6-000/17880) has to be used.In this bounty, you will implement two cryptographic hashing algorithms in Motoko. Keccak-256 is the hashing algorithm used for signing Ethereum transactions. It is similar to the standardized SHA-3 but uses a different padding. Hence, it makes sense to include both variations, although the official SHA-3 is not used in Ethereum.## Acceptance Criteria- Implementation with tests- [Meaningful readme](https://github.com/dfinity/grant-rfps/blob/main/repo-checklist.md) with usage example - Open Source license (e.g. MIT)- Available in the [mops package manager](https://mops.one/)## How to apply? - Include links to previous relevant work.- Include a brief overview of how you will complete the task.- Give an estimated timeline for completing the task.- Post your application text in [this thread](https://forum.dfinity.org/t/open-dfinity-bounty-4-keccak-256-and-sha3-motoko-library-2000-in-icp/18469)## References### SHA-3 and Keccak implementations- https://github.com/ethereum/eth-hash- https://github.com/RustCrypto/hashes/tree/master/sha3### Examples of cryptographic hashing libraries in Motoko- https://github.com/timohanke/motoko-sha2- https://github.com/aviate-labs/crypto.mo- https://github.com/tgalal/motoko-bitcoin

BNT-4: Keccak-256 and SHA3 Motoko Library

Since EOF header changed and exact order of sections in header is defined this [function](https://github.com/ethereum/evmone/blob/master/lib/evmone/eof.cpp#L24) can be much simpler and faster.

Optimize validate_eof_headers

This will provide a small performance and readability boost.

Rules should use Sets to store reviewers

Forta Network

forta-network

Spam Forta Detection Bot

### Describe the bug

EthHub has been deprecated, meaning all of the links to docs.ethhub.io, currently live on the website, are broken

### To reproduce

1. Search for EthHub
2. Click on either link to docs.ethhub.io
3. See error


### Expected behavior

We should remove these links from the website, or replace them with relevant alternatives


### Screenshots

<img width="793" alt="Screenshot 2023-02-03 at 13 19 08" src="https://user-images.githubusercontent.com/37338979/216602241-a6bca7af-90fd-46cc-b2a5-3e0f3f0189bd.png">
<img width="405" alt="Screenshot 2023-02-03 at 13 19 21" src="https://user-images.githubusercontent.com/37338979/216602245-56d5a362-5838-4d8e-8101-e67f44829dcb.png">
<img width="645" alt="Screenshot 2023-02-03 at 13 19 31" src="https://user-images.githubusercontent.com/37338979/216602248-21d8a411-1e9d-4f60-b503-1517d22c547a.png">


### Desktop (please complete the following information)

All

### Smartphone (please complete the following information)

All

### Additional context

_No response_

Remove links to docs.ethhub.io as it's been deprecated

### Description
`pragma solidity` allows version ranges (e.g. `0.8.17-0.8.20`) and using comparison operators before a single version (e.g. `<0.8.17` or `=0.8.20`). Unfortunately it looks like a combination of the two is also allowed, which makes no sense: `<0.8.17 - =0.8.20`.

In version ranges the operator is simply ignored and replaced with `>=` for the first component and `<=` for the second one: https://github.com/ethereum/solidity/blob/ddbef8f65092cd09422366881d0fc1dad5d4b64e/liblangutil/SemVerHandler.cpp#L209-L215

### How to reproduce
This pragma will match `0.8.17`, `0.8.18`, `0.8.19` and `0.8.20`:
```solidity
pragma solidity <0.8.17 - >0.8.20;
```

Version pragma does not disallow prefixing version ranges with comparison operators

OffchainLabs

clean up lint errors in `*.cy.ts` files

_originally posted by @poojaranjan in https://github.com/ethereum/EIPs/issues/6131_

Contribute to top web3 projects

Learn, earn and showcase by contributing to bounties on open source issues to help ecosystems to grow!