Serena is being too kind/accommodating with you; I suffer from neither of those traits. To what details and what volume are you referring? Why bring up Masari? Who cares if you have seen various coins - I've seen various coins, too, but I don't feel the need to point that out in any post*. Finally, what do you mean by the phrase, "original algo is popular in general"?

I don't get the impression you are spamming here, but all of the posts in your history are basically word salad so I suggest you put more effort into improving your English if you wish to participate on this forum, especially if you intend to argue or criticize something. Keep in mind that it isn't necessarily the one who is right that wins an argument, rather, the one who explains his/her position more persuasively.

Oh, and this applies to @kellog9000, too - you are about to get put on my ignore list for positing useless crap like, "when moon" and "more exchanges". Go harass the XMR thread if that is all you have to contribute to the discussion here.


* - well, I guess I just did... how meta of me.

Lol, outstanding work! I've been seeing more plagiarizing, too, and I report it every time.

Part of this is correct. Yes, ctrl-c is the break command in DOS/CMD but it will, indeed, copy text to the clipboard if you highlight the text with the mouse first. That said, the issue here isn't with copying text from the wallet client, rather, it is pasting text into it.

And FWIW, I have no problem pasting my password into any of the other DOS/CMD wallet clients I run (including the old DERO client) so this issue is peculiar to the alpha wallet client.

Even when I'm not entirely thrilled about doing something I still try to do my best.

But just to clarify, note that Speedie's suggestion worked for pasting the seed and/or password into the text entry fields of the wallet, but "normal" copy and pasting (either ctrl-v or right click/paste) still do not work.

Also note that Speedie's trick is how you had to paste text into a command window back in Windows 7, so this is a 9 year old trick, more or less. Not something that sprang to my mind to try until Speedie mentioned it.

Rather than dash off a snappy response about wasting more of my time, I decided instead to try your first suggestion and, low-n-behold, it worked...  

So, not really sure what is going on here, but I can confirm that manually selecting paste from the right-click menu in the title bar does, indeed, paste text into both the password and recovery seed prompts in the wallet.

I suspect this only makes the proverbial water muddier, though, as far as finding a root cause/solution.

EDIT - I did not try #2, but you do get the same menu by left clicking on the DOS box icon.

I copied the seed string by selecting the text with my cursor then hitting ctrl-c to copy. Then I opened an administrator command prompt and pasted the string into it using both ctrl-v and right clicking the mouse and selecting paste - both worked.

So pasting into a command prompt works fine, as it always has in Windows 10.

Trying to recover from seed again, when I hit ctrl-v to paste it shows a non-printable single character; looking closer, it appears to be a ? in a box, so I guess that translates as "unprintable character".

I cannot right-click while sitting at the "Enter seed (25 words):" prompt. Trying again, I also cannot paste using either method to the password prompt.

Right clicking on the title bar for the command window that the wallet is running in and selecting "Properties" I also checked the checkboxes under "Options" and all were enabled EXCEPT for "Quick edit mode," but enabling Quick edit mode didn't change anything. Still can't paste.

And yes, copy-and-paste works fine elsewhere.

Doh! I can't believe I wrote that. All I'll say in my defense is I had not yet drank any coffee... I'll leave the evidence of my stupidity up for posterity, however... 

Either you're a 'tard that didn't read the first post or a bot:

What is that address? I tried searching the thread for such - I suspect it has already been posted - but forum search is failing me here (I just keep getting a reference to email address on the first page).

EDIT - nope, address hasn't been posted to this thread; I just re-read the last 6 pages to confirm. You did post about a likely Baikal address being registered on supportxmr.com a few pages back, though. Naturally, I want to see if this address is being used to mine any other CN coins and will post my findings here.

EDIT 2 - this was really dumb of me... I won't edit it into non-existence, though.

Yeah, I'm curious about this, too. I suspect the cursed ASIC miners are coming on line and some have chosen DERO as their target. As soon as I get closer to the next 2 DERO payout I am dropping the hashrate allocated to DERO mining to the minimum I can deploy (a single FX-8320 CPU that does ~340 H/s) and switching over to mining MUSIC (Ethash).

Challenge accepted... I backed up the wallet.dat file that I had created by doing restore from seed my way (ie - using command line switches) and tried restoring from seed by selecting option 3.

All seemed to be going well until I found out I had to manually type in the 25 word recovery seed because copy and paste was blocked - and yes, this is Windows 10, not Windows 7, so I should have been allowed to paste in the seed. Needless to say, having to manually type in the seed is frustrating, time consuming and prone to typos, and I can't think of a single benefit to blocking copy-and-paste so that should be addressed before releasing the wallet to the wider world.

And yet again y'all roped me into bug hunting...  

Thanks for attempting to help, but this didn't work. It turns out my original switch selection was correct, as adding the --generate-new-wallet and --password switches prevented me from opening the regenerated wallet.dat file. Just in case anyone else has the same issue, the command I entered was:

dero-wallet-cli --restore-deterministic-seed --electrum-seed="a sequence of 25 words"

I was then prompted to enter my password and confirm it, and the wallet regenerated and began scanning the blockchain.

Not entirely painless, mind you - I was definitely cursing getting sucked into doing more alpha testing of a wallet - but everything seems to be working ok now.

That said... I would like to be able to see the transactions and their date in the wallet, but there doesn't seem to be a numerical command for that.

How about providing more details to potentially help anyone else with the same problem? Like, what cards and what driver version did you have before?

 

25-60 minutes to sync, you say? I was running the 386 version up until this morning, then switched over to the amd64 version (it wasn't clear which one to use, given that the laptop I run my wallets on has a Celeron CPU) and had to start the sync all over again, apparently. At any rate, 3+ hours later and I am at ~40xxx out of 53386 which is far slower than your estimate but far faster at syncing than any other wallet I've run.

However, my poor laptop is noticeably slower while running this hot little daemon; CPU load is quite heavy at around 25-30%.

Now, how to load the wallet from the old client to the new one? I presume I'll need to use the --restore-deterministic-wallet and --electrum-seed=<seed phrase> commands?

Well, I woke up this AM to find the daemon stuck on block 8648 with "failed tx" and "mempool stopped" as the last two messages reported. I rather expected the daemon to make a lot more progress than that so it seems whatever "mempool stopped" is, it's fatal.

EDIT - blockchain syncing did resume when I restarted the daemon, btw.

hmmm... I'm getting a veritable sea of "err while loading output data index..." errors on the new daemon as it tries to sync. Currently sitting around 7300 out of 53407.

Not exactly confidence inspiring, and I generally loathe alpha/beta testing software (I do enough of that for my job), hence why I didn't rush to volunteer for doing that here.

This happens to me sometimes, too. If your cards aren't overheating then you can try stopping and restarting xmr-stak; if that doesn't work - and mind you, it sometimes doesn't - then rebooting usually does.

Any chance the new daemon/wallet is messing up the old blockchain? I ask because once again my wallet daemon is unable to sync, but unlike the previous forking incident, this time the "new top block candidate" keeps oscillating between blocks 53023 and 52402, which is puzzling, to say the least.

I thought so too! Although I'd like to think I am fairly technically savvy, I had no idea that to increase the number of threads used in xmr-stak I had to literally duplicate the thread parameter string for each thread. Rather ununintuitive/obtuse, really.


Oh, that I agree with totally, though I suspect it would be even harder to enforce than account selling (hence why the latter is "discouraged," rather than outright banned).

Perhaps two good rules to consider for filtering out potential merit abusers for red trust are on any merit transactions greater than, say, 10, or when one person gives merit to another more than, say, 5x. The latter rule will likely become less useful as time goes on, however.

Argh, no, don't do that! Not all trading of merit is merit trading, so to speak. I've merited people who have merited me because we were participating in a thread where we were all trying to solve various mining issues - I solved one issue and got merited, then the same person that merited me solved another issue so I merited him*. Of course, I freely admit that I was more inclined to merit someone who had merited me - that's just human nature - but said individual did, indeed, post something merit-worthy.

* - I was merited on this post: https://bitcointalk.org/index.php?topic=2046072.msg30157009#msg30157009 & I merited the person who merited me for this post in the same thread: https://bitcointalk.org/index.php?topic=2046072.msg30407678#msg30407678