Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed mint too small amount case #1525

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fixed mint too small amount case #1525

wants to merge 1 commit into from

Conversation

levonpetrosyan93
Copy link
Contributor

No description provided.

Copy link

coderabbitai bot commented Feb 10, 2025

Walkthrough

The pull request updates the CreateSparkMintTransactions method in the CSparkWallet class. It adds error handling to ensure that transaction outputs meet the minimum required amount. Specifically, the method now checks if the output list is empty after adjusting for fees and ensures that fee deductions do not reduce any recipient's amount to zero or negative. If these conditions are not met, an appropriate error is set and the transaction creation is halted.

Changes

Files Change Summary
src/spark/sparkwallet.cpp Added error handling in CreateSparkMintTransactions: checks for empty output after fee adjustments and prevents transactions with too small amounts by setting an error and returning false.

Sequence Diagram(s)

sequenceDiagram
  participant Caller
  participant Wallet as CSparkWallet::CreateSparkMintTransactions

  Caller->>Wallet: Invoke CreateSparkMintTransactions(inputs)
  Wallet->>Wallet: Adjust recipient amounts and deduct fees
  Wallet->>Wallet: Verify if singleTxOutputs is empty?
  alt Valid outputs and amounts
      Wallet-->>Caller: Return true (transaction created)
  else Invalid: empty outputs or non-positive amounts
      Wallet->>Wallet: Set error message "transaction amount too small"
      Wallet-->>Caller: Return false (transaction aborted)
  end
Loading

Poem

I'm a rabbit in a magical code spree,
Hopping through checks with precision and glee.
Minting transactions with logic that's tight,
Ensuring each output is just right.
With a hop and a skip, my code sings a tune,
Error-free carrots bright under the code moon!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/spark/sparkwallet.cpp (1)

885-893: Consider adding validation for negative amounts.

While the code handles zero outputs well, it should also validate that output amounts don't become negative after fee subtraction. This could happen if singleFee is larger than the output amount.

 if (singleTxOutputs[i].v <= singleFee) {
     singleTxOutputs.erase(singleTxOutputs.begin() + i);
     reminder += singleTxOutputs[i].v - singleFee;
     if (!singleTxOutputs.size()) {
         strFailReason = _("Transaction amount too small");
         return false;
     }
     --i;
+} else if (singleTxOutputs[i].v - singleFee < 0) {
+    strFailReason = _("Fee exceeds transaction amount");
+    return false;
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a32ec20 and 0d56d7d.

📒 Files selected for processing (1)
  • src/spark/sparkwallet.cpp (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Create Source Distribution
  • GitHub Check: Create Source Distribution
🔇 Additional comments (1)
src/spark/sparkwallet.cpp (1)

888-891: LGTM! Good error handling for small transaction amounts.

The added check prevents creation of invalid transactions when all outputs become too small after fee deduction. The error message is clear and helpful for users.

Copy link

@gevorgvoskanyan gevorgvoskanyan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if (singleTxOutputs.empty()) would read better

@reubenyap reubenyap requested a review from psolstice February 10, 2025 10:06
@reubenyap
Copy link
Member

Credits to Petr Vacha @nrsimha for disclosing this bug to us which we have classified as a minor issue.

We will award a 100 FIRO bounty for finding and disclosing this bug to us as per our bug bounty program.

@nrsimha
Copy link

nrsimha commented Feb 14, 2025

Thank you. This is my address: sm1a00jwsqg8tkd6hk4nxr65dzyaeupt00h09dz8ntepkh0qcchpm8rm83t9jpfx5lljafmlmxj05usnqzmhqh4nh497gp6wtxqdy4w8g6zdfwgrqw4qscafzg0puh80adazgz057scpf7sp

@reubenyap
Copy link
Member

Thank you. This is my address: sm1a00jwsqg8tkd6hk4nxr65dzyaeupt00h09dz8ntepkh0qcchpm8rm83t9jpfx5lljafmlmxj05usnqzmhqh4nh497gp6wtxqdy4w8g6zdfwgrqw4qscafzg0puh80adazgz057scpf7sp

This has been paid. Please confirm. Not putting the TXID here for privacy.

@nrsimha
Copy link

nrsimha commented Feb 14, 2025

Thank you. This is my address: sm1a00jwsqg8tkd6hk4nxr65dzyaeupt00h09dz8ntepkh0qcchpm8rm83t9jpfx5lljafmlmxj05usnqzmhqh4nh497gp6wtxqdy4w8g6zdfwgrqw4qscafzg0puh80adazgz057scpf7sp

This has been paid. Please confirm. Not putting the TXID here for privacy.

Received it. Confirmed.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants