[ANN][CRW] CROWN (MN-PoS) | Platform | NFT framework | Governance | Masternodes

[stonehedge]

...Crown is also the leading proposal for adding to Slush pool at the moment.

That might just make me want to give up my 7.2CRW per block and go back to pool mining.

Haven't seen any of your blocks yet.  Won't be possible after enforcement though. Can you show me a block?
EDIT:  https://chainz.cryptoid.info/crw/block.dws?1307188.htm

Thanks for the bug report.  Even though enforcement isn't on, still shouldn't be possible.  Will look into it.

[ComputerGenie]

...
Thanks for the bug report.  Even though enforcement isn't on, still shouldn't be possible.  Will look into it.

Being robbed by 20% instead of 50% isn't a bug. 

[stonehedge]

...
Thanks for the bug report.  Even though enforcement isn't on, still shouldn't be possible.  Will look into it.

Being robbed by 20% instead of 50% isn't a bug. 

Well, enjoy your extra coins while you can.

[infernoman]

...
Thanks for the bug report.  Even though enforcement isn't on, still shouldn't be possible.  Will look into it.

Being robbed by 20% instead of 50% isn't a bug. 

It's extra income that you wouldn't have received if crown wasnt merge mined in the first place. I could understand your argument otherwise. This is one of the reason's we're working away from being dependent on miners... There should be no argument. And will be no argument when enforcement is enabled. So enjoy it while you can. Nice to know you intentionally changed the code to your benefit though without doing so, it wouldn't be possible.

[ComputerGenie]

...Nice to know you intentionally changed the code to your benefit though without doing so, it wouldn't be possible.

The only code I changed was to make NOMP work with both PeerCoin and CureCoin (with empty args in the [] part to get block template) and that's a NOMP edit. Beyond that, if there is a CrownCoin "issue", it's a dev issue.  

[infernoman]

...Nice to know you intentionally changed the code to your benefit though without doing so, it wouldn't be possible.

The only code I changed was to make NOMP work with both PeerCoin and CureCoin (with empty args in the [] part to get block template) and that's a NOMP edit. Beyond that, if there is a CrownCoin "issue", it's a dev issue.  

Not an issue, enforcement will be enabled shortly. Until then enjoy the extra bit of rewards while the difficulty is low enough. If you didn't make any changes to the core, and you claim to be using NOMP. It wouldn't change the reward for thrones to a random number like 20%... Either way i'm done talking about it. Since miners are not and never will be our main concern... Guess what bumped to the top of my list though?
Enforcement.

[ComputerGenie]

... Guess what bumped to the top of my list though?
Enforcement.

Well, at least fixing the code you screwed up (and are trying to blame on me) is of some import to you. 

[infernoman]

... Guess what bumped to the top of my list though?
Enforcement.

Well, at least fixing the code you screwed up (and are trying to blame on me) is of some import to you. 

The code was never screwed up. Stonehedge was mistaken to think enforcement was enabled already. It hasn't been as I've been allowing for the network to stabilize with the last release. And if you didn't know i'm also a NOMP/UNOMP developer, so I'm quite familiar with the code and how it works. As well as how mining in the current core code works. NOMP won't change the reward structure without the user making changes to the core. And it sure as hell won't adjust the rewards to a random percentage. Fud all you want. I'm going back to work.

[ComputerGenie]

And if you didn't know i'm also a NOMP/UNOMP developer, so I'm quite familiar with the code and how it works...

Yes, I'm aware of that, which is why I know that you know what line I am talking about (but in case you forgot, it is now: https://github.com/zone117x/node-stratum-pool/blob/master/lib/pool.js#L569).

...NOMP won't change the reward structure without the user making changes to the core...

Which is exactly why I said:

...if there is a CrownCoin "issue", it's a dev issue.  

P.S. - Defending myself from your false claim that I did something "wrong" isn't FUD; it's proving that you're an ass and you're wrong. 

[MrZillion]

trying to get a throne going on Windows, firewall disabled, key generated, crown.conf file adjusted, when throne start I get this error:

Not capable throne: Could not connect to xx.xx.xx.xx:9340 (ip address instead of xx)

https://github.com/Infernoman/Crown/releases/tag/fix-hot-throne

Hot thrones had some issues on the last release. And we didnt want to push out a new version for a small release. Please download the client above.

downloaded suggested version, got a different message: "Not capable throne: Could not find suitable coins!" (required 10K CRW is in that wallet)

That worked, thanks! I've also been reading the documentation but I'm not clear about the difference between "Throne" and "Tron"

[ComputerGenie]

... NOMP won't change the reward structure without the user making changes to the core. And it sure as hell won't adjust the rewards to a random percentage...

Because I hate it when some asshole tries to call me a liar...
It is NOMP (more specifically node-stratum-pool) that sets the 20%:
https://github.com/zone117x/node-stratum-pool/blob/master/lib/transactions.js#L136

With line 136 set to 5 (as it was originally coded) --- 9/5=1.8:

Code:

    cad32a4f10a5b2cb931a1949b796efee0adb28334dfc74c2d37bc44f2f5e96ca

    1GoCtfbodeZCrgfj3a1B8h1pDebxp5vgGJ
    7.2 CRW
    1JgvdM83xF7FyQMcrYyigtf9uqgbVe14wc
    1.8 CRW

With line 136 set to 6 --- 9/6=1.5:

Code:

    2c2f45f6dd56522b8e719fc5ddff86507bcd17fddf1687f9a3503b1739bd1241

    1GoCtfbodeZCrgfj3a1B8h1pDebxp5vgGJ
    7.5 CRW
    1GUhjtP8QFUVctnFHEyvxCcoE9NJTwx7Rw
    1.5 CRW

Next time you want to disparage someone, I suggest you pick someone that can't read enough code to prove you wrong....

[max2000irc]

I've reported this bug a while ago on slack when someone got all the reward per block , still didn't fixed?

Thanks

[infernoman]

... NOMP won't change the reward structure without the user making changes to the core. And it sure as hell won't adjust the rewards to a random percentage...

Because I hate it when some asshole tries to call me a liar...
It is NOMP (more specifically node-stratum-pool) that sets the 20%:
https://github.com/zone117x/node-stratum-pool/blob/master/lib/transactions.js#L136

With line 136 set to 5 (as it was originally coded) --- 9/5=1.8:

Code:

    cad32a4f10a5b2cb931a1949b796efee0adb28334dfc74c2d37bc44f2f5e96ca

    1GoCtfbodeZCrgfj3a1B8h1pDebxp5vgGJ
    7.2 CRW
    1JgvdM83xF7FyQMcrYyigtf9uqgbVe14wc
    1.8 CRW

With line 136 set to 6 --- 9/6=1.5:

Code:

    2c2f45f6dd56522b8e719fc5ddff86507bcd17fddf1687f9a3503b1739bd1241

    1GoCtfbodeZCrgfj3a1B8h1pDebxp5vgGJ
    7.5 CRW
    1GUhjtP8QFUVctnFHEyvxCcoE9NJTwx7Rw
    1.5 CRW

Next time you want to disparage someone, I suggest you pick someone that can't read enough code to prove you wrong....

Alright so NOMP is using outdated code which affects the reward structure. When structured properly like it is in UNOMP. This isn't possible without some intentional changes, which in turn benefit the miner. A misunderstanding on my part. This is a bug in NOMP. Not UNOMP. My apologies, I got defensive because I've dealt with miners purposely restructuring code for their benefit before. Both of us are in the wrong here but there's no need for namecalling... One thing I was working toward was giving miners FULL rewards during non-enforcement periods. So you will be able to benefit during version upgrades. But once enforcement enables, NOMP will need changes or it will produce invalid blocks it seems.

[infernoman]

I've reported this bug a while ago on slack when someone got all the reward per block , still didn't fixed?

Thanks

Enforcement has not been activated yet. And the person receiving the full block reward was me doing testing on the network for UNOMP. To allow for miners to get full block rewards during version upgrades. That's also one of the reason's I commented that without changes, This wasn't possible using the software ComputerGenie was using. BUT he was using an older version than i suspected. And got a bit too defensive after a long night.

[ComputerGenie]

...Both of us are in the wrong here but there's no need for namecalling...

If you falsely accuse someone of altering the wallet to "cheat" (by saying, "Nice to know you intentionally changed the code to your benefit") and they don't call you "an asshole" (or worse), then they care nothing of their reputation or truth.

Setting that aside, I'm still not sure what you think I was "in the wrong" about...

[infernoman]

...Both of us are in the wrong here but there's no need for namecalling...

If you falsely accuse someone of altering the wallet to "cheat" (by saying, "Nice to know you intentionally changed the code to your benefit") and they don't call you "an asshole" (or worse), then they care nothing of their reputation or truth.

Setting that aside, I'm still not sure what you think I was "in the wrong" about...

My mistake was thinking you were purposely altering code structure, And instead it's a bug with NOMP. NOMP won't create valid blocks once enforcement is enabled.

... Guess what bumped to the top of my list though?
Enforcement.

Well, at least fixing the code you screwed up (and are trying to blame on me) is of some import to you.  

Your mistake was thinking that it was because of a mistake made by me or the team, In which it was not. And indeed it is a bug caused by NOMP.


Reading the code you must know that once enforcement gets enabled that you wont be able to create valid blocks unless changes to the reward structure you pointed toward are made. And you can see I was working toward giving miners full benefits during version upgrades if you check out github. My work is based on UNOMP though not NOMP. Mistakes were made, Like I said my apologies for jumping to conclusions.

[ComputerGenie]

...Your mistake was thinking that it was because of a mistake made by me or the team, In which it was not. And indeed it is a bug caused by NOMP.
....

Errr..... ummmm.... NO!

...And if you didn't know i'm also a NOMP/UNOMP developer...

...if there is a CrownCoin "issue", it's a dev issue.  

If you're a dev for NOMP and NOMP has a bug, then, yes, it was a mistake by you (not a mistake by me thinking it was a mistake by you). You don't get to claim being a dev for both NOMP and the coin, claim there's a bug in NOMP that makes it not work as you expected, and then say I'm wrong for saying it's a dev issue. Why? Because, logic!

[infernoman]

...Your mistake was thinking that it was because of a mistake made by me or the team, In which it was not. And indeed it is a bug caused by NOMP.
....

Errr..... ummmm.... NO!

...And if you didn't know i'm also a NOMP/UNOMP developer...

...if there is a CrownCoin "issue", it's a dev issue.  

If you're a dev for NOMP and NOMP has a bug, then, yes, it was a mistake by you (not a mistake by me thinking it was a mistake by you). You don't get to claim being a dev for both NOMP and the coin, claim there's a bug in NOMP that makes it not work as you expected, and then say I'm wrong for saying it's a dev issue. Why? Because, logic!

I only have rights to commit on the UNOMP branch. Therefore I am only a developer for UNOMP not NOMP. It was a mistake by me thinking you were using UNOMP. The reward structure is unaltered by UNOMP unless changes are intentionally made to get around it currently. NOMP purposely alters the reward structure in an improper manner and will not create valid blocks once enforcement is enbabled. UNOMP will.

I was working to give miners FULL block rewards during version upgrades while enforcement is NOT enabled. NOMP will still reward the nodes 20% like you are currently. UNOMP not currently but in the future will give miners the full reward during times enforcement is not turned on. and will automatically start to pay nodes once it is turned on.

[chrysophylax]

...Your mistake was thinking that it was because of a mistake made by me or the team, In which it was not. And indeed it is a bug caused by NOMP.
....

Errr..... ummmm.... NO!

...And if you didn't know i'm also a NOMP/UNOMP developer...

...if there is a CrownCoin "issue", it's a dev issue.  

If you're a dev for NOMP and NOMP has a bug, then, yes, it was a mistake by you (not a mistake by me thinking it was a mistake by you). You don't get to claim being a dev for both NOMP and the coin, claim there's a bug in NOMP that makes it not work as you expected, and then say I'm wrong for saying it's a dev issue. Why? Because, logic!

I only have rights to commit on the UNOMP branch. Therefore I am only a developer for UNOMP not NOMP. It was a mistake by me thinking you were using UNOMP. The reward structure is unaltered by UNOMP unless changes are intentionally made to get around it currently. NOMP purposely alters the reward structure in an improper manner and will not create valid blocks once enforcement is enbabled. UNOMP will.

I was working to give miners FULL block rewards during version upgrades while enforcement is NOT enabled. NOMP will still reward the nodes 20% like you are currently. UNOMP not currently but in the future will give miners the full reward during times enforcement is not turned on. and will automatically start to pay nodes once it is turned on.

ive tried installing unomp under centos 7 x64 ...

and let me tell you - it was not a pretty sight ... the prominent issues are obviously the dependencies - and then the installation ... because most of these pools / startums are built under ubuntu / debian based systems - it makes it very difficult for us rhel based users to support a LOT of these pools / stratums ...

if you can help in any way - then i would be happy to commit time and effort - and more importantly - resources to the unomp install ... just so i can get not only a better undertsanding of it - but also build it properly under rhel based / centos 7 x64 system ...

it has been the bane of my life with crypto that almost NO dev understands that ubuntu DOES NOT EQUAL linux ... that debian based systems like ubuntu are a flavour of linux and that rhel systems are in HUGE abundance and proliferation - and that devs of such systems ( like unomp ) would help with us - we could have a much bigger user base and a better manifestation of the pools / stratum ... hence the coin pools as well ...

much kudos to you infernoman - as ive watched you for a long time work your way around many coins and projects like unomp ...

my qualm is simply that ubuntu is NOT the only os that devs should be solely looking at supporting - as people / companies / entities like us do not use ubuntu - but instead centos 7 ... and the rhel based populous is a massive number - and as such could help the development and bug squashing in a bigger way when rhel system users are involved also ...

#crysx

[defunctec]

30th Birthday present