silkaj issueshttps://git.duniter.org/clients/python/silkaj/-/issues2023-08-16T21:12:04+02:00https://git.duniter.org/clients/python/silkaj/-/issues/478Implement authentication on money history command2023-08-16T21:12:04+02:00MoulImplement authentication on money history commandConvenient with account authentication.
- Can be done together with #350 refactoring
- [ ] Implement authentication on `money history` command
- [ ] Write tests
- [ ] Document usage also for `balance` commandConvenient with account authentication.
- Can be done together with #350 refactoring
- [ ] Implement authentication on `money history` command
- [ ] Write tests
- [ ] Document usage also for `balance` commandBackloghttps://git.duniter.org/clients/python/silkaj/-/issues/394Ability to select transaction history range2022-03-29T11:12:51+02:00Mr-DjezAbility to select transaction history rangeHello.
I would like to be able to select a specific range between a start date and an end date in the transaction history of an account.Hello.
I would like to be able to select a specific range between a start date and an end date in the transaction history of an account.Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/391Express relative amounts using previous or next UD2021-04-11T18:51:18+02:00MoulExpress relative amounts using previous or next UDOptions could allow to specify:
- [ ] #218: `history`:
- [ ] Using the UD value when the transaction was written
- [ ] Display relative amounts using a specified UD value (UD from Q2-Q3 2019)
- [ ] `balance`: Using next estimated UD,...Options could allow to specify:
- [ ] #218: `history`:
- [ ] Using the UD value when the transaction was written
- [ ] Display relative amounts using a specified UD value (UD from Q2-Q3 2019)
- [ ] `balance`: Using next estimated UD, to know how much our balance is reducing
- [ ] `tx`: allow to send using previous UD
The fist option for the `history` command is the most valuable and interesting usage. This one should be the first one to be implemented.Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/350Set the priority to the passed pubkey over the authentication method for `bal...2023-08-16T21:11:26+02:00MoulSet the priority to the passed pubkey over the authentication method for `balance` and `checksum` cmdsCommands allowing to pass a pubkey via the authentication and the usual CLI (`balance` and `checksum` for now) are prioritizing the authentication methods over the pubkey.
@matograine suggested to prioritize the pubkey over the authentic...Commands allowing to pass a pubkey via the authentication and the usual CLI (`balance` and `checksum` for now) are prioritizing the authentication methods over the pubkey.
@matograine suggested to prioritize the pubkey over the authentication method or return an error.
That could be an issue when `silkaj -af` is set as a shell alias, where the authentication would always be set on every command, then the user would forget about it, and get the result for public key from the authentication file.Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/218Transaction history table improvements2022-03-16T09:21:19+01:00MoulTransaction history table improvements### First
- [ ] Write unit tests
- [ ] #203
---
### Then
##### Around
- [ ] Use the authentication methods, to get the pubkey we want to get the history of
- [ ] Allow to check transactions from several pubkeys: merge transactions
- [ ]...### First
- [ ] Write unit tests
- [ ] #203
---
### Then
##### Around
- [ ] Use the authentication methods, to get the pubkey we want to get the history of
- [ ] Allow to check transactions from several pubkeys: merge transactions
- [ ] Add options to display the resulting table output in a “`less`” (pager) or directly to `stdout`
- [ ] Paint green incoming txs and red outgoing txs
- [ ] Option to display or to hide the header for faster result (not sure how this will speed up the cmd)
- [ ] Allow to sort rows according to a column as for `net` cmd
- [ ] Add [progression bar](https://click.palletsprojects.com/en/7.x/utils/#showing-progress-bars) when `--uids` option is passed (will become useless with GVA) The progress bar might still be necessary to process the data.
##### Content management
- [x] !160: Add `--full-pubkey` option to display the whole pubkeys
- [ ] Separate columns for the `uids` and for the `pubkeys`
- [ ] #394: Allow to display txs between two dates rather than the whole txs list
- [ ] Always display pending txs (and an estimation date when it’s sure they will enter the blockchain)
- [ ] Option to display one of the UTXO, pending or both
- [ ] Options to display only one of absolute or relative amounts, or both
- [ ] Option to display created UD `--ud`, consummed
- [ ] #391: Display relative amounts using the UD value from a chosed moment or at the time of the tx.
- [ ] Add filter options (remove transaction based on comment matching or issuer)
- [ ] [Handle multi-issuer tx display](https://forum.monnaie-libre.fr/t/comptes-en-negatif/15117/5)
- [ ] Option to display only sent or only received txs
- [ ] Add an option to display inputs and outputs
- [ ] TBR: `--uids` request once duplicate between sent and received, would no longer make sense with GVA
##### Content handling
- [ ] Handle other outputs’ conditions (XHX, CSV, CLTV)Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/211Add safegards if UnitBase or UD value change2023-07-23T13:53:25+02:00MoulAdd safegards if UnitBase or UD value changeIf a node lies about current amount base or UD value, based on that the sent amount in a transfer would be wrong.
This value can be double-checked on two nodes, or checked into a range of value.
It should be done at least on Ğ1 currenc...If a node lies about current amount base or UD value, based on that the sent amount in a transfer would be wrong.
This value can be double-checked on two nodes, or checked into a range of value.
It should be done at least on Ğ1 currency:
- [ ] `10.07 ≤ UDValue < 10.5/11`: should be safe for one year at least
- [ ] `1 == base`: should be safe for many years
---
- [ ] Display everywhere where the amount is used in UD, mostly commands in the `money` group, display the conversion rate (DU = 10.XX Ğ1).Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/209Improve balance command performance when multiple pubkeys are specified2023-05-31T12:47:46+02:00MoulImprove balance command performance when multiple pubkeys are specifiedMake it go faster.
Once #161 will be solved, try to request every pubkeys tx sources and history at the same time.Make it go faster.
Once #161 will be solved, try to request every pubkeys tx sources and history at the same time.Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/205Handle base changement2021-04-07T16:17:53+02:00MoulHandle base changement- https://forum.duniter.org/t/bug-daffichage-des-montants/5966/2?u=moul
- https://forum.duniter.org/t/changement-de-base/5967- https://forum.duniter.org/t/bug-daffichage-des-montants/5966/2?u=moul
- https://forum.duniter.org/t/changement-de-base/5967Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/193Amounts management: cent, unit, and relative formats2021-07-22T23:01:46+02:00MoulAmounts management: cent, unit, and relative formats> Follows #131.
### Context
In the Ğ1 currency, the sources amounts are stored as integers for storage simplicity in nodes’ databases and in order to be able to re-evaluate the UD value.
### Problem
In the end, we are dealing with amou...> Follows #131.
### Context
In the Ğ1 currency, the sources amounts are stored as integers for storage simplicity in nodes’ databases and in order to be able to re-evaluate the UD value.
### Problem
In the end, we are dealing with amounts in cents in the backend and in units in the frontend.
We are constantly dealing with divisions or multiplication by 100 or UDValue (which is in cent format) between the front and the back. Currently, this management is spread all around the code for the money management.
### Solution
The solution would be to have a helper in DuniterPy to take care of this issue.
We would need something in which we can:
- enter a value from the front specifying unit or UD: ie: specifying a tx amount from the CLI
- enter a value from the back: ie: source fetched from a node
- output the value in the three formats: cents, unit, relative: ie: for the frontend display
The best suitable structure for this problem is a class with methods:
- Use methods to specify what type of value is entered to be stored
- The value would be stored in cents
- Its access in unit or relative formats would divide it by `100` or by `UDValue`: `amount`, `amount.unit`, `amount.relative`.
- This class should also take care of [the float multiplication/division issue](https://git.duniter.org/clients/python/silkaj/issues/233#note_16217).
### Extra
- The [`dataclass` format](https://linuxfr.org/news/sortie-de-python-3-7#toc-pep557-dataclasses) would be perfect for this case but it would requires that the minimum supported Python version is 3.7.
- Can or do we want to find a common rule to also include ĞTest and other currencies?Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/139Add command allowing to converts between relative (UD) and quantitative amounts2022-10-27T16:23:15+02:00MoulAdd command allowing to converts between relative (UD) and quantitative amountsWith current UD value and even with older UD values.With current UD value and even with older UD values.Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/110Display blocks contents2022-03-16T09:32:12+01:00MoulDisplay blocks contentsIn `blocks` command: display number of tx, ud, wot in news rows with [`blockchain/with`](https://git.duniter.org/nodes/typescript/duniter/blob/dev/doc/HTTP_API.md#blockchainwith).
Like in [Cesium blockchain view](https://g1.duniter.fr/#...In `blocks` command: display number of tx, ud, wot in news rows with [`blockchain/with`](https://git.duniter.org/nodes/typescript/duniter/blob/dev/doc/HTTP_API.md#blockchainwith).
Like in [Cesium blockchain view](https://g1.duniter.fr/#/app/blockchain/search).Backloghttps://git.duniter.org/clients/python/silkaj/-/issues/48info: Display more information2023-06-01T15:45:27+02:00Moulinfo: Display more informationDisplay following information in a chart:
## Info
### Display
- [x] Display information into a table with `tabulate`.
- [ ] Migrate to `texttable` usage
### Money
#### UD
- [x] current UD value
- [x] Next date of UD re-evaluation
- [x]...Display following information in a chart:
## Info
### Display
- [x] Display information into a table with `tabulate`.
- [ ] Migrate to `texttable` usage
### Money
#### UD
- [x] current UD value
- [x] Next date of UD re-evaluation
- [x] Next UD value
- [x] When will next UD will be reevaluated and to which value? `params["udReevalTime0"]` and `params["dtReeval"]` could help.
---
- [x] Monetary mass amount
- [x] Current money decimal base
- [ ] ~~date of next base reevaluation~~ ([seems too far and hard to calculate with M and N variables](https://git.duniter.org/nodes/common/doc/blob/master/rfc/0009_Duniter_Blockchain_Protocol_V11.md#br_g14-headdividend-and-headunitbase-and-headnew_dividend))
### WoT
- https://forum.duniter.org/t/renouvellement-des-certifications-1-6-28-1-7-x/4757/180?u=moul
### Parameters
- Explain [other parameters in `params`](https://git.duniter.org/nodes/common/doc/blob/master/rfc/0009_Duniter_Blockchain_Protocol_V11.md#protocol-parameters)
### Other
- information which are available in Sakia, Cesium, and Duniter admin interfaces
- retrieve values as in https://g1.duniter.fr/#/app/currency/lgBacklogMoulMoul