Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Heyo Gitcoiners! With an entire city of hackers, coders and blockchain innovators relocated on our platform, the atmosphere is just buzzing with crea…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
Currently Status only supports a limited fixed list which is manually maintained by core contributors.
If a user own some tokens which are not on that list, they would not appear in any of the Wallet screens.
The issue is particularly irritating when the user buys unsupported tokens on one of the exchange dapps listed in Status but then never sees them appear under assets.
Screen designs in figma - https://www.figma.com/file/XUehMnhyD1FGcWzvGz6SXqvh/Wallet_Source-of-Truth?node-id=160%3A3954
* new screens for custom token entry by address and token details (see designs)
* new database operations to store, retrieve and delete custom tokens. Store address and all values retrieved from the contract (name, symbol, decimals).
* addition of custom tokens loaded from database to all-tokens in app-db upon login
* check if the address corresponds to an ERC-20 token contract
* check if the address is already in the token list (either built in or another custom token)
* check that contract defines name, symbol and decimals fields
* check that name or symbol of the added token isn't a duplicate of another token (either built in or custom)
* use the same logo icon for all custom tokens, the default (i.e. unset) icon is ok
## Acceptance Criteria
* User can add new tokens by address (subject to some constraints).
* After the addition, user can see the current balance of new tokens (if any) and send/receive them in wallet and chat.
* Transactions involving user added tokens should appear in Transaction history, in the same way as transactions involving tokens from the default list
parent issue - #6939