GingerAle
Legendary
Offline
Activity: 1260
Merit: 1008
|
|
August 20, 2015, 06:11:44 PM |
|
huh, i just tried logging in with that seed and got
4AYrGeied2XEbaL3uk3gBK1z95DQrcVwncMr5kXPUd7T4UcUpNefenD8HSZ7d9XWSXhmELmfCkvRQGT hzNeCUkaJKDd9nTV
which does match the one you posted (after you correct bitcointalks annoying hey-lets-break-XMR-addresses):
4AYrGeied2XEbaL3uk3gBK1z95DQrcVwncMr5kXPUd7T4UcUpNefenD8HSZ7d9XWSXhmELmfCkvRQGT hzNeCUkaJKDd9nTV
and I get the same spend key:
8c81ca3b40ae5c199ee10819b9c29959dcc4e97242d93cc6119938ea3858c303
and view key:
0ce617dbd51845dd6ada2f3b2d040b5deb6dde38f6640f65abc2a36518045802
|
|
|
|
luigi1111
Legendary
Offline
Activity: 1105
Merit: 1000
|
|
August 20, 2015, 06:31:26 PM |
|
Hey Monero-ites... I have a question RE: MyMonero vs. the offline-wallet generator software.
I made an offline address and then tried to "open" it with the given mnemonic seed words in MyMonero, i.e. I was kinda just testing how all this might work IF some day I wanted to make a safe address, to put some monero on it, and then later (eventually) access it again to move/spend the money.
But the ADDRESSES that resulted were NOT the same!
Is that correct? How is this supposed to work, exactly?
For sake of illustration since I'm not gonna USE these addresses now, here is what I got:
Offline Generated Address: 4AYrGeied2XEbaL3uk3gBK1z95DQrcVwncMr5kXPUd7T4RoHhjxyryRWU7qvsp2wJ6L4g1eFaqM6YbD 6RX52j4KQ8PfuBk8
MyMonero Address: 4AYrGeied2XEbaL3uk3gBK1z95DQrcVwncMr5kXPUd7T4UcUpNefenD8HSZ7d9XWSXhmELmfCkvRQGT hzNeCUkaJKDd9nTV
MyMonero View Key (Private) 0ce617dbd51845dd6ada2f3b2d040b5deb6dde38f6640f65abc2a36518045802
MyMonero Spend Key (Private) 8c81ca3b40ae5c199ee10819b9c29959dcc4e97242d93cc6119938ea3858c303
Mnemonic Seed Was: gigantic motherly lordship worry pool karate lopped certain major demonstrate pepper colony jobs people befit merger lending envy lectures sifting puzzled nanny lodge paper certain
So...? IF I had sent money to that first address WOULD IT have BEEN there at this "second" address? I suppose I could just test it with a few cents worth, LOL, but seriously this doesn't seem RIGHT.
An address is an address and for normal humans to EVER be able to understand any of this stuff I think at least THAT has to be consistent.
That...is...weird. MyMonero's viewkey is completely wrong, it should be 0a731057880aec5b222887ee5101e5d8b6c0734c30cefb293f512f4c75637009. I'm going to have to figure out what's gone wrong. Did you use the HTML offline generator, as in this one: https://github.com/moneromooo-monero/monero-wallet-generator ? I can answer this. It's due to the way the MyMonero code derives the viewkey, which is different than simplewallet. Now, for "MyMonero" 13 word seeds, this is correct as it's the established behavior. For 25 word seeds, things can get a bit wonky. Without getting too technical, simplewallet only generates "seeds" that are valid private keys, but will accept *any* 25 word seed. Mooo's address generator currently produces random seeds, not ensuring they are valid private keys. Due to the way MyMonero creates the view key, it will come up different ("random seed" vs "valid private key seed"). If anyone is interested in the code, I wrote it up here a few days ago: http://pastebin.com/MHYZzWWzSimple answer: if you send coins to either of those addresses, they'll be recoverable; you'll just have to pay attention (you can "properly" generate the view key from the seed and log into MyMonero with the "Login with Public Key" if you want). Bonus: here's the seed for that address which will work for both simplewallet and MyMonero (will produce your first address): hoisting sorry alerts sieve request stockpile eels bemused digit ivory acidic guru jobs people befit merger lending envy lectures sifting puzzled peeled maze mocked lectures
|
|
|
|
fluffypony
Donator
Legendary
Offline
Activity: 1274
Merit: 1060
GetMonero.org / MyMonero.com
|
|
August 20, 2015, 06:36:01 PM |
|
Hey Monero-ites... I have a question RE: MyMonero vs. the offline-wallet generator software.
I made an offline address and then tried to "open" it with the given mnemonic seed words in MyMonero, i.e. I was kinda just testing how all this might work IF some day I wanted to make a safe address, to put some monero on it, and then later (eventually) access it again to move/spend the money.
But the ADDRESSES that resulted were NOT the same!
Is that correct? How is this supposed to work, exactly?
For sake of illustration since I'm not gonna USE these addresses now, here is what I got:
Offline Generated Address: 4AYrGeied2XEbaL3uk3gBK1z95DQrcVwncMr5kXPUd7T4RoHhjxyryRWU7qvsp2wJ6L4g1eFaqM6YbD 6RX52j4KQ8PfuBk8
MyMonero Address: 4AYrGeied2XEbaL3uk3gBK1z95DQrcVwncMr5kXPUd7T4UcUpNefenD8HSZ7d9XWSXhmELmfCkvRQGT hzNeCUkaJKDd9nTV
MyMonero View Key (Private) 0ce617dbd51845dd6ada2f3b2d040b5deb6dde38f6640f65abc2a36518045802
MyMonero Spend Key (Private) 8c81ca3b40ae5c199ee10819b9c29959dcc4e97242d93cc6119938ea3858c303
Mnemonic Seed Was: gigantic motherly lordship worry pool karate lopped certain major demonstrate pepper colony jobs people befit merger lending envy lectures sifting puzzled nanny lodge paper certain
So...? IF I had sent money to that first address WOULD IT have BEEN there at this "second" address? I suppose I could just test it with a few cents worth, LOL, but seriously this doesn't seem RIGHT.
An address is an address and for normal humans to EVER be able to understand any of this stuff I think at least THAT has to be consistent.
That...is...weird. MyMonero's viewkey is completely wrong, it should be 0a731057880aec5b222887ee5101e5d8b6c0734c30cefb293f512f4c75637009. I'm going to have to figure out what's gone wrong. Did you use the HTML offline generator, as in this one: https://github.com/moneromooo-monero/monero-wallet-generator ? I can answer this. It's due to the way the MyMonero code derives the viewkey, which is different than simplewallet. Now, for "MyMonero" 13 word seeds, this is correct as it's the established behavior. For 25 word seeds, things can get a bit wonky. Without getting too technical, simplewallet only generates "seeds" that are valid private keys, but will accept *any* 25 word seed. Mooo's address generator currently produces random seeds, not ensuring they are valid private keys. Due to the way MyMonero creates the view key, it will come up different ("random seed" vs "valid private key seed"). If anyone is interested in the code, I wrote it up here a few days ago: http://pastebin.com/MHYZzWWzSimple answer: if you send coins to either of those addresses, they'll be recoverable; you'll just have to pay attention (you can "properly" generate the view key from the seed and log into MyMonero with the other method if you want). Bonus: here's the seed for that address which will work for both simplewallet and MyMonero (will produce your first address): hoisting sorry alerts sieve request stockpile eels bemused digit ivory acidic guru jobs people befit merger lending envy lectures sifting puzzled peeled maze mocked lectures Oh look at you go, I was trying to figure out how the offline generator could be generating seeds that MyMonero can't detect are simplewallet seeds, looks like you've solved it:) Will you PR it to the offline generator?
|
|
|
|
luigi1111
Legendary
Offline
Activity: 1105
Merit: 1000
|
|
August 20, 2015, 06:43:26 PM |
|
|
|
|
|
myagui
Legendary
Offline
Activity: 1154
Merit: 1001
|
|
August 20, 2015, 06:46:01 PM |
|
Bit of both - syncing up only requires tx/block verification, whereas simplewallet actually has to check each transaction for your viewkey. The other problem is that there's no parallelisation in simplewallet, and it chews memory on large wallets (as it keeps the entire cache in-RAM which is silly). We'll be addressing both of those in a future release.
Thanks for clearing it up fluffypony. I should also correct my previous statement: The wallet rescan was not as impressively fast as the full blockchain sync, but it was not really slow either. I just later realized that I had already initiated solo mining on the daemon, so my CPU was having to work pretty hard
|
|
|
|
e-coinomist
Legendary
Offline
Activity: 2380
Merit: 1085
Money often costs too much.
|
|
August 21, 2015, 12:34:56 AM |
|
If you believe in decentralization, please move some trading volume to @cryptsy this week. It will help liquidity and attract new users #xmr https://twitter.com/XMRpromotions/status/633518825036603392Please retweet. Decentralization matters. So does demonstrating to exchanges like bitfinex and btc38 that new exchanges that add us are able to attract volume. Monero has a touching point onto chinese markets at Bter, trading XMR/CNY with some whopping volume of two bucks. That's the area to support. I could exaggerate more about Cryptsy but decided to stick with polite manners, just for the very moment.
|
|
|
|
bigj
|
|
August 21, 2015, 05:40:38 AM Last edit: August 21, 2015, 05:56:50 AM by bigj |
|
I sympathize with the child there. Freedom of speech is only ever a good thing when I am free to say whatever the fuck I want, and others can only say whatever the fuck pleases my ears. Smooth must not be allowed to express his opinion by means of post/trust/rating/whatever! Oh ... Wait ... I see what you did there Guess you were spotted very early on, off you go back on ignore little Inquisitive Troll(TM). Please stop posting off-topic nonsense on this thread. I haven't followed developments as closely as I would like, do we have any up-to-date community built binaries so I could try out the DB version on my Windows box? I know of the cautionary notes and caveats, just wondering if anyone has published binaries yet. This is from last week: https://downloads.getmonero.org/monero.win.x64.v0-9-beta.zipExercise the appropriate level of care with it being a beta. We've recently found and solved what we hope to be the only major, breaking database issue (that could have caused major issues if we'd tagged prematurely), but that means that prior LMDB sync ups have to be resynced from scratch or imported from a fresh blockchain.raw export. Major thank you for that update :-) I'm going to try it asap! EDIT1: I encounter problems with the --data-dir switch. Bitmonerod only runs when no options are passed. Otherwise, errors are thrown usually starting like this: "2015-Aug-21 07:49:22.432815 ERROR C:/msys64/bitmonero-build/src/daemon.cpp:145 Uncaught exception! ...." EDIT2: Bypassing the --data-dir switch using "mklink /j bitmonero d:\bitmonero" also does not work, error: "2015-Aug-21 07:54:02.986862 ERROR C:/msys64/bitmonero-build/src/daemon/daemon.cpp:145 Uncaught exception! Failed to initialize core" EDIT3: Simply starting bitmonerod.exe without any options and without mklink stuff does work :-)
|
|
|
|
DaveyJones
|
|
August 21, 2015, 08:39:01 AM |
|
I sympathize with the child there. Freedom of speech is only ever a good thing when I am free to say whatever the fuck I want, and others can only say whatever the fuck pleases my ears. Smooth must not be allowed to express his opinion by means of post/trust/rating/whatever! Oh ... Wait ... I see what you did there Guess you were spotted very early on, off you go back on ignore little Inquisitive Troll(TM). Please stop posting off-topic nonsense on this thread. I haven't followed developments as closely as I would like, do we have any up-to-date community built binaries so I could try out the DB version on my Windows box? I know of the cautionary notes and caveats, just wondering if anyone has published binaries yet. This is from last week: https://downloads.getmonero.org/monero.win.x64.v0-9-beta.zipExercise the appropriate level of care with it being a beta. We've recently found and solved what we hope to be the only major, breaking database issue (that could have caused major issues if we'd tagged prematurely), but that means that prior LMDB sync ups have to be resynced from scratch or imported from a fresh blockchain.raw export. Major thank you for that update :-) I'm going to try it asap! EDIT1: I encounter problems with the --data-dir switch. Bitmonerod only runs when no options are passed. Otherwise, errors are thrown usually starting like this: "2015-Aug-21 07:49:22.432815 ERROR C:/msys64/bitmonero-build/src/daemon.cpp:145 Uncaught exception! ...." EDIT2: Bypassing the --data-dir switch using "mklink /j bitmonero d:\bitmonero" also does not work, error: "2015-Aug-21 07:54:02.986862 ERROR C:/msys64/bitmonero-build/src/daemon/daemon.cpp:145 Uncaught exception! Failed to initialize core" EDIT3: Simply starting bitmonerod.exe without any options and without mklink stuff does work :-) Could not find any issue with a linkfile to bitmonerod.exe and the --data-dir
|
|
|
|
nioc
Legendary
Offline
Activity: 1624
Merit: 1008
|
|
August 21, 2015, 09:15:05 AM |
|
bigj and DaveyJones, which version of windows are you using?
|
|
|
|
bigj
|
|
August 21, 2015, 02:43:58 PM |
|
bigj and DaveyJones, which version of windows are you using?
I'm running a plain Windows 7 (x64, all updates) installation. D-drive is an usb-attached hdd, c-drive is a sata-ssd. 8gb memory, asus/celeron 847 mobo.
|
|
|
|
Andretti83
Full Member
Offline
Activity: 297
Merit: 112
PRIVATE AND NOT PREMINED: MONERO, AEON, KARBO
|
|
August 21, 2015, 03:31:33 PM |
|
I'm using monero 0.9 beta, win7 x64 and save blockchain to disk D: and everything works fine. Just in case you may have some error in command line, I'm using this: bitmonerod.exe --data-dir d:\coin\monero\data
|
|
|
|
medusa13
Sr. Member
Offline
Activity: 453
Merit: 500
hello world
|
|
August 21, 2015, 05:25:29 PM Last edit: August 21, 2015, 06:21:00 PM by medusa13 |
|
seems to me like there is some memory leak with 0.9 beta on win 7 x64. after letting it run 24h something like 8 gb of ram was used, but not visible in the task manager. once i stopped it ram droped down to the usual levels. will try to retest so i can give better feedback.
|
XMR Monero
|
|
|
luigi1111
Legendary
Offline
Activity: 1105
Merit: 1000
|
|
August 21, 2015, 06:35:05 PM |
|
seems to me like there is some memory leak with 0.9 beta on win 7 x64. after letting it run 24h something like 8 gb of ram was used, but not visible in the task manager. once i stopped it ram droped down to the usual levels. will try to retest so i can give better feedback. I don't know what actual commit that beta is on, I'm on one from Aug. 10th, and having no issues with memory. I'm usually around 40MB. Edit: run with "--version" to see.
|
|
|
|
canth
Legendary
Offline
Activity: 1442
Merit: 1001
|
|
August 21, 2015, 06:56:03 PM |
|
Someone mentioned a website tracking monero nodes - anyone got that handy?
BTW, I just threw up a .9 Beta instance - looking fast and smooth so far. GJ guys!
|
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
August 21, 2015, 07:16:08 PM |
|
DO NOT DEPOSIT XMR TO CRYPTSY !!
It's NOT POSSIBLE to withdraw coins once you deposit!!! Their system is broken or so they say. Very suspicious! I opened a ticket almost 4 days ago, still waiting !!
|
|
|
|
canth
Legendary
Offline
Activity: 1442
Merit: 1001
|
|
August 21, 2015, 07:34:10 PM |
|
DO NOT DEPOSIT XMR TO CRYPTSY !!
It's NOT POSSIBLE to withdraw coins once you deposit!!! Their system is broken or so they say. Very suspicious! I opened a ticket almost 4 days ago, still waiting !!
Uggh. Thanks for the heads up and keep us updated.
|
|
|
|
medusa13
Sr. Member
Offline
Activity: 453
Merit: 500
hello world
|
|
August 21, 2015, 08:20:56 PM |
|
I don't know what actual commit that beta is on, I'm on one from Aug. 10th, and having no issues with memory. I'm usually around 40MB.
Edit: run with "--version" to see.
bitmonero v0.8.8.7-7792255 page 1337 yolo
|
XMR Monero
|
|
|
bigj
|
|
August 21, 2015, 08:49:56 PM |
|
I'm using monero 0.9 beta, win7 x64 and save blockchain to disk D: and everything works fine. Just in case you may have some error in command line, I'm using this: bitmonerod.exe --data-dir d:\coin\monero\data
I apologize. The problem seems to be related to my usb-attached harddisk (my d-drive). Under heavy load it shuts down but remains visible and "active" in Windows, thus, causing weird behavior and trouble. Usb drivers suck.
|
|
|
|
MoneroMooo
Legendary
Offline
Activity: 1276
Merit: 1001
|
|
August 21, 2015, 09:14:44 PM |
|
Thanks, merged, signed, and pushed. Addresses generated earlier are still totally valid of course, and can be restored with simplewallet.
|
|
|
|
|