ANNOUNCEMENTS and DISCUSSING

[XMR] Monero - A secure, private, untraceable cryptocurrency
Bitcoin Forum
June 28, 2017, 03:56:20 PM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 [1777]
  Print  
Author Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency  (Read 3734384 times)
KizaruOG
Newbie
*
Offline Offline

Activity: 5


View Profile
Today at 09:42:05 AM
 #35521

Update on current and future achievements regarding XMR adoption.
https://www.reddit.com/r/Monero/comments/6juluf/any_new_updates_on_xmr_adoption/

Summarized it seems that the devs are making Monero now quite easier to adopt. Also - the work on mobile wallets is very unique and great.
If the cryptoworld actually has some logic(which I from time to time doubt) and any financial/economic culture Monero should be at top 3 coins.

Good news!
I'm very proud for the monero team! Good development and marketing.
1498665380
Hero Member
*
Offline Offline

Posts: 1498665380

View Profile Personal Message (Offline)

Ignore
1498665380
Reply with quote  #2

1498665380
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
birr
Hero Member
*****
Offline Offline

Activity: 611


View Profile
Today at 01:27:31 PM
 #35522

I'm pleased to hear that subaddresses are on the roadmap.  Sounds like it might be a little clumsy to use them, however:

One slight caveat with this scheme is that when restoring a wallet from the seed, the wallet might miss transfers to subaddresses if they aren't stored in the hashtable yet. To mitigate this issue, for each account, the wallet generates 100 (a constant SUBADDRESS_LOOKAHEAD_MINOR defined in wallet2.h) subaddresses of indices beyond the "fresh" index. The wallet also generates 10 (a constant SUBADDRESS_LOOKAHEAD_MAJOR defined in wallet2.h) accounts beyond the current largest major index. This means that the wallet restoration process is guaranteed to find incoming transfers to subaddresses as long as the major and minor indices of the used subaddresses differ by less than those predefined numbers. Even if the differences are bigger than those, you can still make the wallet recognize the incoming transfers by just expanding the hashtable manually and rescanning the blockchain.
(from https://github.com/monero-project/monero/pull/2056)

It sounds a little bit like the way Bitcoin handled change addresses many years ago, before the advent of HD address generation.  Have a table of pre-generated addresses, and make sure you don't run out of them.  It would be nice to have a more elegant solution for monero subadresses, one that eliminates inconvenience and complication.
Nathan047
Full Member
***
Online Online

Activity: 210


Yo ( ͡° ͜ʖ ͡°)


View Profile
Today at 02:29:12 PM
 #35523

Update on current and future achievements regarding XMR adoption.
https://www.reddit.com/r/Monero/comments/6juluf/any_new_updates_on_xmr_adoption/
Summarized it seems that the devs are making Monero now quite easier to adopt. Also - the work on mobile wallets is very unique and great.
If the cryptoworld actually has some logic(which I from time to time doubt) and any financial/economic culture Monero should be at top 3 coins.
This is great, thanks for the share! Also, I'm glad to hear XMR is being added to Coinomi. I already use it so now I'll have the ability to store my XMR on my phone instead of my usual exchanges and mymonero.com.

What has been will be again, what has been done will be done again; there is nothing new under the sun.
Hueristic
Legendary
*
Offline Offline

Activity: 1302


Doomed to see the future and unable to prevent it


View Profile
Today at 02:58:21 PM
 #35524

I'm pleased to hear that subaddresses are on the roadmap.  Sounds like it might be a little clumsy to use them, however:

One slight caveat with this scheme is that when restoring a wallet from the seed, the wallet might miss transfers to subaddresses if they aren't stored in the hashtable yet. To mitigate this issue, for each account, the wallet generates 100 (a constant SUBADDRESS_LOOKAHEAD_MINOR defined in wallet2.h) subaddresses of indices beyond the "fresh" index. The wallet also generates 10 (a constant SUBADDRESS_LOOKAHEAD_MAJOR defined in wallet2.h) accounts beyond the current largest major index. This means that the wallet restoration process is guaranteed to find incoming transfers to subaddresses as long as the major and minor indices of the used subaddresses differ by less than those predefined numbers. Even if the differences are bigger than those, you can still make the wallet recognize the incoming transfers by just expanding the hashtable manually and rescanning the blockchain.
(from https://github.com/monero-project/monero/pull/2056)

It sounds a little bit like the way Bitcoin handled change addresses many years ago, before the advent of HD address generation.  Have a table of pre-generated addresses, and make sure you don't run out of them.  It would be nice to have a more elegant solution for monero subadresses, one that eliminates inconvenience and complication.

Fucking site lost my goddamn post. no time now i'll retypr later.

BITSLER                 ▄███
               ▄████▀
             ▄████▀
           ▄████▀  ▄██▄
         ▄████▀    ▀████▄
       ▄████▀        ▀████▄
     ▄████▀            ▀████▄
   ▄████▀                ▀████▄
 ▄████▀ ▄████▄      ▄████▄ ▀████▄
█████   ██████      ██████   █████
 ▀████▄ ▀████▀      ▀████▀ ▄████▀
   ▀████▄                ▄████▀
     ▀████▄            ▄████▀
       ▀████▄        ▄████▀
         ▀████▄    ▄████▀
           ▀████▄▄████▀
             ▀██████▀
               ▀▀▀▀
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄            
▄▄▄▄▀▀▀▀    ▄▄█▄▄ ▀▀▄         
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄      
█  ▀▄▄  ▀█▀▀ ▄      ▀████   ▀▀▄   
█ █▄  ▀▄   ▀████       ▀▀ ▄██▄ ▀▀▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
█  ▀▀       ▀▄▄ ▀████      ▄▄▄▀▀▀  █
█            ▄ ▀▄    ▄▄▄▀▀▀   ▄▄  █
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
█ ▄▄   ███   ▀██  █           ▀▀  █ 
█ ███  ▀██       █        ▄▄      █ 
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀  
▀▄            █        ▀▀      █  
▀▀▄   ███▄  █   ▄▄          █   
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀    
▀▀▄   █   ▀▀▄▄▄▀▀▀         
▄▄▄▄▄▄▄▄▄▄▄█▄▄▀▀▀▀              
              ▄▄▄██████▄▄▄
          ▄▄████████████████▄▄
        ▄██████▀▀▀▀▀▀▀▀▀▀██████▄
▄     ▄█████▀             ▀█████▄
██▄▄ █████▀                ▀█████
 ████████            ▄██      █████
  ████████▄         ███▀       ████▄
  █████████▀▀     ▄███▀        █████
   █▀▀▀          █████         █████
     ▄▄▄         ████          █████
   █████          ▀▀           ████▀
    █████                     █████
     █████▄                 ▄█████
      ▀█████▄             ▄█████▀
        ▀██████▄▄▄▄▄▄▄▄▄▄██████▀
          ▀▀████████████████▀▀
              ▀▀▀██████▀▀▀
            ▄▄▄███████▄▄▄
         ▄█▀▀▀ ▄▄▄▄▄▄▄ ▀▀▀█▄
       █▀▀ ▄█████████████▄ ▀▀█
     █▀▀ ███████████████████ ▀▀█
    █▀ ███████████████████████ ▀█
   █▀ ███████████████▀▀ ███████ ▀█
 ▄█▀ ██████████████▀      ▀█████ ▀█▄
███ ███████████▀▀            ▀▀██ ███
███ ███████▀▀                     ███
███ ▀▀▀▀                          ███
▀██▄                             ▄██▀
  ▀█▄                            ▀▀
    █▄       █▄▄▄▄▄▄▄▄▄█
     █▄      ▀█████████▀
      ▀█▄      ▀▀▀▀▀▀▀
        ▀▀█▄▄  ▄▄▄
            ▀▀█████
[]
dEBRUYNE
Legendary
*
Offline Offline

Activity: 1078


View Profile
Today at 03:55:16 PM
 #35525

I'm pleased to hear that subaddresses are on the roadmap.  Sounds like it might be a little clumsy to use them, however:

One slight caveat with this scheme is that when restoring a wallet from the seed, the wallet might miss transfers to subaddresses if they aren't stored in the hashtable yet. To mitigate this issue, for each account, the wallet generates 100 (a constant SUBADDRESS_LOOKAHEAD_MINOR defined in wallet2.h) subaddresses of indices beyond the "fresh" index. The wallet also generates 10 (a constant SUBADDRESS_LOOKAHEAD_MAJOR defined in wallet2.h) accounts beyond the current largest major index. This means that the wallet restoration process is guaranteed to find incoming transfers to subaddresses as long as the major and minor indices of the used subaddresses differ by less than those predefined numbers. Even if the differences are bigger than those, you can still make the wallet recognize the incoming transfers by just expanding the hashtable manually and rescanning the blockchain.
(from https://github.com/monero-project/monero/pull/2056)

It sounds a little bit like the way Bitcoin handled change addresses many years ago, before the advent of HD address generation.  Have a table of pre-generated addresses, and make sure you don't run out of them.  It would be nice to have a more elegant solution for monero subadresses, one that eliminates inconvenience and complication.

If I recall correctly, the hashtable contains 10k subaddresses by default, which should be sufficient for the normal user.

Privacy matters, use Monero - A true untraceable cryptocurrency
Why Monero matters? http://weuse.cash/2016/03/05/bitcoiners-hedge-your-position/
Pages: « 1 ... 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 [1777]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!
WEBSITE