@umma08 they say their codebase will be released following the launch of their testnet, which is currently targeted for September.
For what it’s worth, I think that any constructive discussion and knowledge sharing between our projects will be positive, and I agree that there are opportunities for us to learn from each other.
Just like @mfronczyk I too am curious to hear more about the approach @BigRomanov and the Beam team took for their addressing layer, and how they support both online and offline transactions.
i keep getting this error on trying to install grin-miner for a spin: error: failed to run custom build command for
process didn't exit successfully:
/Users/Mac/grin-miner/grin-miner/grin/target/release/build/libgit2-sys-e0ecf6de4c4a347d/build-script-build (exit code: 101)
running: "cmake" "/Users/Mac/.cargo/registry/src/github.com-1ecc6299db9ec823/libgit2-sys-0.7.3/libgit2" "-DUSE_SSH=OFF" "-DUSE_OPENSSL=OFF" "-DUSE_HTTPS=OFF" "-DCURL=OFF" "-DBUILD_SHARED_LIBS=OFF" "-DBUILD_CLAR=OFF" "-DCMAKE_INSTALL_PREFIX=/Users/Mac/grin-miner/grin-miner/grin/target/release/build/libgit2-sys-371571f714a759f1/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_BUILD_TYPE=Release"
fatal: Not a git repository (or any of the parent directories): .git
thread 'main' panicked at '
failed to execute command: No such file or directory (os error 2)
cmake not installed?
build script failed, must exit now', /Users/Mac/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.29/src/lib.rs:632:5
note: Run with
RUST_BACKTRACE=1 for a backtrace.
warning: build failed, waiting for other jobs to finish...
error: build failed
warning: An explicit [[bin]] section is specified in Cargo.toml which currently
disables Cargo from automatically inferring other binary targets.
This inference behavior will change in the Rust 2018 edition and the following
files will be included as a binary target:
This is likely to break cargo build or cargo test as these files may not be
ready to be compiled as a binary target today. You can future-proof yourself
and disable this warning by adding
autobins = false to your [package]
section. You may also move the files to a location where Cargo would not
automatically infer them to be a target, such as in subfolders.
For more information on this warning you can consult
Finished dev [unoptimized + debuginfo] target(s) in 0.52s