[Test] Comments in the Blockchain & Dust Payments ~> 0.9.3.2 Tests
-
Proposed Help Test for Feathercoin-Qt feature "Comments in the Blockchain:
For use in : https://github.com/wrapperband/FeathercoinWalletGuide
and to improve Wallet on screen Help / Text.Feathercoin Wallet Advanced Feature – Include comments in the Blockchain
Comments can be included in the Feathercoin Blockchain. Click on “Advanced” in the Wallet menu and select “Comments” in the drop down menu.
Comments of up to 40 characters can be included in the Feathercoin Blockchain. The cost of a comment has been set at 10 times the dust, or minimum block transmission value, currently that is .
Once you have made a comment you can find it in the Feathercoin Blockchain. Fist find the transaction with the comment, the copy the contents of OP_RETURN.
You then use Hex to Ascii on OP_RETURN to return your message.
Notes :
I am just doing some help for including comments into the Feathercoin (FTC) Blockchain
A couple of points came up testing 0.9.3.2.
Feathercoin Wallet use the opennames DNS service in the blockchain
Comments on Comments Tests
-
Look and feel, should be cancel box not Exit.
-
Lack of on screen help and instructions
-
Why did I put 35 Characters in first on screen Text? should be 40?
-
What is the cost?
The cost of Comments is not shown any where or how it is calculated. It appears to be caculated on 10 * Dust -
- Shouldn’t the cost be it be 10 * Min Payment?
- Why is (FTC 0.9.3.2) Dust (DUST_HARD_LIMIT) set at 100000?
?Notes: Q 4. How much does comments cost? from Source Code? :
The cost is from UtilityDialog.cpp
rcptmp.amount=DUST_HARD_LIMIT*10;
From main.h
src/main.h
Showing the top match. Last indexed 7 days ago.
/** Dust Hard Limit, ignored as wallet inputs (mininput default) /
static const int64_t DUST_HARD_LIMIT = 1000000;
/* Coinbase transaction outputs can only be spent after this number of new blocks (network rule) */?Notes Q 6. How are dust levels min payments set ?
Dust set in main.h
/** Dust Soft Limit, allowed with additional fee per output /
static const int64 DUST_SOFT_LIMIT = 100000; // 0.001 FTC
/* Dust Hard Limit, ignored as wallet inputs (mininput default) */
static const int64 DUST_HARD_LIMIT = 1000; // 0.00001 FTC mininput>>> From Dogecoin Notes
Yes, I wondered the same. I think the difference is that the DUST_HARD_LIMIT is enforced with the other coins and such small transactions won’t even be relayed by the reference clients. DOGE did remove the dust enforcment and instead the fee has been set higher.
Not sure if lowering that is really of use because sending these inputs potentially costs more than it’s worth, right?
I myself have yet to receive such a small transaction. I’ll close this as it’s solved for now :) -
-
Generally what I’m missing or what I didn’t find, is the possibility to read these comments in the transaction view or somewhere else inside the wallet.
-
@Wellenreiter said:
Generally what I’m missing or what I didn’t find, is the possibility to read these comments in the transaction view or somewhere else inside the wallet.
I’ve got some of Aciddudes tests /comments to include in the help. He found how you can read it from the Block explorer :
http://forum.feathercoin.com/topic/8570/dev-release-candidate-feathercoin-0-9-3-2-check-list/16
I agree, there is a Sx search tool in Help : which need moving to a sub section and cloned to search / find comments? (as a quick improvement).
Minimum is to include help on screen - there is a unused ??? button.
-
@Lizhi @Wellenreiter @Ghostlander
Note : Settings like the dust payment, are the sort of thing that need to be on the Feathercoin release checklist.
If we brainstorm things you can think of, to add to the checklist, I will document them and add them to FTC release / final checklist / overview.
PM me any (rough) ideas and I’ll add them to the list.
We can de- prioritise them after we do a more comprehensive sweep of 0.9.3.X series finalized and produce a “Quick checklist” for intermediate releases.
Notes: Include in Check list of FTC special settings :
Dust Settings
Minimum Payment -
Obvious,but …
Interoperation/compability with/to existing releases, that are still used in the prodnet