Project: Raspberry Pi (and other ARM SBC) BitShares2.0 images and repositories

[warmach]

pi@raspberrypi:~$ witness_node
2903143ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
2903737ms th_a       thread.cpp:95                 thread               ] name:p2p tid:3051082832
2904252ms th_a       application.cpp:127           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:59175
2904272ms th_a       thread.cpp:95                 thread               ] name:ntp tid:3023819856
2904276ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
2904280ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
2904285ms th_a       main.cpp:166                  main                 ] Chain ID is 3a5fd421c8af8d9d6f0e5b70f00c1756c8b1609083196a0ef82e395c5e8f480e
2904283ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
2904317ms ntp        ntp.cpp:81                    request_now          ] sending request to 202.112.29.82:123
2904365ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 202.112.29.82:123
2904369ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: 10573019371415, round_trip_delay 47986
2904373ms ntp        ntp.cpp:181                   read_loop            ] NTP time and local time vary by more than a day! ntp:2015-10-24T08:45:23 local:2015-06-23T23:48:24
3204321ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
3204333ms ntp        ntp.cpp:81                    request_now          ] sending request to 202.118.1.130:123
pi@raspberrypi:~$ witness_node
2903143ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
2903737ms th_a       thread.cpp:95                 thread               ] name:p2p tid:3051082832
2904252ms th_a       application.cpp:127           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:59175
2904272ms th_a       thread.cpp:95                 thread               ] name:ntp tid:3023819856
2904276ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
2904280ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
2904285ms th_a       main.cpp:166                  main                 ] Chain ID is 3a5fd421c8af8d9d6f0e5b70f00c1756c8b1609083196a0ef82e395c5e8f480e
2904283ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
2904317ms ntp        ntp.cpp:81                    request_now          ] sending request to 202.112.29.82:123
2904365ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 202.112.29.82:123
2904369ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: 10573019371415, round_trip_delay 47986
2904373ms ntp        ntp.cpp:181                   read_loop            ] NTP time and local time vary by more than a day! ntp:2015-10-24T08:45:23 local:2015-06-23T23:48:24
3204321ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
3204333ms ntp        ntp.cpp:81                    request_now          ] sending request to 202.118.1.130:123

I get this same thing.  It just sits there without downloading  anything.   Does the Pi have enough RAM to run this?  My windows machine uses 1GB to run a node.

[iHashFury]

Hey,

I followed this instructions and it worked...

Now, to connect the wallet to my local node, do I just put ws://127.0.0.1:8090 as the api connection? or do I have to do something more?

Yes if you are using 1 computer - start your node with

Code Select Expand

witness_node --rpc-endpoint "127.0.0.1:8090"
and connect the api

Code Select Expand

ws://127.0.0.1:8090 in the light client



If you have a node on a Pi and connect the light wallet from another computer

Code Select Expand

witness_node --rpc-endpoint "0.0.0.0:8090" for Pi and connect the api

Code Select Expand

ws://<Pi-ip-address>:8090 in the light client on other computer

[hcf27]

Hey,

I followed this instructions and it worked...

Now, to connect the wallet to my local node, do I just put ws://127.0.0.1:8090 as the api connection? or do I have to do something more?

[iHashFury]

Can I run anything useful on my Raspberry Pi3 now that we've migrated to bitshares 2.0  ?

You could test out my instruction's https://bitsharestalk.org/index.php/topic,21480.msg279541.html#msg279541 ( skip the VirtualBox stuff as it only for Windoze users  :P )

You may be effected by this issue https://github.com/cryptonomex/graphene/issues/568 on arm processors.

[xeroc]

You can run a trading bot there .. and if it also runs the witness node, then you can have it be faster ..
if you open up the witness' p2p port to the internet, it could server as a public API similar to openledger

[JonnyB]

Can I run anything useful on my Raspberry Pi3 now that we've migrated to bitshares 2.0  ?

[yjzll]

pi@raspberrypi:~$ witness_node
2903143ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
2903737ms th_a       thread.cpp:95                 thread               ] name:p2p tid:3051082832
2904252ms th_a       application.cpp:127           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:59175
2904272ms th_a       thread.cpp:95                 thread               ] name:ntp tid:3023819856
2904276ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
2904280ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
2904285ms th_a       main.cpp:166                  main                 ] Chain ID is 3a5fd421c8af8d9d6f0e5b70f00c1756c8b1609083196a0ef82e395c5e8f480e
2904283ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
2904317ms ntp        ntp.cpp:81                    request_now          ] sending request to 202.112.29.82:123
2904365ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 202.112.29.82:123
2904369ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: 10573019371415, round_trip_delay 47986
2904373ms ntp        ntp.cpp:181                   read_loop            ] NTP time and local time vary by more than a day! ntp:2015-10-24T08:45:23 local:2015-06-23T23:48:24
3204321ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
3204333ms ntp        ntp.cpp:81                    request_now          ] sending request to 202.118.1.130:123
pi@raspberrypi:~$ witness_node
2903143ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
2903737ms th_a       thread.cpp:95                 thread               ] name:p2p tid:3051082832
2904252ms th_a       application.cpp:127           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:59175
2904272ms th_a       thread.cpp:95                 thread               ] name:ntp tid:3023819856
2904276ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
2904280ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
2904285ms th_a       main.cpp:166                  main                 ] Chain ID is 3a5fd421c8af8d9d6f0e5b70f00c1756c8b1609083196a0ef82e395c5e8f480e
2904283ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
2904317ms ntp        ntp.cpp:81                    request_now          ] sending request to 202.112.29.82:123
2904365ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 202.112.29.82:123
2904369ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: 10573019371415, round_trip_delay 47986
2904373ms ntp        ntp.cpp:181                   read_loop            ] NTP time and local time vary by more than a day! ntp:2015-10-24T08:45:23 local:2015-06-23T23:48:24
3204321ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
3204333ms ntp        ntp.cpp:81                    request_now          ] sending request to 202.118.1.130:123

[yjzll]

http://pan.baidu.com/s/1gdIx8xP
20150814_bitshares_raspbian.zip

[maqifrnswa]

package updated

[maqifrnswa]

Package updated, to get it:

Code Select Expand

apt-get update
apt-get upgrade
both package and repository  are gpg signed, apt will automatically check md5 sums and signatures for you

[maqifrnswa]

...I get a Segmentation fault (core dumped)...

for those that want debugging symbols,

Code Select Expand

apt-get install graphene-dbg

[iHashFury]

what's your witness node saying? does it load the key? is the new witness id appearing somewhere?

witness node loads the key "id": "1.6.10" and its in the get_global_properties but when the time comes to produce a block I get a Segmentation fault (core dumped) and details of my witness are not on the chain on restart.

So its too soon for mere mortals like me.

[xeroc]

I have the basic witness node running with the 10 defaunt witnesses.

But when I add another after the 10 min 'next_maintenance_time' and restart - it does not recognise the new witness

you need to
a) add the private key and
b) the witness-id to the configutration
c) upvote your own delegate and
d) wait for the maintenance interval

what's your witness node saying? does it load the key? is the new witness id appearing somewhere?

Code Select Expand

GRAPHENE_DEFAULT_MAINTENANCE_INTERVAL in libraries/chain/include/graphene/chain/config.hpp to, say, 10 minutes.

Also

Code Select Expand

--seed-node to connect another computer - it ends up on a different chain

I have been using:
https://github.com/cryptonomex/graphene/wiki/CLI-Wallet-Cookbook
https://bitshares.org/blog/2015/08/04/howto-become-a-witness/#bitshares-20-network-or-graphene-testnet

I know a little knowledge can be dangerous but its only a test net so who has the know-how to coordinate this?

There is no public testnet yet .. I appologize for not stating it properly in the howto ..
for that reason I moved the howto over to the graphene wiki on github!

The howto though is still valid and I expect a public testnet to appear rather soon ...

Familiarize yourself with the progress of becoming a witness node and prepare for the testnet accordingly.

[iHashFury]

I have the basic witness node running with the 10 defaunt witnesses.

But when I add another after the 10 min 'next_maintenance_time' and restart - it does not recognise the new witness

Code Select Expand

GRAPHENE_DEFAULT_MAINTENANCE_INTERVAL in libraries/chain/include/graphene/chain/config.hpp to, say, 10 minutes.

Also

Code Select Expand

--seed-node to connect another computer - it ends up on a different chain

I have been using:
https://github.com/cryptonomex/graphene/wiki/CLI-Wallet-Cookbook
https://bitshares.org/blog/2015/08/04/howto-become-a-witness/#bitshares-20-network-or-graphene-testnet

I know a little knowledge can be dangerous but its only a test net so who has the know-how to coordinate this?

[phillyguy]

Could we collaborate and start a mini graphene arm test net in this thread (or  a new thread)?

I have been trying to start a test net with lafona using the CLI Wallet Cookbook but I think we are on different chains.

Lets see if these little computers can keep up with MasterCard  :P

I have the basic witness node running, but I'm at the point where I need to follow the instructions Xeroc posted the other day for a Witness in 2.0 that processes and signs blocks...I don't have the technical understanding at the command line level to do it on my own with confidence. If someone doesn't mind holding my hand a little, I definitely have some time I can contribute to this though, and would definitely like to learn.