May 24, 2024
55.38 XMR
0 contributors
This project has been stagnant since December 28th, 2023. In taking over, I have updated the original proposal to include essential features for the current Monero ecosystem, such as:
Adding UR (Unified Resource) support Integrating with polyseed Interfacing with the Monero GUI I have already made progress on some of these components, visible in my GitHub repositories, listed at the end of the proposal.
I propose to take over and finish the Monero Signer project, which was funded but never really started. After learning about Monero Signer and researching the existing work, I found it to be a stale project that was never truly initiated. I aim to complete the project by delivering what was originally promised, with some modifications to make it more useful and avoid wasting time on potentially unnecessary features.
I will complete all the work myself, as I prefer to move quickly, keep things streamlined, and discard unnecessary elements. Security and usability are my top priorities, followed by features and fancy extras. This approach leads to more secure and maintainable code, better user experience, and reduced documentation needs.
Reasoning why this is proposal is without password encryption for monero seeds:
On using monero-python there is no password protection implemented and after investigating a little bit,
the reason behind is probably, that the encryption/decryption is not really mad in a "standard" way.
So to be compatible with Monero-CLI and Monero-GUI the encryption must be implemented in CryptoNight and
another propiatary way to add and substract the mask of the CryptoNight password hash.
This will be a rabbit hole I can estimate.
Why not another encryption instead? I dislike to have various standards until nobody knows anymore what and where to use.
A temporary password encryption would in my opinion also only make the things worse on reaching compatibility with the
original implementation. Because now, what to do, support two different standards? Remove the way, people protected the
password of there seeds before?
If there is interest, and somehow funding for it I will implement it later in the monero-python fork (the original was archived) for MoneroSigner. But until then password encryption for seed will only supported for Polyseed.
Send for view key only wallet, to make the workflow natural as possiblegit clone, make, make install, and troubleshootingI want to express that I will try to minimize the need for documentation by making the process easier to build and use. Nobody wants to read a book to get something done.
There is no need for that, I was not aware of Blockchain Commons’ Uniform Resources (URs), but that is the way to go. Sending and receiving data will be implemented using URs.
The given timeline reflects the upper bounds, but I target myself:
I kindly request that the payouts be made promptly upon completion of each milestone to allow me to concentrate fully on delivering Monero Signer successfully.
An expiration date for the proposal is set for 70 days from now, August 3, 2024.
I kindly request that the payouts be made promptly upon completion of each milestone to allow me to concentrate fully on delivering Monero Signer successfully.
An expiration date for the proposal is set for 70 days from now, August 3, 2024.# Monero Signer Resurrection: Reviving and Enhancing the Monero Signing Project
Progress can be watched at: MoneroSigner Emulator polyseed python monero python Todo, where is no work at the moment, but tracked about password encryption
(will add with time other repositories, as soon there is code to see)
View community discussion, comments, and proposal updates on GitLab
To be paid: 5.38 XMR
Completion date: 19 June 2024
To be paid: 5 XMR
Completion date: 28 July 2024
To be paid: 35 XMR
Completion date: 12 August 2024
To be paid: 10 XMR
Completion date: 27 September 2024
Funds Awarded: 5.38
Date: 20 June 2024
Funds Awarded: 5
Date: 29 July 2024
Funds Awarded: 35
Date: 13 August 2024
Funds Awarded: 10
Date: 28 September 2024