Nethereum / Nethereum/Nethereum
Validate if a Function is payable when sending a transaction
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.3k
- Forks
- 744
- PR merge metrics
- No merged PRs in 30d
Description
This should be applicable to ContractMessages only for backwards compatibility.
The Function attribute will be decorated with payable.
If the amount is set at the time of creating a transaction input and/or sending/signing the transaction an exception will be thrown to either change the attribute or usage of an invalid function.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing ContractMessages through transaction input creation and sending/signing, then inspect how the Function attribute is decorated with payable. Done means an amount supplied for a non-payable function raises an exception, while payable functions continue to work and backwards compatibility is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100