Zharta

SporkDAOOfficial

Fuel Labs is building Fuel, the worlds fastest modular execution layer.

Fuel Labs

IPFS

Swarm is a decentralised storage and communication system for a self-sovereign digital society.

Ethersphere

A Rome-based community to gather local web3 builders and foster bottom-up innovation.

urbe.eth

ETHWarsaw

FOAM

DIAdata.org

Foundry is a blazing fast, portable and modular toolkit for Ethereum application development written in Rust.

Foundry

### Component

Forge, Cast

### Describe the feature you would like

I'm currently migrating from `dapp.tools` and it had this nice UX to handle keystore files:

1. Declare the following env vars:
 - `ETH_KEYSTORE`: the path to the keystore **directory**
 - `ETH_FROM`: the account from which send the tx from (I believe this was used to find the right keystore **file** inside the keystore directory).
 - `ETH_PASSWORD`: the **path** to a plain-text password file with the password for the keystore file in the local file system.
2. Anything requiring wallet signing pickups the above variables automatically:
 ```bash
 dapp create src/MyContract.sol:MyContract
 seth send $ADDRESS "myFunc(address)" $ARG
 ```

I'm finding it a bit difficult to work with Foundry for that purpose. Specifically regarding contract deployment. Main differences are:

1. `ETH_KEYSTORE` works, but it expects a keystore **file**, not a directory.
2. `ETH_FROM` is redundant, since the sender wallet is derived from `ETH_KEYSTORE`
3. `ETH_PASSWORD` doesn't work.

Also if I use `CAST_PASSWORD` env var, `forge create` does not pick it up, so I need to be explicit when passing it:

```bash
forge create --password=${CAST_PASSWORD} src/MyContract.sol:MyContract.sol
```

Also ideally such configs could be in `foundry.toml` as well:

```toml
[default]
password-file = '~/.eth-password'

# either
keystore-directory = '~/.ethereum/keystore'
from = '0xdeAD00000000000000000000000000000000dEAd'

# or
keystore-file = '~/.ethereum/keystore/UTC--2022-01-01T00-00-00.000000000Z--dead00000000000000000000000000000000dead'

```

Furthermore, users should have the liberty to overwrite any configs with environment variables. For example, it's very useful to be able to define a keystore directory containing multiple accounts and define the `from` address with env vars.

```
FOUNDRY_ETH_FROM=0x0783...122 FOUNDRY_PASSWORD_FILE=~/.eth-password-0783...122 forge deploy ...
```

### Additional context

As a workaround, I have written a small helper script to allow me to use `forge` the same way I could use `dapp.tools`. Perhaps this can help guiding the implementation.

```bash
#!/bin/bash

# scripts/deploy.sh

set -eo pipefail

function log() {
 echo -e "$@" >&2
}

function die() {
 log "$@"
 log ""
 exit 1
}

function err_msg_keystore_file() {
cat <<MSG
ERROR: could not determine the location of the keystore file.

You should either define:

\t1. The FOUNDRY_ETH_KEYSTORE_FILE env var or;
\t2. Both FOUNDRY_ETH_KEYSTORE_DIR and FOUNDRY_ETH_FROM env vars.
MSG
}

function err_msg_etherscan_api_key() {
cat <<MSG
ERROR: cannot verify contracts without ETHERSCAN_API_KEY being set.

You should either:

\t1. Not use the --verify flag or;
\t2. Define the ETHERSCAN_API_KEY env var.
MSG
}

function usage() {
cat <<MSG
deploy.sh contract_path [--constructor-args ...args]

Examples:

\t# Constructor does not take any arguments
\tdeploy.sh src/MyContract.sol:MyContract

\t# Constructor takes (uint, address) arguments
\tdeploy.sh src/MyContract.sol:MyContract --constructor-args 1 0x0000000000000000000000000000000000000000
MSG
}

function deploy() {
 local ENV_FILE="${BASH_SOURCE%/*}/../.env"
 [ -f "$ENV_FILE" ] && source "$ENV_FILE"

 FOUNDRY_ETH_FROM="${FOUNDRY_ETH_FROM:-$ETH_FROM}"
 FOUNDRY_ETHERSCAN_API_KEY="${FOUNDRY_ETHERSCAN_API_KEY:-$ETHERSCAN_API_KEY}"
 FOUNDRY_ETH_KEYSTORE_DIRECTORY="${FOUNDRY_ETH_KEYSTORE_DIRECTORY:-$ETH_KEYSTORE}"

 if [ -z "$FOUNDRY_ETH_KEYSTORE_FILE" ]; then
 [ -z "$FOUNDRY_ETH_KEYSTORE_DIRECTORY" ] && die "$(err_msg_keystore_file)"
 # Foundy expects the Ethereum Keystore file, not the directory.
 # This step assumes the Keystore file for the deployed wallet includes $ETH_FROM in its name.
 FOUNDRY_ETH_KEYSTORE_FILE="${FOUNDRY_ETH_KEYSTORE_DIRECTORY%/}/$(ls -1 $FOUNDRY_ETH_KEYSTORE_DIRECTORY | \
 # -i: case insensitive
 # #0x: strip the 0x prefix from the the address
 grep -i ${FOUNDRY_ETH_FROM#0x})"
 fi
 [ -z "$FOUNDRY_ETH_KEYSTORE_FILE" ] && die "$(err_msg_keystore_file)"

 # Handle reading from the password file
 local PASSWORD_OPT=''
 if [ -f "$FOUNDRY_ETH_PASSWORD_FILE" ]; then
 PASSWORD_OPT="--password=$(cat "$FOUNDRY_ETH_PASSWORD_FILE")"
 fi

 # Require the Etherscan API Key if --verify option is enabled
 set +e
 if grep -- '--verify' <<< "$@" > /dev/null; then
 [ -z "$FOUNDRY_ETHERSCAN_API_KEY" ] && die "$(err_msg_etherscan_api_key)"
 fi
 set -e

 # Log the command being issued, making sure not to expose the password
 log "forge create --keystore="$FOUNDRY_ETH_KEYSTORE_FILE" $(sed 's/=.*$/=[REDACTED]/' <<<${PASSWORD_OPT}) $@"
 forge create --keystore="$FOUNDRY_ETH_KEYSTORE_FILE" ${PASSWORD_OPT} $@
}

# Executes the function if it's been called as a script.
# This will evaluate to false if this script is sourced by other script.
if [ "$0" = "$BASH_SOURCE" ]; then
 if [ $# -eq 0 ]; then
 die "$(usage)"
 fi

 [ "$1" = '-h' ] || [ "$1" = '--help' ] && {
 log "$(usage)"
 exit 0
 }

 deploy $@
fi
```

```bash
# .env

export FOUNDRY_ETHERSCAN_API_KEY=API_KEY
export FOUNDRY_ETH_FROM=WALLET_ADDRESS
export FOUNDRY_ETH_KEYSTORE_DIRECTORY=PATH_OF_ETHEREUM_KEYSTORE_DIR # i.e.: ${HOME}/.ethereum/keystore/
export FOUNDRY_ETH_PASSWORD=PATH_OF_ETHEREUM_PASSWORD_FILE

T-feature

C-cast

Rust

Solidity

Shell

Dockerfile

Improve wallet management UX using Keystore

Describe what your bounty is about.

FOAM is creating a proof of location protocol for Web3 and other applications. The FOAM Trust Zone Program is currently beta-testing radios for localization. This testing will generate data and lessons learned to improve the FOAM technical stack, ahead of future open releases of the FOAM network. FAQ: https://mirror.xyz/foamspace.eth/9QRjUNdAuw80x9CLvMs76hEp-LVpV92CXVyGmC0H4fU

We are looking for additional locations that can be used to host FOAM radios for testing for participant teams in Austin, Texas.

If you have access to a quality location that could host a FOAM radio for a period of 6 months or more, we would like to briefly meet with you to discuss and evaluate your location.

Describe what your bounty is about.
FOAM is creating a proof of location protocol for Web3 and other applications. The FOAM Trust Zone Program is currently beta-testing radios for localization. This testing will generate data and lessons learned to improve the FOAM technical stack, ahead of future open releases of the FOAM network. FAQ: <a href="https://mirror.xyz/foamspace.eth/9QRjUNdAuw80x9CLvMs76hEp-LVpV92CXVyGmC0H4fU" rel="nofollow">https://mirror.xyz/foamspace.eth/9QRjUNdAuw80x9CLvMs76hEp-LVpV92CXVyGmC0H4fU</a>
We are looking for additional locations that can be used to host FOAM radios for testing for participant teams in Austin, Texas.
If you have access to a quality location that could host a FOAM radio for a period of 6 months or more, we would like to briefly meet with you to discuss and evaluate your location.

HTML

FOAM Location Scouting (Austin)

We are looking for an experienced Go developer who is interested in writing a service which monitors DIA oracles performance metrics.

The service should take these parameters as _input_:
1. Oracle address
2. Chain ID
3. RPC node
 
Given these input parameters, it should connect to the respective blockchain via RPC node and scan for oracle update events.
More precisely, the the following _output_ quantities should be written into a database:
1. Oracle creation date
2. Oracle funding wallet address
3. Transaction hash
4. Block number
5. Timestamp of block inclusion
6. Asset which got updated
7. Asset value
8. Timestamp of data inside (part of the update)
9. Gas usage
10. Gas cost
11. Total transaction cost
12. Remaining gas funds in oracle funding wallet
13. TX sender

As there is no straightforward way to get the Oracle creation date/block/hash please proceed as follows:
Check for the latest transaction in the DB. If there is no entry, iterate backwards in history and fetch all transactions until you hit the contract creation. If there is an entry, continue from this block until now.

Furthermore, please:
- Write the service in Go
- Use timescaleDB as database
- Allow to input more than one contract address per blockchain and run the service on multiple blockchains in parallel
- Develop comprehensive unit tests to ensure functionality and robustness of the oracle monitoring service
- Deliver a docker container with entire functionality
- Provide documentation for setting up the service and running tests 

Resources:
[Documentation for DIA oracles architecture](https://docs.diadata.org/documentation/oracle-documentation)
[Demo oracles](https://docs.diadata.org/documentation/oracle-documentation/deployed-contracts)

If you have questions don't hesitate to ask. Ideally we can connect on our Discord server in order to discuss if necessary.

We are looking for an experienced Go developer who is interested in writing a service which monitors DIA oracles performance metrics.
The service should take these parameters as input:
<ol dir="auto">
<li>Oracle address</li>
<li>Chain ID</li>
<li>RPC node</li>
</ol>
Given these input parameters, it should connect to the respective blockchain via RPC node and scan for oracle update events. 
More precisely, the the following output quantities should be written into a database:
<ol dir="auto">
<li>Oracle creation date</li>
<li>Oracle funding wallet address</li>
<li>Transaction hash</li>
<li>Block number</li>
<li>Timestamp of block inclusion</li>
<li>Asset which got updated</li>
<li>Asset value</li>
<li>Timestamp of data inside (part of the update)</li>
<li>Gas usage</li>
<li>Gas cost</li>
<li>Total transaction cost</li>
<li>Remaining gas funds in oracle funding wallet</li>
<li>TX sender</li>
</ol>
As there is no straightforward way to get the Oracle creation date/block/hash please proceed as follows: 
Check for the latest transaction in the DB. If there is no entry, iterate backwards in history and fetch all transactions until you hit the contract creation. If there is an entry, continue from this block until now.
Furthermore, please:
<ul dir="auto">
<li>Write the service in Go</li>
<li>Use timescaleDB as database</li>
<li>Allow to input more than one contract address per blockchain and run the service on multiple blockchains in parallel</li>
<li>Develop comprehensive unit tests to ensure functionality and robustness of the oracle monitoring service</li>
<li>Deliver a docker container with entire functionality</li>
<li>Provide documentation for setting up the service and running tests</li>
</ul>
Resources: 
<a href="https://docs.diadata.org/documentation/oracle-documentation" rel="nofollow">Documentation for DIA oracles architecture</a> 
<a href="https://docs.diadata.org/documentation/oracle-documentation/deployed-contracts" rel="nofollow">Demo oracles</a>
If you have questions don't hesitate to ask. Ideally we can connect on our Discord server in order to discuss if necessary.

init

Track oracle performances

Build Oracle Monitoring Tool

# Description 📃
This bounty can be split into sub-bounties by each individual RPC request type (e.g. view access key, view access keys list, transaction in the block, view state, etc). Each sub-bounty can be implemented by a different team. In order to benefit from having Near light client integrated into near-api-js, we need the RPC interface of Near node to return proofs for most of the RPC replies (e.g. have an option to do it when “proof” parameter is passed). For example, the proof of a transaction being included into the block would consist of: merkle path towards transaction in a shard, merkle path towards shard hash. For access keys and viewing state you would need to provide the path in merkle patricia trie. We have already implemented proof for Transaction Status, which you can use as an example: https://docs.near.org/api/rpc/transactions#transaction-status.

## Acceptance Criteria 🏁
Please complete your bounties in the form of pull-requests to https://github.com/near/nearcore 

## Reward Pool 💸
USDC **16000**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
This bounty can be split into sub-bounties by each individual RPC request type (e.g. view access key, view access keys list, transaction in the block, view state, etc). Each sub-bounty can be implemented by a different team. In order to benefit from having Near light client integrated into near-api-js, we need the RPC interface of Near node to return proofs for most of the RPC replies (e.g. have an option to do it when “proof” parameter is passed). For example, the proof of a transaction being included into the block would consist of: merkle path towards transaction in a shard, merkle path towards shard hash. For access keys and viewing state you would need to provide the path in merkle patricia trie. We have already implemented proof for Transaction Status, which you can use as an example: https://docs.near.org/api/rpc/transactions#transaction-status.
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
Please complete your bounties in the form of pull-requests to https://github.com/near/nearcore 
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 16000

Create NEAR_Verifiable_RPC_ETHEN_POCIASK

Create NEAR_Verifiable_RPC_ANUP_SWAMY_VEENA

Create NEAR_VERIFIABLE_RPC_Anto.md

Create NEAR_Verifiable_RPC_ANTO_JOSEPH

NEAR: Verifiable RPC replies

# Description 📃
L1, L2, side chains, zk rollups, POA networks, dev tools, wallets, on-chain privacy, etc.

## Acceptance Criteria 🏁
<ul><li>You and your team must be physically present at ETHDenver to work on a project for submission</li><li>You and your entire team must be physically present at the closing ceremonies to win a prize</li><li>You must form a team of 2-4 members</li><li>Your project must integrate blockchain technology (other chains besides Ethereum are fine)</li><li>You cannot work on your project before the event begins on February 24, 2023, 10 AM MST</li><li>You cannot steal another team's source code or use previous code from another hackathon</li><li>Pre-existing projects are not allowed. You may, however, build a new feature for an existing project that is unique and standalone. If you are going to #BUIDL on a pre-existing project, we strongly suggest speaking with the BUIDLx Stewards and get permission from the #BUIDL Steward.</li><li>Please comply with all instructions from ETHDenver organizers</li><li>Be cool - disruptive behavior will not be tolerated and may result in disqualification</li><li>Please refer to the waiver you signed when applying for the event for additional details regarding appropriate behavior.</li><li>Decisions are final for determining prizes and awards by the #BUIDL Steward and/or #BUIDLx TeamThe #BUIDL Steward is like the commissioner of any sports league. The #BUIDL Steward will hav final say in your team and projects eligibility in #BUIDLathon, prizes, and awards for all track prizes and sponsor bounties.&nbsp;</li></ul>

## Reward Pool 💸
USDC **15000**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
L1, L2, side chains, zk rollups, POA networks, dev tools, wallets, on-chain privacy, etc.
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
<ul dir="auto"><li>You and your team must be physically present at ETHDenver to work on a project for submission</li><li>You and your entire team must be physically present at the closing ceremonies to win a prize</li><li>You must form a team of 2-4 members</li><li>Your project must integrate blockchain technology (other chains besides Ethereum are fine)</li><li>You cannot work on your project before the event begins on February 24, 2023, 10 AM MST</li><li>You cannot steal another team's source code or use previous code from another hackathon</li><li>Pre-existing projects are not allowed. You may, however, build a new feature for an existing project that is unique and standalone. If you are going to #BUIDL on a pre-existing project, we strongly suggest speaking with the BUIDLx Stewards and get permission from the #BUIDL Steward.</li><li>Please comply with all instructions from ETHDenver organizers</li><li>Be cool - disruptive behavior will not be tolerated and may result in disqualification</li><li>Please refer to the waiver you signed when applying for the event for additional details regarding appropriate behavior.</li><li>Decisions are final for determining prizes and awards by the #BUIDL Steward and/or #BUIDLx TeamThe #BUIDL Steward is like the commissioner of any sports league. The #BUIDL Steward will hav final say in your team and projects eligibility in #BUIDLathon, prizes, and awards for all track prizes and sponsor bounties. </li></ul>
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 15000

kopy-kat

Create olivert1.md

Create INHERITABLE.md

Create SLANG_NODESLANGER5000

Create olivert1.md 

Create SWAPPY

philogy

Create REENTRANCY_PROXY_ARIEL_TM.md

Create INHERITABLE_PAULLOH.md

Create SLANG.md

Create SWAPPY_PILOT.md

ETHDenver: #BUIDLathon 2023 Infrastructure + Scalability

# Description 📃
This task is designed to incentivize using decentralized architecture in your projects. Pocket Network provides the only reliable and decentralized RPC network in the world governed by a DAO with the most contributor-friendly ecosystem. Pocket offers free connections to dozens of chains, from Ethereum and Polygon to Fantom and FUSE.

## Acceptance Criteria 🏁
● Decentralize your RPC for any project using a Pocket endpoint ● Endpoints must be private and minted by application developers (no public RPC usage) We reserve the right to withhold prizing in cases where low-quality submissions do not meet our bounty requirements.

## Reward Pool 💸
USDC **3750**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
This task is designed to incentivize using decentralized architecture in your projects. Pocket Network provides the only reliable and decentralized RPC network in the world governed by a DAO with the most contributor-friendly ecosystem. Pocket offers free connections to dozens of chains, from Ethereum and Polygon to Fantom and FUSE.
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
● Decentralize your RPC for any project using a Pocket endpoint ● Endpoints must be private and minted by application developers (no public RPC usage) We reserve the right to withhold prizing in cases where low-quality submissions do not meet our bounty requirements.
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 3750

Create scoronelhamilton.md

ferrodri.md

DeFi Detective - Darryl

Blockhead - Darryl

Create Bandit_Club_Albert_Su.md

Create Gelkin_Joshia_Seam

Create Gelkin_Jim_Jim_Valkema

Create Gelkin_YongKang_Chia

Create SQUIRRLY_MATT_LEE.md

zmitzie

Create Squirrly_Adam_Reis.md

Create defi_detective_plotchy.md

Create SQUIRRLY_BEAU_TROXCLAIR

Create DAyOri_Yuzu

Create BEAD_DAO_JAYDEN_WINDLE.md

Create DAyOri_Aru_Sasaki

Create DIATOMIX_PEDRO_GALVEIAS.md

PETERISPRIEDITIS

Create laurens-van-kessenich

Create PEANUT_PROTOCOL.md

Create MEV_NFT DATA SHIELD.md

Create MEV_NFT_JEFF.md

Pokt Network: Build on Pocket Network

# Description 📃
Integrate Web3Auth or Torus Wallet into your project and make the onboarding user experience as seamless as possible for your users.

## Acceptance Criteria 🏁
Incorporate either Web3Auth Plug and Play, Core Kit, or Torus Wallet into your application and build a user-centric onboarding flow. Judging will lean towards projects that are full MVPs that focus on the UX, although a clean and creative implementation of the feature serving as an excellent example of feature usage is also acceptable. Please show a steady commit trail and thought process e.g. sketches, discussion, issues on how you arrived at the decision to incorporate this feature.

## Reward Pool 💸
USDC **1000**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
Integrate Web3Auth or Torus Wallet into your project and make the onboarding user experience as seamless as possible for your users.
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
Incorporate either Web3Auth Plug and Play, Core Kit, or Torus Wallet into your application and build a user-centric onboarding flow. Judging will lean towards projects that are full MVPs that focus on the UX, although a clean and creative implementation of the feature serving as an excellent example of feature usage is also acceptable. Please show a steady commit trail and thought process e.g. sketches, discussion, issues on how you arrived at the decision to incorporate this feature.
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 1000

mobmatt

Krypto_Kredit_luiscmogrovejo

luiscmogrovejo

giorgio-villani

Create SOFAMON_PETER.md

Kenny-Gin1

Create DENOTED_ERIC_ZAKARIASSON.md

Create DENOTED_YANNIS_BOUACIDA.md

Create KYD_ASIYA

Create KYD_Yaron.md

Create KYD_JONATHAN_CRUZ.md

ottodevs

Create RIKO_TRAVIS_WADE

jcruzfff

Create LabsDAO_thomascarr.md

Create LABSDAO_SHADMAN_HOSSAIN.md

Create LabsDAO_THOMAS_CARR.md

Web3Auth: Build with Web3Auth

# Description 📃
Number of Winners: 2Infura is looking for teams interested in leveraging the Lens Protocol’s composable and decentralized social graph to create novel web3 social dApps built with Truffle and deployed with Infura to the Polygon PoS network.<ul><li>Infura makes access to the multi-chain world easy, providing network access to 10 networks including Polygon PoS</li><li>Developers will be expected to use multiple features of the Lens Protocol such as Follow, Comment, Post and Collect</li><li>Check out https://www.lens.xyz/apps for a list of existing apps built on Lens for inspiration and to ensure your app is a unique use-case</li></ul>

## Acceptance Criteria 🏁
- Use Lens Protocol to develop a social app and using Infura and Truffle- Use multiple features of the Lens Protocol such as Follow, Comment, Post and Collect- UI/UX - Functionality- Documentation

## Reward Pool 💸
USDC **2000**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
Number of Winners: 2Infura is looking for teams interested in leveraging the Lens Protocol’s composable and decentralized social graph to create novel web3 social dApps built with Truffle and deployed with Infura to the Polygon PoS network.<ul dir="auto"><li>Infura makes access to the multi-chain world easy, providing network access to 10 networks including Polygon PoS</li><li>Developers will be expected to use multiple features of the Lens Protocol such as Follow, Comment, Post and Collect</li><li>Check out https://www.lens.xyz/apps for a list of existing apps built on Lens for inspiration and to ensure your app is a unique use-case</li></ul>
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
- Use Lens Protocol to develop a social app and using Infura and Truffle- Use multiple features of the Lens Protocol such as Follow, Comment, Post and Collect- UI/UX - Functionality- Documentation
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 2000

Create OPENASK_RAY_ZHU.md

Infura: Best Use of Lens Protocol using Infura

# Description 📃
At INTU, we believe that the key to providing mainstream users with a better experience in Web3 starts with infrastructure. By allowing end-users to self-custody without the risk and stress of private key single point of failure, we can provide a broader audience the confidence to connect to Web3, and continue growing the adoption of Web3.&nbsp; Any project who integrates INTU’s SDK, or makes use of resulting INTU Accounts for their end users will be considered for this prize pool.&nbsp; Examples include:<ul><li>Key management and wallet software, or integrations with existing open wallets (Metamask Snaps, etc)</li><li>Web3 Games, using EOAs as player identity</li><li>DAOs, or other communities with shared ownership</li><li>Web3 Browsers, Discovery Portals, or Launchpads</li></ul>Prize Pool Divided Amongst the Top 3 Projects/TeamsParticipants competing for this bounty will have access to the following resources:<ul><li>INTU’s SDK and Smart Contract system, deployed on Sepolia and Goerli</li><li>INTU’s documentation, and public github repo</li><li>NPM Packages</li><li>INTU will dedicate engineers, cryptographers, and generalists to support in planning, researching, and integrating throughout BUIDL week and the hackathon weekend</li></ul>Dedicated Discord channel.

## Acceptance Criteria 🏁
The coolest/most innovative project or submission who successfully integrates the SDK or Web3 API into their smart contract system, decentralized application, interface, or local application will be considered.&nbsp; A successful integration to qualify for the prize pool will be defined as creating and/or using INTU accounts for end-users. INTU reserves the right to determine eligibility. Submissions earning other INTU bounties are not eligible for the prize pool.

## Reward Pool 💸
USDC **3000**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
At INTU, we believe that the key to providing mainstream users with a better experience in Web3 starts with infrastructure. By allowing end-users to self-custody without the risk and stress of private key single point of failure, we can provide a broader audience the confidence to connect to Web3, and continue growing the adoption of Web3.  Any project who integrates INTU’s SDK, or makes use of resulting INTU Accounts for their end users will be considered for this prize pool.  Examples include:<ul dir="auto"><li>Key management and wallet software, or integrations with existing open wallets (Metamask Snaps, etc)</li><li>Web3 Games, using EOAs as player identity</li><li>DAOs, or other communities with shared ownership</li><li>Web3 Browsers, Discovery Portals, or Launchpads</li></ul>Prize Pool Divided Amongst the Top 3 Projects/TeamsParticipants competing for this bounty will have access to the following resources:<ul dir="auto"><li>INTU’s SDK and Smart Contract system, deployed on Sepolia and Goerli</li><li>INTU’s documentation, and public github repo</li><li>NPM Packages</li><li>INTU will dedicate engineers, cryptographers, and generalists to support in planning, researching, and integrating throughout BUIDL week and the hackathon weekend</li></ul>Dedicated Discord channel.
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
The coolest/most innovative project or submission who successfully integrates the SDK or Web3 API into their smart contract system, decentralized application, interface, or local application will be considered.  A successful integration to qualify for the prize pool will be defined as creating and/or using INTU accounts for end-users. INTU reserves the right to determine eligibility. Submissions earning other INTU bounties are not eligible for the prize pool.
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 3000

Create YielDex_Alfred_Gaillard

raniabou

josephbouassaf

Intu: Integrating INTU Advanced Accounts for End-users

# Description 📃
INTU Web3 Accounts bring revolutionary new potential to Web3 applications.&nbsp; By introducing new characteristics to Web3 accounts, like distributed and dynamic ownership, account recovery, and proactive security, INTU would like to encourage hackathon participants to challenge their assumptions and understanding of Web3 accounts, and build new features and functionality on top of INTU’s SDK and infrastructure.&nbsp; This bounty is for smart contract systems, protocols, or dapps which take advantage of core INTU features to build additional services, functionality, or products. By separating account creation and behavior from program or application functionality, we believe we can build a safer, easier to use Web3 for end-users. Examples include:<ul><li>Purpose-specific operations logic and policies to manage and enforce group actions, like compliance, spending limits, or parental controls, codified into smart contracts or a dapp</li><li>Escrow, transfer, or recovery services, including using off-chain credentials or KYC</li><li>Proxy payments for account use, or subsidized account use by a third party</li><li>Smart Contract Account Abstraction</li><li>Hybrid Custody Services</li></ul> Participants competing for this bounty will have access to the following resources:<ul><li>INTU’s SDK and Smart Contract system, deployed on Sepolia and Goerli</li><li>INTU’s documentation, and public github repo</li><li>NPM Packages</li><li>INTU will dedicate engineers, cryptographers, and generalists to support in planning, researching, and integrating throughout BUIDL week and the hackathon weekend</li><li>Dedicated Discord channel</li></ul>

## Acceptance Criteria 🏁
Winners will be chosen by INTU based on the following criteria:<ul><li>Innovative and useful feature set extending the impact of INTU’s infrastructure</li><li>Qualified projects may not need to fully integrate the SDK, but should expect and make use of either a) decentralized key generation, b) key resharing, or c) participant rotation</li><li>Smart contracts must be deployed on an EVM-compatible platform</li><li>Novel protocols, infrastructure, or additional tooling working in conjunction with INTU’s infrastructure will be considered; a user interface is not required.</li></ul>

## Reward Pool 💸
USDC **4500**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
INTU Web3 Accounts bring revolutionary new potential to Web3 applications.  By introducing new characteristics to Web3 accounts, like distributed and dynamic ownership, account recovery, and proactive security, INTU would like to encourage hackathon participants to challenge their assumptions and understanding of Web3 accounts, and build new features and functionality on top of INTU’s SDK and infrastructure.  This bounty is for smart contract systems, protocols, or dapps which take advantage of core INTU features to build additional services, functionality, or products. By separating account creation and behavior from program or application functionality, we believe we can build a safer, easier to use Web3 for end-users. Examples include:<ul dir="auto"><li>Purpose-specific operations logic and policies to manage and enforce group actions, like compliance, spending limits, or parental controls, codified into smart contracts or a dapp</li><li>Escrow, transfer, or recovery services, including using off-chain credentials or KYC</li><li>Proxy payments for account use, or subsidized account use by a third party</li><li>Smart Contract Account Abstraction</li><li>Hybrid Custody Services</li></ul> Participants competing for this bounty will have access to the following resources:<ul dir="auto"><li>INTU’s SDK and Smart Contract system, deployed on Sepolia and Goerli</li><li>INTU’s documentation, and public github repo</li><li>NPM Packages</li><li>INTU will dedicate engineers, cryptographers, and generalists to support in planning, researching, and integrating throughout BUIDL week and the hackathon weekend</li><li>Dedicated Discord channel</li></ul>
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
Winners will be chosen by INTU based on the following criteria:<ul dir="auto"><li>Innovative and useful feature set extending the impact of INTU’s infrastructure</li><li>Qualified projects may not need to fully integrate the SDK, but should expect and make use of either a) decentralized key generation, b) key resharing, or c) participant rotation</li><li>Smart contracts must be deployed on an EVM-compatible platform</li><li>Novel protocols, infrastructure, or additional tooling working in conjunction with INTU’s infrastructure will be considered; a user interface is not required.</li></ul>
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 4500

Intu: Unlock new potential using INTU’s Account Infrastructure

Create sesame.md

jolow99

zkPoEX

federava

Create BAZAARK_ANUP_SWAMY_VEENA.md

Create BAZAARK_Anto_Joseph

Create BAZAARK_ANTO_JOSEPH

ETHDenver: #BUIDLathon Celebrity Top Pick

# Description 📃
While focusing on your web3 project and pitch, easily add seedless frictionless wallets and powerful web3 functionality (swap, NFTs) with the help of Liquality SDKs.

## Acceptance Criteria 🏁
1. Using Liquality SDKs2. Emailing the github and the pitch deck where you describe the use of these SDKs to &nbsp; ethdenver@liquality.io3. Listing benefits and challenges you encountered in the developer experience, including documented bug fixes

## Reward Pool 💸
USDC **5000**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
While focusing on your web3 project and pitch, easily add seedless frictionless wallets and powerful web3 functionality (swap, NFTs) with the help of Liquality SDKs.
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
1. Using Liquality SDKs2. Emailing the github and the pitch deck where you describe the use of these SDKs to   ethdenver@liquality.io3. Listing benefits and challenges you encountered in the developer experience, including documented bug fixes
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 5000

Create XR-NFTS-Dadong-Hu

Liquality: Build your ETH Denver project  using the Liquality SDK

# Description 📃
This bounty is to be distributed to those that make improvements involving changes to how applications interact with the Ethereum RPC using Pocket Network’s decentralized endpoints.

## Acceptance Criteria 🏁
● Must utilize Pocket Network’s Private RPC Endpoint minted on Pocket’s Portal (see resources)● Must provide a demo/presentation on how &amp; why Pocket Network’s RPC Endpoint is used● Can be an addition to/extension of an existing service or a net new service ● Should solve an existing and real problem ● Nice to haves:&nbsp;● Pocket-specific utility● A free public good service● 2022 ETHDenver Bounty Winners: https://www.blog.pokt.network/pocket-ethdenver-2022-bounty-winners/ We reserve the right to withhold prizing in cases where low-quality submissions do not meet our bounty requirements

## Reward Pool 💸
USDC **11250**

<h1 dir="auto">Description <g-emoji class="g-emoji" alias="page_with_curl" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c3.png">📃</g-emoji></h1>
This bounty is to be distributed to those that make improvements involving changes to how applications interact with the Ethereum RPC using Pocket Network’s decentralized endpoints.
<h2 dir="auto">Acceptance Criteria <g-emoji class="g-emoji" alias="checkered_flag" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f3c1.png">🏁</g-emoji></h2>
● Must utilize Pocket Network’s Private RPC Endpoint minted on Pocket’s Portal (see resources)● Must provide a demo/presentation on how &amp; why Pocket Network’s RPC Endpoint is used● Can be an addition to/extension of an existing service or a net new service ● Should solve an existing and real problem ● Nice to haves: ● Pocket-specific utility● A free public good service● 2022 ETHDenver Bounty Winners: https://www.blog.pokt.network/pocket-ethdenver-2022-bounty-winners/ We reserve the right to withhold prizing in cases where low-quality submissions do not meet our bounty requirements
<h2 dir="auto">Reward Pool <g-emoji class="g-emoji" alias="money_with_wings" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4b8.png">💸</g-emoji></h2>
USDC 11250

HELP ME

COMPANY

RESOURCES