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.
### What was wrong?
When methods are marked with `payable=False` in the ABI, a transaction sending ether to them will (or should) fail. Web3 isn't doing anything to intercept these calls, leaving callers to debug the failing transaction.
### How can it be fixed?
When running a call, transact, estimateGas, or buildTransaction, inspect the transaction's `value` field. If it is present, and non-0, check the function ABI. If payable is present and `False`, raise a validation error explaining that the user must not send ether to functions that are not payable.
Alternative approach: when searching for matching functions in the ABI, filter out options that are not payable if the transaction has non-0 value. Not sure that this really buys anything besides fitting into a framework we already have.