Hmm. Why has my original balance moved to 'Staked' and become unavailable. Now my available balance seems to be counting DOWN when staking, are these transposed?? Haven't seen this with my other PoS wallets.
They'll come back with the percentage gained, it's just the way it works. My ac does the same thing... 
Topic: [ANN]LOVEcoin – POW+POS | 5 Exchanges | Games | On Multipool - page 6. (Read 49658 times)
Hmm. Why has my original balance moved to 'Staked' and become unavailable. Now my available balance seems to be counting DOWN when staking, are these transposed?? Haven't seen this with my other PoS wallets.
my coins are now staking!! Thanks YarkoL!! 
Wallet and source updated. Thanks YarkoL 
We will make the update today.
So whats the score?
Anybody??
Anybody??
Whoops. Looks like I rejoiced a little prematurely...
But things are on the move...
The code is now fixed in the master repository too.
I've been talking to the devs, and I believe "official" working wallet will be soon available.
Once the coin is back on track,
remember...
LWEBHmiAGSS4Mdv8BjMsBx84SD3KxM5UVh
Let's make 2014 Summer of Love...
and what the hell, 2015 and 2016 too!
Code in the github has NOT been fixed. Was last updated 23 days ago.
Once it's completely fixed let me know.
The code is now fixed in the master repository too.
I've been talking to the devs, and I believe "official" working wallet will be soon available.
Once the coin is back on track,
remember...
LWEBHmiAGSS4Mdv8BjMsBx84SD3KxM5UVh
Let's make 2014 Summer of Love...
and what the hell, 2015 and 2016 too!
Website | Twitter | Bitcointalk
Hi,Everyone
We have added your coin to ECOINFUND vote list.（http://www.ecoinfund.com/vote）
Each 1 valid vote requires 10 ECFC, allow repeat voting.Every new altcoin vote over 1,000 votes will list on the market next day! Free vote see below:
Big ECFC GIVEAWAY before 10.May
Tweet this green text on your own twitter account then recive 20 ECFC（ECFC Details）;
Quote
ecoinfund.com |New Exchange,multi-language support,Earn 20 ECFC(fee shares) by every retweet before 10 May,don't miss the train!
Pls post your twitter link and Ecoinfund ID on https://bitcointalksearch.org/topic/annexchange-ecoinfundmulti-language-alt-coin-exchange-official-thread-501030 ,you will get 20 ECFC!ECFC is the fee share program launched by Ecoinfund. Ecoinfund will commit 50% of trade revenue to ECFC program. (highest on market)
Happy trading !
http://www.ecoinfund.com/images/logo.jpg
Website | Twitter | Bitcointalk
Hi,LOVEcoin Community
We have added your coin to ECOINFUND vote list.（http://www.ecoinfund.com/vote）
an effective vote will cost 10 ECFC； repeating vote are allowed； the Exchange Market will be open as soon as the voting reach 1000.!
ECFC is the fee share program launched by Ecoinfund. Ecoinfund will commit 50% of trade revenue to ECFC program. (highest on market ECFC Details)
Here the ways of getting ECFC:
1. buy the ECFC through our ECFC/BTC or ECFC/LTC market.
2. taking part into our GIVEAWAY.
Big ECFC GIVEAWAY before 10.May
Tweet this green text on your own twitter account then recive 20 ECFC;
Happy trading !
Website | Twitter | Bitcointalk
Hi,LOVEcoin Community
We have added your coin to ECOINFUND vote list.（http://www.ecoinfund.com/vote）
an effective vote will cost 10 ECFC； repeating vote are allowed； the Exchange Market will be open as soon as the voting reach 1000.!
ECFC is the fee share program launched by Ecoinfund. Ecoinfund will commit 50% of trade revenue to ECFC program. (highest on market ECFC Details)
Here the ways of getting ECFC:
1. buy the ECFC through our ECFC/BTC or ECFC/LTC market.
2. taking part into our GIVEAWAY.
Big ECFC GIVEAWAY before 10.May
Tweet this green text on your own twitter account then recive 20 ECFC;
Quote
ecoinfund.com |New Exchange,multi-language support,Earn 20 ECFC(fee shares) by every retweet before 10 May,don't miss the train!
Pls post your twitter link and Ecoinfund ID on https://bitcointalksearch.org/topic/annexchange-ecoinfundmulti-language-alt-coin-exchange-official-thread-501030 ,you will get 20 ECFC!Happy trading !
YEAH!
Later I was thinking myself: My search for 10000 did not (directly) help,
but perhaps searching for 10001 would uncover the problem? And it did !
Happy.
When the new sourcecode is available, allcrypt can implement it, so my coins will not be destroyed?
Thanks, YarkoL, very clever:
LoveCoinDev, I guess, your clone-your-coin manual should be extended with "remove existing checkpoints".
Please tell us which manual you used.
Later I was thinking myself: My search for 10000 did not (directly) help,
but perhaps searching for 10001 would uncover the problem? And it did !
Happy.
When the new sourcecode is available, allcrypt can implement it, so my coins will not be destroyed?
Please cooperate with allcrypt to solve their technical problems.
I have tens of thousands of LOVEcoins stuck there, and the message is:
Thanks a lot!
EDIT: Crossposted to allcryptthread
I have tens of thousands of LOVEcoins stuck there, and the message is:
Quote
Coin dead, stalled at 10,000 blocks for 3 days. Removing soon.
I don't mind that allcrypt removes it, but I want to get my coins out before.Thanks a lot!
EDIT: Crossposted to allcryptthread
It is improbable that this is the reason, but I searched for all occurences of "10000" in the source code:
https://github.com/LOVEcoinproject/lovecoin/search?q=10000
If you know a little bit about coin code, please have a look at those 12 hits. Thanks.
Does anyone know from which coin LOVEcoin was forked? We could compare those 12 hits with the original code.
https://github.com/LOVEcoinproject/lovecoin/search?q=10000
If you know a little bit about coin code, please have a look at those 12 hits. Thanks.
Does anyone know from which coin LOVEcoin was forked? We could compare those 12 hits with the original code.
Thanks, YarkoL, very clever:
I found this in kernel.cpp, line 21
Quote
// Hard checkpoints of stake modifiers to ensure they are deterministic
static std::map mapStakeModifierCheckpoints =
boost::assign::map_list_of
( 0, 0xfd11f4e7u )
( 10001, 0xd42268a1u )
static std::map
boost::assign::map_list_of
( 0, 0xfd11f4e7u )
( 10001, 0xd42268a1u )
Quote
AddToBlockIndex() : Rejected by stake modifier checkpoint height=10001
LoveCoinDev, I guess, your clone-your-coin manual should be extended with "remove existing checkpoints".
Please tell us which manual you used.
So love coin is back alive?
I'd like to see it get second chance.
Here's Linux wallet
https://mega.co.nz/#!AwAjXYrL!TcwwikFi90VXjfxXkJQvhmgVZk1oog29ThylVLi9790
I'll try to make wallet for windows bit later.
Fwiw, I can confirm that lovecoin is a clone of mintcoin including the centralised synchronised checkpointing but with a heavily-modded PoS.
Yeah, there's a lot of baggage. At least the regular checkpoints were removed.
... Love Coin is based on MintCoin.
Fwiw, I can confirm that lovecoin is a clone of mintcoin including the centralised synchronised checkpointing but with a heavily-modded PoS.
Codebase transparency can be improved by brutally suppressing the deltas that implement the branding/livery. This vandalism enables the changes to the engine to be more easily perceived, examined and assessed. I built myself a little workbench, allows me to fossick at leisure:
litecoin + (mintcoin + lovecoin)
https://bitbucket.org/gjhiggins/zenlovecoin/commits/branch/lovecoin
litecoin + mintcoin + lovecoin (for completeness):
https://bitbucket.org/gjhiggins/zenlovecoin/commits/branch/zenlovecoin
The git diff is mainly a useful one-page summary. For the actual fossicking, I use meld [1].
[1] http://meldmerge.org/
HTH
Cheers,
Graham
LOL.
Post from BTCtalkcoin thread. Seems our DEV has his fingers on more than one pie
EDIT:
Here's the problem. You didn't delete the old stake checkpoints from the fork:
Line 24 in kernel.cpp
static std::map mapStakeModifierCheckpoints =
boost::assign::map_list_of
( 0, 0xfd11f4e7u )
( 5000, 0x1d88a220u )
( 10000, 0x3bae1eb9u )
( 15000, 0x8c6b5d66u )
( 20000, 0x90881334u )
( 21330, 0xe07fa575u )
Actually I have to admit, I'm not sure how the "stake checkpoints" actually work, but it seems they are affecting, in some way, the checkpointing for the PoW blocks. I checked checkpoint.cpp and it doesn't have any checkpoints mapped. Anyone else comment on this? I don't have the time right now to look over the PoS code.
Great! BCCdev should use the opportunity to change the RPC and P2P port at the same time (in protocol.h and bitcoinrpc.cpp).
Post from BTCtalkcoin thread. Seems our DEV has his fingers on more than one pie
EDIT:
Here's the problem. You didn't delete the old stake checkpoints from the fork:
Line 24 in kernel.cpp
static std::map
boost::assign::map_list_of
( 0, 0xfd11f4e7u )
( 5000, 0x1d88a220u )
( 10000, 0x3bae1eb9u )
( 15000, 0x8c6b5d66u )
( 20000, 0x90881334u )
( 21330, 0xe07fa575u )
Actually I have to admit, I'm not sure how the "stake checkpoints" actually work, but it seems they are affecting, in some way, the checkpointing for the PoW blocks. I checked checkpoint.cpp and it doesn't have any checkpoints mapped. Anyone else comment on this? I don't have the time right now to look over the PoS code.
Great! BCCdev should use the opportunity to change the RPC and P2P port at the same time (in protocol.h and bitcoinrpc.cpp).
Yeah, that's my post.
I feel bad for the coin operator, because he put some effort into this, and it's not his/her fault that the code was broken.
I forked the code, and removed the checkpoints after 0:
https://github.com/YarkoL/lovecoin
Linux client here
https://github.com/YarkoL/lovecoin/blob/master/lovecoin/src/lovecoind
So love coin is back alive?
Yeah, that's my post.
I feel bad for the coin operator, because he put some effort into this, and it's not his/her fault that the code was broken.
I forked the code, and removed the checkpoints after 0:
https://github.com/YarkoL/lovecoin
Linux client here
https://github.com/YarkoL/lovecoin/blob/master/lovecoin/src/lovecoind
Hmmm. Sure some other devs would help on this. A quick google gives me
''To clarify a little, you don't actually need those as they are extra security precaution.
Still it might be a good idea to add one for the genesis block at least.
When you've got your genesis, run getblock on it. Copy the modifierchecksum field, insert into code and recompile.''
Sounds like all but 'block 0....' could be done away with, other coins only have the genesis block checkpoint but hey, I'm not a programmer and don't have a clue what I'm talking about................
EDIT. Hang on... Isn't this a quote from one of your posts^^^^^^^^^^^^YarkoL^^^^^^^^^^^^^^?
?
''To clarify a little, you don't actually need those as they are extra security precaution.
Still it might be a good idea to add one for the genesis block at least.
When you've got your genesis, run getblock on it. Copy the modifierchecksum field, insert into code and recompile.''
Sounds like all but 'block 0....' could be done away with, other coins only have the genesis block checkpoint but hey, I'm not a programmer and don't have a clue what I'm talking about................
EDIT. Hang on... Isn't this a quote from one of your posts^^^^^^^^^^^^YarkoL^^^^^^^^^^^^^^?
?
Welp, that's easily fixed then. Get rid of all the checkpoints.
Dev, do you know what to do?
Send love to
LWEBHmiAGSS4Mdv8BjMsBx84SD3KxM5UVh
Dev, do you know what to do?
Send love to
LWEBHmiAGSS4Mdv8BjMsBx84SD3KxM5UVh
I found this in kernel.cpp, line 21
Those are PoS checkpoints that shouldn't be there.
The first number is block height, the second one modifier checksum.
My guess is that whenever someone tries to generate block 10001, it doesn't get accepted since
the checksum is different from the hardcoded checkpoint ( 10001, 0xd42268a1u )
To verify if my guess is correct, someone who has been mining could look into his debug.log and
see if there's anything like
Quote
// Hard checkpoints of stake modifiers to ensure they are deterministic
static std::map mapStakeModifierCheckpoints =
boost::assign::map_list_of
( 0, 0xfd11f4e7u )
( 10001, 0xd42268a1u )
( 30001, 0x7e0d6e1eu )
( 50001, 0xa5a4473eu )
( 70001, 0xbe5e3360u )
(100001, 0x6cafeba8u )
(133333, 0x011868fcu )
;
static std::map
boost::assign::map_list_of
( 0, 0xfd11f4e7u )
( 10001, 0xd42268a1u )
( 30001, 0x7e0d6e1eu )
( 50001, 0xa5a4473eu )
( 70001, 0xbe5e3360u )
(100001, 0x6cafeba8u )
(133333, 0x011868fcu )
;
Those are PoS checkpoints that shouldn't be there.
The first number is block height, the second one modifier checksum.
My guess is that whenever someone tries to generate block 10001, it doesn't get accepted since
the checksum is different from the hardcoded checkpoint ( 10001, 0xd42268a1u )
To verify if my guess is correct, someone who has been mining could look into his debug.log and
see if there's anything like
Quote
AddToBlockIndex() : Rejected by stake modifier checkpoint height=10001
ERROR: AddToBlockIndex() : Rejected by stake modifier checkpoint height=10001, modifier=0x756f6ca000813145
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: BitcoinMiner : ProcessBlock, block not accepted
Jump to: