I can get it to build in Windows,  but it won't work correctly.   I just get a blank white screen.   I've got htdocs generated and placed in a child directory of the directory holding qt_ wallet. Exe.  Upon startup it builds the chain,  exceptions,  and peers directories in the data directory.   The only other file it builds is node_config.json.  as far as I can make out it is failing to call the client somewhere in the clientwrapper stage.   I'm just about the furthest thing from an expert there is though.   Does anyone know the correct directory layout under Windows for qt_ wallet to function properly?   It would save me a ton of time.

"You offered us a block that we reject as invalid"
Is this message ok?

Code: [Select]

--- there are now 26 active connections to the p2p network
--- in sync with p2p network
Peer 128.199.180.19:51811 disconnected us: You offered us a block that we reject as invalid
--- there are now 25 active connections to the p2p network
delegate (unlocked) >>> about
{
  "bitshares_toolkit_revision": "458342c24ad06f44dc46d0de0f64566f1bc8da5e",
  "bitshares_toolkit_revision_age": "13 hours ago",
  "fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
  "fc_revision_age": "65 hours ago",
  "compile_date": "compiled on Jun 15 2014 at 06:47:07"
}


I got the same error of my delegate node.  I also got a disconnect with the message "You sent me a syunc block that I didn't ask for"

The node still appears to be synced with the main chain, and producing blocks though.

Quote

Wipe your old data-dir

Ubuntu: rm -r ~/.BitShares\ XTS

This command has never done anything for me.  I feel I'm missing some implied instruction.  Anyone care to clue me in.

I've just been either completely rebuilding the server from scratch or using the following

Code: [Select]

rm -r bitshares*
and then cloneing etc.

Does this have the same effect?
I notice i still have my wallet and imported keys, where as, when building from scratch I have to re create wallet and import keys again.

# about
tells me im on the latest revision but was i supposed to remove something that "# rm -r bits*"   misses?

~/.BitShares\ XTS may be referring to an old data directory (I have noticed that the different versions I have downloaded and compiled have had slightly different data directories.  The current data dir is ~/.BitSharesXTS so the command would be

rm -r ~/.BitSharesXTS

This will wipe your wallet though.  You will need to either re-import keys or copy your wallet over to the new directory.  How I've done it is
cp -r ~/.BitSharesXTS/wallets ~
rm -r ~/.BitSharesXTS
mkdir ~/.BitSharesXTS
cp -r ~/wallets ~/.BitSharesXTS
there may be a better way of doing this.

I also currently just wipe out the bitshares_toolkit directory and git clone another one.  that is what your rm -r ~/bitshares* command was doing.  I am sure there is a better way than that to resync to git, but I don't know it.

I should be up and running.  Please remember to add my seed node with

network_add_node "95.85.33.16:8764" add
You can even write it into your config.json so it will attempt to connect at startup. 

Thats what I had to do for  the qt wallet since I can't enter commands in it.  Also I figured out how to get it to open the default wallet.  Right click on the wallet and hit reload.  Wow do I feel stupid.  I still can't get it to accept arguments when launching though.  Is that a known issue?

I know the qt wallet has rightfully taken a back burner to the network code.  I am just playing with it because I am not knowledgable enough about C++ or networking to help out in those areas.

I think I'm back on the main chain.  Actived delegates 13,14,15, and 16.  Inactive delegate puppies (I'm gonna have to change that name before this goes live.)

I've got the qt wallet compiled and running on Ubuntu.  First time I run it, it runs great.  Creates a wallet for me, and has most functions working correctly.  I had to close it due to the fork, and now I don't know how to unlock my wallet from within Qt wallet.  Does anyone know how to wallet_open in Qt client?

I've got my delegates up and creating blocks.  I also have a seed node running on 95.85.33.16:8764.  On a side note, has anyone managed to get the Qt wallet to work outside of OSX?

Now that I think about it.   How does bits xt reduce your xts holdings without your private key to accomplish the annual fee?

Sent from my SCH-I535 using Tapatalk