We should not trust our eyes and ears that were watching the drama unfold,
nor we should pay attention to any of the people that were actually involved in keeping the place alive.
I'd pay more attention if they were posting status reports here and releasing the "solvent" coins instead of sitting around and not communicating at all. When did you last see a status/activity report posted here with regard to releasing the so-called "solvent" coins to their owners? You can trust them all you like, but I'm not drinking the Kool-Aid associated with this one. Trust can be earned, and trust can easily be lost. Trust is not automatic. Some form of communication would be helpful if they are still around. I agree it'd be nice if they'd keep the thread updated more, but the owner and other people working on the exchange are pretty much available all the time at #cryptorush channel on freenode. |
|
|
|
My mistake, the myriadcoin-qt file that is created is 104MB however it is not executable either by clicking on it or by trying to run it from within a console. The file type is shared library not executable.
It really shouldn't be that tricky if you have all dependencies installed, and it really should come out as an executable, but maybe try and explicitly set it as executable, like: chmod 755 ./myriadcoin-qt
and then see if you can launch it. |
|
|
|
myriadcoin-qt is located in the ~/myriadcoin-master/src/qt/ folder, however it is not executable. This file is roughly 1043.MB in size and is labeled as a shared library by Dolphin in the type column. If everything worked properly shouldn't myriadcoin-qt be an application?
When I performed the compile steps what folder should I have been in? After I took care of all the dependencies, I ran these commands
while in ~/myriadcoin-master/
1.) ./autogen.sh
2.) ./configure
3.) make
Come to think of it, I'm not sure why I am not doing my compiling in /usr/local/src. I have only compiled one other wallet and the guide I followed said to place the source code in /usr/local/src. I will move the myriad source there and try again.
Any other ideas about my compiling issue?
Thank you for the response Palawan
It shouldn't matter where you do the compiling. Have you tried just executing the myriadcoin-qt file that it creates from the terminal (I think it should be created with exectuable flag)? Also, 1 GB seems kind of giant for the binary... |
|
|
|
If you delete it, it is a good idea to use a "secure erase" or "shred" type utility. Otherwise the contents may stick around in file system free space. Less of an issue for SSDs, depending on OS and other factors.
Good point, smooth. I will definitely add that into the popup that comes up after you create a new wallet. |
|
|
|
Nice work, jwinterm. Good-looking and functional GUI wallet.  I will get around to trying the new GUI soon. Can you please elaborate on what the version cutoff is for a "deprecated" wallet? (My apologies if it is in the readme or something) To be honest, I'm not sure, but I think it is basically if you created a wallet in April or May. The current workaround for deprecated wallets is to use v0.8.8.4 to import the keys file and update the wallet, then you can use it in v0.8.8.5/6, but it will be fixed in the next simplewallet release. I'm pretty sure if you have an electrum seed for your wallet, then it's not deprecated. My compliments on your work. To be clear, this still takes a lot of your RAM or doesn't it?EDIT: I had to much beers, if I am reading the text correct it shouldn't eat up your RAM. If I can give you some advice, I would make the "tabs" horizontal instead of vertical, bit hard to read now (could be the alcohol, but still  ). Another point, if you create a new wallet the seed will be stored in a plain text file without encryption. I would advise to make some kind of announcement everytime you create a new wallet to encrypt to file or to make it a default thing to encrypt the textfile with the seed. Thanks dEBRUYNE. I will try out the tabs horizontal and see how they look. There is (should be) a message that pops up everytime you create a wallet though, saying this info.txt file has your seed and you should delete or encrypt it. Maybe I should change the name of that file to "DELETE OR ENCRYPT THIS FILE IMMEDIATELY.txt" |
|
|
|
Nice work, jwinterm. Good-looking and functional GUI wallet. I will get around to trying the new GUI soon. Can you please elaborate on what the version cutoff is for a "deprecated" wallet? (My apologies if it is in the readme or something) To be honest, I'm not sure, but I think it is basically if you created a wallet in April or May. The current workaround for deprecated wallets is to use v0.8.8.4 to import the keys file and update the wallet, then you can use it in v0.8.8.5/6, but it will be fixed in the next simplewallet release. I'm pretty sure if you have an electrum seed for your wallet, then it's not deprecated. |
|
|
|
I'd like to announce the first alpha release of my unofficial lightweight GUI simplewallet wrapper, lightWallet. Using this program, you don't need to run the bitmonerod daemon on your own computer or do anything on the command line. By default it uses hegemoOn's (a long time Monero supporter) open node, although you can change it to use a different node (Atrides recently announced another one, for instance), or you can set it up to use a local daemon. The release binary ( https://github.com/jwinterm/lightWallet/releases/download/v0.0.1-alpha/lightWallet.exe ) is a single file that has simplewallet.exe wrapped up inside of it, so you do still still need a 64 bit machine. Please check out the README.md file here as well: https://github.com/jwinterm/lightWallet I'm still working on the tx history part, and I'd like to add an address book, but since simplewallet itself doesn't really have either one of these features, I figured I'd go ahead and release it, since we have (at least) two open nodes to choose from now  The program should work to create new wallets or import non-deprecated wallets from their keys file (wallets with an electrum seed). There is an issue with simplewallet itself that prevents importing deprecated wallets at the moment, but this should be fixed in the next simplewallet release. The created/imported wallets will be stored in your My Documents folder in the lightWallet folder. Here are a couple screenshots of the first two tabs:   Let me know what you think. I hope some people find it useful. |
|
|
|
what's the best pool of BBR ?
If you're using AMD cards then SOLO Mining is best. Give it a day and you'll start finding blocks. How many depends on how many cards you're using. Difficulty and hashrate is low right now but I doubt it will stay that way for long. Now is a good time to mine BBR. Here are some good instructions for solo mining using "MBK's" openCL miner for BBR https://bitcointalk.org/index.php?topic=693118.0I need to buy a new windows laptop. What spec would be best to mine BBR in the background? Intel or AMD? NVidia or Radeon? Laptop will be (primarily) for the wife to do microsoft office-y stuff... I'm assuming I can CPU and GPU mine BBR without too much risk of the laptop overheating? Any advice would be gratefully received. Thanks! Probably something with an i7 and an nvidia 680m card would be best/most power efficient combo. Also probably a bit overkill for MS Office... |
|
|
|
Speaking of mining, remember to help spread the hashrate. Solo mining if you have enough hash and know how to set it up, or support smaller pools like bbr.poolto.be (where I mine), bbr.mbkpool.info, boolberry.extremepool.org, etc.
I don't understand why people are so worried about getting small amounts of BBR continuously rather than larger amounts less often. You can still solo mine and find blocks. It will take longer but you get the entire block when you find it. Mining on a pool that solves the most blocks doesn't equal more BBR for individual miners and it isn't good for the network. The biggest pool also has a 3% fee so you lose that right off the top. Here is some good instructions for solo mining using MBK's openCL miner for BBR https://bitcointalk.org/index.php?topic=693118.0Maybe clintar just has like 900 Mh/s running on his own pool...  |
|
|
|
Speaking of mining, remember to help spread the hashrate. Solo mining if you have enough hash and know how to set it up, or support smaller pools like bbr.poolto.be (where I mine), bbr.mbkpool.info, boolberry.extremepool.org, etc.  |
|
|
|
I've tried everything. These are old wallets from way back before last summer. I don't remember how much exactly is in them but I think one has 1000 XMR. Can a wallet be to old to open?
I think you need to rebuild from keys file using an older version of binary, maybe 0.8.8.4, and then it should work on newer versions as well. Either that or wait for next release, this wallet formatting issue is being addressed now in #monero-dev, and should be corrected in next release. |
|
|
|
Any idea whats going on here? I tried to open a couple old wallets I forgot about and get this same error with both. 2014-Dec-09 21:04:38.576964 Loaded wallet keys file, with public address: TheBiggestMoneroWalletInTheWorld7jdimjgkghdskfikvjmvkvb9900rmvAndICantOpenIt
2014-Dec-09 21:04:38.686532 ERROR C:/bitmonero/src/common/boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=incompatible native format - size of long
2014-Dec-09 21:04:38.686532 ERROR C:/bitmonero/src/wallet/wallet2.cpp:692 !r. THROW EXCEPTION: error::file_read_error
2014-Dec-09 21:04:38.686532 C:/bitmonero/src/wallet/wallet2.cpp:692:N5tools5error15file_error_baseILi2EEE: failed to read file "wallet.bin"
2014-Dec-09 21:04:38.686532 Error: failed to load wallet: failed to read file "wallet.bin"
2014-Dec-09 21:04:38.702196 ERROR C:/bitmonero/src/simplewallet/simplewallet.cpp:429 could not open account
2014-Dec-09 21:04:38.702196 ERROR C:/bitmonero/src/simplewallet/simplewallet.cpp:1381 Failed to initialize wallet Maybe you created wallet on windows and then tried to open on linux, or vice versa. Did you try to rebuild from the keys file? |
|
|
|
What would be really nice in terms of the simplewallet functionality is if there was a way to change your simplewallet password. Is such a feature planned at all? more unprofitable for the botnet dumpers.
Surely they are at 100% profit, others hashing doesnt affect that right? It is a myth that botnets are 100% profit. It is well documented that botnet nodes have a market price. If mining brings in less than that, it is better to sell the node (or do something else with it). Our primary concern though is creating the most secure and private coin and that means (among other things) decentralization of mining. If that includes botnets, well, we can't solve every problem in the world. As fluffypony said it can a relatively small part of the system, assuming a large number of users. But without users, none of this actually matters. I think you can change your password when you recover from the mnemonic seed. |
|
|
|
I updated to 0.8.8.6
When starting simple wallet I was asked to chose a language for my wallet's seed. English was the first choice so I entered 1 not noticing that 0 was for English so I got a seed in Spanish. Whatever. The problem is one of the words has a strange character.
The following I copy and pasted from my wallet leaving one of the regular letters for comparison. It is composed of a vertical line the goes above and below any of the other letters. The part that is attached looks different in simple wallet, it looks like a T that is attached to the verticle line and squashed with the top below the top of the other letters and bottom above the bottom of the other letters.
fé
Is that character supposed to be there? It doesn't look like any Spanish I know. How would I reproduce it? Is there a way to get another seed for my wallet? I would just create a new wallet bu I like the name of it. Could I create a new wallet by changing the case of a letter(s) in the wallet name?
I did the same exact thing with an old wallet. God damn programmers and their god damned zero indexed brains I don't think there's a way to fix it at the moment, but I brought it up with fluffypony and I think it will be considered in future releases. Someone please correct me if I'm wrong... |
|
|
|
I think you're not getting it - you don't adopt a kid if you don't have time to feed it and take care of it
Mining is not a adopting a kid, it is running a computer. Approached in a low-maintenance manner, it can be very similar to running a file server that doesn't require much attention for months or years. The break even electricity rate for Monero GPU mining is not even that low (haven't worked it out recently but maybe 10 cents/kwh). Yes I cringe when I see people posting about how "the difficulty is too damn high" because mining isn't profitable for them at 30 eurocents/kwh, but in locations with low rates you will still be profitable or accumulate coins at a small loss with little to no maintenance effort. Very true, it's not - and I'm not saying people CANNOT mine in an extremely low maintenance manner, I'm saying if they're going to do that, they may as well take some cash out of their wallet, burn a small percent, and use the rest to buy XMR, because that's basically what they're doing. Not to get all righteous or anything, but there is also the possibility that if someone really likes a certain coin's technology, ideals, developer team, logo, etc., then maybe they just want to "support the network", even if that means mining at less than optimal profit or a slight loss. |
|
|
|
At one point, according to the miner outputs, I was simultaneously mining skein and qubit, with about an 80/20 split in terms of relative hashrates. Didn't think that was even possible ?!
Definitely possible, and I'd guess that the difference in hashrate is just due to skein hashrates generally being higher than qubit. Typically if you open two instances of sg/cgminer or whatever, it will just split the work it's doing between them. I was seeing ~200 mh/s per gpu on skein (where I'd usually see 250), and about 1.3 mh/s for qubit (where I'd usually see 6.3). So I was getting about 80% skein, 20% qubit. Hence why I said 80/20 split. Weird. I've never really done it on purpose, but if I open two miners by accident, then it will split the hash right down the middle, but that would be with the same exact miner/binary. Maybe windows is giving the two miners different priorities or something. |
|
|
|
At one point, according to the miner outputs, I was simultaneously mining skein and qubit, with about an 80/20 split in terms of relative hashrates. Didn't think that was even possible ?!
Definitely possible, and I'd guess that the difference in hashrate is just due to skein hashrates generally being higher than qubit. Typically if you open two instances of sg/cgminer or whatever, it will just split the work it's doing between them. |
|
|
|
|
Show Posts
