I would like to help you make this succeed, im willing to dedicate a small amount of personal time to build you a functional site to make this work and look good, hit me up pal.

Freebie is willing to participate in this if anyone is interested

hey pal, freebie servers was first and foremost an advertisement company, we serve upwards of 20k ads a day and have various industry tricks for both the implementation of this as a business model as well as the software behind it, such as ingame videos, offerwalls for credit on our various platforms etc... i really like your idea and some of our goals align, this post is kind of old but if you havent given up please shoot freebie servers or myself a pm

im willing to write a script to help the automatic import of keys but i need an example of a file with a large amount of keys to import, if any users would like to help work with me on this it wouldnt take more than a few hours and we could help a few people with this issue, i have an idea for the approach just need to clear up the data format.

Hey guys, im posting this here because while github and the docs have all this information separately, the github is out of date and both are kind of missing steps...

so I'm gonna compile the information that got me working on this system from building the software until I imported my wallets.

this tutorial assumes your running ubuntu 14.4 64bit with at least 2 gb of ram and 40 gb hdd space.

for the record most of this is here:
http://docs.bitshares.eu/installation/Build.html
but not all of it

lets start with dependencies because we we have all been at that point in compilation where were like wait wtf is doxygen

sudo apt-get install cmake make \
                     libbz2-dev libdb++-dev libdb-dev \
                     libssl-dev openssl libreadline-dev \
                     autoconf libtool git doxygen
next up is boost,

BOOST_ROOT=$HOME/opt/boost_1_57_0
sudo apt-get update
sudo apt-get install autotools-dev build-essential \
                     g++ libbz2-dev libicu-dev python-dev
wget -c 'http://sourceforge.net/projects/boost/files/boost/1.57.0/boost_1_57_0.tar.bz2/download'\
     -O boost_1_57_0.tar.bz2
sha256sum boost_1_57_0.tar.bz2
# "910c8c022a33ccec7f088bd65d4f14b466588dda94ba2124e78b8c57db264967"
tar xjf boost_1_57_0.tar.bz2
cd boost_1_57_0/
./bootstrap.sh "--prefix=$BOOST_ROOT"
./b2 install
a really important step here, especially if your env times out or something,

BOOST_ROOT=$HOME/opt/boost_1_57_0

I started with downloading the github test version a few times by mistake, boy was this embarrassing haha, so to save you the trouble this is the version you want:

git clone https://github.com/bitshares/bitshares-2
cd bitshares-2
git submodule update --init --recursive

now your ready to install it:

cmake -DBOOST_ROOT="$BOOST_ROOT" -DCMAKE_BUILD_TYPE=Release .
make
*get a cup of coffe or something ur gonna be here a while*
make install

from here the most important thing you can do is configure your witness node, i cant tell you how vital this is!

a sample witness config:

# Endpoint for P2P node to listen on
# p2p-endpoint =

# P2P nodes to connect to on startup (may specify multiple times)
# seed-node =

# JSON array of P2P nodes to connect to on startup
# seed-nodes =

# Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints.
# checkpoint =

# Endpoint for websocket RPC to listen on
rpc-endpoint = 127.0.0.1:8090

# Endpoint for TLS websocket RPC to listen on
# rpc-tls-endpoint =

# The TLS certificate file for this server
# server-pem =

# Password for this certificate
# server-pem-password =

# File to read Genesis State from
# genesis-json =

# Block signing key to use for init witnesses, overrides genesis file
# dbg-init-key =

# JSON file specifying API permissions
# api-access =

# Enable block production, even if the chain is stale.
enable-stale-production = false

# Percent of witnesses (0-99) that must be participating in order to produce blocks
required-participation = false

# ID of witness controlled by this node (e.g. "1.6.5", quotes are required, may specify multiple times)
# witness-id =

# Tuple of [PublicKey, WIF private key] (may specify multiple times)
private-key = ["PUBLICKEYHERE","PRIVATEKEYHERE"]

# Account ID to track history for (may specify multiple times)
# track-account =

# Track market history by grouping orders into buckets of equal size measured in seconds specified as a JSON array of numbers
bucket-size = [15,60,300,3600,86400]

# How far back in time to track history for each bucket size, measured in the number of buckets (default: 1000)
history-per-size = 1000

# declare an appender named "stderr" that writes messages to the console
[log.console_appender.stderr]
stream=std_error

# declare an appender named "p2p" that writes messages to p2p.log
[log.file_appender.p2p]
filename=logs/p2p/p2p.log
# filename can be absolute or relative to this config file

# route any messages logged to the default logger to the "stderr" logger we
# declared above, if they are info level are higher
[logger.default]
level=info
appenders=stderr

# route messages sent to the "p2p" logger to the p2p appender declared above
[logger.p2p]
level=debug
appenders=p2p


note the section:
# Tuple of [PublicKey, WIF private key] (may specify multiple times)
private-key = ["PUBLICKEYHERE","PRIVATEKEYHERE"]

this should be specified with the public and private wif key of the witness you wish to enable, why or how this works I have no idea. hope you do x.x

create this with vim or nano or whatever and place it in a directory of chosing, for example 'mynode'

then start your witness, I recomend using a screen rather than its silent feature for debugging:

screen -dmS witness witness_node --data-dir="mynode"
and let it do its magic, screen -x witness to watch, ctrl +a, then d to detach.

next you have to start the cli wallet to control it,

screen -dmS wallet cli_wallet
screen -x wallet
it will prompt you for a password, enter the following commands

set_password yourpassword
unlock yourpassword
next your ready to import from the past or open ledger, this tutorial will assume your new to bts and using open ledger.

hop over to open ledger and make an account type in an 8 char password and unique username, click permissions on the left,

once here click the little key

be sure to repeate this process for each key

you will get a popup showing your WIF import key.

next go back to your wallet and type the following commands:

import_key btsact yourkey truewhere 'btsact' and 'yourkey' are the values you pulled from open ledger

you should see a report of success (or not faulure) and you can now use

list_my_accounts
and see a return of your accounts!

    "whitelisting_accounts": [],
    "blacklisting_accounts": [],
    "blacklisted_accounts": []
  },{
    "id": "1.2.96555",
    "membership_expiration_date": "1970-01-01T00:00:00",
    "registrar": "1.2.90713",
    "referrer": "1.2.90713",
    "lifetime_referrer": "1.2.90713",
    "network_fee_percentage": 2000,
    "lifetime_referrer_fee_percentage": 3000,
    "referrer_rewards_percentage": 0,
    "name": "btstip-io",
    "owner": {
      "weight_threshold": 1,
      "account_auths": [],
      "key_auths": [[
          "",
          1
        ]
      ],
      "address_auths": []
    },
    "active": {
      "weight_threshold": 1,
      "account_auths": [],
      "key_auths": [[
          "",
          1
        ]
      ],
      "address_auths": []
    },
    "options": {
      "memo_key": "",
      "voting_account": "1.2.5",
      "num_witness": 0,
      "num_committee": 0,
      "votes": [],
      "extensions": []
    },
    "statistics": "2.6.96555",
    "whitelisting_accounts": [],
    "blacklisting_accounts": [],
    "blacklisted_accounts": []
  }
]

hope i helped, ill try to monitor this thread and respond to questions.

later ill post a followup on how to install the js gui

Honestly, I think this has a lot to do with the fact that the tech isn't quite as grand as promised, I love what bitshares is doing but if the user experience was more polished from the start we would probably not be seeing such a dramatic drop, overall as we all work to improve the experience for users and administrators, lower the learning curve and increase the adaptability the price will rise again to historic levels.

If i had done a little more research this would have saved me so much time, you sir are a hero.

very cool idea ...
If you used a shorter memo, you could reduce the fee (a part of the fee is derived from the size of the operation)

dang we will keep that in mind!

thanks for the tip, have one of your own

#btstip xeroc 145