smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
March 21, 2016, 03:11:46 AM |
|
@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 There is a bootstrap you can download from getmonero.org, but the import process (blockchain_import) is fairly slow. You can choose to fully trust the download with --verify 0 which will speed it up. Or wait.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
March 21, 2016, 03:12:36 AM |
|
@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.
|
|
|
|
Lepra
Newbie
Offline
Activity: 48
Merit: 0
|
|
March 21, 2016, 03:31:01 AM |
|
Hi all, can I have a little help with with problem? Simple question: Is there way to use my wallet (wallet, keys files) created with - bitmonero wallet v0.8.8.4-771b531, and if have way how? Thanks in advance
|
|
|
|
parker928
|
|
March 21, 2016, 04:07:11 AM |
|
@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
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
March 21, 2016, 04:30:59 AM |
|
@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.
|
|
|
|
parker928
|
|
March 21, 2016, 05:07:06 AM |
|
@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...
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
March 21, 2016, 05:41:31 AM Last edit: March 21, 2016, 07:49:02 AM by smooth |
|
@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
|
|
|
|
explorer
Legendary
Offline
Activity: 2016
Merit: 1259
|
|
March 21, 2016, 08:08:30 AM |
|
bitmonerod .9.2 status tells me 'update required'. getmonero.org has only .9.1 available, and I've seen nothing posted here. Rumor has it there is supposed to be an update later today, just wondering if it is released already.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
March 21, 2016, 08:16:07 AM |
|
bitmonerod .9.2 status tells me 'update required'. getmonero.org has only .9.1 available, and I've seen nothing posted here. Rumor has it there is supposed to be an update later today, just wondering if it is released already.
The update required message is kind of a bug. It is based on the planned hard fork date, but your version is new enough for the hard fork anyway so the message is wrong. Anyway, the minor release is still scheduled for today but not up yet.
|
|
|
|
mangox
|
|
March 21, 2016, 12:07:11 PM |
|
I smell a pump and dump
|
|
|
|
mangox
|
|
March 21, 2016, 12:20:59 PM |
|
We already 0.0035btc Sorry ..
|
|
|
|
|
gaba
|
|
March 21, 2016, 12:30:21 PM |
|
Is everything in order for 1000 USD Monero Party
|
LWWE6dtTUXuaq36KTCne5XqMQHfhfwpadC
|
|
|
yang5034
|
|
March 21, 2016, 01:53:23 PM |
|
use transfer 0 for 200xmr to poloniex.com ,fee is 0.4 xmr,does that too high?
|
|
|
|
pönde
|
|
March 21, 2016, 02:06:33 PM Last edit: March 21, 2016, 02:28:33 PM by pönde |
|
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?
|
|
|
|
TaurusBit
Full Member
Offline
Activity: 183
Merit: 100
TaurusBit.com Administrator
|
|
March 21, 2016, 02:27:01 PM |
|
Having syncing issues after upgrading to v0.9.2.0 2016-Mar-20 23:43:41.271806 [P2P1][94.174.0.11:18080 OUT]Sync data returned unknown top block: 1005891 -> 1006093 [202 blocks (0 days) behind] SYNCHRONIZATION started 2016-Mar-20 23:44:01.504725 [P2P5]Failed to add block blob to db transaction: MDB_KEYEXIST: Key/data pair already exists 2016-Mar-20 23:44:01.504857 [P2P5]ERROR /DISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:2716 Error adding block with hash: <b3131cfdc3a3d971ef20ea4e8872ddf85b46bd459964f0ebdd805f58b58602c8> to blockchain, what = Failed to add block blob to db transaction: MDB_KEYEXIST: Key/data pair already exists
|
|
|
|
nioc
Legendary
Offline
Activity: 1624
Merit: 1008
|
|
March 21, 2016, 02:50:27 PM |
|
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.
|
|
|
|
pönde
|
|
March 21, 2016, 03:00:44 PM |
|
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?
|
|
|
|
parker928
|
|
March 21, 2016, 03:41:00 PM |
|
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
|
|
March 21, 2016, 03:41:55 PM |
|
@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?
|
|
|
|
|