pooltogether / pooltogether-community-ui

UI to use when creating your own custom pools, prize strategies or as reference code for integrating your own pools.

PoolTogether v3 - Reference Frontend.

The newest UI for communicating with the (unreleased) v3 PoolTogether protocol.

A demo of this app is live here.

To run the project against a local node you can use the pooltogether-contracts. With those contracts you can bootstrap a local Buidler EVM instance with test data so that you can develop the app locally.

Setup

Install dependencies:

$ yarn

Make sure you have direnv installed and copy .envrc.example to .envrc:

$ cp .envrc.example .envrc

Fill in your own values for .envrc, then run:

$ direnv allow

To run the local server, run:

$ yarn dev

Developer Tools

• Prettier

pooltogether-community-ui's Issues

Get community pools on Polygon

https://community.pooltogether.com/pools/matic/0x9e299cf900a81b55024398ff2cdb1c9c0fcec902/home

Pool not displaying on https://community.pooltogether.com/ when on Polygon Mainnet

When search a contract with type of stake,throw an error

PoolData.jsx:23 Error fetching pool addresses for prize pool with address: 0xC5445655BB57C645Cc9204c56b65A1c777543fdd: execution reverted. (maybe wrong Ethereum network or your IP is being rate-limited?)

Infura queried on window claim page where it's not needed

When on token claim window presented with static results, frontends queries Infura like crazy. Feel free to close it if not relevant.
URL: https://app.pooltogether.com/account?address=0x......&claim=1
Video:

Screen.Recording.2021-02-22.at.3.28.12.PM.mov

UI does not update after approving contract spending with zero token balance

I just found a (minor) issue with the PoolTogether UI, I am not quite sure if this here is the correct repo, but here is the issue:

Summary:

When visiting https://app.pooltogether.com/pools/PT-cDAI/deposit and approving DAI you can approve it and after the tx confirmed the UI tells you that it is still unapproved. That only seems to happen when you have 0 DAI in your wallet.

Steps to reproduce:

1. Go to https://app.pooltogether.com/pools/PT-cDAI/deposit
2. Enter 0 in the 'Ticket amount' field, click continue
3. Approve DAI via Metamask etc.
4. Now you see that 'Allow DAI' is still clickable, even though the connected wallet has already approved it. That only happens when you enter 0 DAI in the 'Ticket amount' field (Page reload is not helping)

I think users (Like I just did) want to approve DAI (or different tokens) while not actually holding any DAI/Token in the wallet (yet). This leads to confusion and probably double-approving without the UI telling you that it worked on the first time.

Total supply clarification needed

First time user, not sure what does Total supply mean ?. Is it what I'm max out to deposit or already deposited. Especially confusing considering zeros above. And would be good to have explanation why it's limited to 10000 ?

Error with "Deposit" - See JS Console for details

1. Create a new pool with ERC20 contract on Binance smart chain (Testnet).
2. Deposit ERC20
3. Error occurred, see also screenshot
   {
   "code": -32603,
   "message": "Internal JSON-RPC error.",
   "data": {
   "code": -32000,
   "message": "gas required exceeds allowance (30000000) or always failing transaction"
   }
   }

Error: "networkId" is required

After all steps, the app not builds, with an error "networkId" is required.

I guess it comes from @pooltogether/bnc-onboard package but could not find any solution...

Any idea how it can be solved?

Bug: WalletConnect desktop using Trustwallet mobile

Step to reproduce:

• Go to bsc pool for example: https://community.pooltogether.com/pools/bsc/0xbe4F9FaE681a82a350E2b717aE0d4f8012BCb8E5
• Click on "Connect Wallet"

- Select "WalletConnect"

• Scan QR code with Trustwallet and approve
  -After approve Wallet connect in Trustwallet it gives error:
  👋 Your wallet is currently set to
  Ethereum Mainnet
  . Please connect to
  Binance Smart Chain Mainnet
  to participate in this pool.
  ⚠️ You will need to use MetaMask to connect to this network.

Problem
Trustwallet doensn't allow to switch network like Metamask can.

Solution
We need to add network select network

Workaround:
-Add wallet in useWalletNetwork:

export const useWalletNetwork = () => {
  const {
    isWalletConnected: walletConnected,
    network: walletChainId,
    walletName,
    wallet
  } = useOnboard()

  const walletOnUnsupportedNetwork = walletConnected && !SUPPORTED_NETWORKS.includes(walletChainId)

  let walletNetworkData = {}
  try {
    walletNetworkData = getChain(walletChainId)
  } catch (error) {}

  return {
    walletChainId,
    walletOnUnsupportedNetwork,
    walletConnected,
    walletName,
    walletNetworkShortName: walletNetworkData?.name || 'unknown network',
    walletNetwork: {
      ...walletNetworkData
    },
    wallet
  }
}

-Add code in ChangeWalletNetworkNotificationBanner (it's not pretty, but works well):

if (walletName === 'WalletConnect') {
    wallet.provider.chainId = 56
    wallet.provider.networkId = 56
    wallet.provider.rpcUrl = 'https://bsc-dataseed.binance.org/'
    wallet.provider.rpc = {
      56: 'https://bsc-dataseed.binance.org/'
    }
    return <div></div>
  }

Error: A "infuraKey" or a "rpc" object with a parameter of 1 must be included in the WalletConnect initialization object

Unhandled Runtime Error
Error: A "infuraKey" or a "rpc" object with a parameter of 1 must be included in the WalletConnect initialization object

Call Stack
Module.walletConnect [as default]
node_modules/@pooltogether/bnc-onboard/dist/esm/wallet-connect-ee7f8113.js (28:0)
eval
node_modules/@pooltogether/bnc-onboard/dist/esm/onboard-84493676.js (8046:0)

Steps:
Install dependencies:

$ yarn

Make sure you have direnv installed and copy .envrc.example to .envrc:

$ cp .envrc.example .envrc

Fill in your own values for .envrc, then run:

$ direnv allow

To run the local server, run:

$ yarn dev