timbereagle
|
 |
April 13, 2015, 10:21:25 AM |
|
TROLLS going crazy, they were trying to make people dump to 50K but trolls lost their CRAVE (Sell orders are bought), hahaha, see you over 1 Million sats
|
|
|
|
Yaremi
Legendary
Offline
Activity: 2016
Merit: 1160
Community Ambassador of Qzino
|
 |
April 13, 2015, 10:23:59 AM |
|
TROLLS epic facepalm.jpg 
|
Community Ambassador of Qzino Next-generation crypto iGaming platform. Provably fair. With AI inside. Daily profit sharing. https://qzino.com/
|
|
|
Thomasvd
Newbie
Offline
Activity: 30
Merit: 0
|
 |
April 13, 2015, 10:25:57 AM |
|
TROLLS going crazy, they were trying to make people dump to 50K but trolls lost their CRAVE (Sell orders are bought), hahaha, see you over 1 Million sats
Yes  just dont sell them... And btw, i had big bags yes, now im loading trucks....
|
|
|
|
wasref
|
 |
April 13, 2015, 10:27:59 AM |
|
TROLLS going crazy, they were trying to make people dump to 50K but trolls lost their CRAVE (Sell orders are bought), hahaha, see you over 1 Million sats
or it could be those who got dumped at 70k are just pushing up price to sell at profit. look where the buy orders are they careful they are not dumped into this pumper is making you guys look like fools
|
|
|
|
fmz89
Legendary
Offline
Activity: 1764
Merit: 1002
|
 |
April 13, 2015, 10:30:35 AM |
|
hell yeah someone dumped on me 
|
|
|
|
kcanup
Legendary
Offline
Activity: 1484
Merit: 1000
|
 |
April 13, 2015, 10:32:20 AM |
|
How are the masternodes earning? How many coins you are collecting in 24 hours with one masternode? I may buy some CRAVE and setup one now 
|
|
|
|
fmz89
Legendary
Offline
Activity: 1764
Merit: 1002
|
 |
April 13, 2015, 10:33:20 AM |
|
How are the masternodes earning? How many coins you are collecting in 24 hours with one masternode? I may buy some CRAVE and setup one now  6.66
|
|
|
|
wasref
|
 |
April 13, 2015, 10:34:41 AM |
|
TROLLS going crazy, they were trying to make people dump to 50K but trolls lost their CRAVE (Sell orders are bought), hahaha, see you over 1 Million sats
or it could be those who got dumped at 70k are just pushing up price to sell at profit. look where the buy orders are they careful they are not dumped into this pumper is making you guys look like fools lol 28btc buy order at 85k like someone really gonna dump that lol. he just making order look good so he can sell what he has. this shit is too funny
|
|
|
|
timbereagle
|
 |
April 13, 2015, 10:35:36 AM |
|
TROLLS going crazy, they were trying to make people dump to 50K but trolls lost their CRAVE (Sell orders are bought), hahaha, see you over 1 Million sats
or it could be those who got dumped at 70k are just pushing up price to sell at profit. look where the buy orders are they careful they are not dumped into this pumper is making you guys look like fools You know eventually there is very limited number of CRAVE, even IF your scenario is correct, he is getting out of coin, We will be much better without PND groups.
|
|
|
|
kcanup
Legendary
Offline
Activity: 1484
Merit: 1000
|
 |
April 13, 2015, 10:35:47 AM |
|
How are the masternodes earning? How many coins you are collecting in 24 hours with one masternode? I may buy some CRAVE and setup one now  6.66 Thanks 
|
|
|
|
fmz89
Legendary
Offline
Activity: 1764
Merit: 1002
|
 |
April 13, 2015, 10:39:03 AM |
|
TROLLS going crazy, they were trying to make people dump to 50K but trolls lost their CRAVE (Sell orders are bought), hahaha, see you over 1 Million sats
or it could be those who got dumped at 70k are just pushing up price to sell at profit. look where the buy orders are they careful they are not dumped into this pumper is making you guys look like fools lol 28btc buy order at 85k like someone really gonna dump that lol. he just making order look good so he can sell what he has. this shit is too funny no one will dump, just sdc&dash dumper will dump
|
|
|
|
fmz89
Legendary
Offline
Activity: 1764
Merit: 1002
|
 |
April 13, 2015, 10:39:42 AM |
|
sdc&dash dumper running out of coin  strike back dash&sdc
|
|
|
|
fusecavator
Member

Offline
Activity: 117
Merit: 10
|
 |
April 13, 2015, 10:40:24 AM |
|
I pmed the dev about this a few days ago, but haven't received any response, nor has anything been done about these, so I'm posting this here now hoping it'll get some answers. This is not the message I sent, this is reworded for general users who I don't expect to know much about the code. There are multiple things I've found in the code that seem like problems. In the masternode payment enforcement, the code for checking that masternodes are being paid is checking the wrong transaction. In btc(and pow coins like darkcoin which the code came from) the block reward is in the first transaction (vtx[0]), and in PoS forks like crave is, vtx[0] is always left empty and the block reward is in vtx[1]. It can be seen here https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2375 and https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2357 that the code was not updated to look in vtx[1], and continues to look at vtx[0]. It can also be seen a little higher up in the same function that the block verification does check that vtx[0] is empty https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2302 . Since block verification checks that vtx[0] is empty to even get to masternode payment verification, payment verification will never find an output to a masternode in that loop, and should reject all blocks, except it doesn't deadlock due to the next point. The hard fork never happened. If you scroll up a little from the previous section, you'll see a flag used for enabling masternode enforcement. https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2341 Right below it checks it against a timestamp, and sets the flag to true if we're past the fork time. Before we actually use the flag, there's another condition calling the IsSporkActive function https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2341 which is capable of turning the flag back off. If you follow that function https://github.com/industrialcoinmagic/crave/blob/master/src/spork.cpp#L80 what happens in that call is it doesn't see that flag in the map, so heads into the else block where it copies SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT_DEFAULT to r, and then compares r to the current time. If you take a look at the value compared https://github.com/industrialcoinmagic/crave/blob/master/src/spork.h#L28 , and convert that timestamp(2428537599) to normal time ( http://www.epochconverter.com/ ), you'll see that the timestamp used is Dec 16 2046. Clearly this hasn't happened yet, so IsSporkActive returns false, and that causes it to set the flag back to false so the masternode payment enforcement code is skipped over. Until ICM quieted the logging, it could also be seen in the logs that the skipped message was still being logged after the fork supposedly happened. Lastly at https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2320 the constant passed to IsSporkActive is the timestamp from before, not a spork ID, which causes the InstantX checks to be skipped.
|
|
|
|
fmz89
Legendary
Offline
Activity: 1764
Merit: 1002
|
 |
April 13, 2015, 10:42:45 AM |
|
I pmed the dev about this a few days ago, but haven't received any response, nor has anything been done about these, so I'm posting this here now hoping it'll get some answers. This is not the message I sent, this is reworded for general users who I don't expect to know much about the code. There are multiple things I've found in the code that seem like problems. In the masternode payment enforcement, the code for checking that masternodes are being paid is checking the wrong transaction. In btc(and pow coins like darkcoin which the code came from) the block reward is in the first transaction (vtx[0]), and in PoS forks like crave is, vtx[0] is always left empty and the block reward is in vtx[1]. It can be seen here https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2375 and https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2357 that the code was not updated to look in vtx[1], and continues to look at vtx[0]. It can also be seen a little higher up in the same function that the block verification does check that vtx[0] is empty https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2302 . Since block verification checks that vtx[0] is empty to even get to masternode payment verification, payment verification will never find an output to a masternode in that loop, and should reject all blocks, except it doesn't deadlock due to the next point. The hard fork never happened. If you scroll up a little from the previous section, you'll see a flag used for enabling masternode enforcement. https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2341 Right below it checks it against a timestamp, and sets the flag to true if we're past the fork time. Before we actually use the flag, there's another condition calling the IsSporkActive function https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2341 which is capable of turning the flag back off. If you follow that function https://github.com/industrialcoinmagic/crave/blob/master/src/spork.cpp#L80 what happens in that call is it doesn't see that flag in the map, so heads into the else block where it copies SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT_DEFAULT to r, and then compares r to the current time. If you take a look at the value compared https://github.com/industrialcoinmagic/crave/blob/master/src/spork.h#L28 , and convert that timestamp(2428537599) to normal time ( http://www.epochconverter.com/ ), you'll see that the timestamp used is Dec 16 2046. Clearly this hasn't happened yet, so IsSporkActive returns false, and that causes it to set the flag back to false so the masternode payment enforcement code is skipped over. Until ICM quieted the logging, it could also be seen in the logs that the skipped message was still being logged after the fork supposedly happened. Lastly at https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2320 the constant passed to IsSporkActive is the timestamp from before, not a spork ID, which causes the InstantX checks to be skipped. hei dash dumper 
|
|
|
|
fil0
|
 |
April 13, 2015, 10:43:51 AM |
|
Someone wants a lot of cheap CRAVE 
|
|
|
|
BigDaddySherman
Newbie
Offline
Activity: 56
Merit: 0
|
 |
April 13, 2015, 10:44:58 AM |
|
I pmed the dev about this a few days ago, but haven't received any response, nor has anything been done about these, so I'm posting this here now hoping it'll get some answers. This is not the message I sent, this is reworded for general users who I don't expect to know much about the code. There are multiple things I've found in the code that seem like problems. In the masternode payment enforcement, the code for checking that masternodes are being paid is checking the wrong transaction. In btc(and pow coins like darkcoin which the code came from) the block reward is in the first transaction (vtx[0]), and in PoS forks like crave is, vtx[0] is always left empty and the block reward is in vtx[1]. It can be seen here https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2375 and https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2357 that the code was not updated to look in vtx[1], and continues to look at vtx[0]. It can also be seen a little higher up in the same function that the block verification does check that vtx[0] is empty https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2302 . Since block verification checks that vtx[0] is empty to even get to masternode payment verification, payment verification will never find an output to a masternode in that loop, and should reject all blocks, except it doesn't deadlock due to the next point. The hard fork never happened. If you scroll up a little from the previous section, you'll see a flag used for enabling masternode enforcement. https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2341 Right below it checks it against a timestamp, and sets the flag to true if we're past the fork time. Before we actually use the flag, there's another condition calling the IsSporkActive function https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2341 which is capable of turning the flag back off. If you follow that function https://github.com/industrialcoinmagic/crave/blob/master/src/spork.cpp#L80 what happens in that call is it doesn't see that flag in the map, so heads into the else block where it copies SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT_DEFAULT to r, and then compares r to the current time. If you take a look at the value compared https://github.com/industrialcoinmagic/crave/blob/master/src/spork.h#L28 , and convert that timestamp(2428537599) to normal time ( http://www.epochconverter.com/ ), you'll see that the timestamp used is Dec 16 2046. Clearly this hasn't happened yet, so IsSporkActive returns false, and that causes it to set the flag back to false so the masternode payment enforcement code is skipped over. Until ICM quieted the logging, it could also be seen in the logs that the skipped message was still being logged after the fork supposedly happened. Lastly at https://github.com/industrialcoinmagic/crave/blob/master/src/main.cpp#L2320 the constant passed to IsSporkActive is the timestamp from before, not a spork ID, which causes the InstantX checks to be skipped. Can anyone verify the veracity of this? I still have masternodes running...
|
|
|
|
|
timbereagle
|
 |
April 13, 2015, 10:52:36 AM |
|
Please help what am I doing wrong?
not capable masternode: Could not connect to 108.61.190.41:9999
I did everything as instructed. Please help. Preferably in Polish if anyone here poles
Most probably your port 9999 is closed, It also happened to me at my office notebook.
|
|
|
|
Papcio77
|
 |
April 13, 2015, 10:54:17 AM |
|
How to open it?
|
|
|
|
timbereagle
|
 |
April 13, 2015, 10:56:34 AM |
|
How to open it?
I do not know how to open, I had 2 internet connection, thats why I choose the other line in which 9999 port is open. PS: If anyone knows how to open 9999 port, please let us know.
|
|
|
|
|