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

Add optional fee_per_gram field to console wallet Send Tx form #2419

Merged

Conversation

philipr-za
Copy link
Contributor

Description

This PR adds an optional editable fee_per_gram field to the send transaction form in the console wallet.

This field is populated by the default value specified by a constant in LibWallet and is not included in the flow of fields edited while sending a transaction as editing this field should be very rare. If the user wants to edit the field they can use the hotkey and after this transaction is sent the field will be repopulated with the default value again.

How Has This Been Tested?

This functionality was not able to be tested as the network is currently experiencing some issues that make sending transactions difficult.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Feature refactor (No new feature or functional changes, but performance or technical debt improvements)
  • New Tests
  • Documentation

Checklist:

  • I'm merging against the development branch.
  • I ran cargo-fmt --all before pushing.
  • I ran cargo test successfully before submitting my PR.
  • I have squashed my commits into a single commit.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.

@philipr-za
Copy link
Contributor Author

Added a quick update to not quit on a plain 'q' but to quit on ctrl+q and ctrl+c

Copy link
Contributor

@delta1 delta1 left a comment

Choose a reason for hiding this comment

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

clippy fail is from #2413

Copy link
Contributor

@delta1 delta1 left a comment

Choose a reason for hiding this comment

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

just needs a clippy fix then happy to approve

This PR adds an optional editable fee_per_gram field to the send transaction form in the console wallet.

This field is populated by the default value specified by a constant in LibWallet and is not included in the flow of fields edited while sending a transaction as editing this field should be very rare. If the user wants to edit the field they can use the hotkey and after this transaction is sent the field will be repopulated with the default value again.

This functionality was not able to be tested as the network is currently experiencing some issues that make sending transactions difficult.
@philipr-za
Copy link
Contributor Author

Fixed, though issue came from development. Thou shalt appease clippy!

@delta1
Copy link
Contributor

delta1 commented Nov 5, 2020

yeah I blame @mikethetike 😆

Copy link
Contributor

@delta1 delta1 left a comment

Choose a reason for hiding this comment

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

LGTM

use tari_crypto::common::Blake256;

/// The default fee per gram that the wallet will use to build transactions.
/// TODO discuss what the default fee value should actually be
pub const DEFAULT_FEE_PER_GRAM: MicroTari = MicroTari(25);
Copy link
Contributor

Choose a reason for hiding this comment

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

Minimum fee in mobile wallet is set to 100.

Not sure if these should be in sync?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is fee_per_gram not absolute fee. This is also an arb selection and needs to be discussed as stated in the TODO

@stringhandler stringhandler merged commit 820b358 into tari-project:development Nov 9, 2020
stringhandler added a commit that referenced this pull request Nov 24, 2020
Major changes since v0.6.0
---
- [#2431](#2431) Database refactor to remove checkpoints and more efficient calculation of MMR roots
- [#2352](#2352) Add DNS seed support in base node

Minor changes since v0.6.0
---
- [#2448](#2448) Add OpenSSL to Windows install, runtime
- [#2434](#2434) Add supervisord setup notes
- [#2439](#2439) Provide initial sync status to merge mining proxy
- [#2377](#2377) Message malleability detect and ban
- [#2447](#2447) Fix for xmrig powershell script
- [#2440](#2440) Stagenet Setup Guide Corrections
- [#2444](#2444) DHT connectivity waits for comms connectivity before starting
- [#2427](#2427) Update merge mining runtime, README, Win install
- [#2420](#2420) Show base node chain tip and sync status in the console wallet
- [#2419](#2419) Add optional fee_per_gram field to console wallet Send Tx form
- [#2421](#2421) Fix QR code rendering in the console wallet
- [#2423](#2423) Plumb in the balance in the console wallet
- [#2415](#2415) Prevent loop in peer sync by storing all peers attempted
- [#2383](#2383) Implement daemon-mode in tari_base_node
- [#2407](#2407) Simplify automated stress test
- [#2397](#2397) Fix preset config files
- [#2400](#2400) Implement wallet base node service
- [#2403](#2403) Add exclusive file locks to Wallet, Chain and Peer db’s
- [#2408](#2408) Fix wallet conversion error for a valid tx status
- [#2356](#2356) Combine validation code to use same function in pruned and archive mode.
- [#2371](#2371) Add configurable BN service request timeouts
- [#2430](#2430) Implement entry and persistence of custom base node in console wallet
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.

None yet

4 participants