Summary: Raspberry Pi (RPI) and other single-board-computers (SBCs) could be good platforms for distributed, low-power, low-cost witness nodes in BitShares2.0. A convenient way of getting BiShares2.0 on RPIs, especially for those just learning RPI or BitShares, will aid adoption and help the network. This project is looking at ways to simplify access to BitShares2.0 through RPI disk images and repositories.

For CubieBox and archlinux, see https://bitsharestalk.org/index.php/topic,17297.msg220456.html#msg220456

---

Three ways to get it:

1) Download our Raspbian Jessie minimal server preconfigured for graphene and will update graphene when you run "apt-get update && apt-get upgrade":
https://www.dropbox.com/s/qzeeqnhbngoqo99/20150814_bitshares_raspbian.zip?dl=0
$ md5sum 20150814_bitshares_raspbian.zip
9bad200938d32531f5f0c341e5ea482e  20150814_bitshares_raspbian.zipSee "SD card image based on Raspbian Jessie is available for initial testing" below.

OR

2) Download a Raspbian Jessie distribution (such as http://sirlagz.net/2013/07/19/raspbian-server-edition-2-5/) then follow the instructions for "Rapsbian Jessie PPA" below.

OR

3) Upgrade your Raspbian Wheezy to Jessie and then follow the instructions for "Rapsbian Jessie PPA" below:
a) Download and install Raspbian (https://www.raspberrypi.org/documentation/installation/installing-images/README.md)
b) Make sure you're up to date
apt-get update
apt-get upgradec) Optionally remove packages you don't need to speed up the upgrade (e.g., if you're a server and don't care about -dev packages)
apt-get remove  --auto-remove --purge libx11-.* .*-devd) Upgrade to Jessie
sed -i 's/wheezy/jessie/g' /etc/apt/sources.list
find /etc/apt/sources.list.d -type f -exec sed -i -e 's/wheezy/jessie/g' {} \;
apt-get update
apt-get dist-upgrade -o Dpkg::Options::="--force-confold"e) Follow the steps for "Rapsbian Jessie PPA" below

OR

Undocumented, untested 4th way: apt-pin so that you can install packages from Jessie if they are missing from wheezy.

---

Rapsbian Jessie PPA:

As super user or root, grab the archive key and add the repository
sudo wget -O - http://people.debian.org/~showard/raspbian/bitshares_repo.gpg.key | sudo apt-key add -
sudo sh -c 'echo "deb  http://people.debian.org/~showard/raspbian/ jessie main bitshares\ndeb-src http://people.debian.org/~showard/raspbian/ jessie main bitshares" > /etc/apt/sources.list.d/bitshares.list'

Install graphene
apt-get update
apt-get install graphene
4) you now have two new binaries to use, "witness_node" and "cli_wallet"

---

SD card image based on Raspbian Jessie is available for initial testing.

disk image resize doesn't work, but you still have 500 MB to work with for testing

Please test the image and be a pioneer!
What you need:

• a RPI or RPI2
• an SD card > 2.2 GB
• a connection to the internet for the RPI
• another computer on your network to log in to the RPI, or a monitor and keyboard to log in to the RPI

Step one:
Download the image from the link at the top of the post

Step two:
Follow the instructions on how to install the downloaded image on an SD card. Depending on your OS, you can find instructions here:
https://www.raspberrypi.org/documentation/installation/installing-images/README.md

Step three:
a) ADVANCED: Plug in your RPI to your network and plug in to power. If you know how to do SSH already, and know how to find the RPI's IP address, you can just log in with the user name "pi" and "raspberry" as the password. Go to step four.
b) BEGINNER: Plug in a a keyboard and monitor to the RPI. Plug in your RPI to your network, then plug in to power.
Login with the following information when prompted:
Username: pi
Password: raspberry

then type ifconfig in to the terminal

write down the INET address of eth0, should look like:
inet addr:192.168.1.2 or something like that.

you can type "exit" to return to the log in screen. You don't need the keyboard or mouse any more.

Step four:
Log in to the RPI using another computer on your network:
linux/macosx (use the inet address from above)
ssh pi@192.168.1.2windows (use the inet address from above)
https://www.raspberrypi.org/documentation/remote-access/ssh/windows.md

Step five:
Change your password:
ADVANCED: https://www.raspberrypi.org/documentation/linux/usage/users.md
BEGINNER:
1) type "sudo rasp-config" in to the terminal
2) choose "Change User Password" and follow the prompts

Step six (might not work at the moment, and is optional):
Expand your disk so you can use the whole thing:
1) type "sudo rasp-config" in to the terminal
2) choose "Expand Filesystem" and follow the prompts

step seven:
Check out bitshares.
To make sure you're running the latest graphene:
apt-get update
apt-get upgrade[/quote]
"witness_node" and "cli_wallet" are both in the PATH - so just type those commands and it will work
See https://github.com/cryptonomex/graphene
on how to use them for now

step eight:
update with "apt-get update" then "apt-get upgrade". If I put a new version online, it will pull in the new version without having to get a new image

I just wanted to check the purpose of:
https://github.com/BitShares/bitshares/commit/b0efbee1b6d96f07b04788d9df85b7bd9161239d

Is it required for make, but not for regular use? Why is it required for make? thanks

http://www.sec.gov/news/pressrelease/2015-49.html
http://www.coindesk.com/sec-crowdfunding-ruling-revolutionary/

no longer need to only sell to qualified investors, eases rules for selling securities. Probably not related to bitshares directly, although someone could list registered securities on bitshares (but then would the bitshares network need to be registered as an exchange?)

Got this while trying to build the most recent release:

/home/showard/bitcoin/bitsharesx/libraries/cli/pretty.cpp: In function ‘std::string bts::cli::pretty_timestamp(const fc::time_point_sec&)’:
/home/showard/bitcoin/bitsharesx/libraries/cli/pretty.cpp:29:36: error: ‘const class fc::time_point_sec’ has no member named ‘to_iso_extended_string’
       return "<d-ign>" + timestamp.to_iso_extended_string() + "</d-ign>";
                                    ^
/home/showard/bitcoin/bitsharesx/libraries/cli/pretty.cpp:30:22: error: ‘const class fc::time_point_sec’ has no member named ‘to_iso_extended_string’
     return timestamp.to_iso_extended_string();

I'm trying to do an out-of-tree build:
mkdir -p obj-x86_64-linux-gnu
cd obj-x86_64-linux-gnu
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DINCLUDE_QT_WALLET=ON -DCMAKE_INSTALL_PREFIX=/usr/bi
But get:
make[3]: *** No rule to make target `programs/qt_wallet/images/splash_screen.jpg', needed by `programs/qt_wallet/qrc_bitshares.cpp'.  Stop.

and programs/qt_wallet/images/splash_screen.jpg is found in tree but not in:
obj-x86_64-linux-gnu/programs/qt_wallet/images/splash_screen.jpg

thanks

Now that feeds are important, delegates have to pay 0.5BTSX periodically throughout the day for each currency.

The average delegate is making 85.5 * 2.3 * .86 =169.2 BTSX per day. My delegate is making 29.5 BTSX per day, which is enough to pay for the server. However, if the network needs accurate feeds for BTC, CNY, USD (1.5BTSX per feed update), I'll have to operate at a loss. I set my pay rate not knowing about this expense (and to my own fault, I assumed the pay rate market would be free).

This becomes prohibitive if more feeds are required.

Would either of these be possible? (For now I'll just override the minimum fee)

There seems to be some confusion over how fees work, so I think it could be a good to describe it in one place. If it is already explained somewhere, please let me know and I can put a link in place of this post! NOTE: the numbers are not consistent since I pulled them across different blocks, but they are close. Also, these are the fees as of 8/5/2014. They may change.

When you perform a blockchain operation (e.g., register an account or register an asset), you pay fees. Before paying the delegate, your feels are added to a running total of fees to be paid out. You can see the total running fees that still have to be paid out here:
"blockchain_accumulated_fees": "122,421.75559 BTSX"

Once the fees are added to "blockchain_accumulated_fees", the delegate producing a block will get paid the following fee:
blockchain_delegate_pay_rate=specific_delegate_percentage_pay_rate * blockchain_delegate_pay_rate
where
blockchain_delegate_pay_rate = blockchain_accumulated_fees/(number_of_blocks_produced_in_two_weeks)

the rest of the fees are destroyed and blockchain_delegate_pay_rate is the pay rate when a delegate has a 100% pay rate. This smooths out large investments such as registering assets. The current maximum pay, that is when a delegate as a 100% pay rate, can be seen with the console command get_info:
"blockchain_delegate_pay_rate": "1.01193 BTSX"

Delegate registration fees are equal to:
(blockchain_delegate_pay_rate * number_of_blocks_produced_in_two_hours)/number_of_delegates

That means that a delegate breaks even if they are a delegate for two hours with 100% pay rate.

This can be seen with "blockchain_get_info" console command:
"delegate_reg_fee": "7.20891 BTSX"

Asset registration fees are based on the total fees delegates should receive over a two week time, which (at this moment) is the same as "blockchain_accumulated_fees" and can be seen with the command "blockchain_get_info":
"asset_reg_fee": "122,320.80000 BTSX"

Hopefully this clears up some of the misconceptions and helps the discussion going forward!

Hello all, to make it easier for people, this is all you need to install bitshares:

$ sudo apt-add-repository ppa:showard314/bitshares
$ sudo apt-get update
$ sudo apt-get install bitshares
If you want the command line interface only (CLI, e.g. if you are running a headless server):
$ sudo apt-get install bitshares-cliinstead of
$ sudo apt-get install bitshares
You will then have a bitshares icon in your application search (dash) or from command line:
$ BitSharesand/or the CLI:
$ bitshares_client
all the utilities are installed as well, but if they're not needed I can cut them out for space later.

Service of:
https://bitsharestalk.org/index.php?topic=5938
15% delegate: wallet_approve_delegate maqifrnswa
50% delegate: wallet_approve_delegate delegate1.maqifrnswa
(I have two since we're not allowed to raise payrates to remain competitive in the market, which I mistakenly did not know when I made the first one)

Please post bugs/problems here.

Note:
Since there are no such thing as "official" binaries any more [1], the PPA is as official as you can get. They were uploaded by a delegate, the source code used to build the packages is signed with a GPG key in the debian-keyring and is inspectable on the launchpad site. The binaries built from the GPG code are signed by with the PPA key and will be verified by apt when you download and install. This is the same system bitcoin uses for distribution, as well as mozilla, libreoffice, wine, and several others.

[1] https://bitsharestalk.org/index.php?topic=7067.msg148186#msg148186