Hive: honeycomb-spkcc management

gistfile1.txt

This is a Decentralized Autonomous Organization built on the HIVE ecosystem.

THIS BUILD IS PASSING BUT SEVERAL FEATURES ARE UNTESTED. DO NOT RECOMMEND USING ON ACCOUNT WITH HIGH BALANCES

This software builds a network of peers that use HIVE to post and interpret transactions.
This allows these peers to come to a consensus and elect peers to run tasks.
Distributing computing in this way allows a vast amount of potential applications, DeFi, and oracle services.
By distributing authority to perform transactions we can have a frictionless(no intermediate tokens, no central authority,
no intrinsic fees) way to cross asset boundaries(HIVE/COMB) with no information asymmetries, 
ie Finance without securities by definition... just free speech: As no party is required to perfom any function,
or prevented from performing a

My notes: I'm still trying to figure out the purpose of this node layer. I wanted to support the project by running a node and being part of the community. The app layer seem to intergrate with 3speak. As I learn more about the project over time, I'll update this Gist or post on my Hive blog at https://peakd.com/@expire0


Reference links:
Official repo : https://github.com/3speaknetwork/honeycomb-spkcc
IPFS : https://github.com/ipfs/go-ipfs
Step by Step guide to setup SPK Claim chain node : https://peakd.com/hive-163521/@balaz/step-by-step-guide-to-setup-spk-claim-chain-node
SPK Monitor: https://hiveuprss.github.io/spkccmonitor/?node=https://spktoken.dlux.io/
Claim LARYNX portal : https://spk.dlux.io/

SPK Network - Claim Drop Starts on March 20th!
https://peakd.com/hive-112019/@spknetwork/spk-network-claim-drop-starts-on-march-20th

HoneyComb | SPKCC | DLUX - Overview and FAQs
https://3speak.tv/watch?v=disregardfiat/eifxrgnw

Environment file: .env 
Config file : config.js 
ports: 3001

Installing:
- Git clone : https://github.com/3speaknetwork/honeycomb-spkcc.git
- docker-compose build
- docker-compose up -d  # Run the containers in the background 
  - check logs 
    - docker-compose logs -f 


Upgrading:
- Docker-compose down 
- git pull 
- docker-compose build  # rebuild the docker images with the new configs and file changes 
- docker-compose up -d # Run the containers in the background 

Runners: 
one runner gets elected every 5 minutes. anybody who is in consensus with anybody who has more tokens locked getting in first. you might also not have enough tokens to get elected

Errors:
1) Creating network "honeycomb-spkcc_default" with the default driver
ERROR: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-b994e2131d5d -j DOCKER: iptables v1.8.4 (legacy): Couldn't load target `DOCKER':No such file or directory

    - the issue was addressed in https://github.com/docker/for-linux/issues/927 and the fix was to restart docker. 
      Strange but the restart solves the problem systemctl restart docker



2) ipfs_1       | ipfs_1       | Error: '/data/ipfs' is not writable
 {
                "Type": "volume",
                "Name": "honeycomb-spkcc_ipfs",
                "Source": "/var/lib/docker/volumes/honeycomb-spkcc_ipfs/_data",
                "Destination": "/data/ipfs",
                "Driver": "local",
                "Mode": "rw",
                "RW": true,
                "Propagation": ""
            }

data/ipfs doesnt exist 
/var/lib/docker/volumes/honeycomb-spkcc_ipfs/_data } # ls -lsa 
total 60
 4 drwxr-sr-x   5 ubuntu users  4096 Mar  5 16:18 .
 4 drwx-----x   3 root   root   4096 Feb 16 03:36 ..
 4 -rw-r--r--   1 ubuntu users    21 Feb 21 18:03 api
20 drwxr-sr-x 909 ubuntu users 20480 Feb 21 18:03 blocks
 0 -rw-r--r--   1 root   users     0 Feb 22 02:03 ._check_writable
 4 -rw-------   1 ubuntu users  3692 Feb 16 03:38 config
12 drwxr-sr-x   2 ubuntu users 12288 Feb 22 01:39 datastore
 4 -rw-------   1 ubuntu users   190 Feb 16 03:37 datastore_spec
 4 drwx--S---   2 ubuntu users  4096 Feb 16 03:37 keystore
 4 -rw-r--r--   1 ubuntu users     3 Feb 16 03:37 version

          - When the container was initially created . The file ._check_writable was created with the root user as the account and it was failing the writable function in https://github.com/ipfs/go-ipfs/blob/ef866a1400b3b2861e5e8b6cc9edc8633b890a0a/thirdparty/dir/dir.go#L18 . The fix for this is to update the permissions to ubuntu:users ( This may be different on your server. Match the file ownership to the other files in the directory. ) 
          - File Path : /var/lib/docker/volumes/honeycomb-spkcc_ipfs/_data
       
       
       

3) `ipfs_1       | Error: lock /data/ipfs/repo.lock: permission denied
honeycomb-spkcc_ipfs_1 exited with code 1'

 I had to delete the file as root under /var/lib/docker/volumes/honeycomb-spkcc_ipfs/_data
 
 
honeycomb_1  | IPFS: DockerIPFS:5001
honeycomb_1  | Using APIURL:  https://rpc.ecency.com/
honeycomb_1  | Streaming using mode irreversible
honeycomb_1  | Starting URL:  https://rpc.ecency.com/
honeycomb_1  | Watchdog: Monitoring...
honeycomb_1  | LARYNX token API listening on port 3001



Reference :
how long should it take for the updated lock LARYNX to show on the monitor page ?
It won’t update until the network heals
It’s about 4,600 blocks behind I think



 json: '{"hash":"QmbLKwVCMomvuFzY1eHkfyJhBuoUr5Z7JSxn1rjujYkp2o","block":62796201,"ipfs_id":"12D3KooWAbLeyygSftJNL5yEi6rhgoTpAVL3EdA1wyYVkCrV8WRn","version":"v1.0.2"}'
 
 (that announcing your IPFS node address so we can build a cluster and not wait as long to share the ipfs hashes)