Quote from: xeroc on October 07, 2015, 07:10:56 am

Quote from: Troglodactyl on October 07, 2015, 01:54:33 am

Can someone who can successfully build and run graphene-ui report their nodejs version?

node -v
v4.1.1

Thanks.  I'm on v4.1.2 and I'm getting this on "npm install":

Code: [Select]

In file included from ../src/contextify.cc:3:0:
../node_modules/nan/nan.h:261:25: error: redefinition of ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Local<T>)’
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) {
                         ^
../node_modules/nan/nan.h:256:25: note: ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Handle<T>)’ previously declared here
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) {
                         ^
../node_modules/nan/nan.h:661:13: error: ‘node::smalloc’ has not been declared
     , node::smalloc::FreeCallback callback
             ^
../node_modules/nan/nan.h:661:35: error: expected ‘,’ or ‘...’ before ‘callback’
     , node::smalloc::FreeCallback callback
                                   ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(char*, size_t, int)’:
../node_modules/nan/nan.h:665:50: error: ‘callback’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                  ^
../node_modules/nan/nan.h:665:60: error: ‘hint’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                            ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(const char*, uint32_t)’:
../node_modules/nan/nan.h:672:67: error: no matching function for call to ‘New(v8::Isolate*, const char*&, uint32_t&)’
     return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
I've traced it to this issue with contextify: https://github.com/brianmcd/contextify/issues/180

But I have no idea why it's working for you.  Is this an issue for anyone else?  Does anyone have any ideas?

Has anyone else done a fresh clone and build on NodeJS > 4 recently?

Fees can be changed by stakeholder vote, but it seems unlikely that they'll be low enough to support true microtransactions.

Can someone who can successfully build and run graphene-ui report their nodejs version?

Here's a backup of the synced chain from yesterday.  Hope it helps someone...

https://mega.nz/#!CVUzxZpL!4m8Ee8c1rD6fOluqqq7HROMmOG2ERmidykBQRO2GlU8

Quote

A negative miner is one who joins a pool, collects their share, but never returns a wining hash

Aren't pool rewards paid out per share? One share is a solved POW, so if you don't submit a winning hash, you don't have a share in the first place.

To calculate hash rate, pool miners turn in all hashes that meet a significantly lower difficulty level than the mined chain difficulty level to the pool.  Pool payouts are based on how many of these easier hashes each miner submits, as they represent the amount of hash power each miner is contributing.  Miners submitting every single hash regardless of its score would be horribly inefficient; they only submit hashes above the pools set difficulty level, so the vast majority of hashes submitted to the pool are above the pool difficulty but below the blockchain's current difficulty level.

A negative miner is a miner who adds an additional filter onto their mining software so that it submits only hashes that are between the pool difficulty and the chain difficulty, instead of all hashes above the pool difficulty.  This will make very little difference in the miner's payouts from the pool, but it means that the miner is contributing no value at all to the pool.

Quote from: Troglodactyl on October 04, 2015, 12:58:53 pm

Can't we restart the network with checkpoints instead of waiting for bm to do it?  I'm assuming the stress testing just delayed some nodes' block production and caused forking until no branch had minimum participation.

Sounds reasonable, so how do you determine a correct checkpoint parameter value to use in the config.ini file? I have several VPSs ready to go that will serve as a seed once that is determined.

I'm not sure, but I think we need all witnesses to add this checkpoint to their config files: ["36472", "00008e780f52da8c7a599c3a1d0b8dfeaf3a331d"]

Then we probably need one person to enable stale production, and then it's possible that everyone will need to additionally add the first new block on the stale chain as a checkpoint.

Regardless, this is something we need to test and figure out how to do now on the test network.  We shouldn't plan on being totally reliant on bm to fix it if anything breaks.

https://github.com/brianmcd/contextify/issues/180

Running into this when building graphene-ui with the latest NodeJS versions, and it looks like react-foundation-apps doesn't like some of the older versions.

Can someone with an unbroken build configuration post what version they're using?