Lotus from Blurt's rpi image

in lotus •  3 years ago  (edited)

Lotus has really been for me, about getting out of the way and putting tools in other people's hands.

And frankly that's been tough, it is a good deal harder than just building the tech.

But, here are the Pi images:

https://megadrive.blurt.foundation/cryptopie/

that image has starport on it and you can flash it with balena etcher: https://etcher.io

after you flash the image to a microsd card with etcher, you can ssh into the pi with the username and password root (user is root pass is root; change it after booting :) with the command passwd).

from there, you can test starport:

starport network chain create lotus https://github.com/babyblockchains/lotus

Someone may have already done the create step, that makes them the coordinator. To check you'd:

starport network chain list

and see if there is a lotus there.

If there is, you might:

starport network chain join lotus

the next question is if the p2p network comes to life :D!

@megadrive

here ya go :)

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE BLURT!
Sort Order:  
  ·  3 years ago  ·  

@jacobgadikian with the last Image from 15th of June:

sperror.png

Pleasure to see a new image cryptopie-2021-07-01-09:22:55, but then unfortunately frustrating.

1.) startport, same error as previous images.

2.) blurtd aborts with error:
The transaction status plugin state does not contain tracking information for the last 64000 blocks. Re-run with the command line argument '--transaction-status-rebuild-state'.

and runs after:

docker rm blurtd
docker run -d --net=host -v blurtd:/blurtd --restart=unless-stopped --name blurtd faddat/arm-blurt-presync /usr/bin/blurtd --data-dir /blurtd --plugin "witness account_by_key account_by_key_api condenser_api database_api network_broadcast_api transaction_status transaction_status_api rc_api" --transaction-status-rebuild-state


It gets a bit tight on a 64GB SD card:

My heartfelt thanks for testing and providing screenshots.

I think I can solve this.

  ·  3 years ago  ·   (edited)

Same result as @dotwin1981


Important: This image starts with blurt 0.2.0

Once blurtd is started, it should be stopped with docker stop blurtd CPU will otherwise run permanently at 100%.

  ·  3 years ago  ·  

Das Presync Image (faddat/arm-blurt-presync) ist noch vom Februar.
Wenn du den Blurt Teil vom Image nutzen willst, ändere die "firstboot.sh" im Ordner "\usr\local\bin" auf der frisch geflashten SD-Karte bevor sie zum ersten mal im Pi eingelegt wird zu:

#!/bin/bash

# Set Time Zone
# Later, make this automatic based on location.
timedatectl set-timezone UTC

# mdns
systemd-resolve --set-mdns=yes --interface=eth0

# Don't run again
systemctl disable firstboot
sleep 180
docker volume create blurtd
wget -c http://www.dotwin1981.de/backup/blockchain.tar.xz -O - | tar -xJ -C /var/lib/docker/volumes/blurtd/
docker run -d --net=host -v blurtd:/blurtd --restart=unless-stopped --name blurtd registry.gitlab.com/blurt/blurt/megadrive:dev /usr/bin/blurtd --data-dir /blurtd --plugin "witness account_by_key account_by_key_api condenser_api database_api network_broadcast_api transaction_status transaction_status_api rc_api"

Damit geht die Blurt Node zumindest schon einmal. Aber das ändert nichts an dem wohl noch bestehenden Problem vom Lotus.

  ·  3 years ago  ·  

Hi, @jacobgadikian,
great post