Native build Scilla binary------ERROR

#1

Hi I have a native build setup, which I started with in mid January, was able to mine and get rewards. My system crashed due to memory failure and did not function correctly afterwards while mining.

I did a fresh Ubuntu 18.04 installation and now I cant seem to build the Scilla binary?

Followed there steps for OCaml toolchain:

opam init -y
opam switch -y 4.06.1
opam install -y ocaml-migrate-parsetree core cryptokit ppx_sexp_conv yojson batteries angstrom hex ppx_deriving ppx_deriving_yojson menhir oUnit dune stdint fileutils ctypes ctypes-foreign bisect_ppx secp256k1

then:

make opamdep

Results from running:

eval `opam config env`

which seem to be fine: 

OPAM_SWITCH_PREFIX='/home/miner1/.opam/4.06.1'; export OPAM_SWITCH_PREFIX;
CAML_LD_LIBRARY_PATH='/home/miner1/.opam/4.06.1/lib/stublibs:/home/miner1/.opam/4.06.1/lib/ocaml/stublibs:/home/miner1/.opam/4.06.1/lib/ocaml'; export CAML_LD_LIBRARY_PATH;
OCAML_TOPLEVEL_PATH='/home/miner1/.opam/4.06.1/lib/toplevel'; export OCAML_TOPLEVEL_PATH;
MANPATH=':/home/miner1/.opam/4.06.1/man'; export MANPATH;
PATH='/home/miner1/.opam/4.06.1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin'; export PATH;



But once I start with the "make clean;make"

I get the following issues? I dont know how to fix this? Any suggestions? 


miner1@miner1-System-Product-Name:~/Desktop/Scilla$ make clean;make
dune clean
git clean -dfXq
dune build @install
      menhir src/lang/base/ScillaParser.{ml,mli}
Warning: 9 states have shift/reduce conflicts.
Warning: 15 shift/reduce conflicts were arbitrarily resolved.
      ocamlc src/lang/base/.scilla_base.objs/JSON.{cmi,cmti} (exit 2)
(cd _build/default && /home/miner1/.opam/4.06.1/bin/ocamlc.opt -w @a-4-29-40-41-42-44-45-48-58-59-60-40 -strict-sequence -strict-formats -short-paths -keep-locs -g -bin-annot -I src/lang/base/.scilla_base.objs -I src/lang/base/.scilla_base.objs/.private -I /home/miner1/.opam/4.06.1/lib/base -I /home/miner1/.opam/4.06.1/lib/base/caml -I /home/miner1/.opam/4.06.1/lib/base/md5 -I /home/miner1/.opam/4.06.1/lib/base/shadow_stdlib -I /home/miner1/.opam/4.06.1/lib/batteries -I /home/miner1/.opam/4.06.1/lib/bin_prot -I /home/miner1/.opam/4.06.1/lib/bin_prot/shape -I /home/miner1/.opam/4.06.1/lib/biniou -I /home/miner1/.opam/4.06.1/lib/bisect_ppx/runtime -I /home/miner1/.opam/4.06.1/lib/bytes -I /home/miner1/.opam/4.06.1/lib/core -I /home/miner1/.opam/4.06.1/lib/core_kernel -I /home/miner1/.opam/4.06.1/lib/core_kernel/base_for_tests -I /home/miner1/.opam/4.06.1/lib/cryptokit -I /home/miner1/.opam/4.06.1/lib/cstruct -I /home/miner1/.opam/4.06.1/lib/ctypes -I /home/miner1/.opam/4.06.1/lib/easy-format -I /home/miner1/.opam/4.06.1/lib/fieldslib -I /home/miner1/.opam/4.06.1/lib/hex -I /home/miner1/.opam/4.06.1/lib/integers -I /home/miner1/.opam/4.06.1/lib/jane-street-headers -I /home/miner1/.opam/4.06.1/lib/num -I /home/miner1/.opam/4.06.1/lib/ocaml-compiler-libs/common -I /home/miner1/.opam/4.06.1/lib/ocaml-compiler-libs/shadow -I /home/miner1/.opam/4.06.1/lib/ocaml-migrate-parsetree -I /home/miner1/.opam/4.06.1/lib/ocaml/compiler-libs -I /home/miner1/.opam/4.06.1/lib/ocaml/threads -I /home/miner1/.opam/4.06.1/lib/parsexp -I /home/miner1/.opam/4.06.1/lib/ppx_assert/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_bench/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_compare/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_derivers -I /home/miner1/.opam/4.06.1/lib/ppx_deriving -I /home/miner1/.opam/4.06.1/lib/ppx_deriving_yojson/runtime -I /home/miner1/.opam/4.06.1/lib/ppx_expect/collector -I /home/miner1/.opam/4.06.1/lib/ppx_expect/common -I /home/miner1/.opam/4.06.1/lib/ppx_expect/config -I /home/miner1/.opam/4.06.1/lib/ppx_hash/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_inline_test/config -I /home/miner1/.opam/4.06.1/lib/ppx_inline_test/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_sexp_conv -I /home/miner1/.opam/4.06.1/lib/ppx_sexp_conv/expander -I /home/miner1/.opam/4.06.1/lib/ppx_sexp_conv/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_tools -I /home/miner1/.opam/4.06.1/lib/ppxlib -I /home/miner1/.opam/4.06.1/lib/ppxlib/ast -I /home/miner1/.opam/4.06.1/lib/ppxlib/print_diff -I /home/miner1/.opam/4.06.1/lib/ppxlib/traverse_builtins -I /home/miner1/.opam/4.06.1/lib/result -I /home/miner1/.opam/4.06.1/lib/secp256k1 -I /home/miner1/.opam/4.06.1/lib/sexplib -I /home/miner1/.opam/4.06.1/lib/sexplib/unix -I /home/miner1/.opam/4.06.1/lib/sexplib0 -I /home/miner1/.opam/4.06.1/lib/spawn -I /home/miner1/.opam/4.06.1/lib/splittable_random -I /home/miner1/.opam/4.06.1/lib/stdint -I /home/miner1/.opam/4.06.1/lib/stdio -I /home/miner1/.opam/4.06.1/lib/typerep -I /home/miner1/.opam/4.06.1/lib/variantslib -I /home/miner1/.opam/4.06.1/lib/yojson -I /home/miner1/.opam/4.06.1/lib/zarith -I src/cpp/.scilla_cpp_deps.objs -no-alias-deps -opaque -o src/lang/base/.scilla_base.objs/JSON.cmi -c -intf src/lang/base/JSON.pp.mli)
**File "src/lang/base/JSON.mli", line 40, characters 58-69:**
**Error (warning 3): deprecated: Yojson.json**
**json types are being renamed and will be removed in the next Yojson major version. Use type t instead**
**File "src/lang/base/JSON.mli", line 83, characters 60-71:**
**Error (warning 3): deprecated: Yojson.json**
**json types are being renamed and will be removed in the next Yojson major version. Use type t instead**
**File "src/lang/base/JSON.mli", line 133, characters 82-93:**
**Error (warning 3): deprecated: Yojson.json**
**json types are being renamed and will be removed in the next Yojson major version. Use type t instead**
**File "src/lang/base/JSON.mli", line 145, characters 56-67:**
**Error (warning 3): deprecated: Yojson.json**
**json types are being renamed and will be removed in the next Yojson major version. Use type t instead**
**File "src/lang/base/JSON.mli", line 164, characters 43-54:**
**Error (warning 3): deprecated: Yojson.json**
**json types are being renamed and will be removed in the next Yojson major version. Use type t instead**
**      ocamlc src/lang/base/.scilla_base.objs/JSONParser.{cmi,cmo,cmt} (exit 2)**
(cd _build/default && /home/miner1/.opam/4.06.1/bin/ocamlc.opt -w @a-4-29-40-41-42-44-45-48-58-59-60-40 -strict-sequence -strict-formats -short-paths -keep-locs -g -bin-annot -I src/lang/base/.scilla_base.objs -I src/lang/base/.scilla_base.objs/.private -I /home/miner1/.opam/4.06.1/lib/base -I /home/miner1/.opam/4.06.1/lib/base/caml -I /home/miner1/.opam/4.06.1/lib/base/md5 -I /home/miner1/.opam/4.06.1/lib/base/shadow_stdlib -I /home/miner1/.opam/4.06.1/lib/batteries -I /home/miner1/.opam/4.06.1/lib/bin_prot -I /home/miner1/.opam/4.06.1/lib/bin_prot/shape -I /home/miner1/.opam/4.06.1/lib/biniou -I /home/miner1/.opam/4.06.1/lib/bisect_ppx/runtime -I /home/miner1/.opam/4.06.1/lib/bytes -I /home/miner1/.opam/4.06.1/lib/core -I /home/miner1/.opam/4.06.1/lib/core_kernel -I /home/miner1/.opam/4.06.1/lib/core_kernel/base_for_tests -I /home/miner1/.opam/4.06.1/lib/cryptokit -I /home/miner1/.opam/4.06.1/lib/cstruct -I /home/miner1/.opam/4.06.1/lib/ctypes -I /home/miner1/.opam/4.06.1/lib/easy-format -I /home/miner1/.opam/4.06.1/lib/fieldslib -I /home/miner1/.opam/4.06.1/lib/hex -I /home/miner1/.opam/4.06.1/lib/integers -I /home/miner1/.opam/4.06.1/lib/jane-street-headers -I /home/miner1/.opam/4.06.1/lib/num -I /home/miner1/.opam/4.06.1/lib/ocaml-compiler-libs/common -I /home/miner1/.opam/4.06.1/lib/ocaml-compiler-libs/shadow -I /home/miner1/.opam/4.06.1/lib/ocaml-migrate-parsetree -I /home/miner1/.opam/4.06.1/lib/ocaml/compiler-libs -I /home/miner1/.opam/4.06.1/lib/ocaml/threads -I /home/miner1/.opam/4.06.1/lib/parsexp -I /home/miner1/.opam/4.06.1/lib/ppx_assert/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_bench/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_compare/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_derivers -I /home/miner1/.opam/4.06.1/lib/ppx_deriving -I /home/miner1/.opam/4.06.1/lib/ppx_deriving_yojson/runtime -I /home/miner1/.opam/4.06.1/lib/ppx_expect/collector -I /home/miner1/.opam/4.06.1/lib/ppx_expect/common -I /home/miner1/.opam/4.06.1/lib/ppx_expect/config -I /home/miner1/.opam/4.06.1/lib/ppx_hash/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_inline_test/config -I /home/miner1/.opam/4.06.1/lib/ppx_inline_test/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_sexp_conv -I /home/miner1/.opam/4.06.1/lib/ppx_sexp_conv/expander -I /home/miner1/.opam/4.06.1/lib/ppx_sexp_conv/runtime-lib -I /home/miner1/.opam/4.06.1/lib/ppx_tools -I /home/miner1/.opam/4.06.1/lib/ppxlib -I /home/miner1/.opam/4.06.1/lib/ppxlib/ast -I /home/miner1/.opam/4.06.1/lib/ppxlib/print_diff -I /home/miner1/.opam/4.06.1/lib/ppxlib/traverse_builtins -I /home/miner1/.opam/4.06.1/lib/result -I /home/miner1/.opam/4.06.1/lib/secp256k1 -I /home/miner1/.opam/4.06.1/lib/sexplib -I /home/miner1/.opam/4.06.1/lib/sexplib/unix -I /home/miner1/.opam/4.06.1/lib/sexplib0 -I /home/miner1/.opam/4.06.1/lib/spawn -I /home/miner1/.opam/4.06.1/lib/splittable_random -I /home/miner1/.opam/4.06.1/lib/stdint -I /home/miner1/.opam/4.06.1/lib/stdio -I /home/miner1/.opam/4.06.1/lib/typerep -I /home/miner1/.opam/4.06.1/lib/variantslib -I /home/miner1/.opam/4.06.1/lib/yojson -I /home/miner1/.opam/4.06.1/lib/zarith -I src/cpp/.scilla_cpp_deps.objs -no-alias-deps -opaque -o src/lang/base/.scilla_base.objs/JSONParser.cmo -c -impl src/lang/base/JSONParser.pp.ml)
File "src/lang/base/JSONParser.ml", line 62, characters 15-25:
Error (warning 3): deprecated: Yojson.Basic.json
json types are being renamed and will be removed in the next Yojson major version. Use type t instead
File "src/lang/base/JSONParser.ml", line 89, characters 29-39:
Error (warning 3): deprecated: Yojson.Basic.json
json types are being renamed and will be removed in the next Yojson major version. Use type t instead
Makefile:11: recipe for target 'all' failed
make: *** [all] Error 1
miner1@miner1-System-Product-Name:~/Desktop/Scilla$ 

I have been stuck here for 2 days now any help would be appreciated

Cheers

Steven
0 Likes

#2

You cannot use the native build to join the network now as the Yojson dependency got deleted from the opam library.

Please use the docker build till we upgrade the Scilla version on the blockchain to solve this issue.

0 Likes

#3

Hi there

Thanks for the info, pretty disappointing it failed. Just to clarify can one use the docker with AMD GPU’s is the docker not just for Nvidia GPU’s?

When do you expect the upgrade of Scilla to take place so I can rather use Native build?

Much appreciated

0 Likes

#4

You can use both if you do remote mining (Option 2) via Zilminer to yourself. It’s a good workaround for AMD GPUs too.

We are planning an upgrade near end February, will be conducting testing and drill runs before upgrading the mainnet.

0 Likes

#5

Excellent thanks will give it a go.

cheers

0 Likes

#6

This would seem to be 18.04 issue?
You are wrong about Ubuntu 16.04.x - compiles fine.
(Cloned/Fresh VM using Apt version of opam then switch) :

$ make clean
dune clean
git clean -dfXq

$ make opamdep
opam init -y

<><> Required setup - please read <><><><><><><><><><><><><><><><><><><><><><><>

  In normal operation, opam only alters files within ~/.opam.

  However, to best integrate with your system, some environment variables
  should be set. If you allow it to, this initialisation step will update
  your bash configuration by adding the following line to ~/.profile:

    test -r /mypath/.opam/opam-init/init.sh && . /mypath/.opam/opam-init/init.sh > /dev/null 2> /dev/null || true

  Otherwise, every time you want to access your opam installation, you will
  need to run:

    eval $(opam env)

  You can always re-run this setup with 'opam init' later.

Do you want opam to modify ~/.profile? [N/y/f]
(default is 'no', use 'f' to choose a different file) A hook can be added to opam's init scripts to ensure that the shell remains in sync with the opam environment when they are loaded. Set that up? [y/N] y
opam switch -y 4.06.1
opam install -y ocaml-migrate-parsetree core cryptokit ppx_sexp_conv yojson batteries angstrom hex ppx_deriving ppx_deriving_yojson menhir oUnit dune stdint fileutils ctypes ctypes-foreign bisect_ppx secp256k1
[NOTE] Package secp256k1 is already installed (current version is 0.4.0).
[NOTE] Package bisect_ppx is already installed (current version is 1.4.0).
[NOTE] Package ctypes-foreign is already installed (current version is 0.4.0).
[NOTE] Package ctypes is already installed (current version is 0.14.0).
[NOTE] Package fileutils is already installed (current version is 0.5.3).
[NOTE] Package stdint is already installed (current version is 0.5.1).
[NOTE] Package dune is already installed (current version is 1.6.3).
[NOTE] Package ounit is already installed (current version is 2.0.8).
[NOTE] Package menhir is already installed (current version is 20181113).
[NOTE] Package ppx_deriving_yojson is already installed (current version is 3.3).
[NOTE] Package ppx_deriving is already installed (current version is 4.2.1).
[NOTE] Package hex is already installed (current version is 1.3.0).
[NOTE] Package angstrom is already installed (current version is 0.11.0).
[NOTE] Package batteries is already installed (current version is 2.9.0).
[NOTE] Package yojson is already installed (current version is 1.6.0).
[NOTE] Package ppx_sexp_conv is already installed (current version is v0.11.2).
[NOTE] Package cryptokit is already installed (current version is 1.13).
[NOTE] Package core is already installed (current version is v0.11.3).
[NOTE] Package ocaml-migrate-parsetree is already installed (current version is 1.2.0).

More proof:

$ opam remove yojson
 
The following actions will be performed:
  ⊘ remove ppx_deriving_yojson 3.3   [uses yojson]
  ⊘ remove yojson              1.6.0
===== ⊘ 2 =====
Do you want to continue? [Y/n] y

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><><><>
⊘ removed   ppx_deriving_yojson.3.3
⊘ removed   yojson.1.6.0
Done.

$ opam install yojson
The following actions will be performed:
  ∗ install yojson 1.6.0

<><> Gathering sources ><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
[yojson.1.6.0] found in cache

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><><><>
∗ installed yojson.1.6.0
Done.

$ bin/testsuite
............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Ran: 812 tests in: 7.21 seconds.
OK

Warnings - no errors:

$ make clean; make
dune clean
git clean -dfXq
dune build @install
      menhir src/lang/base/ScillaParser.{ml,mli}
Warning: 9 states have shift/reduce conflicts.
Warning: 15 shift/reduce conflicts were arbitrarily resolved.

So I am not sure what you mean by:

“You cannot use the native build to join the network now as the Yojson dependency got deleted from the opam library.”

GPU mining still doesn’t work on ‘local build’/no-docker. Docker also fails as I/others noted on github.

Constants.xml is updated with Scilla path.

Beginning to think you guys should have never left the testnet.
Lots of unresolved major problems.

  • Using docker start script on my 16.04(vm) per Docs results in immediate exit of docker image.
  • Using docker manually (see github) results in --address error & exit. (these docker problems related I’m sure)
  • You cannot GPU mine per mining wiki page with docker or native.
  • My CPU mining node has received nothing since starting 2 days ago. (Address doesn’t exist per lookup) (2 core / 6 gb VM)
  • A new address is always recreated per the ‘native build’ start script. (launch.sh) This seems wrong? Why do this?
  • Scilla path/bins being in Constants show no difference (in logging/output) either way. How do you know if Scilla is broken / not being used?
  • Assuming Scilla affects ‘getWork’/JSON? The CPU node answers getWork requests, but with no data/jobs.

-Tired

0 Likes

#7

Hi bmatthewshea

Thanks for the comment, I can sense you are as tired of this setup as me. Kind of over it now. I am going to run 16.04 and give it a try, just a bit of a hassle again.

I tried running my AMD GPU’s with remote docker today, so much issues as you mentioned. The entire wiki needs an overhaul.

Cheers and like you said Tired!

1 Like

#8

Yes, this seems to be a closed mining operation?
Or at best - extremely poor documentation.

They should get a local (native) build working >>FIRST.<<

Then build out docker(s) based on ‘native build’ deps/etc.
Docker images should be secondary.
“Working” also means the documentation will create a working node.
Part of releasing a public blockchain (not a testnet) is perfecting docs for endusers/PoW setups.
This seems like an aferthought. As long as core-team can mine - all’s good?

A mainnet release means going through the compile/build over and over and over BEFORE pushing code to GitHub and perfecting the release doc(s) along the way. This was clearly not done very well/at all. Why this forum is getting more popular. No answers forthcoming.

1 Like

#9

Thats why I did not even bother with the docker, as I thought native would be the primary way first.

Anyway lets hope these guys get there act together, as you said, this seems to be a closed mining group…

cheers

1 Like

#10

Well I’ll be damned. Figured I should post this here since I just complained.

I now know it only PoW’s every 1.5 hrs. I do not remember this being said on Mining Wiki but could be wrong? I definitely know I have never received an answer like this here or on GitHub. What gives?

From an article unrelated to github or this forum:
Zilliqa miners will only need to run the proof of work process for the first five minutes of every one and a half hour cycle.

So I guess I can just let my ETH ethminer run and get half-PoW/MH when the zilminer kicks in again in 1.5 hours?

Well good to know.
Thanks for telling us - not.
I see a number of just my posts that could have been easily answered already concerning this.
Guess I didn’t read DS Epoch info on Mining Wiki page, but didn’t see how that had to do with a mining setup.
I still do not clearly see it saying that GPU MINER DOES NOTHING MOST OF TIME.

Just:

At the start of each DS Epoch, all mining candidates will run the Proof-of-Work (Ethash algorithm) cycle for a 60 seconds window in order to compete to join the Zilliqa network.

  • Nodes that fulfilled the DS_POW_DIFFICULTY parameter will qualify to join as DS nodes.
  • Nodes that fulfilled the POW_DIFFICULTY parameter will qualify to join as shard nodes.

There are a total of 100 TX epochs (each 1-2 min) within each DS Epoch (2-3 hrs). Every 100th TX epoch is known as the Vacuous epoch .

I just wanted to mine. Not read about how your PoW/proof of concept works.

0 Likes

#11

Please do read the Mining wiki in full to understand how mining in Zilliqa works. This documentation is important because this is a new mining system.

To answer all your other questions:

  • They should get a local (native) build working >>FIRST.<<

    We did ensure the native build works on the day of mainnet launch, however the opam library for Yojson got deprecated the day after unfortunately (we do not control the opam library). Hence, only the docker works properly now. The next network upgrade in late February will resolve this issue.

  • Using docker start script on my 16.04(vm) per Docs results in immediate exit of docker image.

    This shouldn’t be the case, there are ~800 community miners using the docker image on both 16.04/18.04. Did you change a parameter in the constant.xml file accidentally?

  • You cannot GPU mine per mining wiki page with docker or native

    You can do this via Option 2 of the Mining wiki.

  • A new address is always recreated per the ‘native build’ start script. (launch.sh) This seems wrong? Why do this?

    This is not the case. If mykey.txt exists in your join folder you created, the address is the always the same.

0 Likes

#12
  1. As I already mentioned, I was able to build Scilla and was able to install Yojson just fine.Please see my post above. Native build Scilla binary------ERROR

  2. / 3. I am using a VM - does this matter w/ the docker image? I wouldn’t think so. Had same result under 16.04 and 18.04. And no, I didn’t change any constants other than to allow CPU mining only per doc. Exactly per directions. A couple of us have had GitHub issue open for last 7 days. No reply until yesterday. When I run via docs, the docker image immediately exits - no error. It’s simply not running. Running image manually I was getting --address error - but I see via GitHub issue I got reply and was stupid blunder on my part. (Didn’t quote the parameters.) Will try ‘manually’ running later today.

  3. Yes, I see it will probably recreate the same addr each time? but here is what I meant:

Script snippet launch.sh from mainnet config dload:

if [ ! -s $mykeyfile ]
then
    echo "Cannot find $mykeyfile, generating new keypair for you..."
    ${zilliqa_path}/build/bin/genkeypair > ./$mykeyfile
fi

prikey=$(cat ./$mykeyfile | awk '{ print $2 }')
pubkey=$(cat ./$mykeyfile | awk '{ print $1 }')

Then this is run with no if's/always:

$zilliqa_path/build/bin/getaddr --pubk $pubkey > ./$myaddrfile

^ My address is rerun each time. myaddr.txt already exists after first run of script.
Why not just chk if myaddr.txt exists before recreating. If there is a valid reason - all good. I just don’t see it. And just added to my confusion on how this thing works.

0 Likes

#13
  1. If you manage to change the make dependencies by downgrading the yojson dependency, then good for you. That is not a recommended solution as we do not know the implication that will do to your node. We are still recommending you to upgrade to the next Scilla version v0.1.2 by end February if you still wish to use the native build.

  2. Try running sudo docker logs --details zilliqa to find out what is the issue. Btw what exactly is the build you are following? Option 1 with CUDA image for nvidia?

  3. If a User wishes to change his keypairs for signing, a new address will be printed for him. If not, the address will be reprinted as per the old string. This is not an issue.

0 Likes

#15
  1. I didn’t downgrade anything. Just followed Scilla docs.
    Was a fresh 16.04 Ubuntu VM & fresh install install of opam/etc.
  2. I somehow got docker image working yesterday. Not sure how - do not rem doing anything differently. At any rate, it is exactly same as my ‘native build’ (cpu node+remote mining).
    As far as logging/actions -
    I see no difference between docker version and my build in logging/output. (still not seeing any rewards/etc) < Check this thread, too.
    I am/was using option 2 (When using native build I was using ‘remote gpu mining’ via editing constants file before startup)
  3. All I see that single line doing it regenerating the myaddr.txt each time - maybe prompt and ask to regen if it already finds the file. It’s probably fine, but seems odd way of doing things.
    Anyway, small thing. I don’t care - as long as it works and keeps my wallet addr same.

I’ll ask here since I can’t seem to get an answer on GitHub:

What is the minimal mining speed to get ANY rewards?
I see NOTHING rewarded over the course of a week running this.
I see: I am a ds/normal node. as I mentioned in past.
See lastest github post HERE.

Matter of fact if I check my address on API site:
{"error":{"code":-5,"data":null,"message":"Account is not created"},"id":"1","jsonrpc":"2.0"}
Been using same wallet address for a week as well.

0 Likes

archived #16
0 Likes