 Show Posts
|
|
Pages: [1]
|
My xmixer & rpc wallet are running ok, i do have some 'downtime' where its behind a some blocks. But without any action on my site it will catch up after max 30min. eg: got 24/7 logs on this coz am still crawling the blockchain.
But have to agree it is slower atm than it used to be
Thanks for the input. I've been stuck at block 192036 for almost 2 days now. Repeatedly restarting the app doesn't help. Deleting everything in the XCurrency folder besides wallet.dat produces similar results - the blockchain will sync, then stall out. Then I restart the app and it syncs a little more then stalls out. I can get it all the way back to block 192036, but it won't sync past that block for me even with a fresh sync. The end of my debug log looks like this: ProcessBlock: ORPHAN BLOCK, prev=002a42202a6486ad1b0b
received block b7ca4ec6a8874f285070
ProcessBlock: ORPHAN BLOCK, prev=2a1e090037eb92284ea7
received block 3e0e283c332833d3a187
ProcessBlock: ORPHAN BLOCK, prev=b7ca4ec6a8874f285070
received block e27c4177d424d45a3660
ProcessBlock: ORPHAN BLOCK, prev=de50318c3f81aeedac6a
received block de50318c3f81aeedac6a
ProcessBlock: ORPHAN BLOCK, prev=61687da273ae0c18e22f
received block 61687da273ae0c18e22f
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 02777a20faee3771271b52e21df3881a9db86d982edaf6e1036db633b1526d34, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 61687da273ae0c18e22f8af12572ab7dc692bc4e375f8ebde94ea69b6c0a59ab
connection timeout
trying connection 103.6.189.110:32348 lastseen=438.9hrs
connection timeout
trying connection 192.76.27.225:32348 lastseen=300.6hrs
connection timeout
trying connection 72.15.62.103:32348 lastseen=11.8hrs
connect() failed after select(): Connection refused
trying connection 188.24.147.6:32348 lastseen=489.3hrs
ProcessSyncCheckpoint: pending for sync-checkpoint 822a59a1db13dd7f1a343f8059a147b65433b5f546824dd149bc4f9081479272
ProcessSyncCheckpoint: pending for sync-checkpoint 822a59a1db13dd7f1a343f8059a147b65433b5f546824dd149bc4f9081479272
ProcessSyncCheckpoint: pending for sync-checkpoint 822a59a1db13dd7f1a343f8059a147b65433b5f546824dd149bc4f9081479272
received block a2d3b6c58ecf2df54db7
ProcessBlock: ORPHAN BLOCK, prev=9410d79a52c6e286dde0
received block 822a59a1db13dd7f1a34
ProcessBlock: ORPHAN BLOCK, prev=3eba8fd47d44c25d648f
received block 4806753e45fafd19ccdd
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 0f7d218e154506c3bcdf2bca9b27f675d3066288138c72bf540eaa7771bd0b1d, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 4806753e45fafd19ccdd9a0db555883669ccc4f99b76a60e9c289c92dbbf62f0
connection timeout I had a similar problem last night (EST US). wallet on main pc (mac) syncing ok, but the one on notebook (also mac) was stuck at 192477. Tried deleting everthing except wallet.dat several times. Then after about the third time of reloading, the notebook came back into sync. Still ok this morning. Had a lot (16) of "generated but not accepted" transactions, but prior to resyncing, these transactions had anywhere from 1 to 16 confirmations. Then after resyncing, everything was "not accepted" ? |
|
|
|
My blocknet wallet will not sync past 82% anyone else having this problem? If so can you point me in a direction to help?
Yes I had this issue. Essentially it was a bad chain. Backed up my wallet.dat file, and the full folder. Reinstall the QT again then move your wallet back. Worked fine for me after that. Yes mostly always helps after system crash or some file system errors , good to have your wallet backed up on daily basis too  Apologies; I used the wrong quote. Above is what I was referring to. thanks |
|
|
|
Good to see it at last above the previous article That's not good enough for me. The first article has already done irreparable damage . They should pull the first article and publicly apologize for it. I see they removed it from the main site , asked them too to remove the tweet I had a similar problem; got out of sync and could never catch up. So I closed wallet saved the wallet.dat file & deleted blocknet folder. Then ran blocknet app and it seemed to work ok but didn't active connections to network. I then installed the backup wallet.dat file and opened app again. Still no active connections yet my network is ok for XC app and other internet. In Transactions menu, my original buy of Block is shown along with the mined block except the mined are shown as 'generated buy not accepted'. In Overview tab, Spendalbe is shown as 0.00. What should I do? |
|
|
|
Someone please give me 3 reasons to turn some of my XC into Blocknet tomorrow. Or, if you prefer, give me 3 reasons not to. Thanks.
Anyone? One blocknet share cost around .002 btc. One XC coin cost around .007 BTC at this moment, that means you get a little more 3 blocknet shares per 1 XC. Do the math The latest XC cost is closer to .0007 btc, not .007. Not sure about ratio of blocknet to btc, but if .002 is correct then you only get 0.35 blocknet shares per XC |
|
|
|
I'm off to bed, but I'd like to ask:
Who's had any issues with the latest wallet releases?
Version 2.49.08 on Windows, Mac and Linux.
Seriously. If there are any issues outstanding, we want to straighten them out pronto.
Still don't have Coin Control for the Mac; don't know about Linux Coin control is available on the Mac xc client. Not sure what version your using but perhaps you need an upgrade? I downloaded the latest version on XC website which was: XCurrency-qt-08 prod.dmg. When I open that up the "About XCurrency" shows the id as XCurrency version v0.9.2.49.08.XCurrency-Rev2. There is no 'options' under the settings menu as in Windows and on 'Send coins' button, no coin control. Is there a later version somewhere else or am I missing something else X-Currency-qt/Preferences.../Display/Display coin control features (experts only!) My mistake; I see. Thanks! |
|
|
|
I'm off to bed, but I'd like to ask:
Who's had any issues with the latest wallet releases?
Version 2.49.08 on Windows, Mac and Linux.
Seriously. If there are any issues outstanding, we want to straighten them out pronto.
Still don't have Coin Control for the Mac; don't know about Linux Coin control is available on the Mac xc client. Not sure what version your using but perhaps you need an upgrade? I downloaded the latest version on XC website which was: XCurrency-qt-08 prod.dmg. When I open that up the "About XCurrency" shows the id as XCurrency version v0.9.2.49.08.XCurrency-Rev2. There is no 'options' under the settings menu as in Windows and on 'Send coins' button, no coin control. Is there a later version somewhere else or am I missing something else |
|
|
|
I'm off to bed, but I'd like to ask:
Who's had any issues with the latest wallet releases?
Version 2.49.08 on Windows, Mac and Linux.
Seriously. If there are any issues outstanding, we want to straighten them out pronto.
Still don't have Coin Control for the Mac; don't know about Linux |
|
|
|
Synechist: Regarding your op announcement (So, there's a new OP...):
Under the section "XCHAT MESSAGE PROCESS", step 3), recommend the following change for clarity:
change from: ".....encrypts a packet containing his/her public key and sends to user B."
to: ".....encrypts a packet using user B's public key and sends to user B."
My first impression was that that step 3 implied it was (or could be interrupted as) user A's public key. It's only when you get to step 4 that it becomes clear that it's user B's public key being used to encrypt the packet.
Nice one. Yes. Though it'll need to be "user A encrypts a packet that contains his/her public key, using user B's public key." Yes, that's better |
|
|
|
|
Synechist: Regarding your op announcement (So, there's a new OP...):
Under the section "XCHAT MESSAGE PROCESS", step 3), recommend the following change for clarity:
change from: ".....encrypts a packet containing his/her public key and sends to user B."
to: ".....encrypts a packet using user B's public key and sends to user B."
My first impression was that that step 3 implied it was (or could be interrupted as) user A's public key. It's only when you get to step 4 that it becomes clear that it's user B's public key being used to encrypt the packet.
|
|
|
|
I have XC client in a win7 and mac pc. I sent 20 XC from the mac client to win7 client. Everything is ok; balance on mac reduced by 20 XC plus small fee and balance in win7 increased by 20 XC. However, i can't see where the 20 XC came from (which address) on the mac client. The "show transaction details" only shows where the XC went, not where it came from. How do I find out which XC address the 20 XC came from? Is is necessary to have coin control operational (not yet in mac) or is there something else I'm missing. Also, will XChat update for mac be in Rev 2 for 9/15 or for later Rev 2.5. thanks
Hi hi You can specify which address a payment comes from by using coin control. After the payment's made you'll need to use a block explorer to identify the address sent from. Check out the OP for a block explorer. If you made a private payment, block explorers (and anything at all) won't help you. ;-) I don't use Mac. Is XChat on Mac working for anyone else here? Ok, thanks; that make sense. But when will coin control be included in the mac client Last I tried (which was a few weeks ago), XChat doesn't work on Mac. Just heard from Dan. It'll be working sometime before Rev 2.5. Sorry I can't give you a more precise ETA at the moment. We're pretty busy getting the finalised Rev 2 ready for Monday. Ok, thanks |
|
|
|
I have XC client in a win7 and mac pc. I sent 20 XC from the mac client to win7 client. Everything is ok; balance on mac reduced by 20 XC plus small fee and balance in win7 increased by 20 XC. However, i can't see where the 20 XC came from (which address) on the mac client. The "show transaction details" only shows where the XC went, not where it came from. How do I find out which XC address the 20 XC came from? Is is necessary to have coin control operational (not yet in mac) or is there something else I'm missing. Also, will XChat update for mac be in Rev 2 for 9/15 or for later Rev 2.5. thanks
Hi hi You can specify which address a payment comes from by using coin control. After the payment's made you'll need to use a block explorer to identify the address sent from. Check out the OP for a block explorer. If you made a private payment, block explorers (and anything at all) won't help you. ;-) I don't use Mac. Is XChat on Mac working for anyone else here? Ok, thanks; that make sense. But when will coin control be included in the mac client Last I tried (which was a few weeks ago), XChat doesn't work on Mac. |
|
|
|
|
I have XC client in a win7 and mac pc. I sent 20 XC from the mac client to win7 client. Everything is ok; balance on mac reduced by 20 XC plus small fee and balance in win7 increased by 20 XC. However, i can't see where the 20 XC came from (which address) on the mac client. The "show transaction details" only shows where the XC went, not where it came from. How do I find out which XC address the 20 XC came from? Is is necessary to have coin control operational (not yet in mac) or is there something else I'm missing. Also, will XChat update for mac be in Rev 2 for 9/15 or for later Rev 2.5. thanks
|
|
|
|
|
Are there plans to update the mac client to include coin control (which only seems to be in windows client)? Or is this no longer needed? thanks
|
|
|
|
I'm new to XC. Have Mac client on my pc and wife's pc. We exchanged addresses/pubkeys but when we try to send msg, we get error msg: "message encryption failed". Is this due to known bug in Xchat or is it something I may be missing? I have 710 XC in my client, wife has zero right now. thanks
This is a bug within the Mac wallet only. Dan is aware of it and we've been told it'll be fixed with the next release I believe. If you want to try out XChat right now on a Mac, you'll have to set up a TORstick using the latest .ISO. Understand, thanks |
|
|
|
I'm new to XC. Have Mac client on my pc and wife's pc. We exchanged addresses/pubkeys but when we try to send msg, we get error msg: "message encryption failed". Is this due to known bug in Xchat or is it something I may be missing? I have 710 XC in my client, wife has zero right now. thanks
If you are both on the same internal network (home network) that won't work as it goes out to other nodes to be mixed and tries to connect to the client coming back in. I just tried sending XChat msg to your addr/pubkey and I get the same error message? |
|
|
|
I'm new to XC. Have Mac client on my pc and wife's pc. We exchanged addresses/pubkeys but when we try to send msg, we get error msg: "message encryption failed". Is this due to known bug in Xchat or is it something I may be missing? I have 710 XC in my client, wife has zero right now. thanks
If you are both on the same internal network (home network) that won't work as it goes out to other nodes to be mixed and tries to connect to the client coming back in. Yes, we are on the same network; thanks. Can I try Xchat with you? address: XKKqf2xpvLiRiiBLaZXkEtL6dUjPvYsPby PubKey: pJSebmE2j79qsn5XHf1mzrN4Y7AsmUivktJt46sD2f4B |
|
|
|
|
I'm new to XC. Have Mac client on my pc and wife's pc. We exchanged addresses/pubkeys but when we try to send msg, we get error msg: "message encryption failed". Is this due to known bug in Xchat or is it something I may be missing? I have 710 XC in my client, wife has zero right now. thanks
|
|
|
|
|
