dangerousfreedom - wallet development 2

What and Why ?

Transaction history component with knowledge proofs

The idea is to collect transaction records (both for legacy and seraphis) authored by the wallet in order to provide the user the information he wants to look back. This component should import or update authored txs by looking at their enote's key-image and spent status.

The plan is to go in the direction of building a component to handle transactions by integrating the following non-comprehensive list of equivalent wallet2 methods into a component: get_transfers, get_payments, get_payments_out, get_unconfirmed_payments_out, get_unconfirmed_payments, export_outputs, import_outputs, import_outputs_from_str, export_payments, import_payments, import_payments_out, get_num_transfer_details, transfer_details, get_tx_proof, check_tx_proof, get_spend_proof, check_spend_proof, get_reserve_proof, check_reserve_proof.

An initial discussion about this topic can be found here.

Since some of these functions are not purely wallet functions as they depend on a daemon, I expect to help and get help to properly interface them with a proto daemon.

All the efforts will be documented and unit_tests will be provided whenever possible.

Who?

• I did this and this previous works and I believe I'm sharpening my skills and understanding of Jamtis and Seraphis to accomplish this work as described.

I propose to work for 30 USD per hour, 20h per week, for 8 weeks (2 months). Which makes 31 XMR considering 155 USD/XMR.

df-wallet-development-2.md

@@ -3,10 +3,10 @@ layout: fr
 title: dangerousfreedom - wallet development 2 
 author: DangerousFreedom
 date: February 26, 2022
-amount: 150 
+amount: 31 
 milestones:
   - name: deliver of proposed wallet functions
-    funds: 150
+    funds: 31
     done:
     status: unfinished
 payouts:
@@ -16,24 +16,20 @@ payouts:
 
 ## What and Why ?
 
-Following the [discussions](https://matrix.to/#/!YTcgTfFJREAkktLyKC:libera.chat/$FNuKwy92PO0_NtUllBNjgMlT8xBddd5ivav-WQKMhSE?via=libera.chat&via=matrix.org&via=monero.social) on February 7, at the #no-wallet-left-behind group, I believe I can contribute by implementing the following wallet features: 
+Transaction history component with knowledge proofs
 
-- Transaction history component:
-The idea is to collect transaction records (both for legacy and seraphis) authored by the wallet master key in order to provide the user the information he wants to look back. This component should import or update authored txs by looking at their key-image and spent status. I will initially do the following tasks:
-    - Collect all txs that master key has authored using view_balance key
-    - Filter and update transactions by its enotes statuses (OFFCHAIN, UNCONFIRMED, ONCHAIN / SPENT_OFFCHAIN,SPENT_UNCONFIRMED, SPENT_ONCHAIN) 
-    - Return information requested by user.
+The idea is to collect transaction records (both for legacy and seraphis) authored by the wallet in order to provide the user the information he wants to look back. This component should import or update authored txs by looking at their enote's key-image and spent status. 
 
-- Knowledge proofs integrated into wallet:
-The idea is to use the transaction history component (and also an enote scanner for the proofs that require knowledge of the unspent enotes) to create the knowledge proofs that the user wants, both for legacy and seraphis. 
+The plan is to go in the direction of building a component to handle transactions by integrating the following non-comprehensive list of equivalent wallet2 methods into a component: get_transfers, get_payments, get_payments_out, get_unconfirmed_payments_out, get_unconfirmed_payments, export_outputs, import_outputs, import_outputs_from_str, export_payments, import_payments, import_payments_out, get_num_transfer_details, transfer_details, get_tx_proof, check_tx_proof, get_spend_proof, check_spend_proof, get_reserve_proof, check_reserve_proof.
 
-- Some specific functions:
-I would like to keep an eye and discuss about the loading/storing functions of the wallet, the shape that the initial functions will take considering a multi-threaded scheme, the password-hashing algorithm, etc. Following the bottom-up approach, I believe I could contribute to some functions here too.
+An initial discussion about this topic can be found [here](https://github.com/seraphis-migration/wallet3/issues/49).
 
+Since some of these functions are not purely wallet functions as they depend on a daemon, I expect to help and get help to properly interface them with a proto daemon.
 
-## Who?
+All the efforts will be documented and unit_tests will be provided whenever possible.
 
-- I did [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/298) and [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/344) previous works and I believe I'm sharpening my skills and understanding of Jamtis and Seraphis (and its coding style) to provide a better and better quality work. 
+## Who?
 
+- I did [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/298) and [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/344) previous works and I believe I'm sharpening my skills and understanding of Jamtis and Seraphis to accomplish this work as described. 
 
-I propose to work for 48 EUR per hour, 25h per week, for 18 weeks (4 months). Which makes 150 XMR considering 144 EUR/XMR.
+I propose to work for 30 USD per hour, 20h per week, for 8 weeks (2 months). Which makes 31 XMR considering 155 USD/XMR.