[ANN] [JUDGE] Judge Coin | Multipool is UP @ http://judge.bemining.net/

[jc12345]

All staking coins in every wallet goes to the dev wallet

True of FUD?  

Well, wallet link removed so you can judge now!!

who can confirm what he is saying?

The PoS never kicked in.  We just posted the FIX!  Please see the block explorer http://chainz.cryptoid.info/judge/

If you want 15m coins in circulation and you are planning a hard fork at 6000 after which POS kicks in, should you not then instead of making the blocks fewer, make it more to about 53500?

It seems that the hard fork will kick in then at 2014/07/09 23:46 PM GMT. If the current block explorer is up to date and POS kicks in at block 6000, POW will then end at 2014/07/21 7:46 AM GMT and total money supply will be an estimated 11,157,000. Extending the blocks to 53500 takes end of POW to 2014/07/26 11:39 AM GMT and money supply up to an estimated 14,872,000. P.S. POS block rewards are negligible.

I could of course be completely wrong

[Mastermine]

All staking coins in every wallet goes to the dev wallet

True of FUD?  

Well, wallet link removed so you can judge now!!

who can confirm what he is saying?

The PoS never kicked in.  We just posted the FIX!  Please see the block explorer http://chainz.cryptoid.info/judge/

If you want 15m coins in circulation and you are planning a hard fork at 6000 after which POS kicks in, you should instead of making the blocks fewer, make it more to about 53500.

It seems that the hard fork will kick in then at 2014/07/09 23:46 PM GMT. If the current block explorer is up to date and POS kicks in at block 6000, POW will then end at 2014/07/21 7:46 AM GMT and total money supply will be an estimated 11,157,000. Extending the blocks to 53500 takes end of POW to 2014/07/26 11:39 AM GMT and money supply up to an estimated 14,872,000.

I could of course be completely wrong

did someone screw up on some math? someone better get on this my brain doesnt want to think that hard .

[fairglu]

Judge Explorer updated to 1.1!

Also now displays hashrate, BITTREX ticker and I tagged a part of BITTREX wallet.

[henningml]

Compilation on a clean Ubuntu system with necessary libraries fails for statisticspage.cpp due to an ambiguous overload. My workaround (which doesn't seem to break anything) is to change line 72 to:

Code:

QString qVolume = QString::number(volume);

This should be fixed as well.

[Rainer4256]

Compilation on a clean Ubuntu system with necessary libraries fails for statisticspage.cpp due to an ambiguous overload. My workaround (which doesn't seem to break anything) is to change line 72 to:

Code:

QString qVolume = QString::number(volume);

This should be fixed as well.

+1 This should get fixed in the source. Is there any ETA for the source code?

[MinerMario]

Ouch, rough market folks. About 90% sell..

Come on guys you have to buy coins if you believe. A few hard buy walls are in place to keep the price here, but once those are pulled.....

Put some BTC into this. I am. 

[judgecrypto]

Compilation on a clean Ubuntu system with necessary libraries fails for statisticspage.cpp due to an ambiguous overload. My workaround (which doesn't seem to break anything) is to change line 72 to:

Code:

QString qVolume = QString::number(volume);

This should be fixed as well.

+1 This should get fixed in the source. Is there any ETA for the source code?

Thanks for staying on this.  Since we are facing a pretty hefty change I froze all other minor fixes until the PoS code is 100% working.  While small changes in code may appear innocuous they have the potential to cause unforeseen issues.  Best practice at this point is to only introduce changes necessary to fix the immediate issue at hand.

Once the PoS issue is fixed we can go through and fix the minor bugs on a minor version release.

Then once the minor bugs are fixed we can do any UI tweaks.

EDIT: Source link https://github.com/judgecrypto/judgecoin

[judgecrypto]

All staking coins in every wallet goes to the dev wallet

True of FUD?  

Well, wallet link removed so you can judge now!!

who can confirm what he is saying?

The PoS never kicked in.  We just posted the FIX!  Please see the block explorer http://chainz.cryptoid.info/judge/

If you want 15m coins in circulation and you are planning a hard fork at 6000 after which POS kicks in, should you not then instead of making the blocks fewer, make it more to about 53500?

It seems that the hard fork will kick in then at 2014/07/09 23:46 PM GMT. If the current block explorer is up to date and POS kicks in at block 6000, POW will then end at 2014/07/21 7:46 AM GMT and total money supply will be an estimated 11,157,000. Extending the blocks to 53500 takes end of POW to 2014/07/26 11:39 AM GMT and money supply up to an estimated 14,872,000. P.S. POS block rewards are negligible.

I could of course be completely wrong

We know there will be 6000 pure PoW blocks... 6000 x 500 = 3,000,000 coins
The max coins during block 6000 - 38640 IF all blocks were PoW would be ... 16,320,000
That would give a potential of 19,320,000 coins

However we are probably left with...
6000 pure PoW blocks... 6000 x 500 = 3,000,000 coins
38640 - 6000 = 32640 block / 2 = 16320 x 500 = 8,160,000
Total coin potential = 11,160,000 + PoS blocks.  From what I have seen it is not a 50/50 split though.  The END result will be a total between 11,160,000 - 16,320,000.  Maybe we should have a REDDIT contest to see who can guess the total after PoW?

[Rainer4256]

Compilation on a clean Ubuntu system with necessary libraries fails for statisticspage.cpp due to an ambiguous overload. My workaround (which doesn't seem to break anything) is to change line 72 to:

Code:

QString qVolume = QString::number(volume);

This should be fixed as well.

+1 This should get fixed in the source. Is there any ETA for the source code?

Thanks for staying on this.  Since we are facing a pretty hefty change I froze all other minor fixes until the PoS code is 100% working.  While small changes in code may appear innocuous they have the potential to cause unforeseen issues.  Best practice at this point is to only introduce changes necessary to fix the immediate issue at hand.

Once the PoS issue is fixed we can go through and fix the minor bugs on a minor version release.

Then once the minor bugs are fixed we can do any UI tweaks.

EDIT: Source link https://github.com/judgecrypto/judgecoin

I tried to build it, no luck. After I changed the line mentioned by rarkenin I also had to add the link to my Berkeley database in the Makefile: CXX=g++ --> CXX=g++ -I /usr/local/BerkeleyDB.5.1/include
After building 20 minutes I got:

Code:

/usr/bin/ld: cannot find -ldb_cxx
collect2: error: ld returned 1 exit status

Any ideas?

[Gibcity]

holy dumpage batman

[MinerMario]

holy dumpage batman

Rough out here. Can't keep any rally going. They just dump into the buy walls. Ouch.

Well, in the for the long haul. Just keep picking up these weak hands.

[karimdr2]

Compilation on a clean Ubuntu system with necessary libraries fails for statisticspage.cpp due to an ambiguous overload. My workaround (which doesn't seem to break anything) is to change line 72 to:

Code:

QString qVolume = QString::number(volume);

This should be fixed as well.

+1 This should get fixed in the source. Is there any ETA for the source code?

Thanks for staying on this.  Since we are facing a pretty hefty change I froze all other minor fixes until the PoS code is 100% working.  While small changes in code may appear innocuous they have the potential to cause unforeseen issues.  Best practice at this point is to only introduce changes necessary to fix the immediate issue at hand.

Once the PoS issue is fixed we can go through and fix the minor bugs on a minor version release.

Then once the minor bugs are fixed we can do any UI tweaks.

EDIT: Source link https://github.com/judgecrypto/judgecoin

I tried to build it, no luck. After I changed the line mentioned by rarkenin I also had to add the link to my Berkeley database in the Makefile: CXX=g++ --> CXX=g++ -I /usr/local/BerkeleyDB.5.1/include
After building 20 minutes I got:

Code:

/usr/bin/ld: cannot find -ldb_cxx
collect2: error: ld returned 1 exit status

Any ideas?

add BDB_LIB_SUFFIX=-5.1 in *.pro file

[Rainer4256]

add BDB_LIB_SUFFIX=-5.1 in *.pro file

This made it even worse. I got tons of undefined references in bitcoin.cpp, bitcoingui.cpp etc. Too long to post here.

Examples

Code:

bitcoin.cpp:(.text+0xacc): Undefined reference to `QString::fromAscii(char const*, int)'
bitcoingui.cpp:(.text+0x195): Undefined reference to `QMetaObject::tr(char const*, char const*) const'

Thank you anyway for trying to help.

[karimdr2]

add BDB_LIB_SUFFIX=-5.1 in *.pro file

This made it even worse. I got tons of undefined references in bitcoin.cpp, bitcoingui.cpp etc. Too long to post here.

Examples

Code:

bitcoin.cpp:(.text+0xacc): Undefined reference to `QString::fromAscii(char const*, int)'
bitcoingui.cpp:(.text+0x195): Undefined reference to `QMetaObject::tr(char const*, char const*) const'

Thank you anyway for trying to help.

I just compiled on ubuntu 14.04 without problems.
purge libdb and install this:

aptitude install libdb-dev

and keep the original *.pro

[Rainer4256]

add BDB_LIB_SUFFIX=-5.1 in *.pro file

This made it even worse. I got tons of undefined references in bitcoin.cpp, bitcoingui.cpp etc. Too long to post here.

Examples

Code:

bitcoin.cpp:(.text+0xacc): Undefined reference to `QString::fromAscii(char const*, int)'
bitcoingui.cpp:(.text+0x195): Undefined reference to `QMetaObject::tr(char const*, char const*) const'

Thank you anyway for trying to help.

I just compiled on ubuntu 14.04 without problems.
purge libdb and install this:

aptitude install libdb-dev

and keep the original *.pro

I did what you suggested. Now I got this:

Code:

/usr/bin/ld: cannot find -ldb_cxx
collect2: error: ld returned 1 exit status

Code:

sudo locate db_cxx
/usr/include/db_cxx.h
/usr/lib/libdb_cxx-5.1.so
/usr/lib/libdb_cxx-5.3.so
/usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.a
/usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so
/usr/lib/x86_64-linux-gnu/libdb_cxx.a
/usr/lib/x86_64-linux-gnu/libdb_cxx.so
/usr/local/db_cxx.h
/usr/local/BerkeleyDB.4.8/docs/programmer_reference/upgrade_3_0_db_cxx.html
/usr/local/BerkeleyDB.4.8/include/db_cxx.h
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.a
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.la
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.so
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.so
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx.a
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx.so

[judgecrypto]

holy dumpage batman

Rough out here. Can't keep any rally going. They just dump into the buy walls. Ouch.

Well, in the for the long haul. Just keep picking up these weak hands.

The price is like a woman... she will go where she wants to go.  You can try to control a woman but in reality you never can.

If the price drops people who are interested will buy.  We are building a good long term structure for the coin.

[MinerMario]

holy dumpage batman

Rough out here. Can't keep any rally going. They just dump into the buy walls. Ouch.

Well, in the for the long haul. Just keep picking up these weak hands.

The price is like a woman... she will go where she wants to go.  You can try to control a woman but in reality you never can.

If the price drops people who are interested will buy.  We are building a good long term structure for the coin.

Good analogy. Just shocked at the level of dumping man There are massive buy walls being thrown up, 1 BTC and better and they are just getting eaten alive. Wow.

Doesn't matter to me though my coins are in play now but they will be back in wallet for POS.

Keep up the good work.

[judgecrypto]

ALL POOLS HAVE BEEN REMOVED UNTIL THEY VERIFY THEY ARE ON VERSION 1.1.0.
*** Pool OPS Just Send me a PM or post in the thread to let me know you have updated. ***
*** HARD FORK AT BLOCK 6000 to FIX the PoS issue. ***

[Rainer4256]

add BDB_LIB_SUFFIX=-5.1 in *.pro file

This made it even worse. I got tons of undefined references in bitcoin.cpp, bitcoingui.cpp etc. Too long to post here.

Examples

Code:

bitcoin.cpp:(.text+0xacc): Undefined reference to `QString::fromAscii(char const*, int)'
bitcoingui.cpp:(.text+0x195): Undefined reference to `QMetaObject::tr(char const*, char const*) const'

Thank you anyway for trying to help.

I just compiled on ubuntu 14.04 without problems.
purge libdb and install this:

aptitude install libdb-dev

and keep the original *.pro

I did what you suggested. Now I got this:

Code:

/usr/bin/ld: cannot find -ldb_cxx
collect2: error: ld returned 1 exit status

Code:

sudo locate db_cxx
/usr/include/db_cxx.h
/usr/lib/libdb_cxx-5.1.so
/usr/lib/libdb_cxx-5.3.so
/usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.a
/usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so
/usr/lib/x86_64-linux-gnu/libdb_cxx.a
/usr/lib/x86_64-linux-gnu/libdb_cxx.so
/usr/local/db_cxx.h
/usr/local/BerkeleyDB.4.8/docs/programmer_reference/upgrade_3_0_db_cxx.html
/usr/local/BerkeleyDB.4.8/include/db_cxx.h
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.a
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.la
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.so
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.so
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx.a
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx.so

I can't even build the daemon. Same crappy "db_cxx" error. I think this won't build here and my JUDGE are lost. Congrats!

[judgecrypto]

add BDB_LIB_SUFFIX=-5.1 in *.pro file

This made it even worse. I got tons of undefined references in bitcoin.cpp, bitcoingui.cpp etc. Too long to post here.

Examples

Code:

bitcoin.cpp:(.text+0xacc): Undefined reference to `QString::fromAscii(char const*, int)'
bitcoingui.cpp:(.text+0x195): Undefined reference to `QMetaObject::tr(char const*, char const*) const'

Thank you anyway for trying to help.

I just compiled on ubuntu 14.04 without problems.
purge libdb and install this:

aptitude install libdb-dev

and keep the original *.pro

I did what you suggested. Now I got this:

Code:

/usr/bin/ld: cannot find -ldb_cxx
collect2: error: ld returned 1 exit status

Code:

sudo locate db_cxx
/usr/include/db_cxx.h
/usr/lib/libdb_cxx-5.1.so
/usr/lib/libdb_cxx-5.3.so
/usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.a
/usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so
/usr/lib/x86_64-linux-gnu/libdb_cxx.a
/usr/lib/x86_64-linux-gnu/libdb_cxx.so
/usr/local/db_cxx.h
/usr/local/BerkeleyDB.4.8/docs/programmer_reference/upgrade_3_0_db_cxx.html
/usr/local/BerkeleyDB.4.8/include/db_cxx.h
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.a
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.la
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.so
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.so
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx.a
/usr/local/BerkeleyDB.4.8/lib/libdb_cxx.so

I can't even build the daemon. Same crappy "db_cxx" error. I think this won't build here and my JUDGE are lost. Congrats!

Why would you Judge be lost?  Save your wallet.dat file.  Do you not have the old wallet?