|
Thanks for the responses guys.
It seems there was only a 45 minute window, at 5AM to buy this coin. IMO that is pretty shitty and very much like the Darkcoin/Dashcoin instamine
Some people here are saying "great launch" "successful ICO" Well they are probably only saying that because they were one of the very lucky few that was actually able to get some coins. Everyone else though, is pretty disappointed.
This seemed like a great project but with a bullshit distribution it is hard to trust. Thanks anyway best of luck to the select few who got coins.
|
|
|
|
|
Guys can someone help me out
I wanted to buy this but the ICO ended (unfairly IMO) too quickly but now I don't understand...
Can you still buy this? There is still an option to send ether to the ICO address. Would we still get coins?
Thanks.
|
|
|
|
|
Since when are we having to provide photo ID for crowdsale? And selfie with it?
I want to buy into this but obviously I don't want to put my address, ether address and photo ID on the goddamn internet!? lol...
Am I tripping or is that just draconian?
|
|
|
|
TRST price is climbing!
Yep. With 193.15 volume we can go high. What predictions on price guys? I just bought in around 10k sat feeling really good ESTIMATING a $100 million market cap here This one reminds me of how vericoin was when I bought in around 700 sat lol...IMO 10k sat is absurdly cheap for this coin |
|
|
|
Mods and tech guys -
What do I need to do do upgrade the wallets? I am apparently trying to load an old wallet and it needs some type of upgrade?
If it's the old standard, I think you will have to just send your monero to a new wallet. You should be able to run simplewallet.exe with the flag --wallet-file arg to recover it for starters. Then just make a new wallet and send to a modern mnemonic seed style wallet. Here is a post about it. https://www.reddit.com/r/Monero/comments/3jteca/how_to_import_old_monero_wallet/ and the answer worked. But probably if he had just run it with the flag I talked about above he wouldn't have gotten that error. At this point all I am desperatly trying to do is even get bitmonerod to work. I tried starting over with the new binaries but it reads "Uncaught exception! attempt to get timestamp from height 1105296 failed -- timestamp not in the db What does db stand for? And hat someone tells me to run with the --wallet-file command, what do they mean? when I run that command it returns unknown command... |
|
|
|
Mods and tech guys -
What do I need to do do upgrade the wallets? I am apparently trying to load an old wallet and it needs some type of upgrade?
Do you remember which OS the wallet was created on? If so, download the binaries from the getmonero website for that same OS. Extract the binaries, go to the extracted folder and open bitmonerod (the daemon). Bitmonerod first has to sync fully before you are able to restore your wallet. If bitmonerod is fully synced (you can check this by typing "status" into bitmonerod, it should be equal to the blockheight displayed on moneroblocks.info), place the wallet.bin, wallet.bin.address.txt, and wallet.bin.keys in the same folder as bitmonerod and simplewallet are located. Subsequently, open simplewallet and type in the wallet's name. Simplewallet will automatically update you to a new version and you should be able to see your coins (and transact with them). Link: https://getmonero.org/downloads/Sidenote: if you need help with setting up bitmonerod and simplewallet, you can follow these guides: https://github.com/monero-project/monero-site/blob/master/knowledge-base/user-guides/create_wallet.mdhttps://getmonero.org/knowledge-base/user-guides/simplewalletYes, it was created on windows 7 64 bit and I am trying to load it on 64 bit windows right now as well. The problem is I can't even get bitmonerod to sync. Trying to start over was the first thing I did, When I download new binaries and start over I still get the same problem. The error reads "Uncaught Exception" attempt to get timestamp from height 1105296 failed -- timestamp not in the db |
|
|
|
|
Mods and tech guys -
What do I need to do do upgrade the wallets? I am apparently trying to load an old wallet and it needs some type of upgrade?
|
|
|
|
|
Hey guys, I am having a problem with simplewallet,
I have my keys and address files in the proper directory but when I try to start bitmonerod I get an error message but it shuts down immeaditly there are words flashing in red but it shuts off to quick for me to read them. Looks like it is saying something about some type of file path or storage location.
Are there any tricks to using the blockchain bootstrap? just put it in the directory and blockchain.raw, right?
Can you have two different wallets in the same directory, and load each wallet as you need to using the same daemon?
How do you view the log to see what the error is?
|
|
|
|
Guys I heard the XMR Gui has been released? where do we download it from?
There haven't been binaries released yet. So it's not officially released yet? |
|
|
|
|
Guys I heard the XMR Gui has been released? where do we download it from?
|
|
|
|
I think 18080 is for p2p, whereas 18081 is for RPC. Also, you will need to make sure that 18081 is open on your server. Thanks GingerAle, learning every day. Opened port 18081 on the node as well, please give it a try parker928. Windows: simplewallet.exe --daemon-host 185.112.158.127:18081 Linux: ./simplewallet --daemon-host 185.112.158.127:18081 I type that in the command line? without having simple wallet open and the daemon open? or does the daemon already have to be running Type in the command line with neither simplewallet or bitmonerod running. That command will open simplewallet and tell it to use a remote daemon, so you don't need to run bitmonerod on your comp at all. (This does degrade your privacy a bit.) I don't care about privacy i just don't know if that makes it possible for someone to steal my coins or not |
|
|
|
I think 18080 is for p2p, whereas 18081 is for RPC. Also, you will need to make sure that 18081 is open on your server. Thanks GingerAle, learning every day. Opened port 18081 on the node as well, please give it a try parker928. Windows: simplewallet.exe --daemon-host 185.112.158.127:18081 Linux: ./simplewallet --daemon-host 185.112.158.127:18081 I type that in the command line? without having simple wallet open and the daemon open? or does the daemon already have to be running |
|
|
|
When starting bitmonerod, the message is shown. Last scheduled hard fork time shows a daemon update is needed now. I thought this update would do it. What should I do? I just started getting the same message. I believe it was mentioned that this message is a bug and there is nothing that needs to be done. Also there is a release due out today that will address this and a few other things. Well ok. The synchronization has anyway been very slow. Before and after last update. It takes easily half an hour or more to sync just one days blocks. Has anyone else this problem? mine is very slow too i have the 9.2 on a capable machine and it looks like at this rate i won't be done for about 3 days. To all mods/devs...can someone please give a little bit more specific information on how to use the bootstrap download? i downloaded it but I don't know how to open it or what directory it should be in. I do not know how to code or use command line :/ It seems I am not the only one who feels like they are unable to access their coins despite doing everything right. hopefully one of you hero members or more experienced users can write a dummy's guide or something because this is just a little too complicated lol. I was smart enough to build an 8 gpu mining setup but somehow i have trouble with monero hahaha A "capable machine" doesn't take 3 days to sync. Mine takes just over an hour. I'm guessing using the import isn't going to be significantly faster than syncing. If you really want to try it, please join #monero on freenode and people there can work with you on it much more quickly than this back and forth via forum posts. https://webchat.freenode.net/You can also use simplewallet with a remote node which should be much faster than syncing a daemon from scratch. Someone else would have to provide some names/addresses for remote-capable nodes. I'm just going to wait for it to sync. thanks lol |
|
|
|
@parker928
Most likely invalid address means you typed in the address wrong. It is also possible you put the argument in the wrong order.
You should wait for it to finish syncing before trying to transfer though.
Thought so. can you please remind me what the exact format is, i forgot where exactly the spaces go or if there are commas and parentheses etc. i have been holding for 18 months so its hard to remember how to work this damn thing transfer [mixin] address amount [payment-id] The items in [brackets] are optional. how do i use -- verify command? I typed exactly that "--verify 0" and "-verify 0" and "verify 0" none of those helped to speed anything up! i must be missing something It is used with blockchain_import and the downloaded bootstrap. blockchain_import --verify 0 blockchain.raw I think. May be slightly off, in which case hopefully someone will correct it. I'm not really sure what that means... You download the file blockchain.raw from getmonero.org. Instead of syncing the daemon, you use the blockchain_import utility to import the raw file. The optional '--verify 0' option makes the process go much faster but skips all safety checks. If you aren't comfortable with a procedure like this the best thing to do is be patient and let the daemon sync by itself. EDIT: The correct format for the blockchain_import command (with '--verify 0' added optionally) is blockchain_import --input-file blockchain.raw Thanks a lot I can see you're really trying to help. i still can't do it. i'm missing something. can you make a video or something? |
|
|
|
When starting bitmonerod, the message is shown. Last scheduled hard fork time shows a daemon update is needed now. I thought this update would do it. What should I do? I just started getting the same message. I believe it was mentioned that this message is a bug and there is nothing that needs to be done. Also there is a release due out today that will address this and a few other things. Well ok. The synchronization has anyway been very slow. Before and after last update. It takes easily half an hour or more to sync just one days blocks. Has anyone else this problem? mine is very slow too i have the 9.2 on a capable machine and it looks like at this rate i won't be done for about 3 days. To all mods/devs...can someone please give a little bit more specific information on how to use the bootstrap download? i downloaded it but I don't know how to open it or what directory it should be in. I do not know how to code or use command line :/ It seems I am not the only one who feels like they are unable to access their coins despite doing everything right. hopefully one of you hero members or more experienced users can write a dummy's guide or something because this is just a little too complicated lol. I was smart enough to build an 8 gpu mining setup but somehow i have trouble with monero hahaha |
|
|
|
@parker928
Most likely invalid address means you typed in the address wrong. It is also possible you put the argument in the wrong order.
You should wait for it to finish syncing before trying to transfer though.
Thought so. can you please remind me what the exact format is, i forgot where exactly the spaces go or if there are commas and parentheses etc. i have been holding for 18 months so its hard to remember how to work this damn thing transfer [mixin] address amount [payment-id] The items in [brackets] are optional. how do i use -- verify command? I typed exactly that "--verify 0" and "-verify 0" and "verify 0" none of those helped to speed anything up! i must be missing something It is used with blockchain_import and the downloaded bootstrap. blockchain_import --verify 0 blockchain.raw I think. May be slightly off, in which case hopefully someone will correct it. I'm not really sure what that means... |
|
|
|
@parker928
Most likely invalid address means you typed in the address wrong. It is also possible you put the argument in the wrong order.
You should wait for it to finish syncing before trying to transfer though.
Thought so. can you please remind me what the exact format is, i forgot where exactly the spaces go or if there are commas and parentheses etc. i have been holding for 18 months so its hard to remember how to work this damn thing transfer [mixin] address amount [payment-id] The items in [brackets] are optional. how do i use -- verify command? I typed exactly that "--verify 0" and "-verify 0" and "verify 0" none of those helped to speed anything up! i must be missing something |
|
|
|
@parker928
Most likely invalid address means you typed in the address wrong. It is also possible you put the argument in the wrong order.
You should wait for it to finish syncing before trying to transfer though.
Thought so. can you please remind me what the exact format is, i forgot where exactly the spaces go or if there are commas and parentheses etc. i have been holding for 18 months so its hard to remember how to work this damn thing anyway i think the address i am trying to send to is a newly created address so the daemon may not recognize it because it is only synced to like 900,000 blocks so maybe if that wallet was created within the last 100,000 blocks the daemon just doesnt know it yet. interesting wait nvm it seems i am only 10% done syncing...where can i go to get a downloaded blockchain so i dont have to wait 24+ hours for this to finish |
|
|
|
@parker928
Most likely invalid address means you typed in the address wrong. It is also possible you put the argument in the wrong order.
You should wait for it to finish syncing before trying to transfer though.
Thought so. can you please remind me what the exact format is, i forgot where exactly the spaces go or if there are commas and parentheses etc. i have been holding for 18 months so its hard to remember how to work this damn thing anyway i think the address i am trying to send to is a newly created address so the daemon may not recognize it because it is only synced to like 900,000 blocks so maybe if that wallet was created within the last 100,000 blocks the daemon just doesnt know it yet. interesting |
|
|
|
|
Show Posts
