You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 30, 2024. It is now read-only.
Any reason for not being multitoken?
If I have a bounty contract and I want to send some valuable, rare and fun tokens to be rewarded, such as SNT, ETH, GNT, BEER, Unicorns and DAO.
The text was updated successfully, but these errors were encountered:
This can lead to unknown behavior of external token calls. If unknown tokens are called, they might throw or return unexpected values. An idea would be to create an array of accepted tokens, or turn design into that this would never be an issue (no one would care about an unknown buggy "token", so it will be ignored into the blockchain.
A whitelist of tokens is probably the right answer... The more i think about this, the more I like the idea of ripping the payment struct and the whitelist out of this contract and into an external contract
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Any reason for not being multitoken?
If I have a bounty contract and I want to send some valuable, rare and fun tokens to be rewarded, such as SNT, ETH, GNT, BEER, Unicorns and DAO.
The text was updated successfully, but these errors were encountered: