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

It's getting a bit better it looks like. I will do a newsletter, Twitter etc. push to all MOJO holders I have details of and try to get as many staking as possible whilst we investigate MN issues.

bad idea - don't do ping-pong. To find PoS Blocks we need mature coins (or better transactions). Mature means the must be untouched 24h than they stake and PRODUCE THE BLOCK.

With sending coins we won't move the chain - only staking moves the Chain now.

Set up wallets - good idea - send coins in small portions - good idea - let the mature 24h to start staking ! Thats the goal !!

@cjmining if you withdraw you could split it - every transaction will be a potential winner in staking !!!

regards

I have Mojo on Livecoin Exchange. Is it better to move them to wallet as one large transfer or multiple smaller transfers to help with staking ?

so wee need transactions...
i'm going to start something i hope i wont regret....
I just setup 3 wallets and will start to send nMojo from one to the other 2 every 45 sec
upon confirmation on the receiving end it will send parts to the other two (ping-pong)
i won't be able to stake and anyway i don't have much yet to generate much in stakes so if everyone else can stake i'll generate the splits and we see how it goes


EDIT:  do u think i should make it 20sec or so to do 2-3 transaction/min?

Hi all,

since PoW isn't an option anymore for running the chain we need many transactions in our wallets to let them stake.

I like to start an Pyramid scheme :-) The first 5 People who send my a mojocoin address by pm will receive 100 Mojo.

I please you to use these funds to distribute it in maybe splits by 10 coins to other users via singel transactions and of course keep one for yourself.

A TRANSACTION WITHIN THE SAME WALLET OR TO AN EXCHANGE WON'T WORK !!

Please use these coins wisely to have them stake in an wallet.

If we don't get enough PoS Power the chain will stop again.

The bugs are currently under investigation by developers.

regards


---EDIT---
Could take longer because the network relies on PoS Blocks at the moment :-(
First out to BBoBB : 1283f1e61949f295f3bc44d2615900508d3ebd2c0877d1c66d02672ee366ef2f

seems like it.. i see my IPs in it under /Mojocore:2.0.1/ list

https://chainz.cryptoid.info/mojo/#!network
This list of nodes is actual?
Thanks

chain.blockpioneers.info/mojo updated to latest core


I will work on some masternode info next week to add to the explorer.. I will keep you updated

I did that error but then I closed the wallet and rename the mojocoin folder in roaming folder.
I started again the wallet and it creates a new mojocoin folder but it doesn't start to sync.( I disabled the firewall)

I will check again later....

i have at least 1 node running since V2 was released (except for the time to swap mojocoind v2 with v2.01)
staked twice only and getting  ERROR: CheckStake() : ProcessBlock, block not accepted in debug.log

if restarting the daemon frequently helps... let me know the cycle frequency and i'll comply...
i can setup 3-4 nodes and keep them on... if that is of use to the network -at this stage-, give me the green light

cheers


EDIT:   just noticed this
getinfo:
{
    "version" : "v2.0.1.0-61402",
    "protocolversion" : 90000,
    "walletversion" : 60000,
    "balance" : 17030.23170795,
    "darksend_balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 4537.72644567,
    "blocks" : 28801,
    "timeoffset" : -1,
    "moneysupply" : 105099468.63377468,
    "connections" : 5,
    "proxy" : "",
    "ip" : "0.0.0.0",
    "difficulty" : 0.00024414,
    "testnet" : false,
    "keypoololdest" : 1468668435,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00010000,
    "mininput" : 0.00000000,
    "errors" : ""
}

getstakinginfo
{
    "enabled" : true,
    "staking" : false,
    "errors" : "",
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "pooledtx" : 0,
    "difficulty" : 0.00024414,
    "search-interval" : 0,
    "weight" : 1703023170795,
    "netstakeweight" : 325,
    "expectedtime" : 0
}

EDIT:
wasn't getting past block 28801
debug.log was piling up the following:
    out 4538.88576073
    ERROR: ProcessBlock() : already have block 28802 0a4b353e31d77d2f9d0e1ebcdd4afb94ba210a80442ac69c4dfe63df7ecc37e1
    ERROR: CheckStake() : ProcessBlock, block not accepted

Deleted blockchain and resynced and hit the same error/stuck at 28801


EDIT:
at the time of this edit (reported by BTCT as 1:03am)
   "blocks" : 28806,
   "connections" : 5,
 masternodelist
{
    "062a8afbb689a54ad271f48124002e3e3b3a5d16c79cec92389b7f346d623bd7-1" : "ENABLED",
    "da977953b56dd0ba52704adb51668312eeea8c8795c07135da2b85012d8a2245-0" : "ENABLED",
    "a0743510dc19b802aa47969c3f4e8e76cd6b1f38d60e1c7d12e58991c6c919b4-0" : "ENABLED"
}
+ staking is true
+ staking seems ok (before it got stuck i had 2 generate transaction.. now i have 3 and one immature)


 

You are probably connecting to the old V1 peers. You can do two things. First backup your wallet.dat file. Then do one of the following below.

1. Make a backup of your wallet.dat file. Delete roaming folder.

or

2. Make a backup of your wallet.dat file. Delete peers list in roaming folder.

Then load wallet. The first option is usually the best as it gets rid of all trash and syncs from scratch, but it'll take a bit longer.

You could make a .conf file but why not just start fresh and be done with it?

I downloaded the mandatory wallet but I have 0 connection (sometime 1 connection for 1 second).
Is there a mojocoin.conf?

Can everyone that are able please stake to move the chain forward.

Hi all,

here some update informations.

After playing with the masternodes I still discovered that the first staking block will split the collateral transaction thus making it unusable for the masternode (masternode need one single transaction with the complete amount of coins)

This happens today with both masternodes resulting in shutting them down.

The other problem:

was discovered too - with a misscaclulation in the wallet which produces wrong ballances (the staking amount is not properly calculated) it takes some minutes or blocks until the coins appear again in the wallet back from staking status. Maybe this is normal behavior it still makes the masternode unusable.

At the moment I run the two masternodes again with changed settings.
The first masternode with staking=0 in the config which means it's a complete passive masternode which just receives some fees.
The second as hot/cold masternode which means the wallet of the masternode didn't contain the coins, the coins are in an offline wallet which is only needed to initial start the masternode.

If the Problems are fixed I will write a small tutorial how the different options can be used and the masternodes are set uo.

Until then we need some additional patience because the test need 24h mature time to see the results.

After the tests are finished we will collect the errors (maybe one native english speaker could this better than me) and give it back to the developer.

If this doesn't help we could also add additional external development skill.

I will be away over the weekend ... hopefully starting next week we have all the issues fixed.

Regards

EBK1000 i would suggest you contact Presstab for a code review. He made Hyperstake coin which is the best staking wallet out there. i doubt anyone would disagree with me on this. Unless of course you have another dev already on the case. Just a suggestion. He is a truly honest dev.

On linux Mojo 2.0.1.0
- Checked list of transactions.. only had 1 generated (the one i partied about yesterday)
- debug.log contained alot of :
   ERROR: ProcessBlock() : already have block 28522 99e5c0b723352811e709ab518acd327c1ad0bfd68fa550bbe1b37d2dcad86e36
  ERROR: CheckStake() : ProcessBlock, block not accepted
  ERROR: CheckStakeKernelHash() : min age violation
  ERROR: CheckStakeKernelHash() : min age violation
  CheckStakeKernelHash() : using modifier 0x2908d6ea410698ee at height=28521 timestamp=2016-07-21 15:13:46 UTC for block from timestamp=2016-07-16 11:51:15 UTC
  CheckStakeKernelHash() : check modifier=0x2908d6ea410698ee nTimeBlockFrom=1468669875 n

so i restarted Mojocoind
- Got a second generated transaction
- debug.log only has :
a ton of
  ERROR: CheckStakeKernelHash() : min age violation
and some
  connect() to 83.37.212.26:22255 failed after select(): No route to host
  connect() to 178.62.230.238:22255 failed after select(): Connection refused

EDIT:
  - My first stake transaction shows :
    "walletconflicts" : [
            "f12aae518fa7b2e6c3a10faa55bb9210f2277b9f6018fd7c0727b36a8f3a9dc9"
        ],

The same on my side, windows wallet 2.0.1.0

edit: This is a "old feature" I know from the linux wallet 2.0 too. That is the reason why an open wallet not continues to stake.

Sorry I am using the 2.0.1.0 windows build that was just released.

windows or linux (so i check if the same issue happens on my side)

OK, my wallet is acting weird. I open it and it stakes one block instantly then doesn't stake anymore. All blocks are the same age. I close it down and open it again and it stakes one block instantly again. The staking icon isn't white either and when I hover over it it says not staking. Anyone else having this issue? It says I have 12 connections.