Pages:
Author

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

sr. member
Activity: 381
Merit: 250
When POS will work properly?
When are the fixes?
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Yes, it's a go for the burn, but as I tried to send I may have found another bug unfortunately, so I tried to send 5,000,000 MOJO to MBurnMojoWithNoPrivateKeyXMMHXyKXz and I got this:

Status: conflicted
Date: 29/07/2016 00:34
To: MBurnMojoWithNoPrivateKeyXMMHXyKXz
Debit: -5000000.00 MOJO
Transaction fee: -0.0007 MOJO
Net amount: -5000000.0007 MOJO
Transaction ID: 37755cddcbf95f4ae4a6feb3f816f2c0f7724cd89ffba08fed822b7be4780da2-000



I have tried to restart with -rescan but it stays stuck. It seems it has trouble connecting inputs. In progress ...

full member
Activity: 168
Merit: 100
Also the question is phrased badly. "I will 'burn' MOJO to: MBurnMojoWithNoPrivateKeyXMMHXyKXz - any objections?" ... so we have to vote NO if we agree with the burn?

Sorry, it's just a basic assumption that people actually read the question and have basic understanding of English.

It takes more than a basic understanding of language if no = yes burn and yes = no burn. I was born in England and still didn't vote, because of the ambiguity.

One of the main reasons I am attracted to the Mojo project is your good communication skills, but i would not be surprised if some people voted "yes", actually meant to vote "no".

Same here.. i kind of understood, but since it was pretty unclear, i didnt vote.

I guess i just vote "no", and that means i agree with the burn, yeah?

That is correct. A "no" in that question means giving green light for the burn.

sr. member
Activity: 473
Merit: 252
Also the question is phrased badly. "I will 'burn' MOJO to: MBurnMojoWithNoPrivateKeyXMMHXyKXz - any objections?" ... so we have to vote NO if we agree with the burn?

Sorry, it's just a basic assumption that people actually read the question and have basic understanding of English.

It takes more than a basic understanding of language if no = yes burn and yes = no burn. I was born in England and still didn't vote, because of the ambiguity.

One of the main reasons I am attracted to the Mojo project is your good communication skills, but i would not be surprised if some people voted "yes", actually meant to vote "no".

Same here.. i kind of understood, but since it was pretty unclear, i didnt vote.

I guess i just vote "no", and that means i agree with the burn, yeah?
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Did anyboy find PoS-block without MN, only staking?

You will find PoS blocks but there is a problem that we are working with now
legendary
Activity: 1650
Merit: 1033
Did anyboy find PoS-block without MN, only staking?
full member
Activity: 199
Merit: 102
is it too late to re-word the question? like :

I will 'burn' MOJO to: MBurnMojoWithNoPrivateKeyXMMHXyKXz - Yes or No.

If you object to this address as a 'burn' address then please explain why in the thread.

Kind regards.
full member
Activity: 199
Merit: 102
Also the question is phrased badly. "I will 'burn' MOJO to: MBurnMojoWithNoPrivateKeyXMMHXyKXz - any objections?" ... so we have to vote NO if we agree with the burn?

Sorry, it's just a basic assumption that people actually read the question and have basic understanding of English.

It takes more than a basic understanding of language if no = yes burn and yes = no burn. I was born in England and still didn't vote, because of the ambiguity.

One of the main reasons I am attracted to the Mojo project is your good communication skills, but i would not be surprised if some people voted "yes", actually meant to vote "no".
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Also the question is phrased badly. "I will 'burn' MOJO to: MBurnMojoWithNoPrivateKeyXMMHXyKXz - any objections?" ... so we have to vote NO if we agree with the burn?

Sorry, it's just a basic assumption that people actually read the question and have basic understanding of English.
full member
Activity: 199
Merit: 102
Also the question is phrased badly. "I will 'burn' MOJO to: MBurnMojoWithNoPrivateKeyXMMHXyKXz - any objections?" ... so we have to vote NO if we agree with the burn?
hero member
Activity: 792
Merit: 501
My guess is the people who voted against this address may not know the idea between public / private key pairs , how they related and how one can derive from another ...

but that's ok - if anyone got a question about ask .. not just blind vote something ..

regards.

P.S. sorry for the lack of updates .. I'm quite busy in RL atm.
full member
Activity: 199
Merit: 102

The masternode collateral is NOT staking, the masternode gets 50% of the generated coins in a PoS block.

The masternode collateral did stake for me in the last version, thus disqualifying my masternode. So my question is how to run a masternode and stake extra balance at the same time. But lets see what happens with the reservebalance=200000

Can the people who voted to object against the MOJO 'burn' address please post a little reply and let me know why?

The burn address MBurnMojoWithNoPrivateKeyXMMHXyKXz looks good to me, assuming the mojocoin code is sound, as it should be impossible for anyone to have the private key to that human-readable address. It's also quite a noble initiative of you to burn some coins as part of the addition of pow mining. So from what I know, I think that is all cool to go ahead with the burn, with thanks.
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
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 :-)


I am also trying with reservebalance=200000 and will report if I get any problem too. If this does not allow the masternode to stake then I suggest adding something to the staking code such that it will not use the masternode collateral for staking. I'm surprised that wasn't already the case but I am new to the concept of masternodes. Cheers.

The masternode collateral is NOT staking, the masternode gets 50% of the generated coins in a PoS block.
full member
Activity: 199
Merit: 102
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 :-)


I am also trying with reservebalance=200000 and will report if I get any problem too. If this does not allow the masternode to stake then I suggest adding something to the staking code such that it will not use the masternode collateral for staking. I'm surprised that wasn't already the case but I am new to the concept of masternodes. Cheers.
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Can the people who voted to object against the MOJO 'burn' address please post a little reply and let me know why?
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity

please let me know if there's any bounty action available for a mac Qt Smiley

There is a problem with the PoS system that we are sorting out. I don't see the point of releasing a Mac before the fix is done. After the fix is done (hopefully just a few days) then we can talk again.
legendary
Activity: 1638
Merit: 1036

please let me know if there's any bounty action available for a mac Qt Smiley
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
I am preparing to burn off 5 mill. MOJO to take the total down to allow for the PoW phase. I will 'burn' MOJO to: MBurnMojoWithNoPrivateKeyXMMHXyKXz
Do you have any objections? If you object to this address as a 'burn' address then please explain why in the thread.
I just want to be transparent and give people a heads up and a chance to have their say. Nobody has a private key to this address. I have sent 1 MOJO to prove that it works:

https://chainz.cryptoid.info/mojo/address.dws?MBurnMojoWithNoPrivateKeyXMMHXyKXz.htm

Any comments?
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
Masternode Update

So, I have set up and I am running a MN according to the specs. in my previous post. I started the MN at around 1000 hours (GMT) on 27/07/2016. Here it is in the block explorer:

https://chainz.cryptoid.info/mojo/address.dws?MFtJpsiDm4oEmYTi75Ddq4YapRnioX97HV.htm

I got my first stake reward at 1540 (all the times in GMT) and continued to get stake rewards through the day and today. My MN has now been running for a good few hours past 24 hours and it is seemingly running fault free and I am still getting stakes. Nothing happened after 24 hours and no errors in the log and strange behaviour. I have traced all the stake rewards coming into my MN and they are all 50% of the generated MOJO from PoS blocks found by other stakers that are not running MNs. So, the MNs are getting 50% of every PoS block found and the 200k collateral itself is not staking and is still safely shown as a single 200k UTXO. I would therefore suggest that the MN network is operating as it should harvesting 50% of all the PoS generated coins. The reason the rewards are low is the fact that there are little stake rewards and PoW blocks.

Here are the last entries in my MN debug.log way past 24 hours and the word "error" does not feature anywhere in the logs.

Code:
2016-07-28 16:25:10 CheckBlock() : Found payment(1|98859670) or payee(1|3QJmnh) nHeight 31934. 
2016-07-28 16:25:10 CheckBlock() : Found payment(1|98859670) or payee(1|3QJmnh) nHeight 31934.
2016-07-28 16:25:10 AddToWallet 7ce354dafae68c979d923d4827364dd0ed5219bb21d73e4a559878c951856a26  new
2016-07-28 16:25:10 AddToWallet 7ce354dafae68c979d923d4827364dd0ed5219bb21d73e4a559878c951856a26  
2016-07-28 16:25:10 SetBestChain: new best=3f88c003f8e7fa2c303384904cdc0ae6f02e94547fe05133c1a9cf8d280e04e1  height=31934  trust=96003641496603  blocktrust=1048577  date=07/28/16 16:25:04
2016-07-28 16:25:10 ProcessBlock: ACCEPTED
2016-07-28 16:26:27 CheckBlock() : Found payment(1|74859670) or payee(1|3QJmnh) nHeight 31935.
2016-07-28 16:26:27 CheckBlock() : Found payment(1|74859670) or payee(1|3QJmnh) nHeight 31935.
2016-07-28 16:26:27 SetBestChain: new best=b2d20c2f04b8b7e99c3914df7a42abe6b920006423297cac4baca5f6d81cdb24  height=31935  trust=96003642545180  blocktrust=1048577  date=07/28/16 16:26:24
2016-07-28 16:26:27 ProcessBlock: ACCEPTED
2016-07-28 16:27:08 SetBestChain: new best=4a4e4e10a23f01318e939a2fc51c41ace2a1cc0f0bfcb2a716f397aeb199a291  height=31936  trust=96080966603506  blocktrust=77324058326  date=07/28/16 16:26:26
2016-07-28 16:27:08 ProcessBlock: ACCEPTED
2016-07-28 16:29:16 SetBestChain: new best=0779bcc695a156fa07be26f94949a6c4928f25611738094dc5960315665ae845  height=31937  trust=96144958982100  blocktrust=63992378594  date=07/28/16 16:28:56
2016-07-28 16:29:16 ProcessBlock: ACCEPTED
2016-07-28 16:32:43 SetBestChain: new best=bef6f6717da65fc7e44e40a6b99c19d27885d581a004e86a81f4f5b8355bfd38  height=31938  trust=96198847316028  blocktrust=53888333928  date=07/28/16 16:31:59
2016-07-28 16:32:43 ProcessBlock: ACCEPTED
2016-07-28 16:33:06 SetBestChain: new best=3d00cd526fa3aecb9c3dbe90521475ba6bc2614682a5a4efc0bb09e2c04cf3d1  height=31939  trust=96241957989619  blocktrust=43110673591  date=07/28/16 16:32:41
2016-07-28 16:33:06 ProcessBlock: ACCEPTED

So, My MN has been running for 24 hours plus and it still seems to be operating as expected with no errors.

We are still investigating the PoS rewards and why it seems that some are getting PoS rewards and others not so much. We are are aware of some GUI issues.
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
We are monitoring the blockchain and we are researching the issues that we see. There won't be too many updated for 2-3 days as we want to gather some data. If you have specific problems send an e-mail to team-AT-mojocoin.org with a debug.log file attached and describe in as much detail as possible what is happening.
Pages:
Jump to: