Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)
Pages:
Author

Topic: [MOJO] MOJOv3 has been taken over by new devs - page 50. (Read 167315 times)

hagie
hero member
Activity: 792
Merit: 501
Re: [MOJO] MOJOv3 has been taken over by new devs
July 28, 2016, 03:02:30 AM
#1680
uhmm ...

looks like there is still an error in the staking. After hit an stake block the staking dies with these error messages in the log :

Code:
2016-07-27 12:33:36 CheckStake() : new proof-of-stake block found  
  hash: 131ca7ac016a8b4a59d55c77d2aedbfbc96a3ea1a197759e25436addaa28d955 
proofhash: 0000000000000000000000000000000000000000000000000000000000000000  
target: 0000000000000000000000000000000000000000000000000000000000000000
2016-07-27 12:33:36 CBlock(hash=131ca7ac016a8b4a59d55c77d2aedbfbc96a3ea1a197759e25436addaa28d955, ver=7, hashPrevBlock=7f32a3388d440fa2f64f6896d7da1e5cdc8cb96521acb0617e41c1e099a2dc4b, hashMerkleRoot=325c33ed41fef8bf0074e9e31ee72c304bcb846ea4a565609b194be064e38c00, nTime=1469622816, nBits=1e0fffff, nNonce=0, vtx=2, vchBlockSig=304402201b0334baa08c5e07f9d579f72b471eaedae251d875aecb7a63d8cbe39dc005300220772d80f76d364d5738bdd4928996dc6da3dda59795c28c0f8c8bb432a2e67865)
  Coinbase(hash=0b220017171219bc0894d1ce51eb646c6be50d8fdee5a7fbf9c7e422ceca2ce4, nTime=1469622816, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, 4294967295), coinbase 02e476)
    CTxOut(empty)

  Coinstake(hash=9302a8513ed87c657bcffd57b04cd058436524b3732ddad9d01729fd81731a45, nTime=1469622816, ver=1, vin.size=11, vout.size=3, nLockTime=0)
    CTxIn(COutPoint(3bf67c3c3e, 3), scriptSig=3045022100d9f605980ec7da)
    CTxIn(COutPoint(91a47f0713, 2), scriptSig=3044022078387721a2126980)
    CTxIn(COutPoint(2523588a95, 2), scriptSig=3045022100ce48ae6cd722b4)
    CTxIn(COutPoint(1bdfcc0164, 2), scriptSig=30450221008d48820a19aa4d)
    CTxIn(COutPoint(b12060238b, 3), scriptSig=3045022100802793d236b288)
    CTxIn(COutPoint(4ea55f1153, 2), scriptSig=3045022100c3bcf9e5186b53)
    CTxIn(COutPoint(61406675d6, 2), scriptSig=3044022075dd820216231024)
    CTxIn(COutPoint(91bcba38a6, 3), scriptSig=3045022100e1018e1fd632e8)
    CTxIn(COutPoint(bf3368d5f2, 3), scriptSig=304402200bc8a7ab3a8e7539)
    CTxIn(COutPoint(9bdf6a3bce, 2), scriptSig=3045022100d988d273ed7aa2)
    CTxIn(COutPoint(c506311bb2, 2), scriptSig=3044022041c6ab9cd34459e3)
    CTxOut(empty)
    CTxOut(nValue=3.82228535, scriptPubKey=0330b99c0b2d80a4f3d74968f2d51906fd3efa535491f82caaf295b1e96c05cf74 OP_CHECKSIG)
    CTxOut(nValue=0.00369863, scriptPubKey=OP_DUP OP_HASH160 e5a8f835d95138afe2f1e5aab9080aa3f1821a66 OP_EQUALVERIFY OP_CHECKSIG)

  vMerkleTree:  0b220017171219bc0894d1ce51eb646c6be50d8fdee5a7fbf9c7e422ceca2ce4 9302a8513ed87c657bcffd57b04cd058436524b3732ddad9d01729fd81731a45 325c33ed41fef8bf0074e9e31ee72c304bcb846ea4a565609b194be064e38c00

2016-07-27 12:33:36 out 3.82598398
2016-07-27 12:33:36 CheckBlock() : Found payment(1|369863) or payee(1|3QJmnh) nHeight 30436. 
2016-07-27 12:33:36 CheckBlock() : Found payment(1|369863) or payee(1|3QJmnh) nHeight 30436. 
2016-07-27 12:33:36 ERROR: ConnectInputs() : 9302a8513ed87c657bcffd57b04cd058436524b3732ddad9d01729fd81731a45 prev tx already used at (nFile=1, nBlockPos=14708372, nTxPos=14708520)
2016-07-27 12:33:36 InvalidChainFound: invalid block=131ca7ac016a8b4a59d55c77d2aedbfbc96a3ea1a197759e25436addaa28d955  height=30436  trust=5108375382480  blocktrust=1048577  date=07/27/16 12:33:36
2016-07-27 12:33:36 InvalidChainFound:  current best=7f32a3388d440fa2f64f6896d7da1e5cdc8cb96521acb0617e41c1e099a2dc4b  height=30435  trust=5108374333903  blocktrust=20400889458  date=07/27/16 12:30:58
2016-07-27 12:33:36 ERROR: SetBestChain() : SetBestChainInner failed
2016-07-27 12:33:36 ERROR: AcceptBlock() : AddToBlockIndex failed
2016-07-27 12:33:36 ERROR: ProcessBlock() : AcceptBlock FAILED
2016-07-27 12:33:36 ERROR: CheckStake() : ProcessBlock, block not accepted
2016-07-27 12:33:37 CheckStakeKernelHash() : using modifier 0xfc303d881bfbe613 at height=30435 timestamp=2016-07-27 12:30:58 UTC for block from timestamp=2016-07-26 11:24:00 UTC
2016-07-27 12:33:37 CheckStakeKernelHash() : check modifier=0xfc303d881bfbe613 nTimeBlockFrom=1469532240 nTimeTxPrev=1469532240 nPrevout=2 nTimeTx=1469622816 hashProof=e9d07bf6966da85f56dc6c14a510c770b8718043ee113137d1df88aa2ce8745a
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 ERROR: CheckStakeKernelHash() : min age violation
2016-07-27 12:33:37 CheckStakeKernelHash() : using modifier 0xfc303d881bfbe613 at height=30435 timestamp=2016-07-27 12:30:58 UTC for block from timestamp=2016-07-25 13:24:00 UTC
2016-07-27 12:33:37 CheckStakeKernelHash() : check modifier=0xfc303d881bfbe613 nTimeBlockFrom=1469453040 nTimeTxPrev=1469453040 nPrevout=2 nTimeTx=1469622816 hashProof=2e2aec1f5085a96332040b81b586dc05bc5c8900cc6f85f8c5eec026acda82ec
2016-07-27 12:33:37 CheckStakeKernelHash() : using modifier 0xfc303d881bfbe613 at height=30435 timestamp=2016-07-27 12:30:58 UTC for block from timestamp=2016-07-22 21:34:24 UTC
2016-07-27 12:33:37 CheckStakeKernelHash() : check modifier=0xfc303d881bfbe613 nTimeBlockFrom=1469223264 nTimeTxPrev=1469223264 nPrevout=3 nTimeTx=1469622816 hashProof=cf92debc2f603d3017cdfba5e8c0d738196783b2bccd827ae13450bd31997440
2016-07-27 12:33:37 Masternode payment to MUqVPa59DzNJxLsyZyQz4rTU5HFpHHui9o

the log is filed up with these messages and after some hhours it stops but no more staking occurs.

restart the wallet helps - this was mentioned several times.

regards

P.S. Thanks for the upvote of my steem posts :-)
hagie
hero member
Activity: 792
Merit: 501
Re: [MOJO] MOJOv3 has been taken over by new devs
July 28, 2016, 02:42:57 AM
#1679
Quote from: Emerger on July 27, 2016, 06:09:02 PM
Thank you for the guide. If I want to run a masternode and have > 200,000 coins, is it possible to stake my other coins normally on the same daemon? Or would I need to run a separate NON-masternode daemon to stake my additional coins? Thanks

There is an option - I will setup another MN today and test if this works.

The idea is to use the reservebalance=200000 statement in the .conf file for the daemon. This should keep your balance from being used by stake.

I will post results after 24h :-)

btw I would be happy if you take some time and check my posts on steem (signature) and leave an upvote
Thanks

regards

Emerger
full member
Activity: 199
Merit: 102
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 06:09:02 PM
#1678
Thank you for the guide. If I want to run a masternode and have > 200,000 coins, is it possible to stake my other coins normally on the same daemon? Or would I need to run a separate NON-masternode daemon to stake my additional coins? Thanks
CryptoHobo
legendary
Activity: 1050
Merit: 1000
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 04:13:47 PM
#1677
Quote from: FogHorn_LegHorn on July 27, 2016, 09:49:30 AM

All of my blocks are well past 24 hour min stake age. I have it unlocked for staking only now since new wallet release. One stake only. The wallet isn't staking correctly.


I take it you have multiple inputs? on a previous wallet I had to restart the wallet after each stake to stake the remaining inputs.
I've installed 2.1 on windows as the qt refuses to compile on linux (first missing leveldb then after sorting that secp256k1 and I gave up) but haven't imported my wallet yet as the previous problems meant i couldn't stake 24/7 anyway.

I'm just checking back occasionally to see how things are progressing.
EBK1000
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 03:30:24 PM
#1676
I have written a quick guide to how I set up a MOJO masternode. This worked for me but may not be the only method:

MN local controller wallet w/ 200k collateral / remote MN daemon method

I am using a Vultr 768MB Ram 1 CPU VPS with Ubuntu 14.04 for the MOJO Linux daemon

Log onto your VPS / remote server running Linux

I installed the dependencies for the MOJO Linux daemon as follows:
Code:
sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get install -y libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libgmp-dev libevent-dev libminiupnpc-dev libssl-dev
sudo add-apt-repository -y ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get install -y libdb4.8-dev libdb4.8++-dev
That is 6 different commands.

I uploaded the MOJO Linux daemon 'mojocoind' to /root/ at my VPS using FTP

Run the following command to make 'mojocoind' executable:
Code:
chmod +x ./mojocoind

Then start a “fresh” MOJO v.2.1 wallet locally in Windows with a “clean” wallet.dat not used before.
You can run several MOJO wallets with different data directories using the -datadir= switch.
Sync the wallet and name the default deposit address whatever you want.
Exit your wallet.

have the following in your local mojocoin.conf file:
Code:
server=1
rpcuser=dshdkhasldhalskhdlkajhdljslkdhjlsajwhatever
rpcpassword=sldhakjhdakjshdfka5d6a6d6as7dfjajswhatevernotthesame
rpcport=22255
listen=0
staking=0
logtimestamps=1
mnconflock=0
addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org

IT IS VITAL IT SEEMS TO SET THE staking=0 in the local mojocoin.conf

Send EXACTLY 200,000 MOJO to the local controller wallets address that you named as above. Wait for 10 confirmations.
Go to the console in your local controller wallet and run the command:
Code:
masternode genkey
This will give you your masternode private key which a long string (copy and keep it safe)

Then run the command:
Code:
masternode outputs
This should give you a transaction hash for your 200k MOJO and an index number 0 or 1 (copy and keep safe)

exit your local controller wallet and make / edit the local masternode.conf file like this:
Code:
aliasIP:portmasternodeprivkeytransaction-hashindex
The IP is the IP of your remote VPS and port is 22255
save and exit

on your remote VPS create or edit your remote mojocoin.conf file in /root/.Mojocoin.conf
It should contain the following only:
Code:
rpcuser=slkafhjlasfjmojojsrandom
rpcpassword=randomasdkd123344589dhfjf7jfdkdkkslkd7
masternode=1
masternodeprivkey=6xxxxxxxxxxxxxxxxxxxxxxxxxxxxc
(your masternode private key)

Go back to /root and start the 'mojocoind' with the command:
Code:
./mojocoind -daemon
It should say that the daemon is starting (you may have to hit enter if you don’t see the prompt again)
Check that the daemon is running with the command:
Code:
ps -ef
and look for something like:
Code:
root     16578     1  0 10:43 ?        00:03:30 ./mojocoind -daemon
This means the daemon is running and has loaded your masternode private key from the conf file

Then start the local MOJO wallet and let it sync (as long as you have update both the local mojocoin.conf and masternode.conf as above)
Go to console and issue the command:
Code:
masternode start-many
this should hopefully give you this:

Code:
masternode start-many

{
    "overall" : "Successfully started 1 masternodes, failed to start 0, total 1",
    "detail" : {
        "status" : {
            "alias" : "alias",
            "result" : "succesful"
        }
    }
}

This means that you have sent a start command to your remote server.

On your remote server you can issue the command:
Code:
./mojocoind masternode debug
and you should get:

root@mojomn01:~# ./mojocoind masternode debug
masternode started remotely
root@mojomn01:~#

This means that your remote masternode is now running.

Following this method I have managed to start a MN that is still running after more than 9 hours and has given 4 stake rewards. There may be other methods. Download the daemon from the OP.
EBK1000
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 10:06:43 AM
#1675
I'm doing a simple test stake with a Windows 2.1 wallet (run inside a VM, but this should not make a difference)

at 1600 hours (GMT, London) I made a deposit to a "clean" install wallet with only one address: MEzoqNwXYhSZyWroRrFe5rDiCkRXXcNNts
I sent 10,000 MOJO to this address and this is part of block number: https://chainz.cryptoid.info/mojo/block.dws?30583.htm

The mojocoin.conf file looks like this:
Code:
server=1
rpcallowip=127.0.0.1
rpcuser=mojo167fieuyoiv
rpcpassword=gfdtyuhbvfrt56yhbghjkiuytgfcvbn
listen=0
staking=1
addnode=mojonode01.mojocoin.org
addnode=mojonode02.mojocoin.org

So, I will follow this wallet for 24-48 hours and see how the stake reward works.
FogHorn_LegHorn
full member
Activity: 245
Merit: 100
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 09:49:30 AM
#1674
Quote from: hagie on July 27, 2016, 09:17:06 AM
The GUI is still a bit "buggy" ..

open your debug windows and enter "getmininginfo" there you can check the netstakeweight.

PoS is working I had some small stakes im my local wallet. It's important to unlock it for staking - check the lock symbol !

regards



Yes of course I have latest wallet installed. Here is my getmininginfo


10:46:33

getmininginfo


10:46:33

{
    "blocks" : 30556,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "netmhashps" : 526.91567756,
    "netstakeweight" : 6822.67724877,
    "errors" : "",
    "pooledtx" : 0,
    "stakeweight" : {
        "minimum" : 98643489398625,
        "maximum" : 0,
        "combined" : 98643489398625
    },
    "testnet" : false
}


All of my blocks are well past 24 hour min stake age. I have it unlocked for staking only now since new wallet release. One stake only. The wallet isn't staking correctly.
hagie
hero member
Activity: 792
Merit: 501
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 09:17:06 AM
#1673
The GUI is still a bit "buggy" ..

open your debug windows and enter "getmininginfo" there you can check the netstakeweight.

PoS is working I had some small stakes im my local wallet. It's important to unlock it for staking - check the lock symbol !

regards

muchoman
sr. member
Activity: 465
Merit: 250
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 09:05:06 AM
#1672
Quote from: FogHorn_LegHorn on July 27, 2016, 07:38:35 AM
Quote from: hagie on July 27, 2016, 07:12:59 AM
Quote from: alexxynn on July 27, 2016, 05:05:58 AM
When POS will work properly?

PoS works for normal nodes - only masternodes have some trouble at the moment regarding PoS.

Regards

My POS is still not working correctly. These are in my .conf file

addnode=93.104.209.17:22255  
addnode=212.159.88.206:22255  
addnode=173.199.124.83:34546  
addnode=93.74.33.253:40257  
addnode=212.159.88.205:34447  
addnode=212.159.88.205:36592  
addnode=46.188.4.74:14746  
addnode=185.92.222.11:36305  
addnode=79.117.95.93:51104  
addnode=185.3.34.183:29033  
addnode=77.121.108.134:60243  
addnode=178.92.58.15:51394  
addnode=213.136.94.226:42877  
addnode=90.190.175.217:60709  
addnode=144.76.71.141:47548  
addnode=46.188.4.74:27377  
addnode=76.117.67.131:57352

When I hover over staking it says staking. My weight is the number of coins I have in my wallet which is weird and it says network weight is 0. Time for reward also says 0. Any suggestions? I have 18 connections.

Exactly the same for me, wallet is new v2.1.0.0-61402
hagie
hero member
Activity: 792
Merit: 501
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 08:51:15 AM
#1671
Quote from: FogHorn_LegHorn on July 27, 2016, 07:38:35 AM
Quote from: hagie on July 27, 2016, 07:12:59 AM
Quote from: alexxynn on July 27, 2016, 05:05:58 AM
When POS will work properly?

PoS works for normal nodes - only masternodes have some trouble at the moment regarding PoS.

Regards

My POS is still not working correctly. These are in my .conf file

addnode=93.104.209.17:22255  
addnode=212.159.88.206:22255  
...
addnode=46.188.4.74:27377  
addnode=76.117.67.131:57352

When I hover over staking it says staking. My weight is the number of coins I have in my wallet which is weird and it says network weight is 0. Time for reward also says 0. Any suggestions? I have 18 connections.

You sure have the lastest wallet released yesterday ?

regards
FogHorn_LegHorn
full member
Activity: 245
Merit: 100
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 07:38:35 AM
#1670
Quote from: hagie on July 27, 2016, 07:12:59 AM
Quote from: alexxynn on July 27, 2016, 05:05:58 AM
When POS will work properly?

PoS works for normal nodes - only masternodes have some trouble at the moment regarding PoS.

Regards

My POS is still not working correctly. These are in my .conf file

addnode=93.104.209.17:22255  
addnode=212.159.88.206:22255  
addnode=173.199.124.83:34546  
addnode=93.74.33.253:40257  
addnode=212.159.88.205:34447  
addnode=212.159.88.205:36592  
addnode=46.188.4.74:14746  
addnode=185.92.222.11:36305  
addnode=79.117.95.93:51104  
addnode=185.3.34.183:29033  
addnode=77.121.108.134:60243  
addnode=178.92.58.15:51394  
addnode=213.136.94.226:42877  
addnode=90.190.175.217:60709  
addnode=144.76.71.141:47548  
addnode=46.188.4.74:27377  
addnode=76.117.67.131:57352

When I hover over staking it says staking. My weight is the number of coins I have in my wallet which is weird and it says network weight is 0. Time for reward also says 0. Any suggestions? I have 18 connections.
hagie
hero member
Activity: 792
Merit: 501
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 07:12:59 AM
#1669
Quote from: alexxynn on July 27, 2016, 05:05:58 AM
When POS will work properly?

PoS works for normal nodes - only masternodes have some trouble at the moment regarding PoS.

Regards
alexxynn
sr. member
Activity: 381
Merit: 250
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 05:05:58 AM
#1668
When POS will work properly?
yubit
hero member
Activity: 796
Merit: 529
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 04:02:51 AM
#1667
Great!
39 nodes just now for v2.1.0 on https://chainz.cryptoid.info/mojo/#!network
EBK1000
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 03:25:56 AM
#1666
Quote from: MaxMinersNet on July 27, 2016, 02:27:44 AM
Here is a Pool:

https://maxminers.net/mojo

Thanks, I'll check it out and get back to you shortly. I am mining to your pool now so just let me try it for a little while and I'll list it and pay the bounty.
mikhael
sr. member
Activity: 317
Merit: 317
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 02:46:47 AM
#1665
Quote from: MaxMinersNet on July 27, 2016, 02:27:44 AM
Here is a Pool:

https://maxminers.net/mojo

Congrats for being the first MOJO mining pool.
MaxMinersNet
sr. member
Activity: 392
Merit: 250
Re: [MOJO] MOJOv3 has been taken over by new devs
July 27, 2016, 02:27:44 AM
#1664
Here is a Pool:

https://maxminers.net/mojo
aprilio
full member
Activity: 210
Merit: 100
Re: [MOJO] MOJOv3 has been taken over by new devs
July 26, 2016, 04:22:36 PM
#1663
Quote from: EBK1000 on July 26, 2016, 03:23:06 AM
Windows-qt 2.1
MANDATORY UPDATE PLS DOWNLOAD AND UPGRADE TO VERSION 2.1 ASAP

UPGRADE NOW!!!

Upgraded and getting connections now, went smooth. Thanks dev.  Smiley
EBK1000
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Re: [MOJO] MOJOv3 has been taken over by new devs
July 26, 2016, 03:57:14 PM
#1662
BOUNTY: 300,000 MOJO for the first mining pool (equates to roughly 0.5 BTC right now)
EBK1000
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Re: [MOJO] MOJOv3 has been taken over by new devs
July 26, 2016, 03:44:57 PM
#1661
NEXT

I said I would burn 5 mill. coins to compensate for the X11 mining phase. I have found a 'burn' address which is: M7uAERuQW2AotfyLDyewFGcLUDtAYu9v5V
I have now sent 10 MOJO to this address to prove that this is a 'burn' address and that the coins can never be redeemed. This is the 'raw' transaction details:

{
         "value": 10,
         "n": 0,
         "scriptPubKey": {
            "asm": "OP_DUP OP_HASH160 0000000000000000000000000000000000000000 OP_EQUALVERIFY OP_CHECKSIG",
            "hex": "76a914000000000000000000000000000000000000000088ac",
            "reqSigs": 1,
            "type": "pubkeyhash",
            "addresses": [
               "M7uAERuQW2AotfyLDyewFGcLUDtAYu9v5V"
            ]

https://chainz.cryptoid.info/mojo/tx.dws?30441.htm

So, if someone with knowledge can confirm that those 10 MOJOs are now 'lost' I will go ahead with the rest of the 'burn'

Pages:
Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)
Jump to: