Giter VIP home page Giter VIP logo

lux-core / lux Goto Github PK

View Code? Open in Web Editor NEW
3.8K 3.8K 95.0 168.45 MB

LUX - Hybrid PoW/PoS & Unique PHI2 Algorithm | Masternode | Parallel masternode | Segwit | Smartcontract | Luxgate | Proof of file storage (Decentralised distributed file storage)

Home Page: https://luxcore.io

License: GNU Affero General Public License v3.0

CMake 0.81% Makefile 0.74% Shell 3.13% M4 1.07% Python 3.81% Roff 0.09% QMake 0.14% C++ 80.10% C 7.91% CSS 0.46% Dockerfile 0.03% Batchfile 0.06% Perl 0.01% Assembly 0.92% HTML 0.26% OpenEdge ABL 0.01% Objective-C++ 0.04% Java 0.16% Solidity 0.08% Sage 0.16%

lux's Introduction

LUX Logo

EMPOWERING PEOPLE

Luxcore is GNU AGPLv3 licensed.

Build Status GitHub version HitCount Discord server follow on Twitter

Build history

WebsiteLuxgate - PoS Web WalletBlock ExplorerBlogForumTelegramTwitter

Features

  • Hybrid PoW/PoS
  • Hybrid masternode
  • Smart contract
  • New RX2 algorithm
  • Luxgate

Developed by Luxcore, LUX (LUX Coin) is a hybrid cryptocurrency utilizing both proof-of-stake and proof-of-work algorithms to enhance blockchain security and decentralization. Luxcore's hybrid consensus model employs masternodes to provide specialized functions and further secure the chain while providing additional rewards to coin holders. The LUX blockchain enables developers to utilize smart contracts and decentralized applications.

Luxcore continues to develop products for the LUX blockchain including Luxgate (a trustless, peer to peer decentralized exchange) and Luxedge (a decentralized software development platform and repository).

LUX was created in 2017 as a fork of the Bitcoin codebase, and aims to introduce new innovations and services to the broader crypto community with cross-chain and decentralized solutions.

Coin Specifications

Specification Value
Total Blocks 6,000,000
Block Size 4MB
Block Time 60s
PoW Block Time 120s
PoW Reward 5 (POW) + 2 (MN) + 1 (DEV FEE)
PoS Reward 1 LUX
Stake Time 36 hours
Masternode Requirement 16,120 LUX
Masternode Reward 25% PoW/PoS
Port 26969
RPC Port 9888
Masternode Port 26969
Lux legacy address start with L
p2sh-segwit address start with S
Bech32 address start with bc
  • NOTE: "getrawchangeaddress p2sh-segwit" to get p2sh-segwit address

Instructions

Build Lux wallet

Building for 32-bit Windows

The next three steps are an example of how to acquire the source and build in an appropriate way.

Acquire the source and install dependencies.

git clone https://github.com/LUX-Core/lux
sudo chmod -R a+rw lux
cd lux/depends
./install-dependencies.sh

Set the default mingw-w32 g++ compiler option to auto (option 0) by default.

sudo update-alternatives --config i686-w64-mingw32-g++

Build in the usual way.

./build-wins.sh

Building for 64-bit Windows

The next three steps are an example of how to acquire the source and build in an appropriate way.

Acquire the source and install dependencies.

git clone https://github.com/LUX-Core/lux
sudo chmod -R a+rw lux
cd lux/depends
./install-dependencies.sh

Set the default mingw-w64 g++ compiler option to posix (option 1).

sudo update-alternatives --config x86_64-w64-mingw32-g++

Build in the usual way.

./build-wins.sh x64

Build on Ubuntu

Use

sudo add-apt-repository ppa:bitcoin/bitcoin; git clone https://github.com/LUX-Core/lux; cd lux; depends/install-dependencies.sh; ./autogen.sh; ./configure --disable-tests --with-boost-libdir=/usr/local/lib; make clean; make -j$(nproc)

Add bitcoin repository for Berkeley DB 4.8

sudo add-apt-repository ppa:bitcoin/bitcoin

Clone lux repository

git clone https://github.com/LUX-Core/lux

Build lux

cd lux
./depends/install-dependencies.sh
./autogen.sh
./configure --disable-tests
make -j$(nproc)

Build on OSX

The commands in this guide should be executed in a Terminal application. The built-in one is located in /Applications/Utilities/Terminal.app.

Preparation

Install the OS X command line tools:

xcode-select --install

When the popup appears, click Install.

If you're running macOS Mojave 10.14/Xcode 10.0 or later, and want to use the depends system, you'll also need to use the following script to install the macOS system headers into /usr/include.

open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg

Then install Homebrew

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Dependencies

brew install cmake automake berkeley-db4 leveldb libtool [email protected] --c++11 --without-single --without-static miniupnpc openssl pkg-config protobuf qt5 libevent imagemagick --with-librsvg

Link boost 1.64

brew link [email protected] --force

Build Luxcore

Clone the Lux source code and cd into lux

    git clone https://github.com/LUX-Core/lux
    cd lux
    ./building/mac/requirements.sh
    ./building/mac/build.sh

Setup and Build: Arch Linux

This example lists the steps necessary to setup and build a command line only, non-wallet distribution of the latest changes on Arch Linux:

pacman -S git base-devel boost libevent python
git clone https://github.com/LUX-Core/lux
cd lux/
./autogen.sh
./configure --without-miniupnpc --disable-tests
make -j$(nproc)

Note: Enabling wallet support requires either compiling against a Berkeley DB newer than 4.8 (package db) using --with-incompatible-bdb, or building and depending on a local version of Berkeley DB 4.8. The readily available Arch Linux packages are currently built using --with-incompatible-bdb according to the As mentioned above, when maintaining portability of the wallet between the standard Bitcoin Core distributions and independently built node software is desired, Berkeley DB 4.8 must be used.

ARM Cross-compilation

These steps can be performed on, for example, an Ubuntu VM. The depends system will also work on other Linux distributions, however the commands for installing the toolchain will be different.

Make sure you install the build requirements mentioned above. Then, install the toolchain and curl:

sudo apt-get install g++-arm-linux-gnueabihf curl

To build executables for ARM:

cd depends
make HOST=arm-linux-gnueabihf NO_QT=1
cd ..
./configure --prefix=$PWD/depends/arm-linux-gnueabihf --enable-glibc-back-compat --enable-reduce-exports LDFLAGS=-static-libstdc++
make -j$(nproc)

For further documentation on the depends system see README.md in the depends directory.

Building on FreeBSD

Clang is installed by default as cc compiler, this makes it easier to get started than on OpenBSD. Installing dependencies:

pkg install autoconf automake libtool pkgconf
pkg install boost-libs openssl libevent
pkg install gmake

You need to use GNU make (gmake) instead of make. (libressl instead of openssl will also work)

For the wallet (optional):

./contrib/install_db4.sh `pwd`
setenv BDB_PREFIX $PWD/db4

Then build using:

./autogen.sh
./configure BDB_CFLAGS="-I${BDB_PREFIX}/include" BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx"
gmake

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Lux.

The contribution workflow is described in CONTRIBUTING.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Issue

We try to prompt our users for the basic information We always need for new issues. Please fill out the issue template below and submit it to our discord channel Discord server

ISSUE_TEMPLATE

License

FOSSA Status

lux's People

Contributors

216k155 avatar agora94 avatar alternateam avatar anorganix avatar ars0nic avatar barrystyle avatar chatzich avatar claudebol avatar djm34 avatar dvajdual avatar enkayz avatar fossabot avatar geraroz avatar ggsava avatar giaki3003 avatar grapelux avatar grapelux2 avatar heidi-dang avatar karikaristov avatar mattiasgeniar avatar matwaller avatar nguyenhoangtran11 avatar okislitsin avatar rej156 avatar ssdbkey avatar superdev810 avatar topox84 avatar tpruvot avatar whyamiroot avatar xotonic avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

lux's Issues

having two or more corresponding or identical height and hash , can any one resolve this ?

2018-09-26 07:17:58 ProcessNewBlock: ACCEPTED 419463 71366b0a87d43cd1a9d539948f6d571c385be150a0ccc96ba420be6260fa4b85 (pos)
2018-09-26 07:17:58 ProcessNewBlock: ACCEPTED 419463 71366b0a87d43cd1a9d539948f6d571c385be150a0ccc96ba420be6260fa4b85 (pos)
2018-09-26 07:17:58 ProcessNewBlock: ACCEPTED 419463 71366b0a87d43cd1a9d539948f6d571c385be150a0ccc96ba420be6260fa4b85 (pos)
2018-09-26 07:17:58 ProcessNewBlock: ACCEPTED 419463 71366b0a87d43cd1a9d539948f6d571c385be150a0ccc96ba420be6260fa4b85 (pos)
2018-09-26 07:17:58 ProcessNewBlock: ACCEPTED 419463 71366b0a87d43cd1a9d539948f6d571c385be150a0ccc96ba420be6260fa4b85 (pos)
2018-09-26 07:17:58 ProcessNewBlock: ACCEPTED 419463 71366b0a87d43cd1a9d539948f6d571c385be150a0ccc96ba420be6260fa4b85 (pos)
2018-09-26 07:17:58 ProcessNewBlock: ACCEPTED 419463 71366b0a87d43cd1a9d539948f6d571c385be150a0ccc96ba420be6260fa4b85 (pos)

Provided gitian descriptors do not work

Provided linux binaries use shared libraries. An attempt to build a static version of master branch from the repository using gitian builder has failed since can't find a submodule. It seems there is no such submodule at all by the path.

The gitian builder tested for many coins, so the issue is with Lux descriptors and/or non-standard build sequence (in that case the descriptors must be fixed):

Initialized empty Git repository in /home/debian/gitian-builder/inputs/lux/.git/
remote: Enumerating objects: 161, done.
remote: Counting objects: 100% (161/161), done.
remote: Compressing objects: 100% (110/110), done.
remote: Total 24638 (delta 98), reused 84 (delta 51), pack-reused 24477
Receiving objects: 100% (24638/24638), 155.08 MiB | 5.67 MiB/s, done.
Resolving deltas: 100% (17339/17339), done.
From https://github.com/lux-core/lux
 * [new tag]           v4.3.1                   -> v4.3.1
 * [new tag]           v5.0.0                   -> v5.0.0
 * [new tag]           v5.0.1                   -> v5.0.1
 * [new tag]           v5.0.2                   -> v5.0.2
 * [new tag]           v5.0.3                   -> v5.0.3
 * [new tag]           v5.1.0                   -> v5.1.0
 * [new tag]           v5.2.0                   -> v5.2.0
 * [new tag]           v5.2.1                   -> v5.2.1
 * [new tag]           v5.2.2                   -> v5.2.2
 * [new tag]           v5.2.3                   -> v5.2.3
 * [new tag]           v5.2.5                   -> v5.2.5
 * [new branch]        5.2.X                    -> 5.2.X
 * [new branch]        5.3.X                    -> 5.3.X
 * [new branch]        HDWallet                 -> HDWallet
 * [new branch]        Networking               -> Networking
 * [new branch]        PoS                      -> PoS
 * [new branch]        SPV                      -> SPV
 * [new branch]        TradingPlot              -> TradingPlot
 * [new branch]        backup-master            -> backup-master
 * [new branch]        bip174                   -> bip174
 * [new branch]        btc-0.16                 -> btc-0.16
 * [new branch]        bug_fix                  -> bug_fix
 * [new branch]        bugfix                   -> bugfix
 * [new branch]        coldstake                -> coldstake
 * [new branch]        development              -> development
 * [new branch]        dfs                      -> dfs
 * [new branch]        docker                   -> docker
 * [new branch]        hd_button_encrypted      -> hd_button_encrypted
 * [new branch]        i2p                      -> i2p
 * [new branch]        logrotation              -> logrotation
 * [new branch]        luxgate                  -> luxgate
 * [new branch]        luxgate-fix-sig          -> luxgate-fix-sig
 * [new branch]        luxgate-fix-zmq-undef    -> luxgate-fix-zmq-undef
 * [new branch]        luxgate-global-orderbook -> luxgate-global-orderbook
 * [new branch]        luxgate-qt               -> luxgate-qt
 * [new branch]        luxgate-testing          -> luxgate-testing
 * [new branch]        luxgate-ui               -> luxgate-ui
 * [new branch]        master                   -> master
 * [new branch]        metrics                  -> metrics
 * [new branch]        mining-tests             -> mining-tests
 * [new branch]        p2p-network              -> p2p-network
 * [new branch]        pos-signing              -> pos-signing
 * [new branch]        refactoring              -> refactoring
 * [new branch]        rpc                      -> rpc
 * [new branch]        testing                  -> testing
 * [new branch]        testnet                  -> testnet
 * [new branch]        tests                    -> tests
 * [new branch]        time_drift               -> time_drift
 * [new branch]        topia_keypool_issue      -> topia_keypool_issue
 * [new branch]        tran                     -> tran
 * [new branch]        ubuntu-18.10             -> ubuntu-18.10
 * [new branch]        v6.0.X                   -> v6.0.X
 * [new branch]        web3-api                 -> web3-api
 * [new branch]        win-bug                  -> win-bug
Submodule 'src/lux-installer' (https://github.com/216k155/lux-installer.git) registered for path 'src/lux-installer'
Cloning into '/home/debian/gitian-builder/inputs/lux/src/lux-installer'...
Username for 'https://github.com': git
Password for 'https://[email protected]':
remote: Invalid username or password.

error loading block database

Hi,

My wallet windows 4.2 stop syncing with network around the 26th july. So i tried to install the latest mercury 5.1 windows wallet and since then, i can't open my 4.2 wallet, i'm having the error error loading block database.

I tried to restore my backup on the 5.1 i got the message can't obtain a lock on data directory users/me/appData/Roaming/Lux luxcore is probably already running. But I don't see anything running.

I downloaded version 5.2.2 but when I restore my wallet I got the following messages :
Unable to bind to 0.0.0.0:26969 on this computer. Luxcore is probably already running.
Failed to listen on any port. Use -listen=0 if you want this.
I tried on windows 7 and mac os X sierra, both OS are giving the same error messages.

How can i get around this?

fork lux coin

hi, can we with you to make a fork of your coin with your help ??

Que hago

Para empesar todo es en ingles y no se ni ablar menos leer inglis podrian traducirmelo al español mexico x fa y esplicarme paso a paso que debo haser
Gracias x su comprencion

No block source available

Hello,

My wallet says "No block source available" and it is "8 days behind".

I am using version 5.2.2.0-a2083ff that I compiled myself on linux

What should I do?

Thank you

Make - Error 'Failing to include Boost library':

uname -a:
GE70-2OC-2OE 4.18.0-25-generic #26~18.04.1-Ubuntu SMP Thu Jun 27 07:28:31 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Error 'Failing to include Boost library':

make
Making all in src
make[1]: Entering directory '/home/philfrom1983/lux/src'
make[2]: Entering directory '/home/philfrom1983/lux/src'
make[3]: Entering directory '/home/philfrom1983/lux/src/secp256k1'
make[3]: Leaving directory '/home/philfrom1983/lux/src/secp256k1'
CXXLD luxd
libbitcoin_common.a(libbitcoin_common_a-ChainParams.o): In function std::unordered_set<dev::FixedHash<20u>, std::hash<dev::FixedHash<20u> >, std::equal_to<dev::FixedHash<20u> >, std::allocator<dev::FixedHash<20u> > > dev::eth::commit<dev::MemoryDB>(std::unordered_map<dev::FixedHash<20u>, dev::eth::Account, std::hash<dev::FixedHash<20u> >, std::equal_to<dev::FixedHash<20u> >, std::allocator<std::pair<dev::FixedHash<20u> const, dev::eth::Account> > > const&, dev::SpecificTrieDB<dev::FatGenericTrieDB<dev::MemoryDB>, dev::FixedHash<20u> >&)': /usr/include/boost/random/uniform_int_distribution.hpp:220: undefined reference to boost::random::random_device::operator()()'
libbitcoin_common.a(libbitcoin_common_a-State.o): In function unsigned long boost::random::detail::generate_uniform_int<boost::random::random_device, unsigned long>(boost::random::random_device&, unsigned long, unsigned long, mpl_::bool_<true>)': /usr/include/boost/random/uniform_int_distribution.hpp:117: undefined reference to boost::random::random_device::operator()()'
/usr/include/boost/random/uniform_int_distribution.hpp:220: undefined reference to boost::random::random_device::operator()()' /usr/include/boost/random/uniform_int_distribution.hpp:69: undefined reference to boost::random::random_device::operator()()'
libbitcoin_common.a(libbitcoin_common_a-State.o): In function dev::eth::CodeSizeCache::store(dev::FixedHash<32u> const&, unsigned long)': /usr/include/boost/random/uniform_int_distribution.hpp:220: undefined reference to boost::random::random_device::operator()()'
libbitcoin_common.a(libbitcoin_common_a-ICAP.o):/usr/include/boost/random/uniform_int_distribution.hpp:220: more undefined references to boost::random::random_device::operator()()' follow libbitcoin_common.a(libbitcoin_common_a-FixedHash.o): In function __static_initialization_and_destruction_0':
/home/philfrom1983/lux/src/cpp-ethereum/libdevcore/FixedHash.cpp:29: undefined reference to boost::random::random_device::random_device()' /home/philfrom1983/lux/src/cpp-ethereum/libdevcore/FixedHash.cpp:29: undefined reference to boost::random::random_device::~random_device()'
collect2: error: ld returned 1 exit status
Makefile:5350: recipe for target 'luxd' failed
make[2]: *** [luxd] Error 1
make[2]: Leaving directory '/home/philfrom1983/lux/src'
Makefile:16242: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/philfrom1983/lux/src'
Makefile:636: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Fix:

./make LIBS+=-lboost_random

balance inconsistency

Hi,

After importing priv key on a linux machine the balance value is different:

./lux-cli getinfo
"balance": 16128.80000000, <--- balance ok

./lux-cli listaddressgroupings
[
"Lxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
16129.00000000, <--- it shows balance including immature transactions ... ok
"mn1"
]

./lux-cli getbalance
16128.80000000 <--- balance ok

./lux-cli getbalance mn1
16226.40000000 <----- ???

I restarted luxd with -rescan option

I would like to import multiple addresses and acquire the balance for every address individually
Any ideas ?

thanks,
Andrei

immature amount less than 1 LUX included in balance

hi,

I compiled master and the issue opened on 216k's github is not fixed so I'm opening again:

./lux-cli getinfo
{
"version": 5020000,
"protocolversion": 69500,
"walletversion": 61000,

./lux-cli listtransactions
look at amount ... it shows 0.0000 and it should be 0.2 lux reward
{
"account": "",
"address": "Lxxxxxxxxx",
"category": "immature",
"amount": 0.00000000,
"label": "",
"vout": 2,
"confirmations": 19,
"bcconfirmations": 19,
"generated": true,

./lux-cli getbalance
16124.20000000 <-- here are included all 0.2 LUX with less than 80 confirmations

Andrei

Wallet not syncing

using latet wallet: v5.5.0.0-bf495ad9-Luxcore
number of connections: 11
stuck at block: 1612505
last blocktime: Thu Feb 18 00:58:06 2021

Lux-qt

Problem with lux-qt
BTW: Awesome coin and glad Tanguy is now on the team!

tested in lux.conf
stake=0 and mint=0 does not stop the wallet from staking.

Further TX outputs listed in masternodes.conf are not kept from staking or blocked from spending with a Lock ICON.

When unlocking the wallet to send MN generated inputs during the transaction countdown (5 seconds) to press ok the 16120lux stakes almost instantly requiring an 80 block wait and regeneration of the masternode output.

The current workaround solution we are using is to sync the wallet, close the wallet. Wait a few blocks and quickly make the transaction before the wallet is fully synced again so staking function can't enable.

I realize lux now has a stronger team and a real path forward and wanted to bring this SMALL issue forward that MN holders are experiencing.

Please advise if we have made a mistake somewhere. Thank you!

Integrate decentralized file storage with ipfs

Decentralized file storage (dfs) can be integrated with ipfs ipfs, but there are some difficulties:

  • Dfs cannot use the storage format of a file that uses ipfs
  • Dfs will not support the feature set used in ipfs
  • Files stored in dfs will not be accessible from ipfs.

In this regard, the module of interaction between ipfs and dfs is required.

ProcessNewBlock: block not accepted

Hello there,
during first blockchain download I have this error:

2021-11-29 22:24:15 ERROR: CheckProof: prevented masternode from staking
2021-11-29 22:24:15 ERROR: CheckWork: invalid proof-of-stake (block 2110380f4899658bb8a68f0b42da7b163534d2932d19e99a284b5a3638185382)
2021-11-29 22:24:15 ERROR: ProcessNewBlock: block not accepted
2021-11-29 22:24:34 ERROR: CheckProof: prevented masternode from staking
2021-11-29 22:24:34 ERROR: CheckWork: invalid proof-of-stake (block 2110380f4899658bb8a68f0b42da7b163534d2932d19e99a284b5a3638185382)
2021-11-29 22:24:34 ERROR: ProcessNewBlock: block not accepted
2021-11-29 22:25:50 ERROR: CheckProof: prevented masternode from staking
2021-11-29 22:25:50 ERROR: CheckWork: invalid proof-of-stake (block 2110380f4899658bb8a68f0b42da7b163534d2932d19e99a284b5a3638185382)
2021-11-29 22:25:50 ERROR: ProcessNewBlock: block not accepted
2021-11-29 22:25:54 ERROR: CheckProof: prevented masternode from staking
2021-11-29 22:25:54 ERROR: CheckWork: invalid proof-of-stake (block 2110380f4899658bb8a68f0b42da7b163534d2932d19e99a284b5a3638185382)
2021-11-29 22:25:54 ERROR: ProcessNewBlock: block not accepted

Could you please help me?

Can't mine

[2021-03-24 18:06:12] POOL 0: 127.0.0.1:26969 USER user -s 10
[2021-03-24 18:06:12] CUDA GPU 0 matches NVML GPU 0 by busId 1
[2021-03-24 18:06:12] NVML GPU monitoring enabled.
[2021-03-24 18:06:12] CUDA GPU 0 matches NVAPI GPU 0 by busId 1
[2021-03-24 18:06:12] NVAPI GPU monitoring enabled.
[2021-03-24 18:06:12] 1 miner thread started, using 'rx2' algorithm.
[2021-03-24 18:06:12] HTTP request failed: Empty reply from server
[2021-03-24 18:06:12] get_work failed, retry after 30 seconds

Packages/macOS_SDK_headers_for_macOS_10.14.pkg not there anymore

Hi

I am following the OSX build instructions in OSX 15 beta, probably it is similar in OSX 14. The .pkg does not seem to be there anymore, instead there are directories of this kind

/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/Library/Apple/System/Library/

Any ideas what this means for the future of OSX compiling?

Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.