While testing cool new Ethereum dapps with minimal funds, we realised, we don't actually remember where we used them and where we might still have some funds associated with our addresses.

WIMM use cases

For liquid tokens (immediately spendable) -ERC20 contracts (classic use case) -Decentralized exchanges (deposited) -Funding market maker (e.g. uniswap)

For illiquid/locked tokens

  • Token locking for community tokens (e.g. GNO to obtain OWL)
  • Bounty networks
  • Auction processes (ENS / DutchX)
  • Escrow services
  • DEFI (decentralized lending, decentralized debt positions)
  • Pre-scheduled / committed funds
  • State channels
  • Vested employee token plans
  • DAO experiments (locking tokens for voting powers) -Funding Prediction Market marketmaker

WIMM features

  • For ERC20 tokens
  • View by various address (EOA, smart contract address, ENS name) (for any user)
  • Add new snippets (Dapps) (for technical user)
  • Upvote / downvote snippets (Dapps)
  • Claim liquid tokens (e.g. releases of token locks etc.)
  • View pages of illiquid tokens

WIMM value proposition

  • Permissionless
  • Community to be active which derives scalable (not dependent on centralized entity adding/whitelisting/accepting individual smart contracts)
  • Release storage by users claiming amounts
  • Missing piece of infrastructure
  • WIMM to improve usability and help adoption
  • Paying attention to smaller amounts!
  • Problem magnifies with upgradable smart contracts and updates to graphical user interfaces (tracks balances of "outdated" contracts)

What's next? // add features

  • Notifications when amounts become newly claimable (change from illiquid to liquid)
  • Adding further token standards
  • Feature to approve tokens to smart contract addresses and remove approval (important due to possible malicious smart contract upgrades)
  • Adding Etherscan links to contracts
  • Evolve into a smart contract standard via ERC
  • Integration into wallets

Built With

+ 5 more
Share this project: