Quote from: visdude on November 25, 2017, 08:47:52 PM

Quote from: sumogr on November 25, 2017, 08:36:59 PM

Quote from: visdude on November 25, 2017, 07:38:00 PM

Quote from: sumoshi on November 20, 2017, 07:19:15 AM

Subaddresses (Part 1) merged

FYI, the first stable part of "subaddresses" code has been merged to master branch at Github. This is mainly for early user experiments and GUI wallet design.

Please refer to PR #28 for usage: https://github.com/sumoprojects/sumokoin/pull/28

As current wallet version doesn't recognize subaddresses as valid ones, please DO NOT use subaddresses for:

Withdrawal from exchanges
Mining receipt addresses
Sending funds to them from old (cli/GUI) wallets

Subaddresses (Part 2):

- Support sending to multiple subaddresses or mix of sub/primary addresses
- Improve scanning speed and stability

Expected release date: By Nov 30, 2017

After full-featured subaddresses code is completely merged, binaries will be officially bumped to version v.0.2 (code name: Sapporo)

GUI wallet with subaddresses:

Design target: Simplifying user experience with pre/auto subaddresses generation. User can freely pick any unused subaddress for receiving fund without revealing true main address.

Expected release date: In December 2017

Is "subaddress" a really high-priority implementation than a cold wallet/offline signing feature at this point in time? I mean, the forked version of Monero is already very secure, private and anonymous whereas users' wallet keys remain vulnerable to attacks while residing on online machines. The former is icing on the cake while the latter is a necessity.

Hi. Actually subaddresses besides the extra privacy/anonymity that they obviously offer they do "commercialize" the coin a lot, exchanges can issue seperate addresses for each user than using a common one for everyone and separate each by a unique id (which is quite confusing for users that had no previous experience with cryptonotes) same goes for online markets that can issue a unique deposit address for each of their customers.
Although I quite agree with the fact that the feature you are proposing is indeed a factor of a totaly secure coin (of course it doesnt affect anonymity & privacy) to take on the role of the devil's advocate I might ask why is this coin's or any coin's obligation to secure your online machine from incoming attacks aiming to steal your keys, this is mainly the user's responsibility.

Actually, my post wasn't meant for you to reply to. I prefer a very knowledgeable person like a dev to answer me.

With your attitude? You should be feeling glad that I cared to reply to you let alone a dev....